Lineage is a Plone extension. It allows subfolders of a Plone site to appear as autonomous Plone sites to the everyday user. This hub and spoke structure allows site administrators to easily manage multiple, seemingly independent, sub-entity websites in one Plone. Furthermore, the "parent" site can access and view the content in all the "child" sites while the child sites only view their own content. The parent site can also syndicate chosen content to the selected child sites. Lineage is less complex and easier to manage than a cluster of nested Plone sites but gives users all the same benefits.
Lineage can be used within a large organization to manage multiple microsites, such as school district sites, university departments, corporate product sites, public library satellites, professional association events, and more.
- 3.x: Plone 5.2, 6.0 - Python 3.8+
- 2.x: Plone 5.0, 5.1, 5.2 - Python 2.7
- 1.x: Plone 4.3
- pypi: http://pypi.python.org/pypi/collective.lineage
- Plone: http://plone.org/products/collective-lineage
- issue tracker: https://github.com/collective/collective.lineage/issues/
- code repository: http://github.com/collective/collective.lineage/
Bootstrapped your buildout with all the dependencies.
Install Lineage via Site Setup -> Add on Products.
Now you are ready to go.
Add a Child Site:
- In Plone, go to the place where you want to add a new child site.
- Click Add New, and add a Folder.
- Enter the title and description for the Child site.
- Click Save.
- Click the Actions drop down and select Enable Subsite. This "activates" the child site behavior.
- The Plone site now has a child site. A drop down will appear at the top of the Plone to the left of the site actions area. A user can select the parent site or any child sites from this drop down.
There is a bunch of extensions available. They are helpful when there is the need of more special features within subites.
- lineage.index
- Adds an index and metadata that allows to search for content of a specific childsite only
- collective.rooter
- Force catalog queries to obey the current subsite
- lineage.registry
- Provides a plone.app.registry for Lineage subsites. It adds a local component with a layered-/proxy-registry
- lineage.themeselection
- Provides custom theme selection for Lineage subsites.
For more search Pypi
Lineage 2.0 is a major upgrade to the software and will require you to have updated to the 1.1.2 version before you migrate any existing Lineage child sites to the new version. Lineage 2.0 removes all dependencies on p4a.subtyper and makes the product Plone 5 ready. The 1.1.2 release of Lineage is only used to migrate your existing Lineage 1.1 sites up to the needed state for the new 2.0 release.
Steps for upgrading:
- Install version 1.1.2 into your existing Lineage powered site
- Go to the Plone Site Setup and from the Add-Ons panel click the button to upgrade the Lineage product
- Install version 2.0 into your existing Lineage powered site
- Go to the Plone Site Setup and from the Add-Ons panel click the button to upgrade the Lineage product
- Enjoy Lineage 2.0