When I set (admin) …
Items: Children
Order by: Default
Order: Ascending
… than I have the correct output at the front-end. But the back-end (admin) is something totally different.
I think it is sorted alphabetically.
How can I manage to have both front-end and back-end to match what I define?
And why does GRAV change my custom order – explicitly set in the MD-file – if I change order or order by? That is confusing as hell
The admin really doesn’t take into account the ordering the page sets. It just gets the pages as they are found in the filesystem. This way it mimics how it would look if you looked at the folders in Explorer or Finder (or whatever file browser your OS uses).
This is because Grav is a file-based CMS, and as such, we find things make more sense if the admin mimics the files. The admin really is a GUI for those that don’t have direct access to the filesystem after all.
It could be this capability to take parent page ordering into account, but it’s something that would need to be implemented. You could create a request here: https://github.com/getgrav/grav-plugin-admin/issues
I can follow what you mean. But that makes GRAV not a Content Management System, but rather more of a Content System in that particular field.
Image a developer defines that order:
Homepage
About us
Products
History
FAQ
Get in touch
Credits
Links
… and the editor sees in GRAV
Homepage
About us
Get in touch
History
Products
FAQ
Links
Credits
If you have to follow a straight line throughout your copy that is a nightmare.
What about if a client wants to edit the content in a year and needs to reorder the blocks?