CMS Made Simple Forums

About Terminology and namegiving in CMSMS Admin Panel.

I do find the program itself to be intuitive, but some of the names used
are the same for different things or used in a misleading or inconsistent way.

I suggest that the whole namegiving system should be rewritten in CMSMS 2.0
to make it easier to write documentation of how CMSMS works.


Suggested changes:

Templates (link) renamed to Page Templates
Current Templates renamed to Current Page Templates

Menu Manager (link) renamed to: Menu Templates
Menu Manager (page) renamed to: Current Menu Templates

Content type renamed to: Menuitem types
content renamed to: Page Content
Pages (link) renamed to: Menu Manager
Current Pages renamed to: Current Menuitems
Add new content renamed to: Add new Menuitem

Reorder Pages renamed to: Reorder Menuitems


What do you think?


GDS

I do not like this idee. I'm used to it the way it is and I like it that way. Except for the dutch translation with has the menu-item templates and stylesheets the same (sjablonen) I never changed it or had the idee that it should change.

I formaly worked with joomla and mambo. (about 2 years ago) and find that CMSMS has a much better terminology and namegiving then joomla and/or Mambo.

Please guys, keep on doing that great job for us.

Musicscore

at least for the "templates" name I disagree, we are trying to get all templates centralized under the same menu(so that modules dont have to worry about it) and renaming the menu would not be good if it has all templates.

The reason menu templates arent advertised much is that they are hard. and you generally dont have to change them (styling should be done in css)

I could go for renaming some things under templates, particularly the menu manager but don't agree at all with:

Content type          renamed to:  Menuitem types 
content        renamed to:  Page Content   
Pages (link)        renamed to:  Menu Manager   
Current Pages        renamed to:  Current Menuitems 
Add new content      renamed to:  Add new Menuitem

As this is the place where you manage 'pages'.  Pages are not related to menu items, the menu manager module handles that. 

First, to clear up one possible misunderstanding:
I do not want to change the use of Content as you find in the Admin Panel top Menu.
I am refering to the use of content in the dropdown "Add Content Type:" in the page Add New Content
(How many different items are actually named Content and Pages  in CMSMS?)


For me, it seems inconsistent to call something for Pages, when it actually consists of a list of links to menuitems
(of which most of them are referring to Page content, but others are referring to Links or Separators or Section Headers )
Anyway, none of these are Pages. HTML pages are produced when Templates are filled with Page Content and sent to the browser.

I do find it logical to name the admin-page that contains all these menuitmes for a Menu Manager.
(We already have a Image Manager and a File Manager under the Content section in the Admin menu,
so a Menu manager here will follow the same pattern)


But as I see that this name already is used by another page, that actually is not a menu-manager,
but a list of menu templates, then my suggestion is: Why not call the current Menu Manager for "Menu Templates" then?
(or Menutemplate Manager)

I do understand how you are used to the names currently in use, but I suppose this should be of less importance,
as this interface is ment to be used on a daily basis by an (hopefully) incerasing number of content editors.

To keep CMS Made Simple in accordance to it's name, I do find it useful to make it easy to understand
for editors that might not even know anything abot HTML and CSS. I think a consistent and clean namegiving could help to achieve this.



GDS

For me, it seems inconsistent to call something for Pages, when it actually consists of a list of links to menuitems
(of which most of them are referring to Page content, but others are referring to Links or Separators or Section Headers )
Anyway, none of these are Pages. HTML pages are produced when Templates are filled with Page Content and sent to the browser.

I think you're not understanding an important piece of the functionality.

'Content >> Pages' has little to do with menus or menu items.  it's a page hierarchy.  it allows you to manage your pages.  Each content item has a menu label property, but that's it.  I can configure menus however I want independent of the page hierarchy.

The MenuManager module reads the content hierarchy, and is capable of quickly and easily building a menu, but I can quickly build a menu of whatever menu items I want in whatever order, simply by hard coding the page aliases into my {menu} call.  Therefore 'MenuManager' is seperate from content.

Perhaps 'MenuManager' is the wrong word, maybe 'MenuMaker' or something like that, but it's a minor point.

The items under the 'content' menu usually relate to the content in the site.  News items can be re-used on multiple pages, and they are data (aka content).  The same with the Uploads module, the company directory module, and a few others.  Therefore 'Content' makes sense to me.