Search code examples
aemjcr

Should content node structure align with its semantic URL

I would like to know what is best practice in regards to structuring content in AEM. Or JCR for that matter.

Lets say I have 1000 articles. And these articles have categories. The user would find them via semantic URLs like this

http://domain/category/subcategory/title

I could create a tree node structure in AEM to reflect exactly that

enter image description here

I get the feeling this is not maintainable, and if there are changes (like dropping a category out), then content needs to be moved manually somewhere else.

Is there a rule of thumb as to how to plan/structure these websites?

Solution

  • Your content structure looks pretty efficient to me. Not quite sure what u meant by manually moving content somewhere else. If you want to drop a category, why would you want to move it somewhere else?

    Btw, there is no specific rule of thumb to designing content hierarchy, just few nitbits you need to be aware off. Content design depends a lot on the business scenario, data growth and how efficiently you can model the structure keeping the following points in mind:

    • Scalability and maintainability
    • Caching: dispatcher rules
    • Search Query costs: Flat structure would affect query efficiency
    • Meaningful content organization
    • ACL's: permission cascade hierarchically

    This link here will probably shed more light