Difference between revisions of "WAT:Create A Project Website"
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
*Need a collaboration space on the web to work on a project application? | *Need a collaboration space on the web to work on a project application? | ||
*Want to publish something like the sengbusch collection? | *Want to publish something like the sengbusch collection? | ||
== Wordpress μ Blog == | == Wordpress μ Blog == | ||
| Line 25: | Line 24: | ||
=== And The Ugly === | === And The Ugly === | ||
=== Examples === | === Examples === | ||
| Line 44: | Line 42: | ||
=== And The Ugly === | === And The Ugly === | ||
== Trac instance + Subversion repository == | == Trac instance + Subversion repository == | ||
| Line 53: | Line 49: | ||
=== The Good === | === The Good === | ||
*very good support for collaboration, including relatively fine grained access control. | *very good support for collaboration, including relatively fine grained access control. | ||
=== The | === The bad === | ||
*relatively hard to change the layout. | *relatively hard to change the layout. | ||
=== And The Ugly === | === And The Ugly === | ||
*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. | ||
| Line 76: | Line 69: | ||
*complete control over the site. | *complete control over the site. | ||
*suitable if the bulk of the site is made up by additional resources, i.e. the handmade pages serve merely as table-of-contents for a file-system full of other stuff. | *suitable if the bulk of the site is made up by additional resources, i.e. the handmade pages serve merely as table-of-contents for a file-system full of other stuff. | ||
=== The Bad === | === The Bad === | ||
*with power comes responsibility. | *with power comes responsibility. | ||
=== Examples === | === Examples === | ||
*http://srvd.livingreviews.org/mdbase/trunk/ | *http://srvd.livingreviews.org/mdbase/trunk/ | ||
== WAT:Tools== | |||
*[http://chrispederick.com/work/web-developer/ web developer toolbar] - an indispansable firefox plugin. | |||
*[http://getfirebug.com/ firebug] - another indispensable firefox plugin to inspect pages which use javascript. | |||
*[https://www.google.com/webmasters/tools/ Google webmaster tools] | |||
== Validators == | |||
*[http://validator.w3.org/ w3c (X)HTML validator] | |||
*[http://validator.w3.org/feed/ w3c feed validator] | |||
*[http://jigsaw.w3.org/css-validator/ w3c CSS validator] | |||
Revision as of 11:29, 5 January 2011
|
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]
You can also maintain web pages manually (but assisted by version control) in a subversion repository which is checked out on a web server. Ask Robert for details.
The Good[edit]
- complete control over the site.
- suitable if the bulk of the site is made up by additional resources, i.e. the handmade pages serve merely as table-of-contents for a file-system full of other stuff.
The Bad[edit]
- with power comes responsibility.
Examples[edit]
WAT:Tools[edit]
- web developer toolbar - an indispansable firefox plugin.
- firebug - another indispensable firefox plugin to inspect pages which use javascript.
- Google webmaster tools