WillMorris

I'm trying to see if PW is a good fit for our project. It looks like it is, but I'm not quite sure the best way to structure and build it out.


Looking for some input on best practices for setting up a system of sites in PW.

Right now, we have a main site with CMS-driven content here:

http://ebird.org/content/

The content follows this kind of structure:

Home

* News
** News Item 1
** News Item 2
** News Item 3

* About / Help
** Help Item 1
** Help Item 2
** Help Item 3

We also have sub-sites that are navigationally and structurally the same, but have different logos and sometimes different content.


Home

* News
** News Item 4
** News Item 5
** News Item 6

* About / Help
** Help Item 1
** Help Item 2
** Help Item 3

** Help Item 4


Example:

http://ebird.org/content/ak/

With our current CMS, when we create one of these new sub-sites, we copy the existing main site pages into a new folder, and the sub-site admins only have access to that folder.

For instance, only the AK admin only has access to the /ak folder.

The nice part about this setup is sub-site admins are free to add, edit, and delete pages as they see fit within their folder. They never see any of the other sub-sites or main site content.

The problem with this setup is most of the content stays the same between the main site and sub-site. It quickly gets out of sync, especially help/tutorial content that pertains to using the web app.

We want to see if we can set up Processwire to organize content with the following permissions:

Type 1
* Written by main-site staff
* Show on main-site only

Type 2
* Written by main-site staff
* Show on main-site and sub-site
* Not editable by sub-site
* Changes from main-site are reflected on sub-site
* Sub-site does not have the option to hide content (always appears)

Type 3
* Written by main-site staff
* Show on main-site and sub-site
* Not editable by sub-site
* Changes from main-site are reflected on sub-site
* Sub-site has the option to hide content
* When main-site creates content it is initially hidden on sub-site

Type 4
* Written by sub-site staff
* Show on sub-site only

What is the best way to structure this in PW?

Is this possible within the stock PW admin screens or will parts need to be done with our own custom screens accessing the PW API?

If so, how would you go about breaking it up?

Thanks.

We're evaluating Processwire to see if it will work for our site. One of the major requirements is being able to maintain a large taxonomy . You can see our current example here:

http://neotropical.b...al/species/tree

We need to be able to maintain a set of terms with key values and associated metadata (e.g. common name, scientific name, alternate name, etc.) and then associate content with those terms.

Does Processwire allow us to create and maintain a taxonomy of this size? What are the upper performance limits?

Thanks.