The first key concept: instance-instances. Each project must have at least one author instance and at least one public instance. The following will tell you why:
Basic concept: JCR
JSR-170 definition: is an advanced information management system, which is a traditional data warehouse extension, it provides such as version control, full-text search, access control, content classification, access control, content event monitoring and other content services.
The Java Content Repository API (JSR-170) attempts to establish a standard set of APIs to access the content repository. If you are unfamiliar with the Content management system (CMS), you will certainly be confused about what the content warehouse is. You can understand this by understanding the content repository as a data store application that stores text and binary data (images, Word documents, PDFs, and so on). One notable feature is that you don't have to worry about where your real data is stored and what is a relational database? Is the file system? Or is it XML? More than just storing and reading data, most content repositories offer more advanced features such as access control, find, versioning, lock content, and more.
Why do
A typical scenario:
A company's marketing team is doing key content updates.
Problem:
1. The website has 20,000 clicks per day. All updates are subject to confirmation by the legal team and global marketing executives.
2. In order to assess the impact on the public, legal and marketing teams need to see the changes and communicate any necessary changes as part of the change management process.
Solution:
1.Magnolia CMS uses a set of author instances and a common instance. All creations occur in the author instance. Public content is the copy of all edited content to the public for public viewing.
2.Magnolia CMS Authors cannot publish changed content to public instances directly to the public. Must have a release administrator to do it.
3. The publishing administrator also uses author instances, but permissions are limited to publishing changes from the author instance to the public instance.
Results:
The purpose of this is to carefully protect the reputation of one of the company's most valuable assets.
What's an instance?
the Magnolia CMS is divided into two Web applications: "Author" and "Public". An instance is a separate copy of the system . Magnolia requires at least one author instance and at least one public instance. We provide pre-configured authors and public instance packages.
Public instances must never be registered, and the public will have to publish the content through the author. So the public instance publishes content on the website is not afraid to attack. (safety and security advantages)
How does an author edit a Web page?
Creation always occurs in the author instance, Magnolia CMS on the page using edit bars to delete and modify the page elements, WYSIWYG.
How does the publishing site work?
- Community Edition. When an author publishes a change in the author instance, that's change was visible on the public instance immediately.
- Enterprise Edition. The workflow is enabled by default. Before any changes be made on the public instance, a publisher (this is a particular user role) must first confirm the CH Ange through the PULSE notification system. Learn about WORKFLOW:C6 workflow
Install the community version of the program, ready to contact.
Official Download Link: http://sourceforge.net/projects/magnolia/files/magnolia/
Practice-Superuser vs Eric vs Peter
- Open the example-http://localhost:8080/magnoliapublic.
- Log in to Http://localhost:8080/magnoliaAuthor using Superuser (Superuser/superuser).
- Log out.
- Then log in with Eric (Eric/eric).
- Notice what's different.
- Try editing some of the content in pages. Preview directly see the editing effect. Support Phone Tablet PC preview.
- Then sign in with Peter (Peter/peter) to publish the edits.
- Refresh the example http://localhost:8080/magnoliaPublic see the updated effect.
Superuser and Eric is different users with different privileges.
Web content Management System Magnolia Departure-mining Excellent architecture (3)