-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Claire,
We set up an installation of WordPress MU a short while (at
http://blogs.ecs.soton.ac.uk/) for our department (Electronics and
Computer Science) at the University of Southampton.
It currently hosts a mix of project and individual blogs.
The installation itself is pretty painless, and took minimal
configuration to get a basic install up and running. Work on getting
some branded styles added is ongoing though.
We haven't integrated blog usernames/passwords with any of our other
systems though - this means that members of a project can all contribute
to the blog through a single username if necessary (and keeps
institutional data safer should any security flaws be found in WordPress).
One important thing we've done is to set up a separate blog request
form, and added that to our intranet. This logs exactly which user
requested a blog, and for what purpose. This means we can
approve/reject requests, and track which blog belongs to which user(s),
and keep an eye on blogs that belong to users who've left the University.
Only issues that I can think of:
- - Plugins: we get a fair few requests for additional wordpress plugins
or functionality to be added
- - Preservation: we've not really looked into what to do with blogs long
term (i.e. how do we preserve a valuable blog should we move away from
wordpress in future? What happens when a blog owner leaves?)
Cheers,
Dave
Claire Gibbons wrote:
> Hello all!
>
>
>
> Has anyone else looked into, or used, http://mu.wordpress.org/ for
> multiple instances of Wordpress?
>
>
>
> Or does any else use something else for ‘institutional’ blogging?
>
>
>
> Cheers
>
>
>
> C.
- --
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
__
( (oo)
Dave Challis ) ) ^^^^ )
[log in to unmask](_____________________(__________________(__
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkqStk4ACgkQv26GZvAVVFEYIACfUM5As2NRuJtBcb0sqJnfLIZr
pBkAnRULB7diu5TH9ylEi9iJI4ZDFpQN
=CbMo
-----END PGP SIGNATURE-----
|