Magnolia 4.5 reached end of life on June 30, 2016. This branch is no longer supported, see End-of-life policy.
Pages are created and stored in the
website workspace. The Website menu in AdminCentral displays the contents of this workspace as a site hierarchy. Here you can add pages and move them around in the hierarchy.
Pages on a site are displayed in a tree. Each site tree has a root page (typically the home page) and child pages. The work area where the tree is displayed has five columns by default:
titleelement, in the
h1heading on the page and in the navigation title. You can edit the title here in AdminCentral or in the page editing view.
The site hierarchy determines the navigation structure of the site. Each root page and its child pages constitute one site.
This default behavior can be customized in the site definition .
Although strictly speaking there is no limit on the number of pages in a website, depending on the back-end you use, there could be limitations regarding website structure and total size.
JackRabbit page/node limit - The extensive use of nodes dramatically increases the number of SQL statements necessary to retrieve referenced nodes. This has a serious impact on overall repository performance. With JackRabbit the absolute maximum number of pages permitted at any single level in the site hierarchy is 1000. However, the recommended total is no more more than 100 pages at a single level.
Content size - The total size of content in the repository should not exceed 2 TB. Note that several Magnolia clients have successfully run repositories sized 50-200 GB in production over an extended period of time.
SEO - For search engine optimization (.pdf) keep the hierarchy as flat as possible. If editors find a deeper site hierarchy easier to manage, elevate pages to higher levels using URI mapping.
Page moves - A page's position in the site hierarchy determines its URL. When the page moves, the URL changes. This can have a negative SEO impact. Use a permanent redirect to tell search engines that the page was moved.
To create a page:
untitledand type a new name.
All pages are based on Templates. The template assigned to a page is displayed in the Template column. The template determines what content is displayed and how. The Standard Templating Kit includes templates for common use cases.
To assign a template to a page:
When you create a new page the template is assigned automatically. By default the Home template is assigned to root level pages. The Section template is assigned to page at level 2. The same template as on the parent page is assigned at level 3 and below.
You can assign templates to pages as permitted by template availability. Availability is a combination of configurable and hard-coded rules which determine whether a given template is allowed to be used on the page.
You can change the page template at any point by selecting a new one. If the content that already exists on the page is not rendered by the new template the content will not be displayed. The content is stored in the repository, however. If you revert to the initial template selection, the content is displayed again.
When you open a page for editing, the in-place editing view is displayed. This is a way of working where the edited page looks and behaves just like the live page. When the page is ready to be published, activate it from the author instance to the public instance.
To open a page:
The Preview button is in the main bar at the top of the page. There are three options: Desktop, Smartphone and Tablet.
In preview mode, no edit bars are rendered. The page is displayed as it would be on the live website.
Broken internal links are rendered in the preview to assit in discovering them. However, they are not rendered on the public instance (live website) because they can lower your SEO ranking and irritate users.
To return to edit mode from desktop view, click >>.
In smartphone or tablet view, click outside of the preview box to close.
You can also use the Esc (Excape) key to toggle between preview and edit mode.
All Magnolia pages have a Properties dialog that controls the page properties.
The options available in this dialog are identical for all pages, except the home page where site-wide options are also available.
To access the dialog click Properties in the main bar at the top of any page.
The first tab of the Page Info dialog is labeled Site for the home page and Info for all other pages. The Page in Navigation, Window Title and Navigation Title fields are common to all pages and function in the same way. The rest of the fields are only available in the home dialog.
The Meta Data tab is identical for all pages. Fields are provided for meta keywords and descriptions that will be included in the HTML code of the page. If you do not include a meta description the page abstract is used.
Search engines that use meta tags, use the meta description in their listings on the search results page. This is the portion that appears in the search results below the main title. For this reason it is best to keep the description under 200 characters and include important keywords.
The Output Channels tab is identical for all pages. By default pages are included in all variations of the site. Deselect one or more variations to exclude the page from the deselected variation.
For more information on channel variations see Channels and Mobile.
The Dependencies tab lists the status indicator and path of dependent content, including:
Content dependencies is an Enterprise Edition feature and is useful in many instances, for example when taking a decision to activate or delete a page.
Pages are made up of components within areas. The use of each component in covered in Components.
Pages are not deleted immediately. The page is first marked for deletion. The actual deletion occurs when the change is activated. This provides an opportunity to restore pages that were deleted in error.
Like activation and de-activation, page deletion is subject to a Workflow process only if the Workflow module is installed and a workflow is configured for deletion. The Workflow module is installed by default. Deletion requests are sent to the
group-publishers inbox for approval.
Watch a video about this feature.
Deletion and de-activation have different consequences. When a page is de-activated it remains available on the author instance for future use. When a page is deleted it is permanently removed from both instances.
To delete a page:
Note the following about deleting pages:
Pages marked for deletion can be restored prior to activation of the deletion, but not afterwards. When a page is marked for deletion, a new page version is created automatically to facilitate restoration.
You can restore a single page from the page list in AdminCentral or the editing view. A hierarchy of pages (parent page with child pages) can be restored in a single action in the editing view but not in AdminCentral.
To restore a page marked for deletion in AdminCentral:
To restore a page or site structure in the editing view: