The Pages app displays your site hierarchy. Here you can add pages and move them around.
Pages on a site are displayed in a hierarchical tree. Each site tree has a root page (home page) and child pages.
- Page: Name of the JCR node. JCR character restrictions apply to the name, meaning some characters are not allowed in page names. Invalid characters are automatically substituted with a hyphen. The page name is used in the URL. The convention is to use lower-case words separated by hyphens, for example
- Title: Displayed to visitors. It may be different from the page name and can contain any character. The title string is used in the HTML
titleelement, in the
h1heading on the page and in the navigation title.
- Template: Template assigned to the page.
- Status: Shows the publication status of the page:
- Published (green, solid): Content was published from the author instance to the public instance. Identical content exists on both instances.
- Modified (yellow/amber, two rings): Content was modified since publication. The author instance is not in sync with the public.
- Unpublished (red, one ring): Content exists only on the author instance. It was never published.
Modification date: Timestamp showing when the page was last modified. The timestamp is displayed in the user's own timezone if one has been set in the user profile, if not, the server timezone is displayed.
Website content, asset, configuration and everything else is stored in the . Each item is stored in a node. The node name is generally displayed in the first column in AdminCentral, for example the page name in the
website workspace and asset name in the
dam workspace. Besides being an internal reference to the node, the name is also used for various purposes such to create a page URL.
Character restrictions apply only to node names and not to other user-entered content. For example, you can only use certain characters in a page name but any character in the page title. When a disallowed character is used it is automatically substituted with a hyphen ( - ).
The Path Java class governs character restrictions. All alphanumeric characters (a-z, A-Z, 0-9), hyphen ( - ) and underscore ( _ ) are safe to use in node names. We recommend that you use lowercase letters separated by a hyphen.
JCR 2.0 specification defines the following invalid characters in a local name.
Forward slash (solidus)
Left square bracket
Right square bracket
Vertical line (pipe)
Node names are used to create URLs and cannot contain characters that are disallowed or have special meaning in URLs. These conventions are established by the Internet Engineering Task Force (IETF) Network Working Group on URLs.
Solidus (forward slash)
Number sign (pound, hash)
Characters disallowed by Magnolia.
Apart from the exceptions above, Magnolia allows you to use the full UTF-8 character set for node names and other properties, but UTF-8 encoding is disabled by default. See UTF-8 in pages names for instructions on how to enable it. When enabled, all special characters and notations covered by the Unicode specification can also be used.
The dot character (full stop, Unicode 2E) can be used in node names with the single limitation that it cannot be the first character. You can create a user
john.smith, a page
article.one, a document
Magnolia-Flyer-4.0.pdf, a configuration node
Assigning a template to a page
All pages are based on Templating. The template assigned to a page is displayed in the Template column. The template determines what content is displayed and how.
Template availability defines what template you can assign to a page.
You can change a page template. However, the new template may not be able to render content entered using the previous template. If content cannot be rendered, you cannot edit it. The original content exists in the repository, however. If you change the template back to the original, the content is rendered again.
If a template is able to render a component that was originally entered with a different template, the component may be displayed even if the current template does not offer it in the corresponding area. For example, if you enter a text component on a Travel Standard page and later change the page template to a custom template that also offers a text component, the component may still be displayed.