Say hi

Good reasons to write

• A question about a post. If something in a Build Journal post or a framework page didn’t make sense, or you want more detail on how a fix worked, ask.
• A correction. If a number, link or claim on this site is wrong, tell me. I correct the post rather than leave a mistake in place. Point me to the line and, if you can, the source that shows the right figure.
• A broken link or page. If something here doesn’t load, or a link goes nowhere, send me the address and what you clicked.
• A product question. Not sure which framework fits your project, or want to know when one becomes available? Mention the product by name.
• Something you built. If a post helped you fix or plan a site of your own, I’d like to hear what happened.

Before you write

A few things that help me give you a useful answer: link the post or page you’re asking about, include the numbers you’re seeing if it’s about your own site, and say what you’ve already tried. If your question is about one of my sites rather than a GardySpace post, the projects page links to each one and shows where it stands today, which often answers it before you need to ask.

What happens next

Your message comes straight to my inbox at contact@gardyspace.com. It isn’t posted anywhere or stored on this site, and I reply from that same address. The privacy policy has the details.

Client work and consulting

GardySpace is the journal. Client builds and consulting go through ignepublishing.com, which is set up for project inquiries.

Prefer not to write?

You can get new Build Journal posts by email instead, or start with the Start Here page.