Writing a piece

What it does

"Write the blog" runs the whole pipeline: competitor research, link research, the brief, the draft, quality checks with up to two revisions, and images. It posts progress in the thread and a link to the piece's page when it's done.

Use it

1. "Write the blog [title]." Use the exact calendar title, or its date.
2. Open the piece's page from the link or the calendar. Every field (title, slug, meta, excerpt, body) is editable there.
3. Change one thing instead of redoing it:
   • "Rewrite the meta description of [title] to lead with cost savings."
   • "Revise [title]: add a manufacturing example to section 2."
   • "Regenerate the hero image of [title]: brighter, no text."
4. Need a Google Doc for the client? "Export [title] to a Google Doc."

Before you publish

Before publishing, check:

• the facts and figures (anything not on file should be marked for a source);
• the internal and external links open the right pages;
• the images;
• the CTA at the end.

Troubleshooting

• QA keeps failing on the same check. Some checks can't be fixed by rewriting (too few pages to link to, no author set). Nexus says what to fix outside the draft.
• The piece reads generic. Add documents to the knowledge base or answer Nexus's open questions about the client.

Prompts

• "Write the blog [title]."
• "Rewrite the meta description of [title] to lead with cost savings."
• "Revise [title]: add a manufacturing example to section 2."
• "Regenerate the hero image of [title]: brighter, no text."
• "Export [title] to a Google Doc."

Machine twins: /help/content-production.json · /help/content-production.md · /help.json · /llms.txt

Reviewed 2026-10-14. In Slack, ask Nexus how do I … and it answers from this guide, with where your company stands.