Garvin: Please differentiate between the look and the content of my proof of content-page!
Yes: The look with the memu above and the hover-effect should be an alternative no standard. But this is not the topic here - I just did not want to design a second page for this issue here.
The content on the other hand should be rethought!
Please believe me, the actual arrangement is a problem for non-techie-users. I have/had to multi-user-blogs with "normal" people, I have to explain a lot for the menu-items.
and in the moment these changes must be equal to all, because - as I understand this - the menu is made in the core-php-source, or? If it would made by a template, we can make this an alternative
I pretty much favor "Entries" as the top item. I don't like this new "content" nomenclature, also because s9y users should be used to "Entries" and IMHO it fits.
I think this name is from the time where entries are one and only, or at least the main part in thist top-item. But now:
In what way is a static page, a poll, a calender item, a comment-managment an "entry"?
The sub-items depend on your amount of plugins.
of course, but I do not have very uncommon plugins and it is too long.
I do think that event plugins also affect the broader term "Appearance", because it changes how your blog looks&feels.
First of all the enhance the functionality. And in german "Aussehen" is much more irritating.
I'd be interested in this, too. My current belief is, that it's understandable. But there's a more complex trouble, we cannot really rename "event-plugins" to something like "technical plugins" or whatever else, because 1. all kind of documentation and threads on the forum would no longer fit, 2. "event plugin" at least for me is something I got so used to that I would surely continue to use it when I write/talk about it
Hm, this is a reason. I do not know if this argument should stop an necessary change, but in the moment we discuss the necessity - the consideration would be the next step, I think.
First of all, what is about "Design & Enhancements"?
I think short menu items are more preferrable, no "dual wording".
short is good, well. But it is not an end in itself, the goal should be usability. And sometimes detailed is better for this.
I like it pretty much that I can maintain plugins on a single page easily. Technically, it would also require a lot of work to split the pages in two.
hm ... this argument and the last about the docs: What is about a compromise to place an explenation beneath the headlines on the plugin-page?
It's nice for a "proof of concept" or for some alternate templates. By default I would not like to have such a menu. I want to have ALL menu items quickly assignable,
As written above: this look is only intended as an alternative! And the look should not the topic here, this should be seperated in the other thread.