Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • I absolutely agree to everything you said! As a full-time Perl developer and part-time web designer I'd really love to help renovating the appearance of Perl. I've recently done a redesign for which got the approval of the core dev team (sadly, it's still not online though). So ... what's the best place to start offering help? :)
    • Step 1. Politics

      If we're going to start redesigning websites wholesale it needs buy-in from the appropriate people who built and own the websites, so that anything we create is suitable for purpose and reusable across all of the websites properly.

      • it needs buy-in from the appropriate people

        Which also means some technical constraints*, because it has to be able to run on the existing hardware budget if not the existing hardware, and scale to the size of known traffic peaks. Yes, these sites can end up on the front page of slashdot, so the "static" pages better not be making umpteen calls to a database to generate their content.

        * constraints are good. A good artist uses constraints to channel their creativity and inspire them. Well, that's my story an

        • I don't know the current infrastructure, but IMHO it'd be a good idea to utilize some sort of flexible and static content generating CMS (Bricolage comes to mind ... Maybe we can even get David Wheeler to help with the setup and planning of the site)?
          • I think you're missing the point. Adam is talking about presentation and layout design, not a CMS or whether we're using a flavour of the month framework. Templates and CSS can be integrated into any site. Ruby on Rails largely got peoples attention because the initial websites looked well designed, and had nothing to do with the backend codebase.

            The problem is that many of us are decent coders, and can put together a functional site pretty well. However, we're mostly not website designers and that's what w

            • The main reason Digital Craftmen didn't manage a full implementation of our proposed glossy design for is that combust (the CMS) requires apache 1.3 and mod_perl 1 to run... we don't have any servers that out of date, and we couldn't spare one to downgrade for the build and test.

              While I agree that the back-end shouldn't be the driving force in an aesthetic redesign, it seems that it can sometimes be a very effective brake.

              Perl is Alive