DocsGuides
PublishedGuides

Content Engine

Research with Live Data, draft with Recipes, repurpose with Plan Mode, and publish from Canvas — a repeatable content workflow without legacy Pipelines.

Goal: A repeatable research → draft → repurpose → review loop — not one-off Chat threads you lose on Monday.

The Four Layers

LayerSpringbase toolJob
ResearchContext + Live DataStay current on topics and competitors
DraftRecipesRepeatable outlines, posts, newsletters
RepurposePlan ModeBlog → LinkedIn → email from one goal
PublishCanvas artifactsEdit, export PDF/Word, share links

Note: Classic Pipelines are deprecated (sunset July 2026). Use Plan Mode for multi-step content workflows.

Layer 1 — Research Context

Create a Research Context

Examples: Competitor Intel, Industry News, Product Launch Research.

Add sources:

SourceType
Competitor blog RSSLive Source
Competitor docs sitemapLive Source
Your brand guidelines PDFStatic upload
Voice and tone docStatic upload

Live Data requires Pro/Max. See Live Sources.

Weekly research Recipe

Variables: week_ending, focus_competitors (multiselect)

Using @Competitor-Intel, summarize the most important changes this week
for {{focus_competitors}}. Format: bullet list with source citations,
"So what for our messaging", and 2 content angles we could publish.

Schedule it every Monday 9am from Automations.

Layer 2 — Draft Recipes

Build Recipes per content type:

Blog outline

Variables: topic, audience, word_count, seo_keywords
Output: H2/H3 outline + intro hook options

Long-form draft

Variables: outline (textarea), tone, audience
Attach: Brand voice Context
Output: full draft in markdown

Social snippet

Variables: source_url_or_text, platform (LinkedIn / X / Threads)
Output: 3 variant posts under character limits

Test each Recipe with messy real inputs before sharing with the team.

Layer 3 — Repurpose With Plan Mode

For one asset → many channels, use Plan Mode in Chat (Pro/Max):

Example goal:

Turn our Q1 product launch blog post into: (1) a LinkedIn post,
(2) a customer email teaser, (3) five slide titles for a deck.
Use @Product-Launch-Context for facts. Flag anything not verified in sources.

Plan Mode generates editable steps — research, draft, creative variants, optional image step. Remove steps you do not need before Execute.

Common Plan shapes from product docs:

  • Research → deep analysis → creative copy → image hero
  • Extract quotes → write thread → suggest hashtags
  • Compare sources → synthesis memo → executive summary

Layer 4 — Publish With Canvas

When a draft is ready:

  1. Ask for output in markdown or open in Canvas.
  2. Edit in the rich markdown editor or export PDF / Word.
  3. For landing pages or interactive content, use HTML artifacts in Canvas.
  4. Share published artifacts as unlisted links for stakeholder review.

See Artifacts & Canvas.

Operating Cadence

CadenceWorkflow
DailyScan Research Context in Chat for breaking news
WeeklyRun research Recipe; team standup on content angles
Per assetOutline Recipe → draft Recipe → Plan repurpose → Canvas review
MonthlyPrune Live Sources; refresh brand Context uploads

Quality Checklist

Before publishing externally:

  • Claims cite Context or Live Source material
  • Tone matches brand voice doc
  • No placeholder {{variables}} left in output
  • Human reviewed numbers, dates, and product names
  • Image steps (if any) match brand guidelines

Optional Agent Steps

If Notion, Google Docs, or Slack are connected:

  • Agent: "Create a Notion page draft from this markdown"
  • Agent: "Post 'Draft ready for review' to #content with link"

Keep humans in the loop for external publish actions.

Example: Weekly Newsletter

  1. Monday: scheduled research Recipe → bullets in Chat
  2. Tuesday: Plan Mode — "Build newsletter from research + @Company-Updates"
  3. Wednesday: edit in Canvas markdown; export to email tool
  4. Thursday: Plan Mode — repurpose top story to LinkedIn + blog teaser
  5. Friday: archive final version upload to Newsletter Archive Context

Related docs

© 2026 Springbase. Docs are managed by the Springbase CMS.