WordPress development for a site your staff can edit

What we do on a WordPress site

Work starts in the WordPress admin, then in the theme and plugins. New sites get the post types you publish, an editable theme, and a short plugin list.

Themes are classic PHP templates or block themes: theme.json, HTML templates, and patterns. Post types, taxonomies, and fields live in a plugin so a theme change keeps them. New work uses the block editor. Fixes on a classic editor stay there.

WordPress plugin development is for your own logic: a directory, a form, a members area, a sync to another system, or a block editors can place. A plugin that already fits gets configured.

Jobs that show up in the inbox

Hosting, DNS, and staging sit in accounts you own, before the site is public. Editors can change copy and cannot install plugins.

Custom WordPress theme work, or a deep edit of a theme you already have, covers page, post, archive, and search. A child theme holds your edits so a commercial theme can still be updated. We will not install a paid theme or plugin from a forum zip.

Gutenberg blocks repeat a layout cleanly: a staff list, a spec table, a notice, a landing pattern. Static blocks store HTML. Dynamic blocks render in PHP from live posts.

WordPress fixes include other people's sites: fatal errors after updates, forms that never mail, WP-Cron that never runs, and Elementor, Divi, or WPBakery overwriting a parent theme. We read the theme and plugins before we propose a rebuild.

Host moves use WP-CLI so serialized PHP survives URL changes. Squarespace, Wix, Webflow, and older WordPress moves include redirects and a gap list. Cart and checkout are a WooCommerce scope. We implement technical accessibility and do not certify compliance.

From the first email to handoff

Send the URL, the problem or the launch goal, and a date tied to a real event.

Reproducible bugs are estimated hourly. Themes, plugins, and migrations are fixed quotes after scoping. A brief that only asks for a better site starts as paid discovery, and you keep the writeup.

You keep the host, the domain, and the owner user. Our access is an administrator you can remove, shared by invite or a password manager. The repository is yours. We build on staging and ship after review, and we do not edit PHP in the dashboard theme editor. You leave with a note on the blocks and plugins that matter, written by the person who built them. Only a few projects run at once.

Themes, blocks, and WordPress speed

Tools are the admin, the block editor, theme.json, PHP, MySQL or MariaDB, WP-CLI, and Git. A Gutenberg block is a block.json file, an editor script, and PHP when it renders from live data. Advanced Custom Fields stays only if the site already uses it.

WordPress speed work reads the site before another cache plugin. We look for assets on every URL, oversized images, site-wide fonts, heavy autoloaded options, and queries that load every post to show five. The cause comes out first. Old PHP or missing staging puts the host in scope.

Next.js, React, and TypeScript on the REST API are there when a separate front end is actually needed. A site your staff edit all week should stay a theme, so a headline does not wait on a deploy.

Who should email

It suits owners, marketers, and agency leads in Canada or the United States who want a WordPress developer and can describe the job, and teams that already have a developer and want one piece beside them.

If the brief is still open, paid discovery can turn it into a defined feature list and acceptance checks. If you already have a developer or agency, we can take a bounded part of the work and agree how it joins the wider project. Share the target date so we can assess capacity and dependencies before committing.

hehe.software is based in Vancouver, British Columbia, and works remotely with businesses across Canada and the United States.

What we can show, and what to send

This website is our hand-built static site, and our App Store apps are also owned products. A WordPress project is assessed through its own implementation: a theme preview, editor workflow, plugin behaviour and staging checks. We document where custom code lives and how the site is updated, so the handoff is useful to the next developer as well as the owner.

Send the URL, theme name, host, plugin list, logo and type files, and who approves copy. Say whether editing is blocks, classic, or a builder. Migrations need the old URLs that must keep working. Administrator access can wait until both sides agree to look.