Prev Next

Print

Administrators should take into account that performance degrades as the number of items under any item increases. Usability is also affected - trying to locate an item in a long list of items can be challenging and time-consuming (think about locating a file within a directory containing hundreds of files). This is true anywhere data is stored hierarchically - in Content Editor, in User Manager or anywhere else. As a general precaution, no item should be the parent of more than 100 other items. Plan for growth over time as well - consider how frequently and how many children will likely appear under an item over the lifetime of the solution.  

Architects should design their content trees to be deep rather than shallow to achieve optimal performance. For instance, consider a solution designed to sell a large number of various camera models, each within a primary category such as "Point&Shoot" or "Professional". Rather than simply creating categories with models directly beneath each, consider additional subcategories such as brands. The hierarchy should also be designed for maximum usability by the content editors and to support rendering logic required for the site.  

If a company has a thousand users who access the site or more, architects should group users such as by location, by office, by department, by team, by first letter(s) of login name or other criteria to support a limitted number of users under each folder in user manager.

Prev

Next