About Page Builder Prerequisites | Before Page Builder is operational, verify that your team has accomplished its prerequisites.
Page Builder offers a convenient way for its users to design pages without extensive web-development techniques. In Page Builder, content creators work within pages to insert preconfigured content units, the basic building blocks of Page Builder, into layout templates. Prior to the Page Builder design work, CMS administrators create content units from either single field schemas or a composite of field schemas (i.e., component schemas). Developers contribute to the Page Builder process by creating the presentation layer for content units.
The following sections outline the tasks that CMS administrators and developers need to accomplish before users can complete their work in Page Builder.
Embedded component schemas are required to create component content units. See Creating Component Schemas for details. See Component Content Units for details about the relationship between component schemas and content units.
Field and component content units serve as building blocks that you add to Page Builder layouts. By default, Page Builder provides basic form content units. See Forms in Page Builder for details.
To build other content units, users must have administrative rights to Administration > Presentation Content Units. If a non-administrative user will create content units, refer to Setting Content Unit Permissions below.
Before content units can be applied in Page Builder presentations, ASP.NET developers must create views (for some organizations, developers may need to extend legacy XSLT stylesheets for page type and content unit presentations.). In most cases, the content unit views are similar to their schema type counterparts. Developers can use the views of the embedded schemas as a foundation when building content unit views.
Even though schema type views and their content unit counterparts have inherent similarities, it's a best practice not to use schema type views for the dual purpose of styling content units. A change to the schema type view may affect the styling of the content view, inadvertently. For this reason, even when the code for a content unit view is exactly the same as its schema type counterpart, the field name of the content unit should be different than the tag name of the embedded schema. If you follow this practice, the code for these respective views reside in separate files.
Complete the following tasks:
Note: If you are new to ASP.NET MVC development, see Building an MVC Website as a starting point.
In order for Page Builder pages to be styled with CSS at runtime, you must apply a formatter. By default, Ingeniux CMS provides the Bootstrap v3.0 framework. If you require Bootstrap 2.33 or either of the two custom formatters, see Presentations Formatter. You can access the Page Builder Presentation Formatter sets in Administration > Publishing System > Publishing Targets view > [ Choose Appropriate Publishing Target] > Info tab > Page Builder Settings.
Usually CMS administrators create content units; however, any CMS user group can be given permission to do so. To set these group permissions, administrators navigate to the appropriate group(s) in Administration > Users/Groups > Groups > Info tab.
For details about how administrators set permissions on groups, see Creating Groups.
Note: Keep in mind that specific groups can be blocked from accessing individual content units. See Blocking Group Content Unit Access for details.
Users must have these permissions to access Administration > Presentation Content Units. Select the following permissions:
Tip: Navigate to the Permissions on page presentations designing block.
Tip: Navigate to the Miscellaneous block.
Users may benefit from having other permissions in addition to required PCU permissions. For example, to enable users to complete related tasks, you can assign permissions that expand the user's toolset and flexibility (e.g., access built-in views in the Assets Tree). If you wish to assign responsibilities to respective users, you can designate specific permissions to a user group for managing presentation content units, another group for managing content unit built-in views, etc. Administrators can establish a workflow to process work between these groups.
See List of Group Permissions for details about all permissions. Choose permissions that best meet your team's needs.
Recommended permissions include:
Permissions on asset manipulations: Assigns or removes the following block of permissions related to asset manipulations.
Permissions on Assets Tree manipulations: Assigns or removes the following block of permissions related to modifying objects in the Assets Tree.
As an administrator, ensure that Page Builder designers and content contributors have adequate access to their respective work areas. To set group permissions, navigate to the appropriate group(s) in Administration > Users/Groups > Groups > Info tab.
For details about how administrators set permissions on groups, see Creating Groups.
Users must have these permissions to access ICE and Page Builder in the Design tab. Select the following permissions:
Permissions on page manipulations: Assigns or removes the following block of permissions related to modifying pages.
Permissions on page presentations designing: Assigns or removes the following block of permissions related to designing page presentations.
Users may benefit from having other permissions in addition to required permissions for Page Builder. For example, to enable users to complete related tasks, you can assign permissions that expand the user's toolset and flexibility (e.g., enable access to Site Tree, page history, publishing options). If you wish to assign responsibilities to respective users, you can designate specific permissions to a user group for designing Page Builder presentations, another group for editing content inside designed presentations, etc. Administrators can establish a workflow to process work between these groups.
See List of Group Permissions for details about all permissions. Choose permissions that best suit you and your users' needs.
Recommended permissions include:
Permissions on page content viewing and manipulations: Assigns or removes the following block of permissions related to viewing and modifying page content.
Permissions on site tree manipulations: Assigns or removes the following block of permissions related to modifying objects in the Site Tree.
Permissions on publishing: Assigns or removes the following block of permissions related to publishing site content.