Destinations

A managed website keeps its own design while BrandKind supplies the saved article, selected image and author snapshot. Open a library piece, choose Send, select the assigned website, then choose Publish blog.

• Images follow your layout choice. Hero, inline, feature-left, feature-right and full-bleed are translated into the website's responsive native layout. Decorative images keep empty alt text; other selected images need reviewed alt text before publishing.
• Authors are snapshotted. A selected author can publish their name, role, biography and portrait. Without one, BrandKind uses the original creator name.
• Saving is not publishing. Later edits stay private until you confirm an update. Unpublishing stops the public article and its managed media from being served.

BrandKind works with a WordPress site on your own hosting and with WordPress.com on any paid plan. WordPress.com Free is not supported. The WordPress account you connect needs Author access or higher.

1. Add a destination.

   Open Settings → Destinations, choose WordPress, then give the connection a name and enter the public address of your site.

2. Approve BrandKind in WordPress.

   Choose Connect to WordPress. Your browser opens your own WordPress admin, where you approve the connection. BrandKind stores the generated credential securely and tests the connection when you return.

3. Use the manual fallback when needed.

   Older or unusual sites may not offer the approval screen. Choose Enter an Application Password instead, then enter your WordPress username and a password created under Users → Profile → Application Passwords. Do not enter your normal WordPress account password.

4. Test, fix and try again.

   A failed test does not discard the destination. BrandKind keeps it and tells you what is wrong; after you or your web host makes the change, choose Test again.

The first message is written for you. When a host or site administrator needs to make the change, open Send this to your web host and copy the technical note to them. It contains the exact server setting without exposing your Application Password.

• App passwords are switched off. Wordfence commonly controls this with one setting. Send the supplied technical note to whoever maintains the site.
• The username or Application Password was not accepted. Generate a new Application Password under Users → Profile and copy it in full.
• The account cannot create posts. Ask a site administrator to give the account Author access or higher, or connect a different account.
• WordPress.com Free. Activate or upgrade to any paid plan, then test the destination again.

Headings, lists and paragraphs arrive as editable Gutenberg blocks. A selected image is uploaded and attached as the featured image when WordPress accepts it.

A webhook sends signed event data to an endpoint your team controls. Someone technical needs to provide the public endpoint and decide how it authenticates. Give them the Delivery API page for the full payload, retry and signing contract.

1. Name the endpoint.

   Use a name people will recognise later, such as “Main website workflow”.

2. Enter its public address.

   Private network addresses and unusual ports are refused before anything is sent.

3. Choose events, content format and authentication.

   Choose json unless the receiver specifically needs HTML or Markdown. Bearer and custom-header credentials are stored write-only.

4. Create, test and activate it.

   A new webhook starts paused until it has a signing secret. Test it, then switch it on when the receiver is ready.

Use Send to… in the editor and choose an active destination. Sending is manual unless a content job is set to deliver automatically. Sending requires a member role or higher.

Webhook failures retry automatically on a widening schedule. The exact timings are in the Delivery API retry guide.

Pausing keeps the settings but stops new sends. Use it during a site migration or outage. Deleting removes the destination and its delivery history and cannot be undone.