Page History

Content Structure

To view the content structure and source, login to AdminCentral with username and password superuser.

• Open the Pages app and expand the travel, about and meta nodes.
  • The pages under about and meta are a simple hierarchy. Content for these pages is added in the page editor. The meta parent page is not displayed in navigation because the Hide page option is enabled in the Page properties dialog. 
  • The travel subpages, tour-type, destination and tour display the content for all tours. This content is added and stored in apps. Based on the URL, the content page retrieves the appropriate content item from the app and displays it.

• Open the Tour Categories app to see the tour types and destinations. 
  These are the tour type and destination categories that link the tours together.
  
• Open the Tours content app to see the tours.
  This is where the bulk of the site content resides. In a way, the site builds itself  - the navigation, category overview pages and tour pages are dynamically generated based on the content added in this app.
   

Magnolia Features

Some of the key Magnolia features are showcased in the Travel demo.

User roles

Magnolia has a powerful and flexible security mechanism based on roles, groups and users. You can specify which apps and actions, and even which content within an app, a user can access. You can also limit who can request and publish workflows. 

Open the Security app to explore. Log out as superuser and log in as eric (password eric). Notice that fewer apps are available, for example the Security app is no longer available.

The Travel demo includes three users to illustrate typical roles: (Password is always the same as the user name.)

• eric: An editor who can edit all content. In the Pages app in CE he cannot access the Publish action. In EE he can submit items for publication with the Publish action, but he cannot actually publish content. 
• peter: A publisher who can also edit all content. In the Pages app in CE he can access the Publish action. In EE he can also view items submitted for publication in the Pulse, and approve (publish) or reject them. 
• tina: A tour editor who cannot access content in the Pages app.

Publication and Workflow

Magnolia's publication takes advantage of the Workflow system. While any workflow can be implemented, in the Travel demo you can try the standard "four-eye" publishing workflow which comes with Magnolia out-of-the-box. Eric the editor can edit content, and submit it for approval. Peter the publisher receives notifications in the Pulse, and can review the changes made, and finally publish the changes to the public instances - or reject them.

Multilanguage website

The Travel demo supports two content languages, English and German.

To see this in action, edit the contact page.

• Use the language selector in the top bar to change from English to German. The content of the page is now displays in German.
  Image Removed Image Added
• Click on Main bar and then on the edit icon in the Jumbotron bar. Use the language selector in the Text and Image dialog to view and edit the content in either language.
  

Multilanguage authoring

Admincentral can also be translated into multiple languages,

Log in as eric-de (password eric-de) to see the administration interface in German. Each user can set their language in their user profile.