| Commit message (Collapse) | Author | Age | Lines |
| |
|
|
|
|
| |
Signed-off-by: Hassan Abouelela <[email protected]>
|
|
|
|
| |
Signed-off-by: Hassan Abouelela <[email protected]>
|
|
|
|
|
|
|
| |
Adds support for tag groups in content. This involves some modification
to the routing, and templating.
Signed-off-by: Hassan Abouelela <[email protected]>
|
|
|
|
|
|
| |
Add a template for the tag page itself, and add a route to use it.
Signed-off-by: Hassan Abouelela <[email protected]>
|
|
|
|
|
|
|
|
|
| |
This could probably be improved by making it less hardcoded, but since
there's a bunch of special cases, and since it only affects deploy
previews, I'm choosing to solve this with a simple solution.
I don't think realistically that we're gonna be adding a ton of resource
types down the line anyway.
|
|
|
|
|
| |
Adds configuration which specifies how routes should be handled when
building a static preview.
|
|
|
|
|
|
|
|
|
| |
Rather than having two views for the base page and all other pages, all
pages now use the same view.
The view context handler is simplified to take advantage of pathlib
features.
The markdown folder is now /content/resources/* rather than
/content/resources/content/*, as the latter is unnecessary nesting.
|
|
|
|
|
|
| |
Articles was a good name, but we want an `articles` category in
the future. `/pages/guides/` and `/pages/articles/` are clearer in name
than `/articles/guides/` and `/articles/articles/`.
|
| |
|
| |
|
| |
|
|
As this system will be used for more than just guides,
I had to do some refactoring to match this system with plans.
Basically now there isn't guides, but articles instead.
|