Notes edited from Laura Whitehead from 05/13:

• It was a pro theme built to suit a wide range of uses rather than much custom-ness for a specific purpose.

• It's a bought theme (not back in some extents, and fitted-ish what they were seeking at the time) and they have spent quite a bit on other devs in the past from places as far as India (!) to do work for them, plus my bit.

• It was hacked in summer 2012, then Laura the web manager/WP developer did some freelance work to get it back up and running, provide back ups and advice. (The backups are now done automatically on the PARROT server). Laura also did some tweaks and additions (e.g. download counter). It's not clear if the suggestion is that the plugins led to the hacking or something else.

• It wasn't my code and some of it at some point needs a good ole tidy to modernize which they are aware of. I've gotten used to the code on their site, but when it's not your own, does take a bit of time to see why the original coder did things in a certain way.

• They could be really using custom post types to the full on their site rather than all their case studies and wotnots just being a blog post with a category attached. This would have much more benefit to the end reader too.

• I would suggest that they look at commissioning a new theme, or get one that is simple and can be enhanced economically to meet their needs.

(eg, for an example - I don't really use others themes as code em up specially, but one case where I did use another theme - I used this free and robust lightweight theme - ​http://wordpress.org/extend/themes/responsive as a quick and v cleanly coded base, and literally just a few hours later and some custom design and bouncy boxes and rewriting bits of code transformed it into ​http://www.wildmayor.org.uk/ as the dosh and timeline of just one day for getting this microsite live didn't warrant a design from scratch as such.).