Editorial, website, and CMS publishing

Winglo can manage website content and send eligible published records to a connected CMS. These features depend on workspace entitlement.

Work with editorial records#

Open Marketing, then the Editorial or Website area. Supported views can include blog posts, documentation, case studies, changelog entries, media, and website settings.

Each record has its own lifecycle. A draft is not public. Review its title, slug, body, metadata, images, and status before publishing.

Configure the Winglo-hosted website#

Use Website → Settings for the site controls available to the workspace. Review navigation, brand, SEO, analytics, domains, and integrations where shown.

A saved setting and a published content record are different things. Preview the site after important changes.

Connect a CMS#

Open Website → Settings → Integrations. CMS connectors are available only when enabled for the workspace. Winglo supports these CMS choices in this panel:

• WordPress
• Webflow
• Ghost

Enter the site URL and credential requested by the form.

For WordPress, use your username, a colon, then a WordPress application password. Do not use your normal login password.

For Webflow, use a Site API token. You must also supply the CMS Collection ID that receives the content.

For Ghost, use an Admin API key from a custom integration. A Ghost Content API key will not work.

Store and share credentials through your approved secret manager.

Understand what is synchronized#

CMS connectors carry blog posts and documentation. Other Winglo editorial types are not CMS post types.

When synchronization succeeds:

• Publishing creates the external post, or updates the previously linked post.
• Updating published content updates the linked post.
• Archiving withdraws the linked post.
• Deleting removes or trashes the linked post according to the CMS behavior.

Do not create a second connector to repair one bad credential. Fix or replace the existing connection.

Publish safely#

1. Check the record is complete.
2. Confirm the correct site and connector.
3. Review the slug and public URL.
4. Check images, links, SEO text, and legal claims.
5. Publish or approve the guarded action.
6. Confirm the external result.

A Winglo publish state does not prove that the CMS accepted the delivery. Check the connector's last synchronization time and error.

Handle archive and delete#

Archive when content should stop being public but may still be needed as a record. Delete only when you intend to remove the Winglo record and trigger the connector's delete behavior.

External platforms can use trash or retention rules. Inspect the external CMS after a destructive action.

Fix a failed sync#

Confirm the site URL, credential type, permission, Webflow Collection ID, and target content type. Check whether the external post still exists. Correct the cause, then publish one controlled update and verify the external page.