https://github.com/onionhammer/nim-templates

Pages are static layouts.
Posts are based off of single.html.
Posts are exposed via a Posts object which you can iterate over in your main page template layout.

Layouts must be parsed to find if they have partials in them. If they do, insert the HTML from partial into that layout file.

Partials cannot have embedded partials. (future?)

• Layouts can have partials
• Layouts can be static, which means they can be immediately rendered without content. about.html / contact.html ... etc
• Content can specify their layout render type. Else, we should default to default content layout.
• Render method that takes a template string and arguments, and returns a rendered string.

Inspired from Hugo

• HTML templating
• Markdown Parsing
• File-watching compiler
• Development server with file-watching compilation
• Prettier error handling

• Refactor to be generate instead of seed.
• Be able to generate compiled layout under a given name. (new content type template)
• Be able to generate a static page under a given name. (new about me page)
• Be able to generate partials under a given name. (new navbar partial)
• Be able to generate content under a given name. (new blog post!)

• Parse content markdown for the frontmatter JSON.
• Make sure the above has appropriate error messages.
• Figure out a way to implement string templating.

That's what they're supposed to be used for!

That way we can buffer and mark files that contain partials as we're reading them from the file, rather than importing all files into memory.

How we can do this:

We skip reading the partials folder/files until we've properly marked the other files.
Then, we read the partials and inject them where we need to.

READ index.html
Found partial header.html at line 2

READ partials/header.html
partials/header.html is needed at index.html line 2
REPLACE index.html buffer at line 2 with contents of partials/header.html

https://github.com/sass/libsass

Should be doable.

nima serve --port=3000 should spin up a quick development web server with automatic file watching/compilation.

• Must wrap Jester or implement simple async static file webserver
• File watchers using fsmonitor (windows support pending)

Async/Parallel build process

1. Partial Build/Caching - Inject partials in partials, then cache into the PartialCache
2. Template Build/Cache - Inject partials into templates and then output into TemplateCache. One process per template type.
3. Content Render - Content fetches their template type from the TemplateCache and renders out the compiled HTML, which then gets outputted into the template type directory.

• Parallel builds! SPEED IT UP!
• Partial/Layout/Content dependency tree - So we can efficiently compile those that are dependent on each other.