[Gimp-web] New page layout and new menu (summary)

Wed Sep 3 15:59:14 2003

Recent changes have left the /admin pages misaligned and mislayed.  Should I
jump in and ix them, or is a better arrangement/fix already on it's way and
I'm just impatient? :-)

Helvetix

On Mon, Sep 01, 2003 at 05:47:34PM +0200, Raphaël Quinet wrote:
> On Sat, 30 Aug 2003 12:06:20 +0200, Niklas Mattisson <scizzo@gimp.org> wrote:
> > Could you after the commit make a status mail about:
> > - What big changes will have the commit done?
> 
> To summarize:
> - Changes to the page layout.  The result should work better in
>   text-based browsers and in Netscape 4.x.  Other browsers should not
>   see a big difference.  Note that I have just changed the inclusion
>   of the style sheet in order to hide if from NS4.  It works better
>   that way.
> - New menu.
> - Removal of several old files that were not used anymore.
> - Some pages have been moved from /unix/ to /source/.  Not finished
>   yet.
> 
> > - Is there any problems with the new layout as you can see it?
> 
> The contest page is broken (when you load it for the first time).
> This is probably due to the extra <div> used for the "NEXT" button,
> although I am not sure about that.  It should not be too hard to fix
> the HTML code for the gallery, but this is not a high priority for
> me.  I'd rather launch the site without the contest pages than delay
> the launch.
> 
> There may be some problems in the admin pages because they are still
> using the old layout, but this is not very important either.
> 
> I haven't updated the include files for the tutorials and howtos.  Is
> it really necessary to use a different template for these pages?  The
> main differences are the absence of menu and the custom copyright
> message.  I would prefer to use the same template as the other pages,
> but with one extra line of code that would hide the menu when the page
> is loaded (the user could still view it by clicking on the image).  As
> for the copyright, it could be moved to the top of the page (below the
> title) and we could use the standard footer everywhere.  What do you
> think about that?
> 
> > - What bugs does the commit close?
> 
> Here is a list:
> - http://bugzilla.gnome.org/show_bug.cgi?id=120667
>   (Better accessibility for text-only browsers.)
> - http://bugzilla.gnome.org/show_bug.cgi?id=119759
>   (Support for Netscape 4.x.)
> - http://bugzilla.gnome.org/show_bug.cgi?id=119477
>   (Style sheet: differences between <h2> and <h3>.)
> - http://bugzilla.gnome.org/show_bug.cgi?id=119246
>   (Moving pages from /unix/ to /source/.)
> The last one is not closed yet because /source/index.html still has to
> be written.
> 
> > - Is there anything we should maybe take a better look at after the
> > commit is done so everyone can help with testing the site?
> 
> Try to test it with less popular browsers.  I am rather confident that
> it works with Mozilla and MSIE, but I haven't tried it with Opera,
> Safari, OmniWeb, Amaya and others.  Also, check what happens when you
> disable style sheets or scripting.  Or if you switch to very large or
> very small fonts (you may have to hide and re-show the menu).  So the
> idea is to test it with unusual combinations of browsers and browser
> settings.
> 
> > - After the commit what might be the big things that needs to still be
> > done on the site before the move? (You are the coordinator and should
> > have at least some idea of what still needs to be done before the move)
> 
> I was hoping to have most of the stuff ready today.  Unfortunately, I
> did not have enough time to work on the contents.  I will probably be
> very busy at work this week (I will be on a business trip in Sweden
> from tomorrow until Thursday) and I doubt that I will be able to do
> much before Friday.
> 
> Here are some of the things that should be done.  Not necessarily
> before the move, though.  Even if the current site contains several
> broken links and pages without real contents, I wouldn't mind
> launching it now.  We can always fix the contents later.
> 
> * Re-organize the platform-specific sections: Unix, Windows, MacOS X
>   and OS/2.  The index pages for these sections should follow the same
>   structure.  Here is a proposal for that structure:
>   - Getting and Installing the GIMP
>     - how to get binaries for that platform? (downloads, CDs, ...)
>     - how to get the sources and build them for that platform (this
>       should only be a link to a page in the /source/ section)
>   - Requirements
>   - Configuration
>     (platform-specific configuration options: fonts, etc.)
>   - Help and Documentation
>     (links to platform-specific help and documentation)
>     (optional: links to platform-specific bug lists)
>   The first two sections of the MacOSX page are already close to what
>   we should have for the other platforms.  In the Unix page, some of
>   these sections should have separate items for Linux, Solaris, etc.
>   The following bug reports are relevant:
>   - http://bugzilla.gnome.org/show_bug.cgi?id=119537
>     (Unix section should start with links to binaries)
>   - http://bugzilla.gnome.org/show_bug.cgi?id=119538
>     (remove "our support / your support")
>   - http://bugzilla.gnome.org/show_bug.cgi?id=119539
>     (more informative download links for Windows - applies to others too)
>   - http://bugzilla.gnome.org/show_bug.cgi?id=119246
>     (move /unix/ files to /source/)
> 
> * Update the /downloads/ page and link to the platform-specific pages
>   for downloading binaries.  Add references to the /source/ section
>   for compiling the sources.  Update the list of mirrors.
>   Relevant bug report:
>   - http://bugzilla.gnome.org/show_bug.cgi?id=119562
> 
> * Write some decent contents in /source/.
>   - http://bugzilla.gnome.org/show_bug.cgi?id=119246
> 
> * Improve the contents in /develop/ ("Getting Involved").
> 
> * Update the page layout for the tutorials and howtos.  See the
>   proposal above.
> 
> * New screenshots
>   - http://bugzilla.gnome.org/show_bug.cgi?id=119560
> 
> * Several files (INSTALL, HACKING, ChangeLog, ...) should be fetched
>   automatically from CVS.  I would like to take care of this after the
>   move, not before (I don't care if the links are broken in the
>   meantime).  I already keep a checked-out tree on wilber, updated
>   twice a day by a cron job.  Several links to it are already used on
>   the developers site and I would like to do the same for the main
>   site.  But this requires the user accounts to be moved first.
> 
> -Raphaël
> _______________________________________________
> Gimp-web mailing list
> Gimp-web@lists.xcf.berkeley.edu
> http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-web