Possible New Organization for Revolution Manager's Menus

I love to be organized, so I’m always thinking about better ways to arrange my files and things like that. To me, the menu options in Revolution’s Manager aren’t very well ordered. So here is my suggestion for the arrangement of menu options. Please do make suggestions as well!

--

This is a hierarchy with the top level being the menus you see across the top of the manager, and the second level being the options in the submenus that appear when you hover the mouse over the top level menus. I actually wanted to make suggestions for the layout of the tables within each page, but I figured that would take up too much space on here.

• Overview (previously called Home)
• Search (previously under Site)
• Components
• Security
  [list]
  [li]Users (previously called Manage Users)
• Access Controls
• Resource Groups

[/li]
[li]System

• Contexts
• Packages
• Property Sets
• Content Types
• Actions
• Form Customization (previously under Security)
• Languages
• Namespaces
• Settings

[/li]
[li]Import (previously called Tools)

• Static Resources
• HTML

[/li]
[li]Reports

• Site Schedule
• Manager Actions
• Error Log
• System Information

[/li]
[li]Support (this really should go somewhere by itself since it isn’t actually part of managing the site)

• About (previously under Reports)
• Forums
• Wiki
• JIRA
• API Documentation

[/li]
[/list]

These should go over on the right where "Logout" currently is.

• Messages (previously under User menu)
• Profile (previously under User menu)
• Logout

--

You’ll notice that there is no Site menu. The whole MODx installation is for managing the website, so I think it’s unnecessary to have a menu called Site.

I put Search as its own menu (perhaps support could be added for search content elements as well, otherwise it would just be for searching resources like it is now). I think that Clear Cache and Remove Locks, as well as Flush Permissions and Flush All Sessions (previously from Security menu) need to be put on a page somewhere, perhaps Overview (home), instead of stuck in menus. All of the other menu options go to a page rather than do something, so I don’t think they really fit on a menu. This is just my opinion, though.

I completely dropped the four "New [Resource Type]" menu options that were on the Site menu because there is no need to have them in a menu. The same functionality is provided in one click from the panels/tabs on the left of every manager page. And if we had menu options for them, why don’t we have menu options for New Template, New Chunk, and so on? Finally, Logout seemed completely out of place on the Site menu, especially since it’s already it’s own menu option on the right side of the manager.

I also don’t think that Preview belongs on a menu for a couple reasons. For one, it isn’t even really a "preview". It just goes to the site. I would expect a preview button for an unpublished resource or something like that. Perhaps there could be a "Go to Site" button on the Overview (Home) page or something.

--

I have renamed some options as well as reordered them. I’m not even completely happy with this layout, so be sure to give your input. Also, this is just a suggestion, and I’m sure it’s impossible for everyone to agree on a system of organization. However, with no offense intended, I don’t think the current organization is very intuitive.

I don’t necessarily expect any of this to be used, but I just wanted to open this for discussion while Revolution is still being created so there aren’t regrets when it’s released and people are confused by the menus. Do discuss! Thanks.

Interesting suggestions...a comp would have been nice (hint, hint). I get lost in all the text. That "form customization" is under security baffled me too....

cheers/k

What’s a comp? I’d be glad to make one, but I’m not sure what you’re referring to.

In this case, a sketch..:)

cheers/k

A while back, I suggested putting Lexicon Management, Namespace Management, and Package Management on the Tools menu. I still think that’s a good idea.

Otherwise, I’m actually pretty comfortable with how things are set up now so it’s hard for me to assess how the current setup would work for new users.

I think the Site item is familiar to Evo users and should stay where it is.

I rarely use Search, so I’d prefer to have it remain under Site.

I think you’ve left out Property Sets.

The point of the Tools menu, was to keep the System menu from getting too long.

I also had trouble finding "Form Customization," but once I did, it made sense to me to have it there since it’s mainly a security issue.

My main concern is that we finalize the default Menu structure as soon as possible so we can write accurate documentation on how to do things in Revo.

Quote from: BobRay at Sep 07, 2009, 04:45 PM

I also had trouble finding "Form Customization," but once I did, it made sense to me to have it there since it’s mainly a security issue.

Really, Bob? I think it is mainly a usability issue...not to overwhelm content editors and also of course not to let them mess up the site...But hey, this is arguable

My main concern is that we finalize the default Menu structure as soon as possible so we can write accurate documentation on how to do things in Revo.

Good point

cheers/k

I think you’ve left out Property Sets.

Whoops. That I did. I’ll add it.

I’ll second kongondo. I see customizing the forms more as a convenience than as an issue of security.

The problem I have with the Tools menu is that they aren’t really tools. I suppose the importing ones sort of are, but how is Property Sets a tool? It’s just a page to configure settings. To me, a tool need to *do* something. Even Lexicon Management and Namespace Management don’t really do anything but give you tables. I could see Package Management as a tool, but that still just makes three (two import ones plus that), and I don’t think it’s worth having a whole menu for three items that fit fine in another. Just my opinion.

Bob, I think it makes sense to leave Site since it was in Evo, and I guess it makes sense anyway, but I think there’s too much on it the way it is that isn’t necessary. I also agree now about leaving Search there. I’ve never used it, so it’d just be taking up space if made as its own menu.

I am 100% against removing the Clear Cache menu. I use it extensively.

Also, you’ve omitted Property Sets, and I’m not convinced about removng the permissions/session flushes, either.

I also agree with Bob that Form Customization at its core is a Security issue; you want to "secure" those fields from client usage. But it could also belong in Tools as well.

splittingred, I’m regretting removing Clear Cache and the permission flushes. It’d be inconvenient to have them on a page somewhere. However, I’m still sticking with my idea that they don’t really belong on the menus they are currently on.

I always find myself over-organizing and then getting frustrated because I can’t decide on a certain way to organize, so I think I’d even agree with just a few adjustments to the menus instead of revamping them. I’d probably never settle upon a certain way to organize them even if it was my own project and I was making the decision.

Anyway, I still don’t think Form Customization is a security issue, even when hiding fields from clients. Don’t you think that MODx security means keeping people out who shouldn’t be there, rather than protecting people who are supposed to be there from themselves? I realize that it’s meant to help prevent clients from messing things up by hiding things they don’t need to see, but I don’t think that really qualifies as security. Anyway, I don’t mean to be pushy or anything. I’ll be happy with it on either menu. I’m just supporting my suggestion.

Quote from: Compeek at Sep 07, 2009, 05:29 PM

splittingred, I’m regretting removing Clear Cache and the permission flushes. It’d be inconvenient to have them on a page somewhere. However, I’m still sticking with my idea that they don’t really belong on the menus they are currently on.

That’s fine; clear cache was on Site because it was that way in 096. It could be changed, if necessary, but IMO still needs to be accessible from any page.

Anyway, I still don’t think Form Customization is a security issue, even when hiding fields from clients. Don’t you think that MODx security means keeping people out who shouldn’t be there, rather than protecting people who are supposed to be there from themselves? I realize that it’s meant to help prevent clients from messing things up by hiding things they don’t need to see, but I don’t think that really qualifies as security.

That’s fair. I am open to other places; I don’t think System is the right menu for it, though.

Anyway, I don’t mean to be pushy or anything. I’ll be happy with it on either menu. I’m just supporting my suggestion.

You’re not being that at all; I appreciate your opinions and hope you’ll continue to share them. My apologies if I came off otherwise.