Stories
Slash Boxes
Comments
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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • ...would be to get a professional designer to create a real logo and a site template, imo this is long overdue.
    And by professional designer i mean someone prominent, like Jon Hicks.
    • The logo we already have. The onion can be used really well and in different ways.

      It's the site template, done in a way that we people making up new perl.org/cpan.org websites can easily integrate, that we badly need.

      • A proposed redesign for use.perl.org, created by Andy Wardley the last time this discussion happened:
        http://wardley.org/use.perl.org/test.html [wardley.org]

        A few different people tried to contact pudge with no response, so plans/hopes to improve the looks of use.perl were abandoned.

        Trying to do something useful with the wave of enthusiasm for Perl websitey things, at Digital Craftsmen we built this:
        http://perlisalive.com/ [perlisalive.com]

        Which obviously uses a modified version of Andy's design. Meanwhile, Andy was working on a redesign of the London.pm website:
        http://london.pm.org/ [pm.org]

        Which also has the 'glass onion' theme/style going on.

        Back at Digital Craftsmen, we started looking at adapting the first design for use on www.perl.org instead:
        http://digitalcraftsmen.net/perl.org/slice.png [digitalcraftsmen.net]

        Unfortunately after discovering that we'd need an Apache 1.3 environment to host the combust CMS that perl.org runs on, we lost momentum on implementation of that idea. It'd be nice to pick it up again, but currently client work takes priority. As mentioned previously, it's also a bit tricky to find an entire spare server so that we can downgrade it enough that it will run combust - an example of how the technology used on the back-end can sometimes influence the availability of design/implementation efforts for the front-end.

        So... there have been some efforts recently to try to generate a 'suite' of sites with a co-ordinated look-and-feel, but not a great deal of concrete progress, particularly where the core sites are involved. If there's a willingness to make more progress now, then people will probably step up to do the work.

        As a footnote, last I heard dev.perl.org was very open to suggestions and help in improving the look and feel of that site, so that might be a good staging ground for any improvements eventually intended for www.perl.org

        --
        Perl is Alive
        http://perlisalive.com [perlisalive.com]
        • Wait wait wait... that THING [perl.org] is a CMS?

          I can't see anything there I couldn't replicate with an svn repository and a copy of DreamWeaver.

        • It's nice to see that somebody has been trying to do something.

          I suspect, however, that we might need to be one step more abstracted from where your examples are.

          I've been part of two site redesigns of this kind, the Cisco design they used on all their sites during most of the 2000s, and a smaller more recent one at my current employer.

          The first phase almost never results in a useful website and often not any useful prototypes either, it's a look and feel process.

          The result is usually separate CSS and HTML

        • Most of Andy's changes were meaningless cosmetic changes, and I simply don't care about that, and don't have the time to give to shepherding through things that to me are unimportant. I have too many actually important things to ignore! I know a lot of you care deeply about how shiny a web page is. I am not one of these people. I don't apologize for it, and I find it odd that your perception of the site would be so drastically impacted by that.

          As to the lack of news that Alias mentioned, I've many times

          • Oh and BTW, I think Andy's changes mostly look good, I am not attacking him or them; I am just saying it's something I don't have the time to care about.

            • If someone had the time and inclination to apply some of those visual changes here, would you be willing to give access to do so? (I realize that your "I don't care about those things" means that you aren't likely to work on them. I'd just like to know if that means you're opposed to them.)

              • Perhaps. As noted, right now the code on this site is a bit behind. I am planning on updating it soon, within the next few weeks. I would be open to pure CSS+images changes. Unlikely I'll be too interested in code/HTML changes, as those tend to take up a lot of time, but you never know.

          • "I simply don't care... I also don't care"

            Thanks for getting so efficiently to the root of the problem.

            • You appear to be trying to criticize me, but I don't think you actually are.

              • You think wrongly.

                Allow me to rephrase it in a way that you can understand: you have your head so far up your own ass you could kiss your own tonsils. Hope this helps.

                • Nope, you've confirmed I was right all along. You were not, in fact, criticizing me. You were trying to, but you did not. You think it is a criticism of me that I don't care about such things. It's not. You think that the fact that I don't care about such things means I "have my head up my ass." You are wrong.

                  I could, of course, say the exact same thing to you, from my perspective: anyone who thinks a "shiny" web page makes a lick of difference, and actually cares about such things, has his head up hi