As we all know, Sitecore is a leading Web Content Management System, which is built on ASP.NET. Apart from content management, Sitecore supports Website Owners / marketers with facilities like, Personalization, Emailing Campaigns, Analytics, Path Analyzer and many more.
Apart from basics, here I would like to write what I know about Sitecore Items.
While learning Sitecore, the popular sentence we all hear is “Everything in Sitecore is an Item”.
Item is a basic building block of Sitecore site, and can be used to save some sort of information. Every item in Sitecore will have an ID and Name. An Item can be uniquely identified by using ID field.
We could manage items from either Content Editor or Experience Editor. Sitecore items can be versioned and all items by default would be inherited from base template “Standard Template”. An item can be under a single parent items and can have any no of Sub items, Siblings (items under same parent).
All the website content in Sitecore can be viewed under Content Editor as shown in below screenshot.
Root element of the Sitecore content tree is “Sitecore” and below are the main folders(Items) to hold different types of items.
- Content: This folder contains the main website data like Pages, Configurations and other data items. Page items can be created as per our Sitemap.
- Layouts: This folder usually contains all our Layouts(HTML), Sub layouts, renderings and etc. These are most the reference to the physical View file under web root.
- Media Library: This folder contains all the media items like images, videos and etc. These items can be stored in Physical storage or stored in DB as BLOB.
- System: System folder generally holds Standard settings of a Sitecore site like Workflows, Languages, Modules and etc.
- Templates: All our Template items can be created under this Templates folder. A template is nothing but data schema and can be assume this as Class in our Object Oriented Programming. A template can have any no of fields and we could group these fields under Sections. A template can also have Standard Values like layout to render, default values and etc.
Some of these folder would be invisible / locked to users based on permissions. For example, we could restrict Layout, Template and System folder access to Content Editors.