WIP: Add support for rendering extra files for individual pages #30
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
roblillack
force-pushed
the
add-rss-support
branch
from
6f6185f to
4a9f517
Compare
roblillack
force-pushed
the
add-rss-support
branch
from
10e0ad0 to
45e99c3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Depends on #29.
This can be used to render a second file with an arbitrary name—an RSS feed to be created with the index, for example.
Open issues
While the current changes are enough to add reasonable RSS support to tack sites, we are forced to introduce some variables to the rendering context just to be able to render a specific date format. We might want to bite the bullet and implement support for a different templating language for these these cases or implement a specific RSS feature.