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
Currently, all pages are just plain markdown, but they can be (eg) published, have meta-info, etc.
They can also be shown as a list, and there's open proposals to add other rendering styles (eg workflowy-style) and non-text file types (file uploads).
With that in mind, would it make sense to have a set of page types:
Text (default)
List (shows list view by default)
Nestable (shows nestable list view once implemented)
File (renders an uploaded file)
The text was updated successfully, but these errors were encountered:
This is a good idea. I think it could be useful to do something like this in the next iteration? I don't know if the logic in the current version is general enough to be compatible.
Having thought about this a bit more, I think each page could have a 'default action' (stored with the page) rather than a page type. That would also make it easier to support #122
Currently, all pages are just plain markdown, but they can be (eg) published, have meta-info, etc.
They can also be shown as a list, and there's open proposals to add other rendering styles (eg workflowy-style) and non-text file types (file uploads).
With that in mind, would it make sense to have a set of page types:
The text was updated successfully, but these errors were encountered: