wgo CMS Setup

This page documents an ongoing work being discussed at gnome-web-list.

Summary

After deciding that the revamped wgo is going to be based in Plone now it's time to work on the implementation. We will start with a sandbox to play and learn and a separate instance where we will be building the wgo site. This instance will be hosted in a external server and at some point during the beta phase will be moved to the GNOME servers. RamonNavarro coordinates the implementation.

This goal depends on:

• GnomeWeb/CmsRequirements (the selection process where Plone was chosen)

• GnomeWeb/NewWgoStructure (the structure of the site)

• GnomeWeb/Navigation (menus)

• GnomeWeb/LooknFeel (drafts and guidelines for the themes).

• GnomeWeb/WebPolicies

We are currently in the planning phase. (((link here to any URL for testing as soon as you have a prototype))) See GnomeWeb/DevelopmentTimeline to know more about the 2.18 release schedule. See GnomeWeb/Goals for a complete list of goals and their status.

Requirements

1. All the implementation needs to follow GnomeWeb/WebPolicies

2. Have in mind i18n requirements, although in principle the translation work won't start before the 2.18 release. See GnomeWeb/Localization (needs updating, see the Multilingual CMS for some reference.

3. Everybody can access the sandbox. The wgo instance will be operated by the users that are going to work at the end with it, aka the web team.

System Requirements

The Sysadmin team in charge of the GNOME Infrastructure need to know the system requirements in order to prepare the migration and hosting of the wgo 2.18 beta. Please be as accurate as possible in terms of software requirements, permissions, etc.

We need to know :

• Access per second on the wgo on release time :
• Are we going to join wgo users to GNOME LDAP ? :

Tasks

Iteration 0 Buildout

• Create a buildout with all the needed stuff so people can try/develop the site at their local machines DONE

  • http://svn.gnome.org/viewvc/gnomeweb-plone/trunk/wgo.buildout/

Iteration 1 Theme

• Create a plone 3 theme that can be used on all gnome webs, it must have GnomeWeb/Navigation , look like GnomeWeb/PageStructure and GnomeWeb/LooknFeel:

  • The header TO ASSIGN
  • The footer TO ASSIGN
  • The Second Nav portlet TO ASSIGN
  • The Banner portlet TO ASSIGN
  • The Join Gnome portlet TO ASSIGN

    http://svn.gnome.org/viewvc/gnomeweb-plone/trunk/gnome.theme/

Iteration 2 Main Page

• Using feedparser create a default view to show the RSS from news.gnome.org and planet.gnome.org and a splash page. Maybe should be a good idea to create a type MainPage with the content of this splash so we can change and create a new one TO ASSIGN

  • http://svn.gnome.org/viewvc/gnomeweb-plone/trunk/gnome.wgosite/

Iteration 3

• WGO Policy: workflows, types, restrictions, default content, ...

  • http://svn.gnome.org/viewvc/gnomeweb-plone/trunk/gnome.wgosite/

Iteration 4

• Performance ( cachefu, varnish and production configuracion )

Iteration 5

• Content, content, content, content, .... and testing ( big iteration )

Iteration 6

• Production mode on GNOME infraestructura

Participants

Please add your name here if you need permissions to work with the CMS for the wgo revamp. wgo testers are welcome.

If you just want to play wiuth the sandbox you don't need to be listed here.

• RamonNavarro (coordinator)

• QuimGil (editor, learning to be web admin)

• DavidConvent (Plone intgration - theme)

• MariaSoler (testing, i18n)

• JoachimNoreiko (testing, writer, css work if needed)

• SimoneDeponti (Plone theming, css work)

• MattLee (testing, CSS, Accessibility)

• RickyZhou (testing/CSS)

Plone Configuration

High Performance Plone

For enabling a high performance on this implementation we will need to create different zeo servers (two?) as a backend and a reverse proxy as a frontend. We will use LocalFolderNG as the way to store files ( not in the ZDBD ) . We are going to use Squid that is well integrated with ZOPE/Plone using CacheFu or Varnish or pound that is a better reverse proxy. We will have to decide the HTTPProxy polices to make as fast as possible the new portal.

Open Questions ?

• Varnish , pound or squid ?
• Stagging ( edit on one plone and then copy to the public one ) or check-in/check-out of versions (CMFEditions) ?

Content

The content of the website is discussed in the wgo sections goals (to be linked here as soon as they are created). We might use other instances to operate the new subdomains i.e. support.gnome.org. To be decided.

• GnomeWeb/WgoGetStarted

• GnomeWeb/WgoGetInvolved

• GnomeWeb/WgoAbout

• More to come - see 2.18 goals at GnomeWeb/Goals