+- `title` sets the page title
+- `slug` overrides the target URL: `pages/hello` with `slug: banana` would
+ become `out/banana.html`
+- `template` overrides the template with which to render this Markdown file
+
+Blog-specific:
+
+- `author`
+- `date`
+
+
+### Internal linking
+
+Everything that ends up in the final output has a name that identifies it to
+the rest of the website. If a file is derived directly from an input file,
+generally its name is derived from the name of the *input*.
+
+- Markdown files like `content/pages/hello.md` are named their own name
+ relative to the content directory, minus their extension: `pages/hello`.
+- static resources like `static/img/cat.jpg` are named their own name
+ relative to the repository root: `static/img/cat.jpg`.
+- Templates that are rendered from nothing (e.g. to make the index page) are
+ named whatever the config file says to name them.
+- FAQ indexes are named `faq/index/X`, where X is the name of the index in
+ `config/faq.yml`.
+
+cms7 can generate a relative URL to anything with a name from any page. This
+should always be preferred over manually writing links. To generate a relative
+link from a Markdown template, just link to a name:
+
+```markdown
+[A page about frogs](pages/frog)
+```
+
+To do the same from a template, call `url_for`:
+
+```html+jinja
+<a href="{{ url_for('pages/frog') }}">A page about frogs</a>
+```
+
+
+## TODO
+- [ ] Get the basic static page up, and how to connect (latest two news about
+ the reformation + about page, kinda) scheduled release: 2016-02-29
+ - [x] Design ready enough
+ - [x] Preprocessor ready
+ - [x] Templates ready enough
+ - [ ] Content ready
+- [ ] FAQ pages structure, start adding FAQ's (note: tagging could be a good thing for searching and finding)
+- [ ] Add possibility to edit on-site integrated with services (log in with your nickserv acc)
+- [ ] Gms integration
+- [ ] Further development TODO: TODO