Spine, the Perl CMS (Content Management System)

An unrequested criticism of Spine, the Perl CMS. Written with goo intentions.

After I saw Hendrik Van Belleghem mentioning the Spine interview with him on the Australian Techworld I thought I'd take a look at it.

Let me write down my comments so far.

  • It was really hard to find it either using spine cms or open source cms perl. Others might search for CMS in other ways but this alone can contribute a lot to the fact Beatnik mentioned spine does not have many users.
  • The Perl blogging community could could support this project by mentioning it in their blogs and linking to its web site.
  • After I reached the web page my eyes started to hurt. I am very bad at web design so I should not say a word but I think the way SPINE is written made me dizzy. I don't think it is a good strategy.
  • The slowness of my Internet connection might be the reason but it took many second till the screenshots showed after clicking on their link. Once I saw them I was no convinced either. I know it is difficult to show both a full view of how the application looks and readable text but the way it is now would put me off if I was really looking for a CMS.
  • BTW there is no link to styles from the menu bar. It would be nice to add one.
  • When my mouse is over a menu item sometimes it blinks (using Firefox 3.0.7 on Ubuntu 8.10)

So let's try installing it

  • The installation instructions do not include a link to download the application itself.
  • I know there is a link on the navigation bar but not in the text of the installation and even that link lead me to the main Sourceforge web site and not the actual download page. IMHO there should be a single link to the actual file you need to download. (Oh, interesting, after I wrote this down I went back to my browser and clicked on the link again that lead me to the download page this time. A sourceforge hiccup I guess.)
  • The last release was on August 29, 2007 - a year and a half ago - an it is marked as beta. Not promising.
  • After downloading and unzipping it I looked for the tests. After all I am interested mainly on how it is being testes. Unfortunately I could not find any.
  • Then I looked for the version control - maybe the tests are not distributed - but I could not find them. Having an easily reachable version control would increase the chances more contributors.
So the this blog entry did not come out positive as I hoped it will. I hope I am not making Beatnik mad at me that I am writing this. Let me add a few more suggestions here:

  • Setup a public version control and publicize it
  • Start writing tests
  • Start releasing versions to CPAN as well (First I'd rename the main name-space to Spine instead of SPINE)

Published on 2009-03-08 by Gabor Szabo
Code::Maven
Python, JavaScript, Node.js, Ruby, and more.

Twitter RSS feed