Open federicocalvo opened 9 months ago
jonathan-richer
commented
9 months ago Perhaps there could be an checkbox in the Wiki Settings Doctype. When checked, the categories would be collapsed by default. This way, organizations with hundreds of wiki pages can navigate easily through the categories and those with fewer can have the categories expanded by default. Am I fairy tale'ing?
BreadGenie
commented
9 months ago We decided to remove the tree view to make storing and finding Wiki Pages easier and without much mental overhead. I do agree that sometimes it makes sense to have a tree view, but unfortunately for some users they will have to miss out.
You can refer https://wiki.frappe.cloud/wiki/wiki-migration-guide for migration to newer Wiki
Perhaps there could be an checkbox in the Wiki Settings Doctype. When checked, the categories would be collapsed by default. This way, organizations with hundreds of wiki pages can navigate easily through the categories and those with fewer can have the categories expanded by default. Am I fairy tale'ing?
No, You're not 😄 . The option to hide/collapse the items already exist in Wiki Settings doctype. The option is Hide Sidebar Items (on 2nd thought Collapse Sidebar Groups makes more sense).
edit: Changed it to Collapse Sidebar Groups in https://github.com/frappe/wiki/commit/7e68702d64eb0a1bf13d7209022c77883444a71b
jonathan-richer
commented
9 months ago No, You're not 😄 . The option to hide/collapse the items already exist in
Wiki Settingsdoctype. The option isHide Sidebar Items(on 2nd thought Collapse Sidebar Groups makes more sense).
Welll... 😳 This is embarrassing ... Thank you for the clarification 😊. I strongly agree that "Collapse Sidebar Groups" is a better name.
Description:
I think this is not an issue, and I don't know if it is a feature request, because for some reason it was decided to remove a tree structure from the wiki.
The ERPNext documentation as an example, is more complexly organized, the dropdowns are very large, not having subcategories to organize them.
My question is if the idea is to retake the subcategory structure, or with what logic it was decided to take it out.
We are looking to update the Wiki to this new version, but honestly we don't know how to organize the information because of this.
Maybe some recommendation on how they decided to move the ERPNext documentation to this new approach could be useful for those of us who have to leave the tree view?