Support
Questions before or after you buy.
One person answers these, so a specific message gets a specific answer faster.
Email the studio
No contact form, no ticket queue. Email is the fastest route and it keeps a record you can reply to.
info@lambdastudio.ioInclude this in your message
- Template name and version (both are in your README).
- Order email or receipt number, for purchase questions.
- Node and package-manager versions, plus the exact error output.
- A repository link or a minimal reproduction, if the issue is in your own edits.
What support covers
- Installing and running the template as delivered.
- Bugs in the template itself, including build and deploy failures.
- Questions about the content model, tokens and included components.
- Re-sending your download link.
What it does not cover
- Custom design or development work on your project.
- Third-party services, CMS integrations or hosting configuration.
- Debugging code you wrote on top of the template.
Where the documentation lives
Every template ships with a README covering setup, content structure, tokens and deployment. There is no separate documentation site — the docs travel with the version you bought.
FAQ
Support questions.
Inside the template you bought: the README covers setup, the content model, tokens and deployment for that exact version.
Email support from the address you used at checkout and the download link gets re-sent. Lemon Squeezy receipts also contain the original link.
Releases are versioned. Each product page lists the current version, the date and a short changelog. Your download link points at the latest build.
Template name and version, your order email, Node and package-manager versions, and the exact error output. A minimal reproduction speeds things up considerably.
Not as part of support. If you need design or development work on top of a template, say what you have in mind and you will get an honest yes or no.
Installing and running the template as delivered, and bugs in the template itself. Not covered: third-party services, hosting configuration, or code you wrote on top.