Sitecore Best Practice Series:


Sitecore Architecture Best Practices


# Description Rationale
1 Group semantically related fields into sections Increases usability of Content Editor.
2 Utilize branch templates for predefined structure creation Branch templates allow creating a predefined tree of items with a single insert action.
3 Choose item names that are easily understood by users. Increases usability of Content Editor.
4 Avoid excessively using Rich Text Editor fields Rich text editor fields impose a negative performance impact in the Page Editor, as well as may unintentionally provide content editors with ability to modify web page design.
5 Use Rich Text Editor Predefined profiles to restrict available buttons Full functionality access may provide too much control over the page to content editors.
6 Limit the maximum number of template fields Excessive fields may cause negative performance impact.
7 Utilize icons for item data definition templates Icons help to visually separate semantically related content items.
8 Place most frequently modified fields closer to the top Increases Content Editor usability.
9 Create item data definition template standard values Standard values define default field values.
10 Utilize tokens in Standard Values Tokens allow automatic generation of field values.
11 Provide field Help information Increases Content Editor usability.
12 Use Display Name instead of Item Name in Content Editor Item Name may get unnecessarily long for SEO purposes, as it is used in the URL; use Display Name to show a shortened name in the Content Editor tree.
13 Do not concatenate field and section names Increases Content Editor usability.
14 Utilize inheritance for reusable fields Sitecore inheritance eliminates unnecessary redundancy in item data definition templates.
15 Avoid modifying system templates Sitecore system templates are used by the application itself, changing them may negatively affect its operation.
16 Manage presentation layer settings, default field values, insert options and assigned workflows in the item data definition template standard values Managing such settings in the standard values of the item data definition template modifies all items inheriting such template; this practice also allows to easily reset content item settings to the original standard values.
17 Use TreeListEx vs TreeList field-type TreeList will load all items in that field on the item selection, while TreeListEx will only do that if the selection is being edited, increasing the Content Editor performance.
18 Set default image paths Restricts image storage for a particular field to a certain location in the Media Library.
19 Use Droplink instead of Droplist Droplist stores the text of the option, which could make referential integrity problematic.
19 Avoid overuse of RTE fields Giving editors too much freedom in page presentation via excessive use of RTE may backfire; additionally RTE are heavy on Page Editor performance.


  • VC
    May 31, 2016 at 8:10 am

    These are the tips which you can follow while designing Content tree, But Can you explain about architecture of Content on a broader level, Like separating Data from Presentation components, How to Build Content tree ?

%d bloggers like this: