01 / CONTACT GENERAL ENQUIRIES / QUESTIONS / CONNECTIONS

GET IN TOUCH

Have a question? Send me a message.

Use this page for general enquiries, questions, collaboration ideas, technical conversations, or anything that does not require a full project brief.

QUESTION / CONVERSATION / PROJECT PG — C01

02 / CONTACT ROUTES

Choose the route that matches your message.

General questions, new projects, existing work, and theme-related enquiries need different levels of context. Choose the closest route and continue from there.

01 GENERAL

General Enquiry

Use this for questions, conversations, collaboration ideas, technical discussions, or anything that does not yet require a structured project brief.

GOOD FOR Questions / Collaboration / Conversation
Contact Me
03 EXISTING WORK

Existing Project or Support

If we are already working together, include the project name, website or system, the current issue, and any relevant context so the request can be understood quickly.

GOOD FOR Support / Maintenance / Existing Work
Send Support Context
04 THEMES

WordPress Theme Question

Use this route for questions about one of my themes, installation, compatibility, documentation, customization, or theme-related feedback.

GOOD FOR Themes / Documentation / Feedback
View Themes
NOT SURE WHICH ROUTE?

Use the general contact option. I can route the conversation from there.

03 / DIRECT CONTACT

Send a simple message.

For general questions, collaboration, theme enquiries, or existing work, a short message is enough. For a new commercial project, use the structured project intake instead.

NEW MESSAGE GENERAL ENQUIRY
GENERAL CONTACT
QUESTION CONTEXT CONVERSATION

04 / BEFORE YOU CONTACT

A little context makes the conversation much more useful.

You do not need to write a long message. A clear description, the relevant link, and the actual question are usually enough for a general enquiry.

01 CONTEXT

Tell me what this is about

Mention the website, theme, project, technical topic, or business context so the message can be understood without guessing what you are referring to.

02 LINKS

Include the relevant URL

If the question relates to a page, website, theme, product, performance report, or public resource, include the relevant link when possible.

03 TECHNICAL

Share the actual error or behavior

For technical questions, explain what you expected, what actually happened, and include relevant error messages or screenshots where they help describe the problem.

04 SECURITY

Do not send credentials

Do not include passwords, private API keys, database credentials, server login details, authentication tokens, or other sensitive access information in the initial message.

05 PROJECTS

Use the project brief for commercial work

If you need WordPress development, WooCommerce, Selldone, speed optimization, maintenance, or a custom web system, the project intake page provides the context needed for a proper review.

Open Project Intake
06 SIMPLE

Keep general enquiries simple

You do not need a formal proposal or specification just to ask a question. A short message with enough context is usually the best starting point.

SIMPLE MESSAGE MODEL
WHO / WHAT CONTEXT QUESTION RELEVANT LINK
05 / PROJECT ENQUIRIES WORDPRESS / COMMERCE / SYSTEMS

NEED SOMETHING BUILT?

Have an actual project requirement?

If you need a website, WooCommerce store, Selldone implementation, WordPress performance work, maintenance, or a custom web system, use the project intake instead of the general contact form.

RECOMMENDED ROUTE Structured Project Intake

Tell me what you need, what already exists, and what outcome you are trying to achieve.

Start a Project
WORDPRESS DEVELOPMENT WOOCOMMERCE SELLDONE SPEED OPTIMIZATION MAINTENANCE CUSTOM SYSTEMS