A section is defined by each unique URL in a web site. A section can be either static or dynamic. The sections in the scheme above which are presented in bold are dynamic– they are the result of records placed in the related objects. The other sections are static. If we had to expand the structure of the sections, which are presented in the sitemap, it would look like this:
- Home
- About Us
- News
- Products
- ProductGroup.View (View a group of products)
- Product.View (View a product)
- Team
Dynamic sections are not real URLs, but are rather a way of showing where we want to place all the records of a given object. Which is why, each URL is defined as an ID of a section and an ID of a record (if the section is dynamic). While enumerating the structure, whenever a dynamic section is reached, the definition of the selected object is picked, the necessary business object is created and thus records are shown. The issue with the ProductGroup.View and Product.View sections is a bit more complicated. Here we declare that we would like all the products organized in relevant groups. As this information is added by the user of the website, it is dynamic and we should count on the existing relations between objects to create the proper information structure. Whenever the Product.View section is reached, as long as its parent section is also dynamic, a check is run to identify the announced relation between the objects, e.g. the object Products must be related to the object Groups of Products through a predefined property. Having this information at our disposal we can now obtain the filter necessary to create the list of products in this group. The definition of a section covers:
- Code
- Name
- Main template
- One or more templates
- One or more blocks
- One or more related links
- Meta-tags definition
- One or more texts
