Magnolia 5.6 reached end of life on June 25, 2020. This branch is no longer supported, see End-of-life policy.
...
As you browse the site, imagine what your products or services could look like in a site like this. Tours could be replaced with whatever products, information or departments are important in your organization.
...
To view the content structure and source, login to AdminCentral with username and password superuser
.
travel
, about
and meta
nodes.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. 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.Some of the key Magnolia features are showcased in the Travel demo.
HTML Wrap | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
Watch: Overview of 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.HTML Wrap | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
Watch: Overview of 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.
HTML Wrap | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
Watch: Multilanguage features |
The Travel demo supports two content languages, English and German.
To see this in action, edit the contact
page.
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.
...
...