developer.gnome.org cleaned up

Every now and then I try to do some more clean up of developer.gnome.org, aiming to move any good content to

  • library.gnome.org, as docbook in a source code module, so it can be kept up to date by the relevant people, and translated, or
  • library.gnome.org, as an external link to some other website, or
  • live.gnome.org, if many non-developers will want to change it often.

It has taken a long time, with lots of emailing, searching, hacking, incredibly quick library.gnome.org help from Frederic Peters, and advice from Shaun McCance, but I have finally reached the point that the main developer.gnome.org page is now just a link to the library.gnome.org developer section and two links to some archived stuff.

There is still stuff in the projects directory, which is only really used by the Usability and Accessibility projects. I don’t think that summary page was ever linked from anywhere. I’d like these to be moved to a new projects.gnome.org subdomain, combining with the www.gnome.org/projects/ stuff that seems to have lots more content. Actually projects.gnome.org exists already, as a bad (no stylesheet) version of the www.gnome.org/projects summary page. Moving all this projects/ stuff into a new svn module would make future changes to www.gnome.org easier.

Then we could kill developer.gnome.org completely. I don’t think anyone has any other plans for it. I don’t even think the archive of old content has any real value, but maybe we could move that to dgo_archive.gnome.org or such suchlike.

6 thoughts on “developer.gnome.org cleaned up

  1. FWIW, I’ve already moved most of the projects/usability stuff to live.gnome.org (except the stable HIG, which is on library.gnome.org), and I’m pretty sure all the useful accessibility stuff has already moved too– check with Willie Walker. So I’m not sure the current projects stuff can’t just go away altogether, very soon.

    Only thing I really still need to find a home for from the usability pages is the HIG devel branch, which currently gets auto-built and posted to projects/usability whenever there’s a new checkin. But since that’s a rare occurrence at the moment, it wouldn’t hurt to move it somewhere static for now. (And hopefully library.gnome.org itself will provide that capability at some point, for docs development branches.)

  2. Sounds fine. I’m really not overly concerned about the funky build stuff; it’s quite possible it won’t be needed for much longer anyway, depending on what direction we decide the next version of the HIG should take over the next few months.

Leave a Reply to Murray Cumming Cancel reply

Your email address will not be published. Required fields are marked *