Define Article structure

[flipactual]

Both how structures are described in MANIFEST.ymls and formatting within the markdown files.

[wayspurrchen]

For issue 1, I've decided to keep it simple and go way lo-fi.

Pages

For the first issue, let's use a simple "page" abstraction. A page is a markdown file that is optionally preceded by YAML front-matter (I'm assuming remarked / whatever we're using can parse this - if not, I have tooling that can parse and strip front-matter hanging around, so let me know). There will not be any page length measuring so we will have to manually make sure that each file's content does not exceed the length of a regular page. Otherwise, the markdown file can include arbitrary HTML for formatting on a per-page basis. This will be fairly manual, but we'll keep issue 1 simple and short. Eventually, we should probably settle on a list of design elements, and the classes used to style those.

MANIFEST.yml

The MANIFEST.yml will probably not change at all.

Expected "Dressings"

Most of the work will come in the different renderers' derived metadata from the page or MANIFEST.yml. At the moment, the only thing I see this being is attaching page number metadata to each page's representation in whatever rac-pub mode, and then setting up a base template that the page is then rendered into.