Templates and page collections
A portable design needs meaningful content, safe markup, local media references and clear page destinations. It should be useful after it leaves the preview.
Read portable website guidanceDeveloper centreBuild with a clear contract.
Build with a clear contract.
Contribute when the doors open.
The ecosystem is being designed for documented, versioned extensions. The CMS source remains private, and third-party submissions and public listings are currently closed.
Submissions and third-party listings are closed.
There is no public package upload or automatic listing route. You can review the extension approach here while the first-party catalogue and review process are established.
The extension approachSmall responsibilities.
Small responsibilities.
Documented boundaries.
Connectors
A connector needs a versioned identity, compatibility requirements, permission declarations, a verified package and documentation for its exact setup.
Explore the connector modelUpdates
A release moves from review to staging and activation. Eligible installations discover it through a signed catalogue and prepare it before source changes.
Understand the update modelPackage identityKnow what it is.
Know what it is.
Know what it needs.
A useful connector manifest is a contract: the package identity, tested compatibility, declared capabilities and the location of its exact guide. A publisher signature is part of the trust model, not a substitute for review.
- Stable connector ID and version
- CMS and PHP compatibility requirements
- Declared permissions and provider destinations
- Documentation, release notes and safe removal behavior
{
"connector": "publisher.connector-name",
"version": "1.0.0",
"compatibility": "tested CMS versions",
"permissions": ["declared capabilities"],
"documentation": "exact setup guide",
"signature": "verified publisher envelope"
}
Conceptual fields; this is not an installation package or a promised final SDK schema.
Distribution policyA deliberate path
A deliberate path
from a package to a customer.
Author and document
Give the package one clear responsibility and explain what it requires.
Review and test
Check behavior, permissions, compatibility and rollback in isolation.
Sign and stage
Use a retained publisher identity and an explicit reviewed release.
Activate and maintain
Make the package discoverable, retain history and handle compatibility changes.
Is telaForge open source?
The CMS source remains private. Distribution through hosting services, portable websites and signed connectors is distinct from an open-source source-code licence.
Can I submit a template or connector now?
Third-party submissions and public listings are currently closed. There is no enabled upload form on this website.
Will a valid signature guarantee that a connector is safe?
No. A signature verifies origin and integrity. Review, compatibility checks, permission enforcement and tested behavior remain necessary.
Where will gateway setup documentation live?
Implemented payment connectors will link to a guide at docs.telaforge.com/payment-gateway. Guides will be written against the tested interface and use real, redacted screenshots.
A useful ecosystem starts
with useful boundaries.
Explore the current website platform and the connector direction while the developer programme takes shape.