# Blog posts in Marketing

A blog post tells your customers the fuller story behind an announcement made in
[Marketing](/user-guide/product/marketing). You choose what it's
about, Productmind writes the first draft in the background, and your team edits it together before
you approve it. A Marketing release can have any number of blog posts, each about something
different.

## To write a blog post

1. In **Marketing**, open the Marketing release and choose **+** beside **Blog posts** in its menu.
   Or choose **New blog post** on its overview.
2. Choose what the post is about. You can select:
   - **Features** among the Marketing release's sources: the features you attached, and those its
     releases, feature requests and feedback lead to. Each one shows how many customer requests are
     behind it, and **No specification** when it has no specification yet.
   - **Sections** of one of its published public release notes: when it has several, choose which
     first.
   - **Excerpts** of those published notes: highlight the text, then choose **Add excerpt**. An
     excerpt is 20 to 2,000 characters, within one section of the notes.

   Before any public release notes are published, you can choose only features, and the dialog says
   **Publish the release notes to write about passages of them.** A post can be about up to 10
   features and 12 passages, all from the same notes.
3. Optionally, choose a **Tone** and a **Length**, and enter an **Angle**.
4. Choose **Generate**.

The post appears in **Blog posts** as **Writing draft**. Productmind writes it in the background, so
you can open other pages meanwhile. When it's done, the post opens as a document with the draft in
it: a title, an introduction, then sections on the problem, how it works and what your customers can
now do.

## When a feature has no specification

A feature's specification is what Productmind writes most of the post from. When a feature you
chose has none, Productmind warns that its part of the post will be thin, and names the feature.
- Choose **Generate anyway** to write the post as it is. For that feature, the post says only what
  its delivered work and the public release notes support.
- Or choose **Cancel**, write the feature's specification in
  [Features](/user-guide/product/features), and start again.

Productmind checks again each time it drafts the post, so a feature whose specification is still
empty is warned about again.

## To draft a post again

1. Open the blog post.
2. Optionally, in the toolbar, change the **Tone**, **Length** or **Angle** (the last draft's, at
   first).
3. Choose **Regenerate**. Productmind asks **Write a new draft?**, or **Replace your edited
   draft?** when the post was edited since, and shows what it is written from and the guidance.
4. Choose **Generate**, or **Generate anyway** when it warns a feature has no specification.

## To change what a post is about

In the post's **Written from** tab, choose **Attach feature**, or point at a feature and choose its
**x**. Highlight text in the release notes and choose **Add as a passage**, or click a highlight
and choose **Remove passage**. Each change is saved at once; the text changes only when you choose
**Regenerate**. The last feature or passage can't be removed.

Productmind writes a new draft in the background and it replaces the post for everyone when it is
ready. Comments stay, but may no longer point at their text. The approved versions don't change.

## To stop a draft

While a draft of the post is being written, choose **Stop**.

Productmind stops waiting for the draft, and the post's text, if any, stays as it was.

## When Productmind can't write the post

**Writing the draft failed**, **Writing the draft took too long**, or **The draft came back
incomplete.** Nothing is saved: a draft that fails never changes the text a post already has. Choose
**Try again**.

When the first draft of a new post fails, the post keeps what you chose it to be about, and has no
text. Choose **Try again**, **Change scope** to choose again what it's about, or **Delete**. A post
whose first draft you stopped offers **Write the draft** instead of **Try again**.

## Editing a blog post

You edit, comment on and tag a blog post as you do the notes: see
[Editing the notes together](/user-guide/product/marketing#editing-the-notes-together). Your changes are saved as you type, and
everyone with the post open sees them as they are made. If the post was **Approved**, it now shows
**Approved, with changes**, and its last approved version stays as it was until you approve again.

A title over 150 characters is kept as you wrote it, but you must shorten it before you can approve
the post.

## Approving a blog post

**Before you approve**, in the rail, lists what approving checks, as you write:
- **Attached releases are out**, when a release is attached: every attached release shows
  **Released**;
- **Title**, with its length;
- **Sections**: at least one;
- **Customer quotes**, when the post quotes customers: you confirm them when you approve.

**Approve** is unavailable until every attached release shows **Released**, while a draft is being
written, while your latest edits are still saving, while the post has no title or no section, and
when the post is already its newest approved version. Point at it to see why. Until an attached
release is out, it names the release, such as **Can't approve until REL-4 shows Released.**, and you
can keep editing the post meanwhile. With no release attached, approving waits for nothing.

## To approve a blog post

1. Open the blog post, and choose **Approve**.
2. Review the post in the dialog. This is exactly the text the approved version keeps.
3. If the dialog lists names that may be your customers', check that the post doesn't identify
   them.
4. If the post quotes customers, confirm that the quotes identify no one.
5. Choose **Approve version** followed by its number, for example **Approve version 1**.

Productmind keeps the post as its next numbered version, and the post shows **Approved**. Nothing is
published: the approved version is the text your team agreed on.

## To delete a blog post

1. Open the blog post, and choose **Delete**.
2. Productmind asks you to confirm. Confirm to delete the post.

The post leaves **Blog posts**, with its drafts, comments, tags and approved versions.

:::caution
Deleting a blog post can't be undone, even when it has approved versions.
:::

## Troubleshooting

### I can't choose passages of the release notes

None of the Marketing release's public release notes is published yet: **Publish the release notes
to write about passages of them.** You can still write a blog post about the features of its
sources. An excerpt must be 20 to 2,000
characters, within one section of the notes: text that runs across two sections can't be added.

### The release notes were published again

Someone published a new version of the release notes after you chose your passages. Choose the
passages again, from the new version.

### Approve is missing

Your role doesn't include **Marketing: Create**.

### Approve is unavailable

Point at it to see why, or check **Before you approve** in the rail. The usual reasons:
- a release you attached isn't **Released** yet;
- your latest edits are still saving: wait a moment;
- the post has no title or no section, or the title is too long;
- a draft is being written: wait for it, or choose **Stop**;
- the post is already its newest approved version.

### Delete is missing on a blog post

Your role doesn't include **Marketing: Delete**.

## Related topics

- [Marketing](/user-guide/product/marketing)
- [Customer emails in Marketing](/user-guide/product/marketing-customer-emails)
- [Documentation links in Marketing](/user-guide/product/marketing-documentation-links)
