Hi! Sorry for the late-ish response. I've been busy getting back up to speed with my classes after the sprints.
At the sprints, most of my work was centered around applying (cutting, pasting, and changing classnames to work with Plone 3 from Christopher Warner's code) the existing CSS to the new theme directory that we created (which is pretty-much done, but needs some cleanup) and porting the Plone 2 templates to Plone 3 viewlets. The viewlet work is pretty much done. We have a buildout (which I'm pretty sure runs out-of-the-box) at: https://svn.plone.org/svn/collective/gnomeweb-plone/trunk/. The folder buildout that we're using is wgo.buildout-dev. Just bootstrap.py it and bin/buildout it and you'll be good to go. There's still a fair bit of work to do, though. In general, here's what we need to get done: 1. Cleanup and consolidation of stylesheets (remove !importants that I added during development and get rid of default Plone styles whenever possible). 2. Making portlets look more GNOME-ish and less Plone-ish 3. Styling of the secondary sidebar navigation. There's some code that displays the secondary navigation as a portlet. Right now, that portlet would need to get ported from Plone 2 to Plone 3. In Plone 3, the navigation portlet appears to be able to be customized (through the GUI) to do exactly what that code did. We may be able to cut development time by doing that. 4. Creating a custom homepage view that displays the RSS feeds. 5. Switching to a tableless layout. Plone 3 uses a table-based layout now. To maintain code continuity with the current GNOME site and improve the site's semantic-ness, we should probably make the layout tableless. Luckily, there's http://plone.org/products/plone-tableless which accomplishes that. A few members of the OOTB Plone Themes project have reported success with using the page templates from this theme in their own custom themes. 6. Public test server, beta testing, etc. Here's my recommendations on how to finish up those tasks as fast as possible: 1. Create a publicly-visible task list of what needs to get done. We could use http://bugzilla.gnome.org/ or another hosted service, such as Remember the Milk. 2. Create a list of everything that needs to get done before launch. To make it easy for others to participate, we should make them very specific. ("Style the navigation portlet according to the styling in the mockup at ..." rather than "Finish CSS") 3. Come up with an estimate for how long each task will take. 4. Claim tasks. Try to complete tasks within the time estimate. This makes it easier to keep track of who's working on what and how far along they are. What are your thoughts on this? Did I leave anything out? Do you think a public task list would be helpful for coordinating our efforts? Cheers! Jonathan On Fri, Oct 17, 2008 at 4:05 AM, Murray Cumming <[EMAIL PROTECTED]> wrote: > > On Wed, 2008-10-15 at 20:53 -0700, Alexander Limi wrote: > > On Fri, 10 Oct 2008 23:47:09 -0700, Ramon Navarro Bosch > > <[EMAIL PROTECTED]> wrote: > > > > > This saturday we are going to sprint on gnome web at the plone > > > conference sprint Arlington Career Center ( Washington D.C. ) > > > http://www.openplans.org/projects/plone-conference-2008-dc/sprint . The > > > idea is to have a funcional site with the visual design and features of > > > www.gnome.org CMS site so every body can download a buildout and try it, > > > fix bugs, ... If anybody wants to goin us will be at 9 a.m. I'll inform > > > about the state of the sprint during the weekend. > > > > Since Ramon hasn't commented yet (he's probably en route to Barcelona), > > I'm happy to inform you that Jonathan Wilde did lots of great work on the > > theme + portlets, and he showed me a very nice-looking Plone 3.1 with the > > GNOME design. > > > > I'll let Ramon or Jonathan cover the details, but I just wanted to make > > sure that you know that it seemed to be a successful sprint. Now, it's > > time to fix the process issues around this. ;) > > Interesting, and well done, though I am not yet ready to be change our > plans back. I'll need to see real results to be convinced. > > Now it's time to get these changes into svn and to prove that it can be > deployed by someone else. > > If anyone has the ability to put up a reliable test site of this, before > gnome.org does, that would also be useful. > > Thanks. > > -- > [EMAIL PROTECTED] > www.murrayc.com > www.openismus.com > > _______________________________________________ > gnome-web-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/gnome-web-list -- Jonathan Wilde My Blog: www.speedbreeze.com _______________________________________________ gnome-web-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-web-list
