custom elements as pages (aka one off page templates) #170
Labels
enhancement
Improve something existing (e.g. no docs, new APIs, etc)
question
Further information is requested
v0.10.0
Milestone
Type of Change
Summary
Currently to generate a page, Greenwood goes through the pages directory and builds out a route for every .md file.
However, if you predominantly want to write a page in just JavaScript to generate HTML content dynamically you would have to do something like this in a page template instead:
Basically every page needs a markdown file and a template. This is great for many to one (many pages, one template) but if your page is better authored as JavaScript, you still need to create two files.
Details
So it would be great to see if maybe doing something like this would essentially treat about.js as a Template by default?
This way, if you have one off or JavaScript heavy pages, you only have to make one file for it.
Additionally, it would make sense that the templates folder would essentially just be a collection of layouts, which is most useful when stamping out many pages of the same structure (like a blog post)
The text was updated successfully, but these errors were encountered: