Difference between revisions of "WAT:Create A Project Website"

From MPDLMediaWiki
Jump to navigation Jump to search
Line 63: Line 63:


*Served via HTTPS using a root certificate which isn't pre-installed in most browsers. Thus, not the first choice for public facing websites.
*Served via HTTPS using a root certificate which isn't pre-installed in most browsers. Thus, not the first choice for public facing websites.
=== Examples ===
*[https://dev.livingreviews.org/projects/wals/ the wals project pages]


== Web checkout of a Subversion repository ==
== Web checkout of a Subversion repository ==
example: http://srvd.livingreviews.org/mdbase/trunk/
example: http://srvd.livingreviews.org/mdbase/trunk/

Revision as of 09:51, 17 April 2009

Webmaster Apprenticeship Training

How to create a project website
Tools

edit


So you're a webmaster for a website that doesn't exist and your first task is to create it? There are several options of getting this done within the MPDL infrastructure.

Use Cases[edit]

  • Need a collaboration space on the web to work on a project application?
  • Want to publish something like the sengbusch collection?


Wordpress μ Blog[edit]

Wordpress isn't only a blogging software. It can easily serve as CMS. New blogs in our installation can be created by Lars and Robert, same goes for user accounts.

The Good[edit]

  • relatively easy to change the layout, in particular because there are lots of themes to choose from.
  • something like a "news" section is pretty much built-in - it's a blog after all.
  • Interaction with the general public possible via comments.

The Bad[edit]

  • when it comes to support for collaboration

And The Ugly[edit]

Examples[edit]

Colab Portal[edit]

As you currently read this information, you already discovered the colab wiki. It is a publicly available installation of the mediawiki software. Everybody can register for an account and start to create new pages or to modify existing articles.

The Good[edit]

  • probably the easiest way to publish "single pieces" of information

The Bad[edit]

  • layout is defined for complete installation
  • very weak measures for access control

And The Ugly[edit]

Trac instance + Subversion repository[edit]

https://dev.livingreviews.org/projects/ Initial setup and user management can be done by Robert and André.

The Good[edit]

  • very good support for collaboration, including relatively fine grained access control.

The Bad[edit]

  • relatively hard to change the layout.

And The Ugly[edit]

  • Served via HTTPS using a root certificate which isn't pre-installed in most browsers. Thus, not the first choice for public facing websites.

Examples[edit]

Web checkout of a Subversion repository[edit]

example: http://srvd.livingreviews.org/mdbase/trunk/