Yep – design specifically for WordPress. It’s super important to have a handle on the tech you’re wanting to use during design (and preferably before you start design). Because you’ll want to know the parameters you need to work to.

Just to point out through, I’m not referring to limitations – but knowing early on what’s possible from a tech perspective and what’s not, and what will be easy and what will be hard, can be the difference between project success and project failure. When I think about the times I’ve been part of a project that is in a tricky spot, it’s almost always because of either a mis-alignment with design and dev (i.e. the designers have designed something that’s taking ages to develop, or something’s gone awry with the estimates).

I’ve come across plenty of instances where a designer has designed something that looks great in abstract form as a standalone piece of design, but because the designer wasn’t aware of what WordPress, or WooCommerce, or FacetWP, or Easy Digital Downloads could do, they designed something that whilst possible, would take way longer, and be far more difficult, than if the designer knew how WooCommerce templating worked for example, or had first-hand knowledge of the various ways you can extend WooCommerce, FacetWP, EDD etc.

WordPress is extremely powerful and capable of handling any project (because WordPress became popular for its theming capabilities, people associate it with themes more than anything, but it’s so much more than that).

Also, the barrier to entry used to be low (that’s changing) – that’s great because so many people can build stuff with it, but equally it can mean that quality can suffer. That’s why it’s really important to work with a dev who knows WordPress inside out and knows how to push it, and how to make sure your tech is built properly.

At its core, WordPress is a way to interface with a relational database (mostly MySQL but also MariaDB and even SQLite). And it’s even possible to use more than 1 database. Plus WordPress has an infinitely powerful REST API. What’s more, WordPress has introduced the ultimate editor allowing WordPress to be used for pretty much any type of website or web app. These things combined make WordPress the best platform to build your tech on.

Just a note, WordPress.org and WordPress.com are different. Some people get confused because they are both called WordPress. But, WordPress.org is the open source version that can be downloaded and used for any purpose – that’s what I use. WordPress.com is itself built on top of WordPress.org (albeit with about a bazillion customisations). WordPress.com is the exemplar of how scalable WordPress can get.

Nope, none. I use the block editor (Gutenberg) and build custom react blocks.

It depends. If the service you want to integrate with has a good API with good documentation then probably. Send me an email or schedule a call to check.

If it’s well designed then yea of course. If the design needs more work, or is a bit rough around the edges then I can advise of this before starting the work. I can also supplement work designed, for example if you have an eCommerce web app that’s been designed, but is missing designs for things like password reset, emails, updating address details etc, then I can usually design these using the same designs. If you want more info, send me an email or schedule a call.

Send me an email or schedule a call and I’ll do what I can. I’m hard-working, passionate, professional, experienced and honest; but I’m not a miracle worker (just being honest). If deadlines are super tight I can only do what I can – but I will be completely honest with my timings upfront.

It depends. Sometimes it’s quicker and easier to start again, other times I can use some of what was built by someone else – it really depends how the developer/s built the project. If they were trying to use something like WPBakery or Divi then I’d start again because page builders like that are simply not good enough. If though they had a well structured src directory, and were making proper use of things like PHP classes and were building things in a modular way then I’d probably be able to use some of the code already written. Send me an email or schedule a call to talk through your project.

I started my career doing just that 10 years ago. If you need a simple brochure site that looks just like everything else on the internet and you want to spend as little money as possible, then I’d recommend buying a good quality theme from Themeforest or using a proprietary service like Squarespace, Wix or Webflow. But when you’re ready to create something custom that’s high quality, easy to maintain, doesn’t sap all your time and energy, is scalable, can be easily iterated upon, and offers an amazing experience for both editors and customers, I’ll be here.

It depends on the project. But if I do, I’m super careful about the ones I use. Most medium to large scale projects I build will consist of dozens of plugins, most of which will be custom plugins written by me specifically for the project. For example, a project I developed recently had a total of 40 plugins, 23 of which I built (learn more about the project here). The WordPress plugin architecture is a really elegant way to ensure a project is built in a modular way and is easy to maintain, provided of course it’s used responsibly.

I offer a ton of flexibility in how you request work. Some common ways clients request designs is directly via Trello, sharing Google docs or wireframes, or even recording a brief Loom/Vimeo video (for those who prefer not to write their briefs out). Basically, if it can be linked to or shared in Trello, or sent via email, it’s fair game.

That’s fine. You can pause your subscription when finished and return when you have additional WordPress design or development needs. There’s no need to let the remainder of your subscription go to waste.

You can pause your subscription right from your account – there’s no need to let me know beforehand – you literally just click a button. Pausing your subscription pauses all work. When you’re ready to continue, you can resume your subscription. Here’s an example scenario: you sign up for a monthly subscription and add a job to build a custom WordPress theme. The job takes 2 weeks. When your job is complete you pause your subscription for 3 weeks. You resume your subscription 3 weeks later and as you only used 2 weeks of your subscription before you paused it, you have 2 weeks left before your subscription renews.

It depends what you want. A well-designed landing page could be done in less than a week. A complex web-app could take months. I’ll always let you know how long I think it will take to complete a request before starting the work so you’ll know when to expect it.

No probs – we can iterate until you’re happy.

Due to the high quality nature of the work, there will be no refunds issued.