Support

The fastest path is email.

We answer within a few business days, usually same-day. Solo team — no ticket portal, no AI bot, just us reading your email.

What we answer fast

“I think this is a bug, can you reproduce?”
“Where in the source should I look for X?”
“How do I do Y with the bundled config?”
“The theme won’t build, here’s the error.”
“I have a Gumroad receipt question — order number XYZ123.”

What’s out of scope

We’re a theme shop, not an agency. We don’t do:

Custom development against your specific business logic.
One-on-one customization sessions or screen shares.
Deployment / hosting troubleshooting beyond pointing you at the relevant docs page.
“Can you tweak the design for me?” requests — we can’t, even for a fee.

For custom work, an Astro freelancer on Upwork or Contra is your best bet. Send them a link to the relevant docs page and they’ll spin up fast.

What makes a good bug report

The faster we can reproduce, the faster you have a fix.

A good bug report includes:

Which theme + version. Look at package.json — the version field, and the astro dep version.
Node version. Run node --version and paste the output.
The exact command that triggers the bug.
The full error output, not just the last line.
What you expected to happen instead.
(If a visual bug) a screenshot or a 5-second screen recording.

Example:

Theme: Aurora 1.2.0 (Astro 5.18.1) Node: v20.11.0 Command: npm run build Error:
Error: Cannot find module '/blog/index.mdx'
    at /node_modules/astro/dist/…
Expected: Build should complete. I haven’t edited the blog files since downloading. Screenshot: [attached]

Sending the full error block — not “build fails” — saves us a back-and-forth round.

Common things that look like bugs but aren’t

How we use feedback

When you email a question, you’re telling us what’s missing from these docs. If we answer “oh, that’s covered in [Customize → New sections]” we know that page wasn’t clear enough — and we improve it. Your boring “how do I…?” is genuinely helpful.

If you find a typo, an outdated screenshot, or a bad link in these docs, send it. Tiny issues are easy to fix and we appreciate the heads-up.

Where else to look

Before emailing, the most-overlooked sources:

The bundled README.md at the root of every theme. Quickest answers.
The bundled /sections/ route in your dev server — a live preview of every component.
Astro docs for anything Astro-specific (content collections, routing, the image service).
Tailwind v4 docs for utility classes.

If you’re past those and stuck — write to us. We’d rather hear from you than have you bounce.