User Experience Stack Exchange is a question and answer site for user experience researchers and experts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Let's say we're building a CMS administration site.

This site (roughly basing myself on Orchard CMS here) is split up in parts like "Content", "Navigation", "Blogs".

"Blogs", is then split up again into: "Authors", "Blog entries", ...

These are concepts that are not useful to the end user, but mean a lot to the manufacturer of the application. In day-to-day communication between developers, testers, PM's, in the source code, and so on, these levels need to be named.

Is there any convention concerning these names? Eg. 1st level is Section, 2nd level is Module, ... Is there a reason something should be called a Module vs a Section vs anything else, does one have a heavier connotation than the other?

share|improve this question

closed as not constructive by ChrisF, Ben Brocka Apr 24 '12 at 14:21

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

If you want to move this to Programmers could you make it more clear that you're talking about developer communication (and how)? Then I can request a move – Ben Brocka Apr 24 '12 at 13:42
@BenBrocka I have tried to make it more clear now. – Bertvan Apr 24 '12 at 13:49
The consensus was "Not Constructive" since it basically doesn't matter as long as you're clear and consistent in the terms you use (whether it's to users/your team). Myrddin's answer is a pretty good explanation. – Ben Brocka Apr 24 '12 at 14:01
up vote 2 down vote accepted

There is rarely a reason to name these unless the user can manage them. For example, if the end-user can create new sections and modules then it is appropriate to name those levels. But if they are just managing existing sections and modules it is unlikely that the UI needs to give a name to the hierarchal level at all.

To put it another way, containers that the user doesn't manage need not be named. You personally might have classes in your code named 'Section' and 'Module', but there is no reason to display those names on the screen unless there are buttons named 'Add new Section' or 'Remove Module', etc.

As far as what to name these if this is the case, I have not seen any particular literature on the subject, nor does it seem that there is a significant semantic weight to the words to imply one is higher than the other. I have seen them used in both orders (modules in sections and sections in modules).

They are both very generic though; you may be able to provide better context to the user by using names more specific to your domain. If you have Blogs and Articles, perhaps 'Content Type'? If you expose Authors, Categories, and Tags, then perhaps call them 'Views' since they are multiple ways of looking at the same items. Section and Module are very generic, and if you have any way of providing semantic hints about how the hierarchy is organized it would be better to provide names that inform users.

share|improve this answer
I'm indeed not talking about making these available to the user. I'm asking if there's any convention for naming these for communication purposes, eg. between PM and devs, and as a result of that in code as well. Is there a reason something should be called a Module vs a Section vs anything else, does one have a heavier connotation than the other? – Bertvan Apr 24 '12 at 13:30
But since, this has indeed little to do with UX, I might be in the wrong place here. – Bertvan Apr 24 '12 at 13:37
Clear naming conventions are a UX issue. – Myrddin Emrys Apr 24 '12 at 13:43

Not the answer you're looking for? Browse other questions tagged or ask your own question.