Publishing integrations
Publish where your blog already lives.
Choose the publishing route that fits your site. Native CMS connections deliver articles; custom-domain hosting and the read-only content API support other setups. These are different delivery methods, not interchangeable promises.
WordPress
Connect with an Application Password and choose draft or live publishing. Re-publishing an already linked article updates its existing post rather than intentionally creating another copy.
Webflow
Map a CMS collection and its article fields. Staged and live publishing are distinct; your site still needs a Collection Page template to display the article.
Shopify
Choose a store blog and configure the required API permissions. Publish blog articles as hidden or live content; this does not mean automatic product or collection-page editing.
Custom domains and headless websites
Essel can host articles on a connected custom domain. Developers can also fetch released articles and metadata through the content API and render them in their own site. The documented API is read-only; it is not a promise to push to arbitrary REST endpoints.
One automatic destination per workspace
Choose one active publishing destination, then enable automatic publishing for it. Article release, CMS draft/live state, and search indexing remain separate steps. Check the connector's requirements before assuming every platform supports identical formatting or media behavior.