How to produce content in Continu that actually gets used — for partner enablement, customer education, channel training, franchise operations, and employee development. The discipline of going from blank page to published asset without burning out the SME.
Why Content Authoring Is Different From Content Strategy
Strategy decides what content should exist and why. Authoring is the work of actually producing it.
Most programs underinvest in authoring discipline. The result is the same in every organization: a content library that's part well-crafted modules from a hero author, part hastily-recorded videos from someone who left two years ago, part SME-produced documents nobody can find, and part draft articles that have been "almost ready to publish" for fourteen months.
The content library that scales is built on an authoring practice that scales. Not heroics. Not blank-page-on-Monday and shipped-by-Friday. A repeatable workflow that takes a topic from raw source material through structured drafts, review, accessibility checks, and publication — and does it the same way the next time, and the time after that.
This guide is about that workflow — what each step does, how to set up the people and tools, and what the difference is between content that gets used and content that doesn't.
What "Published Asset" Actually Is
Strip away the medium and a published asset in Continu is a piece of content that does three things.
Teaches a specific thing. The asset has a defined job — explain a concept, demonstrate a workflow, walk through a decision, verify retention. Generic "good to know" content rarely earns engagement. Specific, job-focused content does.
Sits in the right object. Continu has multiple content types: articles, videos, files, embedded content, and others. The medium should match the job. A workflow demonstration belongs in video; a reference table belongs in an article; a downloadable template belongs as a file. Mismatched medium kills engagement.
Lives where the audience will find it. Authored in isolation, content is invisible. Placed in the right track, journey, or assignment — and surfaced by Eddy and search — it gets used.
The job of authoring is to produce assets that hit all three of those criteria. Anything else is draft.
The strategic question: for each piece of content you're authoring, what's the job, what's the right medium, and where will the audience find it?
The Authoring Workflow
A repeatable authoring workflow has five stages. Skipping stages produces brittle content; fully executing them produces a library that scales.
1. Brief. Define the job before you write. What capability is this asset building? Who is the audience? What's the medium? How long should it be? What does success look like? A one-page brief takes 15 minutes and saves hours of rework later.
2. Draft. Produce a first version. Whether the SME drafts it directly, an instructional designer drafts from SME interviews, or AI-assisted authoring produces a first cut from prompts, the draft is the raw material. It is not the finished asset.
3. Review. SME validates accuracy. Instructional designer checks structure and audience fit. Compliance or legal reviews where required. Multiple eyes catch what the author cannot.
4. Polish. Apply the format the medium needs — headers and structure in articles, captions and chapters in videos, alt-text on images, accessible markup throughout. This is where the asset moves from "first draft" to "published-quality."
5. Publish and place. Move the asset into the right object, link it from the right tracks and journeys, and confirm it surfaces in search and recommendations the way you intended.
The discipline is in not skipping stages. The hero authoring of jumping from brief to publish in one afternoon produces content that needs to be redone in six months.
Content Types in Continu
Each content type has a job. The job determines the medium, not the reverse.
Articles. Best for reference content, conceptual explanation, structured walkthroughs that benefit from headings and search. Good for content that gets updated — text is easier to edit than re-recording a video.
Videos. Best for demonstrating workflows, showing physical or visual processes, conveying tone and presence, and content where the SME's expertise is the asset (an executive talking about strategy, a customer success leader walking through a real account scenario). Hard to update once produced; design with that in mind.
Files. Best for downloadable templates, reference documents, slide decks the audience will use in their own work, datasheets, one-pagers. Files are durable — they leave the platform with the learner.
Embedded content. Best for content that lives elsewhere — Loom videos, external articles, vendor documentation — that should be surfaced in the context of a learning program but not duplicated into Continu.
Surveys. Best for gathering input, capturing reactions, calibrating sentiment. Not for verification (assessments do that job).
The most common authoring mistake is medium-by-default: defaulting to video because it feels comprehensive, or defaulting to articles because they're cheap to produce. The medium should be chosen for the job, not for the author's habit.
Best Practices
Brief before you author. A 15-minute brief on audience, job, medium, length, and success criteria. SMEs especially benefit from a brief — it gives them constraints, which makes their job easier, not harder.
Match content length to the audience's attention budget. A partner mid-sales-motion has 90 seconds for a video. A customer admin in onboarding has 5 minutes. A new hire in compliance training has 20. The same topic produces different assets at different lengths. Don't ship a 25-minute video to someone with a 90-second window.
Structure articles for scanning, not just reading. Headings, subheadings, short paragraphs, bolded keywords. Most readers scan before they commit to reading. An article that doesn't reward scanning loses the reader on the first scroll.
Write the headline last. The first time you draft an asset, you don't yet know what it's really about. Write the body, then come back and write the headline that promises what the body actually delivers.
Use AI-assisted authoring as a draft starter. Continu's AI authoring assist can produce a first version of an article, quiz, or summary. Use it to escape the blank page. Then put a human SME between the draft and publication — the AI doesn't know your product, your customers, or your compliance posture.
Caption videos and add transcripts. Accessibility, retention, and AI readability all benefit. Eddy reads transcripts; learners with English as a second language read captions; learners in noisy environments read both. The cost is real (production overhead); the benefit is durable.
Design content for update, not for permanence. Product changes. Regulation changes. Strategy changes. Author every asset as if you'll need to revise it within 18 months. Articles are easier to revise than videos; short videos are easier to revise than long ones; modular content is easier than monolithic content.
Standardize structure within content families. All Workshop pre-reads have the same shape. All product overviews follow the same template. All compliance modules follow the same structure. Learners pattern-match across content; consistency reduces the cognitive load.
Run a review with the right reviewers. SME for accuracy. Instructional designer or content lead for structure. Compliance or legal for regulated content. Native speaker for translations. The right reviewer for the right risk; not one person reviewing everything for everything.
Track what's stale. Build a review cadence into the program. Every six months, the program owner pulls a list of content older than a year and decides what to refresh, archive, or retire. Stale content is worse than no content because it confidently misleads.
Anti-Patterns
Blank-page-on-Monday. Asking an SME to "write the article on X" with no brief, no template, and no structure. The SME writes a wall of text. The instructional designer rewrites it. The SME complains they were asked to do work that got changed anyway. Brief first.
Hero authoring. One person who writes most of the library, holds the institutional knowledge, and leaves. The library degrades over the following year because no one else knows how to maintain it. Distribute authoring; build the template; document the workflow.
Video by default. Recording a 20-minute video where a 4-paragraph article would do. Production is expensive, updates are painful, and the video is harder to find later. Reach for the medium that fits the job.
The single hour-long video. A monolithic asset that learners can't scan, can't navigate, can't update. Break long video into chapters or — better — into a sequence of shorter videos. The aggregate runtime can be the same; the usability is different.
The wall-of-text article. No headings, no structure, no scanning affordances. The learner sees a wall and bounces. Even a 300-word article needs a heading. A 2,000-word article needs four or five.
Publishing the draft. Skipping review because the deadline is tight. The asset goes out with the wrong fact, the wrong tone, or the wrong audience framing. The review window catches the error; the deadline isn't worth more than the review.
Forever drafts. Articles in "almost ready" state for nine months. Either they get to publish-ready, or they get archived. Forever drafts clog the workflow and demoralize the authoring team.
AI-published as AI-drafted. Using AI authoring assist to produce a draft and shipping it without human review. The draft looks polished; the content is subtly wrong about your product. Partners and customers notice.
Accessibility added later. Producing the asset, publishing it, then adding alt-text and transcripts months later when an audit catches the gap. Accessibility is part of authoring, not a post-launch task.
Title-by-keyword-stuffing. Naming the article "How to Configure SSO for Partners Using Single Sign-On Setup Guide" because someone said long titles help search. Long titles confuse readers and rarely help search anyway. Name the asset what a learner would call it.
Authoring without strategy. Producing assets because someone asked for one, without checking whether the asset fits the broader program. A content library should look like a designed system, not a content debt log.
In the Continu Architecture
Authored content is the raw material the rest of Continu operates on.
- Tracks and Journeys. Made of content assets. The quality of the track is bounded by the quality of its content.
- Assessments. Often authored alongside the content they verify. Question-writing is its own authoring discipline.
- Smart Segmentation. Reaches the right audience, but only matters if the content the audience reaches is worth their time.
- Eddy. The conversational learning agent reads from your content. Better authoring produces a better Eddy.
- Notifications. Carry the content to the learner. The notification can deliver attention; the content has to deliver value.
- Reporting. Surfaces what content gets engaged with, completed, and abandoned. The reporting layer is feedback for the authoring practice.
A high-functioning authoring practice makes every other Continu feature work better. A weak authoring practice means the rest of the architecture has nothing useful to operate on.
External Audience Patterns
Partner enablement content. Short, application-focused, structured for partners working a sales motion. Pre-call briefings, objection handling, integration scoping, customer case studies. Update cycles match your product release cadence — partners notice when the content lags reality.
Customer education content. Mix of getting-started articles (text, scannable), workflow demonstrations (short video with captions), and downloadable templates (files). Designed for customer admins who are juggling implementation alongside their day job.
Channel education at scale. Standardized templates across a large reseller network. Translated where the channel is multilingual. Versioned so different cohorts can be on different content snapshots if needed. Heavy on reference content; light on monolithic videos.
Franchisee operational content. SOPs, brand standards, compliance procedures, training videos for in-store staff. Modular so updates can be released one section at a time. Versioned to match the franchise operations calendar.
Customer-facing public content. Help center articles, public knowledge base, public video library. Authoring standards higher than internal because the audience is unfiltered. Editorial discipline matters — typos and inconsistency are visible to prospects, not just to customers.
Member or association content. Educational paths for association members, certified affiliates, accredited practitioners. Often longer-form than partner or customer content; the audience is engaged with the topic, not just executing a task.
Internal Audience Patterns
New hire onboarding content. Mix of company-overview articles (text), tool-and-process demonstrations (short video), policy reference (articles with embedded files), and compliance modules (structured tracks). Designed for an audience absorbing a lot in a short window.
Compliance training content. Modular, audit-grade, versioned. Authored to the regulation, not to the comfortable explanation. Caption and transcript every video. Document the source for every claim.
Sales enablement content. Short, scannable, action-oriented. Battle cards, competitive briefs, deal-stage playbooks. Updated frequently — sales reps notice the lag faster than any other audience.
Manager development content. Mix of conceptual articles, case studies, and discussion guides. Designed to drive 1:1 conversations between manager and learner, not to be consumed in isolation.
Engineering and technical content. Long-form articles, code examples, deep-dive videos, integration documentation. Authoring discipline often delegated to technical writers or engineers; the same brief and review workflow still applies.
Cross-functional ramp content. New product launches, strategy changes, organizational announcements. Authored centrally, surfaced widely. Versioned so the historical record is preserved when the strategy changes.
Known Behaviors and Limits
Video updates are expensive. Once a video is produced, updating it means re-recording, re-editing, re-captioning, re-publishing. Design video content around stable concepts; use articles for content you'll iterate on.
File versioning is per-upload, not per-edit. When you replace a file in Continu, learners who downloaded the old version still have the old version. For high-stakes documents, plan a communication motion for updates, not just a re-upload.
AI authoring assist is not aware of your specific product reality. AI drafts from general patterns and from the content you've already published. It does not know what shipped last week, what's deprecated, or what your compliance officer just changed. SME review catches this.
Embedded content is a dependency you don't fully control. A Loom video that was external content can be deleted by the team that owns it. An article you linked to can be moved. Plan for the failure mode — own critical content in Continu rather than embedding it.
Multimedia accessibility takes production effort. Captions, transcripts, audio descriptions, alt-text — each one adds cost. Plan it in advance; retrofitting an entire content library is a much bigger project than building it accessible from the start.
Article length affects retention more than completion. A 600-word article gets read more thoroughly than a 3,000-word article. Long articles get scanned. If the content is critical, break long articles into a sequence of shorter ones inside a track.
Search and discovery depend on titles and metadata. A perfectly authored article with a vague title doesn't get found. Spend the last 10% of authoring time on the title, summary, and tags — that's the work that determines whether the asset gets used.
Translation introduces lag. Localized content trails source content by the time it takes to translate, review, and re-publish. Plan the cadence so partners and customers in non-source-language markets don't get stale content during the translation window.
Author handoffs lose context. When an author leaves and someone else inherits the content, the why-this-was-written is often gone. Document the brief alongside the asset. The next maintainer will thank you.
Where to Go Next
- Content Strategy: Designing Learning Assets That Scale — for the strategic decisions that should precede authoring.
- Tracks and Journeys: Designing Learning Paths — for the structures that authored content lives inside.
- Assessments: Designing Knowledge Checks That Earn Their Cost — for the verification content that pairs with most assets.
- Eddy: The Conversational Learning Agent in Continu — for how AI authoring assist fits the broader workflow.
- Reporting: Which Report Should I Use? — for the feedback loop that tells you what content is working.
Design first. Click second. Author content that earns the audience's attention, the medium it lives in, and the place it shows up.