Page Types
Introduction
Creating a page in C1 CMS implies not only adding content to it but also attaching metadata, selecting a proper page layout, reuse of content and other necessary activities to make a page dynamic and good-looking.
By using page types, a website developer can control and automate all those activities and thereby empower users (content editors, writers) to create a page with a lot of predefined content and settings practically in one click.
Page types take care of necessary additions, required limitations and reasonable defaults on web pages and can be viewed as one of the efficient tools for rapid website development.
This guide is aimed at website developers who are going to learn how to create page types.
We assume that you know how to work with the Layout and Content perspectives of C1 CMS and have an idea of page hierarchy of the website in C1 CMS.
As a website developer, you will primarily work with the Page Types functionality in the Layout perspective and need access to it. To test page types you are going to create, you will also need access to the Content perspective.
To add the metadata fields and default content to page types, you should to know how to work with metadata types and layout templates, be able to edit content in the Visual Content and Source Code editors.
If you are going to create your own page data folders and metadata types to use in page types, you should have access to the Data perspective, too.
To take steps in the example as well as test your knowledge after finishing this guide, you should have access to the System perspective with permissions sufficient to install add-ons.
To get started with page types, you are supposed to take a number of steps.
Getting Started | ||
Step | Activity | Chapter or section |
1 | Create a page type | |
2 | Quickly edit a page type | |
3 | Use a page type | |
4 | Add page data folders | |
5 | Add applications | |
6 | Add metadata fields | |
7 | Add default content | |
8 | Allow or disallow presetting the menu title | |
9 | Set the default child page type | |
10 | Select the default layout | |
11 | Limit templates available for pages | |
12 | Limit page types available for pages | |
13 | Limit page types by homepages or subpages | |
14 | Limit page types by their parent page types | |
15 | Troubleshoot possible issues | |
In the following few chapters, you will learn more about these and other activities.
The following is the list of terms and their definitions used throughout this guide.
Terms and Definitions | |
Term | Definition |
Page data folders | One of datatypes used in C1 CMS to store structured data and specific to a single page. Presented in the Administrative Console UI as a folder with data items under a page. |
Applications | Custom XML-based tree structures in the Administrative Console UI that conveniently combine all relevant and related elements and commands |
Metadata types | One of datatypes used in C1 CMS to store page metadata and specific to a single page. Presented in the Administrative Console UI as one or more fields on the Metadata tab of a page open in the editor. |
Metadata fields | Instances of a metadata type attached to a page via a page type. |
Layout templates | A master page used when creating web pages, predefining formatting, layout and - not infrequently - default content. Also known as page templates and website templates. |
Content placeholders | Segments in a layout template to add content to when editing a page in the content editor. |
Placeholder ID | A unique identifier of a specific content placeholder in a layout template. Used in page types for default content insertions. |
Homepages | The root pages of websites that normally represent website (1 homepage = 1 website). Each website in C1 CMS can have only one homepage. |
Subpages | Any pages added under the homepage of a website. |