Yes, 'sane' is my goal here. And, Namespaces is the kind of solution I'm
looking for.
So, is it practical to add 10 or more namespaces? Will it be a big burden on
the system, and affect performance/speed?
Thanks,
-e
-----Original Message-----
From: mediawiki-l-bounces(a)lists.wikimedia.org
[mailto:mediawiki-l-bounces@lists.wikimedia.org] On Behalf Of Platonides
Sent: Wednesday, January 20, 2010 7:20 AM
To: mediawiki-l(a)lists.wikimedia.org
Subject: Re: [Mediawiki-l] MediaWiki for user documentation, including
partner company branding
Evelyn Yoder wrote:
Hello all -
We use MediaWiki for user documentation. As the sole author, I can build
and
manage new versions of the wiki in order to support
software version
releases.
The issue is that we now have partner companies who want to create their
own
support pages, and use a custom skin (with their own
logo/skin).
Is there a practical way to allow me to continue to make regular updates
to
the base wiki, without overwriting the partner
content? Can we provide
each
partner with a space they control, individually?
Any suggestions would be much appreciated.
Best,
Evelyn
- - - - - - - -
Evelyn Yoder
Technical Communications
www.LongJump.com <http://www.longjump.com/>
What do you mean with "new versions of the wiki"?
You would update pages, so you would only need not to write the same
page from both sides (even then, MediaWiki would warn you before
overwriting another person save at the same time, not to mention the
history).
If you want to separate them from mediawiki POV, place each group of
support pages at a different namspace. But any sane convention would
work to "avoid overwriting each other's content".
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l