[ISSUE][DOCS] Standardize an Editor Extension Taxonomy on the Human Titles

[amzn-leenguy]

Describe the issue

Standardise an Editor Extension taxonomy with Human Titles, which is read by the users. There are also Meta Titles, which are for the crawlers to improve a webpage's SEO.

• Keep the Human Title short and to the point
• Ensure that all instances of Editor Extension have the same nomenclature
• Create Meta Titles, which is better optimised for search engines, and include keywords that would be used by users to search for Editor Extension (e.g. customisation, tools, control gallery, etc.)

Impacted page(s)

TBD

Expected experience

TBD

[amzn-leenguy]

@bhanuja-s can you expand on this one please

[bhanuja-s]

Standardise an Editor Extension taxonomy with Human Titles, which is read by the users. There are also Meta Titles, which are for the crawlers to improve a webpage's SEO.

• Keep the Human Title short and to the point
• Ensure that all instances of Editor Extension have the same nomenclature
• Create Meta Titles, which is better optimised for search engines, and include keywords that would be used by users to search for Editor Extension (e.g. customisation, tools, control gallery, etc.)

[amzn-leenguy]

Do you have any examples of pages that this impacts as well currently @bhanuja-s . Thank you

[amzn-leenguy]

@bhanuja-s I would love for you to open a discussion on this topic. You don't need to own this task, but I would love to talk to you about how we can use this opportunity to perhaps start the conversation of getting a gathering of people together in a meeting / event to create a page that houses the importance of this topic.

For example: Things like diversity and inclusion words (master/slave etc), or common "technical level" terminology that particular users can use that may not be friendly to other levels of users. This can be all collected and advised on a page to help remind users of these common mistakes and guidance on how we can avoid this.

I think moving forward, we should set up an audio meeting and a topic and eventually deliver a page to help guide users on this.

[amzn-leenguy]

Here is a small start on this topic area done here by Docs: https://o3de.org/docs/contributing/to-docs/terminology/#terms-to-avoid-and-their-alternatives

I think we can further expand on this with more detailed information, and reference this page for others if we feel like a page could benefit from some guidance of less heavy technical jargon and more friendly writing style.

[chanmosq]

@bhanuja-s Is there any status update on this issue? Is this still an open conversation that's going on?