Release announcements

Write the release note once; the page and the post follow from it.

The reason a product's social channel goes quiet is rarely that there is nothing to say — it is that saying it is a second job. Every release already produces the words, so when a changelog entry goes public CoreX turns it into:

  • a content brief, holding the release title and body, ready to become a public page;
  • a social post, drafted with the release headline and a tracked link to your listing.

Rules it follows

  • Once. The announcement fires on the transition to published, not on every edit. Fixing a typo afterwards does not announce the release a second time.
  • Drafts, never sends. The post lands as a draft and the brief as an idea. Nothing is published on your behalf; an automated announcement that publishes itself is how a workspace discovers it has been posting without being asked.
  • Optional at both ends. No Content app, no brief. No Social app or no connected channel, no post. Either one being off never costs you the other, and neither can stop the release itself.
  • Tracked. The link in the post is minted as a tracked link when the growth engine is on, so the clicks it earns show up in attribution under Social rather than in Direct.

Where they land

Briefs appear under Content → Briefs; posts appear as drafts in Social. Edit either before publishing — the draft is a starting point written from your own release note, not a finished piece.