Support

Help Center

Help from the team behind the product you're using.

Find your way in

  • Read the docs

    Installation, options, and the design system behind each template.

    Documentation
  • Quick answers

    The questions that come up most often, answered once.

    FAQ
  • Something broken?

    Bug reports go to the channel for your product, below.

    Report a bug
  • Pre-sale question

    Licensing, browser support, whether a template fits your project.

    Ask us

What support covers

What support covers Paid (active licence) Free products
Bug fixes in the template itself Yes — prioritised Best effort, via GitHub Issues
Help using documented features and options Yes Docs and README only
Guidance with included assets (fonts, demo setup) Yes Not included
Access to updates Lifetime, per licence Public releases on GitHub
Customisation or new features on request Not included Not included
Third-party services (hosting, form providers, CMS) Docs guides only Not included
General web development teaching Not included Not included
Guaranteed response time 2 business days No SLA — genuinely best effort

Before you write

The more of these you include, the faster your fix — each one saves a round trip.

  1. Product and version The footer of your documentation copy has both.
  2. Browser and operating system
  3. A URL, or a reduced test case Somewhere we can see it happening.
  4. Steps to reproduce
  5. A screenshot, or the console error

Where to write

Running the latest version? Your issue may already be fixed — check the changelog.

Paid product support

Email support

For templates you bought — free releases are supported on GitHub. Have your licence key or purchase code ready: it is required with every request.

Email support

Free products

GitHub Issues

Each free release has its own repository on GitHub — open an issue there. Keeping issues public means answers help the next person too.

GitHub

Paid support replies within 2 business days, usually faster. (Mon–Fri, EET)

We don't offer custom work, so our time goes into updates and new products. Developers can build on the products using the documentation.