On Wed, 26 Jun 2013 02:53:16 +0200, Josh Berry <tae...@gmail.com> wrote:
Just curious, what features drove the creation of your own CMS?
Basically, I previously used Infoglue, a FLOSS Java CMS. It was good, and I presume it's still good, but it's bloated with stuff. Being FLOSS it was expandable, but being also bloated made it harder than needed to learn its APIs. Introducing stuff such as Twitter Bootstrap, or JavaScript libraries, or hi-density support etc... was always harder than needed. Also, I realized there's no need for having a relational database behind it, since a CMS it's about files. A filesystem is enough, and Git or Mercurial can provide all the needed features of transaction support and history; furthermore, they make it possible to easily have multiple instances running, such as one on my laptop where I do edits, and then push changes. And I can branch too. Admittedly, this might sound not as friendly for a non-programming end-user, but I'm a programming user, so I feel much more at ease in this way.
The most photographic oriented feature are, trivially, the capability of extracting all the metadata from the image for captions (including the title and shooting data). I suppose other CMSs support this, but I suspect some details aren't done as I wish (such as extracting the model of the lens used - I'd say two years ago there was nothing like that).
-- Fabrizio Giudici - Java Architect @ Tidalwave s.a.s. "We make Java work. Everywhere." http://tidalwave.it/fabrizio/blog - fabrizio.giud...@tidalwave.it -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To unsubscribe from this group and stop receiving emails from it, send an email to javaposse+unsubscr...@googlegroups.com. To post to this group, send email to javaposse@googlegroups.com. Visit this group at http://groups.google.com/group/javaposse. For more options, visit https://groups.google.com/groups/opt_out.
