Skip to content
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

Organize admin menu #481

Open
wioux opened this issue May 4, 2018 · 0 comments
Open

Organize admin menu #481

wioux opened this issue May 4, 2018 · 0 comments

Comments

@wioux
Copy link
Member

wioux commented May 4, 2018

A number of admin pages try to insert themselves in the menu at a particular spot but fail to do so. For example, Dashboard registers itself as the 1st menu item, Pages as the 2nd, and Content as the 3rd:

menu priority: 1, label: proc{ I18n.t("active_admin.dashboard") }

menu.add label: "Pages", priority: 2 do |pages|

menu.add label: "Content", priority: 3

But instead, Pages is the last menu item

admin

It seems confusing and bug prone to hard code priories across separate files like this. It would be great if we could define the menu link sequence all in one place.


The pages menu in particular has some other quirks.

  • Homepage appears in the menu but not in the pages index table.

  • Articles Overview is linked under Pages, but if you navigate to it indirectly through the index table, you get a different form that doesn't allow full editing of the page.

  • I think ideally the overview links should be grouped together, but right now they're split by a link to Credits.

A fix for these issues could be not exposing the pages index and only allowing navigation to them through the menu. That menu should start with Homepage, then the Overview pages, and then an alphabetical list of the other pages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant