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.

Survey: Which feature do you expect in a good CMS? 4 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • Hackability (Score:1)

    by Juerd (1796) on 2003.08.24 16:10 (#23437) Homepage
    Hackability (includes documentation)

    Ease of use (includes documentation)

    Scalability (efficient programming. No needless complex and large OO structures for simple templating, for example)

    Image management (javascripts to insert the images in the html after uploading)

    Almost everything disabled by default (options enabled only when needed, so simple things can stay simple)

    Comment fields for internal use (at least one for every type of storage)

    Integrated version control and easy backups

    A good way to separate test servers from live servers and synching

    An easy way to provide alternative interfaces for the disabled (and text-browser lovers)

    Last, but very important item: NO OBSCURE URLs! URLs should be easy to remember, easy to type and easy to parse. Write your own web server or mod_perl handler, or use PATH_INFO, or mod_rewrite. No "&", no "?", no ";".
    • I forgot:

      Mailinglist interface. If the CMS supports news items, it should also support sending the news to a mailing list.
    • What if I provide a very easy way to add both front end handlers (preprocessing certain tags) as back end handlers (adding admin sections) by just allowing module drop-in? :)

      Documentation is always a hard part but I already included POD everywhere.

      Obscure URL bits.. I use mod_perl handlers, for example to fake real HTML files.

      Alternative Interfaces shouldn't be a problem, I barely have any layout data hardcode (except for some form generating).

      I'm not sure what you mean by Image Management...

      Version C
      • Image management ::= the ability for the user to upload an image and have it inserted in the page that is currently being edited, at the location of the text cursor, combined with means of removing images from the server

        Comments for internal use ::= comments attached to pages, images, forms, etcetera, used by the people who maintain the site. I include these things with every project, and people always seem to find a use for them :)
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.