FS#42 - Website Redesign
Attached to Project:
General
Opened by Phillip Smith (fukawi2) - Sunday, 28 February 2010, 00:51 GMT
Last edited by Phillip Smith (fukawi2) - Sunday, 28 February 2010, 00:52 GMT
Opened by Phillip Smith (fukawi2) - Sunday, 28 February 2010, 00:51 GMT
Last edited by Phillip Smith (fukawi2) - Sunday, 28 February 2010, 00:52 GMT
|
DetailsWebsite redesign to take account of the following:
- Low resolution scaling (See FS#38: http://bugs.archserver.org/task/38). - Creating our own identity rather than just looking like Arch Linux with a green filter. - CSS for mobile clients (eg, iPhone etc) Possible move of platforms from CMS Made Simple to: - Drupal? - Wordpress? - Something else? Anything else? |
This task depends upon
http://www.archserver.org/index.php?page=test-only
http://www.cmswire.com/cms/web-cms/drupal-vs-ez-publish-vs-wordpress-vs-cms-made-simple-004744.php
I saw that Drupal caching is quite good, and I believe that we mostly have anonymous visitors (since the forum, wiki and the bug tracker are separated from the website itself) and static content (with one exception, the front page).
One downside however is that drupal is quite heavy for the database (52 tables on my computer, core-install).
I don't see a large number of DB tables being a barrier to adoption of a package -- CMS Made Simple already uses 40 tables, plus sequences.
What are your requirements from a CMS? You mention caching (to help with high usage) anything else?
The main 'requirements' are detailed in the bug details -- although I've experimented with Drupal recently and I don't think it is a suitable platform. Joomla looks very nice, but perhaps overly complex, plus it doesn't seem to support PGSQL as the DB backend :(
With the correct templates and stylesheets, CMS Made Simple is still a winner IMHO:
- Simple
- PGSQL Backend
- Easy to theme
- Easy to extend
- Already being used for the site :P
I'm happy to put up a testing and development installation of CMS Made Simple if someone wants to play with it...
Generally CMSs like Joomla I find are not easy to work with, but CMSs that sit in the background and don't get in the way I like; sitecmd is one of these https://launchpad.net/sitecmd.
Criticism welcome. Likes and dislikes?
Website "on a page"? Or do you prefer the original "whole page" design?
Is the menu too simple?
@fukawi : I would like to hear more about this please. I'm running drupal on my own server so I would like to know what is wrong with it ? Performences, security, lack of features ?
@jsteel : Well... currently it is just a white box with a grey border... Doesn't look really professional to me :/
I'll do some work on Photoshop (but I'm quite busy right now).
@jsteel - Personally I like the 'whole page' approach. In reference to bug 38 (http://bugs.archserver.org/task/38), we don't want to waste any screen real estate. Both the FreeBSD and PC-BSD websites often receive comments that they are clean, clear and easy to use/navigate so perhaps we could use them for some inspiration: http://www.freebsd.org/ http://pcbsd.org/
1) The banner, which the site's logo plays a huge role in. In this case I have kept it as it is; do you think the banner needs work?
2) The page. If you prefer a "whole page" design then there's nothing to consider further; there will be no borders/rounded corners etc. It will fill the page.
3) A menu. I created a very simple menu as you can see. I like to start things as simple as possible and build upon them. In terms of positioning, colours etc. am I going in the right direction?
4) The content, I assume doesn't need changing apart from keeping the fonts etc. in theme with the design.
http://bbs.archserver.org/viewtopic.php?id=6
The main thing with the menu is there needs to be a common, site-wide menu (home, forum, bugs, wiki etc) and a defined area for a sub-menu that each sub site uses for links that are specific to that sub-site (eg, the forum has Index, User List, Rules, Search, Profile etc).
There is also the Graphic Charter (aka Design Guidelines) in the wiki:
http://wiki.archserver.org/index.php/Graphic_Charter
I have not yet decided on how to provide the second layer of links. I was going to go down the route of having static links beneath the menu as you have now, or would you prefer drop-down links like you created in your proposed design?
The menus are probably easier to maintain from a technical point of view if they're separate like they are now, but I do like the CSS drop down style. A big plus IMHO for the drop-down style is it allows all parts of each sub-site to be accessible from all other sub-sites (eg, from the wiki I can click thru immediate to the Forum Search page for example).