The Creation Phase: Building New Content With Intention

This sub-chapter is not where pillars, spokes, glossaries, comparisons, and evidence pages get defined. That work belongs entirely to Chapter 8, and it's assumed as known ground here rather than repeated. What this sub-chapter covers is narrower and specifically operational: when creation happens within this chapter's cycle, how a specific gap gets routed to the right page type, and how new content gets sequenced once the decision to create, rather than restructure, has actually been made.

What This Sub-Chapter Covers, and What It Doesn’t

Chapter 8 established what a pillar page is, what a spoke resolves, and what distinguishes a glossary, comparison, FAQ, or evidence page from each other. None of that gets redefined here. A reader arriving at this sub-chapter is assumed to already understand these distinctions, and this page’s job is entirely about operational sequencing: when creation happens within this chapter’s broader cycle, and how a specific identified gap gets matched to the right type of page to fill it.

This scoping is deliberate rather than an accident of brevity. Redefining page types here would duplicate Chapter 8’s actual doctrine, and this chapter’s whole purpose is sequencing and executing principles already established elsewhere in this framework, not restating them.

Creation as the Output of Restructure-First, Not a Starting Point

Chapter 13.3 established that the default instinct toward new content is usually wrong, and that restructuring existing content should be the first option considered for any given gap. Creation, in this chapter’s cycle, is reached only once that check has genuinely ruled restructuring out, not treated as where content work naturally starts.

This ordering matters practically. A creation phase that begins without first checking whether restructuring would have resolved the same gap risks producing new content that competes with, or duplicates, existing material that only needed structural improvement. The gap analysis from Chapter 13.2, filtered through Chapter 13.3’s restructure-first check, is what arrives at this phase: genuine gaps, confirmed as genuine, ready for actual creation work.

Routing a Gap to the Right Page Type

Once a gap is confirmed as genuine, it needs to be matched to the correct functional page type, using the six types established in Chapter 8.4. A definitional gap, an intent cluster asking what something is, routes toward a glossary entry. A comparative gap, weighing options against each other, routes toward a comparison page. A gap requiring full narrative depth on one specific need routes toward a standard spoke. A cluster of related, high-value questions that don’t belong to any single spoke’s narrow scope might route toward a dedicated FAQ page.

This routing logic isn’t new; it’s Chapter 8.4’s existing framework, applied here as the specific mechanism for matching mapping-phase gaps to production decisions. Getting this routing right matters because a definitional need forced into a narrative spoke, or a comparative need addressed without the parallel structure a comparison page requires, produces content that resolves its intent cluster less effectively than the correctly matched page type would have.

Sequencing Within a Content Operation

Once page types are determined for a set of gaps, production sequencing follows the same convention this framework has used in its own construction throughout: spokes before pillar. A pillar page written before its spokes exist tends to describe them in vague, aspirational terms that may not match what actually gets written, exactly the reasoning Chapter 8.2 already established for why this framework itself follows that order.

This sequencing applies at the silo level during a creation phase just as it applied to building this framework’s own chapters: if a creation phase is filling gaps across an entire silo, the individual spokes resolving specific gaps should be produced before any pillar page framing that silo gets written or revised, so the pillar’s framing accurately reflects content that already exists rather than content that’s still planned.

Where Multimedia Assets Fit In

Chapter 12 established that video, images, audio, and platform content are genuine source material, not branding, and a creation phase filling a gap sometimes means producing multimedia content rather than, or alongside, a written page. The routing logic covered above still applies: a gap best resolved by a well-structured video, following the architectural decision in Chapter 12.1 that multimedia pages apply spoke discipline, gets treated as a spoke-equivalent creation task, not a separate category of work requiring its own process.

This is a brief connection rather than a full treatment, since Chapter 12 already covers multimedia content creation in depth. What matters here is recognizing that the creation phase’s routing decision isn’t limited to written page types; it extends to whichever medium actually resolves a given gap most effectively.

Handoff to Technical Implementation

New content, once written or produced, isn’t finished simply because it exists. It needs the technical execution covered in Chapter 13.5: schema implementation, internal linking connecting it to the rest of its silo, and the other infrastructure work that makes newly created content actually reachable and correctly structured for generative retrieval.

This handoff is worth naming explicitly rather than assumed to happen automatically. A creation phase that produces excellent content and stops there, without the technical implementation that follows, leaves that content in an incomplete state, publishable but not yet fully integrated into the site’s technical and structural systems the way the rest of this framework requires.

Building With Intention, Only Once It’s Actually Warranted

Michael Rubinstein treats the creation phase as the point in this operating cycle where genuine craft matters most, and also the point most likely to be reached prematurely by a team that skipped the restructure-first check that should have preceded it, producing new content for gaps that a cheaper fix would have resolved just as well.

ScribePress routes confirmed gaps to the correct functional page type automatically as part of its production pipeline, applying Chapter 8.4’s routing logic consistently rather than leaving that determination to case-by-case judgment that can drift inconsistently across a large content operation.

Learn more about the work behind this framework at michael-rubinstein.com.

Put the framework to work