[J 4.3.x] Language String for Menu Item Type Headline Articles

[coolcat-creations]

What needs to be fixed

An interesting finding of the Joomla Kids: When you create a new Menu Item, the headline of the menu Item types for Articles and Categories is "Articles" instead of "Content". That's not logical because Categories are below Content (Backend Menu)

Why this should be fixed

Because it follows more the logic of the Joomla Structure

How would you fix it

Change the Headline Articles to Content

Side Effects expected

Unfortunately, a lot of documentation screenshots or explanations to be corrected. But honestly, I think we should change it to be more consistent.

[brianteeman]

Articles is correct.

Content is a heading just like components

Content includes media and since you changed it for j4 modules as well

[coolcat-creations]

Yes but Articles does not contain categories, that does not make sense. I would chose the heading Content because its com_content and not com_articles

[chmst]

Agree with @coolcat-creations. It is not obvious if you are new to Joomla that Categories are beblow Articles. Categories contain articles, not the other way around.

Content is not quite accurate either, as in a content managment system everything is content but it would match the menu.

[brianteeman]

Sorry but you are wrong.

OR do you want to take categories out of articles/banners/contacts etc

[brianteeman]

or I have completely misunderstood what you are saying

[chmst]

Sorry for poor english. No, it was just a remark that in a content management everything is "content".

I agree with @coolcat-creations. "Content" instead of "Articles"

[brianteeman]

sigh If everything is content in a CMS (i agree) then even more reason that this should be specific and say articles and not content

[brianteeman]

what is there in that menu type that is not exclusively for displaying or editing articles

[coolcat-creations]

The name of the Component is com_content and not com_articles. That should be reason enough to show that it's not logical to write "Articles" there. Articles can be in Categories but Categories can't be in Articles.

[brianteeman]

You really need to think about this a bit more

[brianteeman]

and the internal name of the component is irrelevant com_finder = Smart Search com_config = Configuration

[coolcat-creations]

I suppose we are lost in translation and I could not describe the issue properly.

If I want to add a new Menu item type for Kunena, the Headline of the selection is Kunena, just like the Components Name If I want to add a new Menu item type for User, the Headline of the selection is User, just like the Components Name If I want to add a new Menu item type for Tags, the Headline of the selection is Tags, just like the Components Name

If I want to add a new Menu item type for com_content, I would search for Content as headline and not for one small part of com_content

[brianteeman]

If I want to add a new Menu item type for com_content, I would search for Content as headline and not for one small part of com_content

1. How would you even know it is coded as com_content - the name of the component is Articles
2. small part??

[chmst]

I think th components name is not relevant, users in general don't know the component name.

It should be consistent with the name of the corrresponding main menu item, no matter what is in the code.

[coolcat-creations]

It should be consistent with the name of the corrresponding main menu item, no matter what is in the code.

Which would be Content as well

[brianteeman]

I think th components name is not relevant, users in general don't know the component name.

agree

It should be consistent with the name of the corrresponding main menu item, no matter what is in the code.

as I stated before that logic would mean all components would be under a new components container

[coolcat-creations]

1. How would you even know it is coded as com_content - the name of the component is Articles

Because of the headline in the admin menu

2. small part??

yes because Categories are another part

[coolcat-creations]

as I stated before that logic would mean all components would be under a new components container

The menu item of Smart Search is Smart Search (in the second level)

[brianteeman]

headline in the admin menu

that is NOTHING to do with the component name see smart search as an example

[coolcat-creations]

Smart Search as example:

[coolcat-creations]

Another Solution would be to create a new Group named "Categories" and place there all com_content Category stuff in this group.

[chmst]

I think this is what users see. The name of the component in the code doesn't matter

[coolcat-creations]

Thank you @chmst Yes thats why I said in the initial post "That's not logical because Categories are below Content (Backend Menu)"

[brianteeman]

Thanks @chmst you prove my point.

You are expanding the Components menu You are Not expanding the Content menu

[coolcat-creations]

Then lets create a second menu item type group "Categories"

[brianteeman]

and are you also going to do the same for Banners, contacts, newsfeeds

makes no sense

[brianteeman]

This is the exact type of pointless UI change that users object to - especially after 17 years

[coolcat-creations]

and are you also going to do the same for Banners, contacts, newsfeeds

makes no sense

Makes more sense to me to Name it Content. I agree :-)

[chmst]

It is an UX issue and it would be much better to ask users

[coolcat-creations]

This is the exact type of pointless UI change that users object to - especially after 17 years

Sure, after 17 years, it would be a shame if we suddenly became interested in progress and improvements. 👎

[brianteeman]

It is an UX issue and it would be much better to ask users

after 17 years with no one else saying anything dont you think they have already spoken?

time for me to bow out of Joomla

[coolcat-creations]

time for me to bow out of Joomla

I'm sorry you feel that way. My goal was not to upset you or make you leave Joomla. This comment because of a headline changes is shocking me. I think our differing opinions show how passionate we both are about finding the best solutions for Joomla and its users. Let's get together to discuss the pros and cons of the proposed changes and look for a compromise that we're all happy with. In the end, we all want what's best for Joomla and a growing user base. I think that the kids had a very valid point and maybe we can do something to make new users understand Joomla easier.

[chmst]

after 17 years with no one else saying anything dont you think they have already spoken?

Finally someone said what I have thought so often. I think we should take these issues which come directly from users seriously and be open for improvement.