Although I work mostly with Drupal, I also work with Craft CMS — supporting, developing and maintaining sites built on the excellent Craft CMS.
I generally work with people who can't get the support and development they need from the development agency that built their company's Craft CMS website.
I've worked with some great companies, charities and agencies over the years— both as a contract developer and as a freelance developer.
"Pete has been amazing to work with, especially as we know nothing about web developing! He took over our site and has made it into something that we can use and update ourselves really easily.
He always explains things to us in a way that makes sense, and in English, not developer-speak! And we especially love the videos he makes to teach us how to implement changes!
We feel like Pete is an extended part of our team because he cares about helping us to make the website support the work that EYNP does, and he always gives that little bit extra.
What's great about working with Pete and not an agency is how accessible and easy to contact he is — plus he's super efficient!"
EYNP Programme Manager, Danone UK & Ireland
The popular platforms like Drupal and WordPress are very good but they often suffer from two major problems:
1. Drupal sites are typically built with little thought to the editorial experience. So, once a Drupal site is built, content editors often then need to "jump through hoops", so to speak, to get content published on the site in the way they want it to appear.
2. Conversely, WordPress sites generally ship with a much nicer editorial workflow. This results in a better experience for content editors. However, the code that runs a WordPress site can have the tendency to get very messy, very quickly. This is due to the fact that WordPress is less strict about the way it "allows itself" to be themed and extended.
Note: This is also one of the reasons WordPress sites get hacked more then Drupal sites.
Craft CMS, however, with it's strict MVC architecture (Yii), it's simple templating system (Twig), and a well thought out and easily extendable editorial back-end, seems to be solving these issues for a lot of people.
For the reasons (amongst others), Craft CMS has been picking up some nice market share from the big platforms.
The BuiltWith Craft CMS statistics say that in 2017 alone 232 sites* migrated from Drupal to Craft CMS and 1,555 sites* migrated from WordPress to Craft CMS.
* BuiltWith data is not a complete snapshot of the web so we can assume these numbers are quite conservative.
So, because of my years of experience with Drupal, I'm now helping an increasing number of companies with their Craft CMS sites — notably those companies who have migrated from (or are migrating from) Drupal to Craft CMS.
If your site is built on Craft CMS and you need support, development, or maintenance, just send me a message below and I'll get back to you.
"Working with Peter was an absolute pleasure — thanks to his flexibility, excellent communication skills and honesty."
"Peter is proactive with technical solutions and produces high quality, sustainable work."
"Peter helped us launch the site and took ownership as a developer till the end; which sets him apart from other freelancers we’d ever worked with."
"Pete's vast experience and knowledge, along with being a great communicator, made him a great mentor for the development team."
"We moved away from our old agency for various reasons, but we're glad we did. Pete takes care of all the technical stuff, leaving us to focus on fundraising."
"Peter has been a pleasure to work with. The development phase itself and the aftercare have been fantastic."