---
title: "Write a derivative post from a group of docs pages"
description: "How to write a derivative blog post from a group of Truth vault pages by picking one customer problem, scripting it and checking it yourself."
type: "Trust post"
docType: "Tutorial"
from: "content-system/distribution/introduction"
tags: ["Content distribution"]
entity: "Write a derivative post"
---

> Documentation Index
> Fetch the complete documentation index at: https://cuongthach.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Write a derivative post from a group of docs pages

When you finish, you can write a piece of [derivative content](/docs/content-system/distribution/concepts/derivative-content) from a group of docs pages: a post that solves one problem for one specific customer, told through your own stories, with every fact matching the vault. Once it is done, it moves on to [publishing the blog post](/docs/content-system/distribution/guides/how-to/publish-a-blog-post).

## What you need before writing

- **A group of docs pages that solve one problem together.** A blog post usually stands on 2 to 4 pages, not one. A page that is only for looking things up comes along as support for another page, and once you have many of them, they give posts of their own.
- **Pages with enough facts.** You have done what the page teaches yourself, and the page has the pictures, videos and traces of that work. If you cannot do it yet, do not teach it: go and do it, then fill in the missing page as soon as you can, before you write the post.
- **Your own stories.** A docs page holds only facts and steps, not the journey. The stories live in the idea vault (the ideas pulled out of your recordings), or you record once more.
- **A place to think through the script.** A note-taking app with recording, such as Tana, lets you plan the script and record extra material in one place.

## One group of pages, one post

![One group of pages, one post](/docs/_astro/illus-docs-nhom-trang-thanh-bai.en.BOrVMBm5_ZTKTiY.svg "Each new grouping of pages is a new post")

**A derivative post stands on a group of pages, not on one page.** You do not try to pull 4 or 5 blog posts out of one docs page. You write many docs pages, then combine them: each different grouping, each comparison between two pages, is a new post.

So the number of posts follows the number of pages in the vault:

| The vault has | Posts you can get |
| --- | --- |
| 3 pages: one overview, 2 how-to guides | Very few, not enough for a publishing plan |
| 10 pages | About 2 or 3 posts |
| 60 to 70 pages | About 30 posts, enough for a month |
| A vault large enough and kept up to date | Almost endless, because the pages combine from many angles |

The vault takes the most work at the start, when it has few pages. Aiming for 30 posts a month with only a few pages is the wrong strategy from day one. Once the vault has 70 or 80 pages, every new post inherits ready-made material, so it comes out faster and lighter.

A second post on the same subject **solves a different problem**, so it stands on a different group of pages. For example, the first post uses 4 pages and the next one shares only 2 of them, swapping the other 2.

## 3 Steps to a derivative post

The three steps go from the vault to a draft: you decide what the post says, you add what the vault does not have, then AI arranges it and you check it.

:::caution[Do not tell AI to write the whole post]
A prompt like "Here are 4 docs pages, write me a blog post" gives a post that looks like the docs page and has no script, so readers feel nothing. Forcing AI to write about something the vault does not have, or pushing its creativity too high, makes it invent content, even product features you do not have.
:::

1. **Pick one customer problem**

   One post solves one customer problem. Read the pages you wrote closely, back and forth, and ask what problem this group of pages solves for your customer. Then settle the [core message](/docs/content-system/idea-write-edit/concepts/core-message): who the customer is, their pain, whether the solution is reasonable, and the result it promises.

   Your first post comes from the **overview page** of one part of the vault. The overview page is the [Love post](/docs/content-system/know-trust-love/concepts/love-post) of the Truth vault: it has what it is, why, how it works, its parts and its strategy, so it turns easily into the Love post of the blog. You end up with a one-line core message and the list of pages the post will stand on.
2. **Build the script and tell your story**

   The content script (the outline) is what makes the post worth reading, and only you can write it: AI does not know your stories, your customers or their pain. Build the script around the customer's situation and what they really care about, with conflict and a clear lead, like a piece of writing rather than a textbook.

   Look at the script for places that lack a story, then record or write the missing parts: the journey to the facts on the page, the failures, the wins, what you struggled with. You end up with a complete script drawn from two sources: the docs and the idea vault.
3. **Let AI arrange it, then check**

   AI only arranges what you have said, following your script: it groups ideas, cuts the excess and fixes spelling. For example, 10,000 words of recording are cut down to about 2,500 words, then AI checks them against the vault and adds the links to its pages. The post draws only on the docs, your stories and the idea vault, never on the internet.

   Read the draft against the vault, because **you are the final reviewer and the one responsible in the end**. Link to docs pages naturally: link the pages the post mentions, and leave the rest. You end up with a draft ready for the Edit step.

## Signs the post is right

![Signs the post is right](/docs/_astro/illus-docs-thuoc-do-bai.en.P4rb3niV_ZTKTiY.svg "A good post is much longer than its source page")

A good post is much longer than its source pages. A docs page averages 800 words or more. Once you add the core message, the customer's situation and what only you have, 800 words growing into 2,000 to 3,500 is normal.

- **The post has one problem, one customer and one core message.** The docs page speaks in general terms, while the post speaks about one specific case.
- **Every number matches the vault.** If the page says 30% off, the post says 30% too.
- **The post has your story**, with pictures of what you did.

Wrong signs and how to fix them:

| Sign | Cause | Fix |
| --- | --- | --- |
| The post reads like the docs page and is boring | No core message and no story | Name the customer's real pain and add your journey |
| The post says 50%, the page says 30% | You did not check when reviewing | Fix the post from the vault, the vault is the correct version |
| The post has gaps and sends you back to fix the vault | The post did not start from the overview page | Build the post on the overview page and the pages that explain it |

:::note[Example]
The first Love post the cuongthach.com blog wrote from the vault took a few separate parts, definitions and strategies, not the overview page, as its base. The post had gaps, and the Truth vault had to be updated until it was complete.
:::

## Related pages

- It does not fix old posts when the vault changes: see [When your product changes](/docs/content-system/truth-vault/guides/how-to/update-the-vault-first).
- It does not turn the blog post into emails or social posts: see [Repurposed content](/docs/content-system/distribution/concepts/repurposed-content).
- It does not send the post to subscribers: see [Send a newsletter](/docs/content-system/distribution/guides/how-to/send-a-newsletter).

Source: https://cuongthach.com/docs/content-system/distribution/guides/tutorials/write-a-derivative-post/index.mdx