Comic Posts

Comic posts are placed in the content/comic/ directory. In general all content is placed in the content/ directory. The root subdirectory will also determine the category, but this can be overwritten with a category metadata field. Further directories can be used for personal organization, but will have no other impact.

The comic image will be defined with the comic metadata field and automatically added to the page. The contents of that field can be any of the following.

yml comic: 1.png

Here the image 1.png will be used for the comic image, and the title will be the alt text, you can also set a list of files and each will be included below the other.

yml comic: - 1a.png - 1b.png

You should manually set the alt text by explicitely using the src and alt subfields for comic like this:

yml comic: src: 1.png alt: alt text

You can also have a list of images here:

yml comic: - src: 1a.png alt: the first row - src: 1b.png alt: the second row

Instead of a comic you can also include a feature this is just a html page or snippet that gets included instead of a comic.

The body of the comic md file will be used as the accompanying post for the comic.

HyperComics

HyperComics are a seperate type of comic with their own layout, a hypercomic is made by adding a folder under the /content/hyper section with the following content:

• index.md: the main page with the frontmatter and news post
• paths.md: the multiple choice paths taken

Blog posts

Blog post content is put in the content/blog/ directory and will be put in the 'blog' section of the rendered pages.

You link the comic image using the comic attribute in the frontmatter. The comic attribute can contain an image, but it can also contain a link to any different kind of content. Right now we support images of any known format as comics, as well as .html files which will be included verbatim in the same section as the comic image will go. I am currently using this myself for choose-your-own-adventure style comics.

Any explicitely linked file will be included in the render. Any non-explicitely included files you want included, say a custom javascript, can be mentioned in the frontmatter with the includes attribute.

Optionally you can also use the blog attribute, similar to the comic attribute to include blog post content from an external file. We support .html files if you want more control over the content, and .md if you want to keep the blog content in a seperate file for some reason.

The template attribute points to the html template you want to use for this post. The template is delibrately kept seperate from any category, chapter or tag, so you can change the appearance seperate from any classification.

Chapters

Comics can be divided into chapters, extra data and overwritten assets can be placed in the chapters/ folder.

NOTE: Actually just use a different template for chapters instead?

Other Content

Files placed directly in the content root directory will be turned into standalone pages, this can be used for pages such as about or archive.