[MGNLSTK-863] Improve component names Created: 15/Mar/12  Updated: 02/Aug/16  Resolved: 02/Aug/16

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: demoproject, paragraphs
Affects Version/s: 2.0.1
Fix Version/s: 2.0.x

Type: Improvement Priority: Neutral
Reporter: Andreas Weder Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: usertestresult, ux
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

While areas seem to be named quite well, many components still feature too technical sounding names. Please revisit all components and try to use declarative, non-technical terms to what a component contains or points to. It might be a good idea to ask Antti (or any other technical writer) for assistance.

During the user tests, this has caused several frowns. Having better names would have improved orientation significantly during some user tests, especially in complex scenarios involving nested components. Since the editor might not perform well in such cases, having better component names would have helped somewhat.

Names could be chosen to match expectations, e.g. if I've just added a Carousel, I'd like to see that name appear on the bars. So, in the example I've attached, instead of using "Stage"/"Teaser Group - Stage Paging"/"Teaser items"/"Teaser Group - Carousel item" we could e.g. use "Stage"/"Carousel"/"Carousel items"/"Single item", or if this has to remain somewhat more generic "Stage"/"Stage item"/"Carousel"/"Carousel item".



 Comments   
Comment by Michael Mühlebach [ 02/Aug/16 ]

Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
Given that the this issue has seen no attention for quite a while and belongs to an old version, we're not going to address this issue any more. Instead we will focus on issues with a higher impact and more votes.
Under the assumption this issue is no longer relevant, I'm going to close it to set expectations so the issue doesn't stay open for ages with no updates. If it is still relevant please feel free to open a new issue in the appropriate project.

Generated at Mon Feb 12 07:31:08 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.