The person who can give you the best over view of Plone Multisite is Duncan Booth (Oxfam GB - & subscribed to this list)
Duncan is on leave for a couple of weeks.
But in essence, Plone Multi-site allows one CMS (Database) to be used to publish to many websites by making copies of the content
and pushing it out to the relevant site or sites, whilst the management of the content remains within the core CMS.
We developed the product because we felt strongly that we wanted a single content repository for all our different sites.
There's a mention of Multi-site within Duncan's Ploneability slides (pages 8 and 18) & an illustration of this process.
The PDF is called: Ploneability 2006_Building a Site in Plone.pdf
And can be found at: http://www.oxfam.org.uk/ploneability/ploneability_slides.zip
It's fair to say that it's not well documented at the moment.
This is something that we hope to do fairly soon, as well as make it into a slightly more polished product suitable for non-Oxfam use.
Andrew
| Paul Everitt <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 03/07/2006 07:39
|
To: "A list for NGOs \(Non-Governmental Organizations\) using Plone." <[email protected]> cc: Subject: Re: [NGO] Plone MultiSite? |
Andrew Hatton can give more detail, but Plone Multisite has some
interesting features, such as bulk publishing/retracting a piece of
content and all the items it references.
--Paul
On Jul 3, 2006, at 1:16 AM, Shaun Hills wrote:
> I missed Ploneability, but I noticed there was some discussion
> around Plone
> MultiSite. Having had a bit of a look at the code and docs (ahem ;)
> it seems
> like it's a product for pushing content from a central "editing"
> instance out to
> multiple other Plone sites. Is this a fair summary? Is there
> anything else it
> does that I'm missing?
>
> I have a reason for asking. We at NHS CFH run a fairly large but
> ultimately
> quite bog-standard Plone site. And we're starting to hit two
> limitations of
> Plone's out-of-the-box publishing model. Firstly content is all "up
> front" on
> your site, and live the minute the owner hits "save". Risky. So we
> made a minor
> customisation to default all new content to "Private"; at least
> then if it's WIP
> it can't be found by users. But this has an unfortunate side-effect
> when users
> forget to publish their content - they'll create a hyperlink to it
> which will
> work just fine when they're logged in. But as soon as an anonymous
> user hits the
> link, they're prompted for a login.
>
> I think we need to get away from the current system and put in some
> kind of
> staging or editing --> production propagation mechanism. Is this
> the kind of
> problem MultiSite is intended to solve? Or should I be looking at
> one of the
> other staging frameworks?
>
> - Shaun
>
>
> _______________________________________________
> NGO mailing list
> [email protected]
> http://lists.plone.org/mailman/listinfo/ngo
>
_______________________________________________
NGO mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/ngo
|
_______________________________________________ NGO mailing list [email protected] http://lists.plone.org/mailman/listinfo/ngo
