In my last article Usability Tip: Use Categories to Prefix Component Names (LINK), I showed how pre-pending a category name to the beginning of the component name aids in sorting and is a quick way to help find the component you want to use. After receiving a few questions regarding the post, a follow-up article is due in the form of a Q&A:
Q: “Why not use the componentGroup property?”
A: This is an excellent way to sort components when the content author manages only one site. You can use the componentGroup sort and categorize and restrict access to the components by use of permissions. However, if the content author manages more than one site within the same instance, this approach breaks down. It is possible to have two or more components with the same name but have different functionality. Joe Gunchy would totally do something like this. My approach uses the site name for the componentGroup property, then further segregates them by adding the category to the name itself.
Q: “Would you be willing to share your macro list of categories for reference?”
A: Yep. Here is the list of categories I used on my most current implementation:
- Content – Any straight, content-managed components like Promotion Pods, Rich Text Editors, or anything that a content author uses to fill in the copy, imagery, or other content on the page.
- Layout – Column controls, tabbed-panes used to divide a page into additional content areas
- Navigation – Buttons, links, calls-to-action, list of links (footer, side rail, related links), etc. that help the user navigation the site.
- Search – Components related to search functionality, faceted results, pagination, etc.
- Social – Components used to share or display social content such as “Add This”-type features, Twitter, Facebook, Pinterest, YouTube
- Video – Brightcove, YouTube, or any video player, thumbnail library, carousels, etc.
What other categories can you suggest? Please let me know in the comments and we can add them to our list!