Slashdot Mirror

← Back to Stories (view on slashdot.org)

How To Choose An Open Source CMS

Posted by ScuttleMonkey on from the focus-on-the-problem dept.

An anonymous reader writes "Content management specialist Seth Gottlieb has written an easy to understand how-to on selecting an open source CMS. Gottlieb is also responsible for the whitepaper 'Content Management Problems and Open Source Solutions' which summarizes 15 open source projects and distinguishes between open source CMS and proprietary software selection."

5 of 191 comments (clear)

  1. Best CMS by Anonymous Coward · · Score: 5, Funny

    Two of the most popular and flexible open-source Content Management Systems are vi and emacs...

    1. Re:Best CMS by maxwell+demon · · Score: 3, Funny
      Emacs sucks, though.

      Just add (setq suck nil) to your .emacs file.
      --
      The Tao of math: The numbers you can count are not the real numbers.
    2. Re:Best CMS by Elixon · · Score: 2, Funny

      I usually write new CMS in my old CMS (Emacs).

      Emacs is good, but I didn't found the sufficient support of keystrokes like C-x C-e in modern browsers. That's why I didn't choose the Emacs for the front-end for my newest and brightest CMS. ;-)

      But I hope that they will evolve to be at least as supportive for ten-strokes-in-one commands as the Emacs was twenty years ago... ;-)) I foreseen that the Web 4.0 will support all Emacs' fundamentals at least in "transitional" mode for the beginning. Refer to W3C eXHTML (Emacs-eXtensibleHyperTextMuleLisp) draft on http://www.w3c.org/ .

      --
      Well, I've got to get back to work. When I stop rowing, the slave ship just goes in circles.
    3. Re:Best CMS by garethwi · · Score: 2, Funny

      So, if I were to choose one of these, which one would be best? Vi or Emacs?

      --

      Find funky gifts
  2. Re:Killer features by Anonymous Coward · · Score: 3, Funny
    Our choice ended with slashcode.

    You're such an asskisser. ;-)