Alpha.15 lets independent deployments build customer documentation editions from one shared content project. Each deployment supplies its own profile for purchased products, grandfathered features, branding, and publication selection. Customer profiles can stay outside the shared repository.
Upgrade to CLI 0.1.0-alpha.15 and rebuild your site and content exports to use the feature. Existing projects keep their current behavior unless they enable deployment profiles. See Build customer documentation editions for the complete workflow.
Select purchased and grandfathered features
A shared stock keeping unit (SKU) manifest maps explicit product revisions to feature IDs. Profiles combine those grants with direct feature entries, including features customers still own without a SKU. Historical revisions remain selectable; lifecycle labels do not revoke grants or automatically select older documentation versions.
Pages use feature requirements, and <ForFeature> selects sections inside shared pages. Selection removes excluded content from the build instead of hiding it in the browser. Deployment profiles can also apply supported titles, logos, favicons, theme choices, links, and publication subsets.
Require deliberate page classification
By default, pages without feature requirements remain shared. Enable profiles.requireClassification: true to require each eligible source page to explicitly declare shared: true or feature requirements. Inherited defaults do not satisfy the check, and missing classification fails before customer selection.
Shared pages can still contain feature-specific sections. Classification catches forgotten declarations; authors must still review the content and place requirements around product-specific instructions.
Validate each edition
Pass the same external profile to baseline capture, authoring validation, build, and export. Validation captures the profile and its declared assets; later changes make that evidence stale. The packaged authoring, setup, and recipe skills explain this workflow and how to check included and excluded content.
Profiled API builds support selected references and focused operation contracts. Full raw OpenAPI downloads, standalone schema embeds, and profiled chat-function builds are not supported. Use build/serve or snapshot validation/preview rather than dev for customer editions.
HTML, Markdown, and agents
The compiler applies feature selection to HTML, Markdown, search, discovery, and content exports. Agents receive the selected content rather than browser-hidden alternatives. Pages excluded by the chosen profile have not had their rendered content validated; check another profile that includes a changed page before accepting that edit. Customer access to the resulting edition remains the deployment's responsibility.