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
We want the system to be flexible enough so it can be either used to write a book, or a website.
We want to support some arbitrary navigation system. here are 4 types I was thinking about
All posts are completely independent: tag based navigation/reverse chronology blog post like navigation.
Some posts are related some are not, some categorization might be useful: The user can specify the navigation tree related to each post.
The posts are VERY related: then make this into a book.
This is completely inherent from the folder: in each folder there is a navigation.yaml which would specify which form it is. If non-exists, it defaults to reverse chronology based.
A book is a linearly ordered list of chapters. Occasionally, maybe allowing parts.
Here, we want each "post" to be the same as a chapter.
One issue might be a single chapter is too long for a post, it could also be just a section.
This should be something user can decide.
The text was updated successfully, but these errors were encountered:
We want the system to be flexible enough so it can be either used to write a book, or a website.
We want to support some arbitrary navigation system. here are 4 types I was thinking about
This is completely inherent from the folder: in each folder there is a
navigation.yaml
which would specify which form it is. If non-exists, it defaults to reverse chronology based.A book is a linearly ordered list of chapters. Occasionally, maybe allowing parts.
Here, we want each "post" to be the same as a chapter.
One issue might be a single chapter is too long for a post, it could also be just a section.
This should be something user can decide.
The text was updated successfully, but these errors were encountered: