You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Templates should have access to more information about the current page than just its content. They should be able to see any custom data defined in that page (see #7), as well as probably the path to the page and any children (see #4).
It would probably make sense to stick all this data under a page variable structured like so:
[page]
path = "path/to/page.html"data = {} # hashmap of metadata defined in the pagechildren = [] # array of child pagescontent = ""# page content
This will probably rewrite significant refactoring, the implementation of some kind of page struct, and a way to do frontmatters. Child pages might also necessitate path normalization.
The text was updated successfully, but these errors were encountered:
Templates should have access to more information about the current page than just its content. They should be able to see any custom data defined in that page (see #7), as well as probably the path to the page and any children (see #4).
It would probably make sense to stick all this data under a
page
variable structured like so:This will probably rewrite significant refactoring, the implementation of some kind of page struct, and a way to do frontmatters. Child pages might also necessitate path normalization.
The text was updated successfully, but these errors were encountered: