While writing my post about the last tutorial, I noted that indexhibit had been updated for the first in a long time.

When building out my artist site last year, I did a quick scan of CMSs and selected one that I thought would work well (grav). At the time I needed to get something up and running very quickly for the Interim Show. When selecting which one to use I looked at a few CMSs and noted that indexhibit, along with cargo were the two that seemed tailored and for art and creative portfolios. I dismissed both as they seemed to be getting a bit long in the tooth without having any updates, hence my use of the more modern Grav.

Now that indexhibit has been updated, I thought I’d take a quick look at it… to avoid FOMO (fear of missing out).

The verdict is: meh. I had hoped to love it. But, no: its very much showing its age; the software stack has MySQL in there whereas all the cool kids are going NoSQL or file based (for the obvious advantages); the admin interface is clunky; etc.

But, it has got me thinking. When I get around to updating my artist site, do I twist it to be like indexhibit (a known pattern)… or do I do what Rachel Maclean did for her site and do something very completely not. There are pros and cons to either approach. I need to reserve some time to look into this.

comments powered by Disqus