carousellisted

# Write a useful carousel Choose the reader, the problem and the decision the post helps them make. Write the argument before choosing images. The reader should get useful progress with each swipe. A consistent text layout is enough when the idea is clear. ## Framework The cover makes a specific, credible promise. Slide two starts paying it off with an example, consequence or useful distinction. Later slides explain the method, show evidence or address an objection. The final slide gives one relevant action. For a change story, establish the problem and its cost, introduce another approach, show the method and evidence, explain what improves, and lead to a decision. These are possible beats, not a mandatory seven-slide formula. Combine or cut beats that do not help. A comparison should apply both choices to the same task and end with a usable decision rule. A playbook should leave a method the reader can repeat. Use supplied or verified results only. Label hypothetical examples. A reference creator's reach claims do not establish what caused that reach. Offer a download or course only when the user has it and wants to promote it. ## Four layouts | Editor name | JSON layout | Job | |---|---|---| | Cover | `cover` | A clear headline and one short subtitle in `body` | | Body 1 | `content` | A bold lead in `title` followed by short paragraphs in `body` | | Body 2 | `note` | One statement or a visual example; `title` only | | CTA | `closing` | One next action in `title` and