-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Define order of "categories" and "basics" #12
Comments
Quite forward thinking! The ecosystem relies on everyone informally agreeing on features and pushing fourth. So the best way to propagate a feature like this through the community, would be to find one of the more active themes. And propose that it would be nice to be able to pass an array of sections to sort e.g. Anyone looking to do this, should contact their themes developer. Let's keep this thread open in the mean time so others can chime in and we can look at adding some helper to the boilerplate which encourages this practise. |
General
Where is actually the right place to discuss export related "rules"?
Because these kind of ideas/issues (like #6) are related to any export format (json->pdf, json->html, json->txt) and are not supposed to be relevant in the schema definition IMO.
Ordering
Currently there is no definition (or i can't find) on how to tell the export middleware how you'd like to sort the main categories. This is also useful (maybe mandatory?) for the basics entries. Let me show you some use cases:
And no, this should not be the function of the "theme" to force me the way it should visualize my data. A theme (and any kind of export middleware) should define how it visualizes the data, but the ordering should be also in my hand.
Also I think this is nothing schema-related, so it should be a separate definition which could also solve the #6?
Interested in your thoughts :)
The text was updated successfully, but these errors were encountered: