Publish tested templates for teams and clients
Create an Agency publisher and release reusable source only after the exact commit passes a managed build.
Last updated 2026-08-18
What you'll achieve
- Create a template publisher
- Publish from tested source
- Share privately or publicly
Create a publisher and channel
Open Project settings → Source control → Agency template publishing. Create the publisher identity your clients will recognize. Then create a channel for one template family.
Choose Selected clients for work that must not appear in the public catalogue. A publisher must complete BlinkHost verification before a channel can be listed publicly. Do not publish client-owned source, personal data, credentials, licensed media or third-party code you cannot redistribute.
Publish a version
Connect the source repository and run a successful BlinkHost build for the exact commit. Select that build, enter a version and explain what the release helps teams build. BlinkHost refuses publication if the source is not trusted, the managed build failed or verified dependency evidence is missing.
Published versions are preserved as released. Make changes in source, build the new commit and publish a new version. Installing a template copies reviewed text source; it never copies the publisher's secrets, databases, assets or billing resources.
Help improve this page
Sign in to send page-specific feedback. For account-specific help, email support@blinkhost.me.