Does this skill support standard vCluster releases?

No, this skill is specifically for vCluster Platform releases. Core vCluster releases use a separate skill called vcluster-docs-releaser.

How does the rc-1 process work for documentation?

Documentation is created and deployed in a hidden state at the rc-1 stage, allowing for validation via direct URLs before being made visible in the UI on release day.

Does Claude run the final build process?

No, for safety and verification purposes, the user is responsible for running the final build and Hurl tests after Claude prepares the configuration.

What is the 'config flip' mentioned in the workflow?

The config flip is a low-risk PR performed on release day that changes version labels, visibility settings, and SEO priorities to make the new docs public.

How does the skill handle cross-plugin links?

The skill enforces the use of @site aliases for cross-plugin imports to ensure that links between platform and vcluster plugins remain functional after versioning.

vCluster Platform Documentation Releaser

Name: vCluster Platform Documentation Releaser
Author: loft-sh

byloft-sh

•

Content Management

Automates the complex documentation release lifecycle for vCluster Platform including API generation, versioning, and SEO configuration.

The vCluster Platform Documentation Releaser skill is designed to manage the high-stakes process of publishing new platform documentation versions. It facilitates a sophisticated two-stage workflow: an rc-1 phase where documentation is generated and deployed in a hidden state for validation, and a 'config flip' phase for public release day. By automating technical tasks like Go-based API partial generation, Docusaurus configuration updates, and cross-plugin link verification, it ensures that platform releases are consistent, SEO-optimized, and free from broken internal references.

Key Features

01Two-phase release management for hidden pre-releases and public launches

027 GitHub stars

03SEO automation for sitemap priorities, redirects, and announcement bars

04Smart configuration of Docusaurus versioning, labels, and visibility

05Cross-plugin import validation using @site alias enforcement

06Automated API partial generation from vCluster schemas using Go scripts

Use Cases

01Standardizing API resource documentation across versioned platform folders

02Preparing hidden documentation versions during the rc-1 release candidate window

03Performing the final 'config flip' to expose stable documentation on release day

Key Features

01Two-phase release management for hidden pre-releases and public launches

027 GitHub stars

03SEO automation for sitemap priorities, redirects, and announcement bars

04Smart configuration of Docusaurus versioning, labels, and visibility

05Cross-plugin import validation using @site alias enforcement

06Automated API partial generation from vCluster schemas using Go scripts

Use Cases

01Standardizing API resource documentation across versioned platform folders

02Preparing hidden documentation versions during the rc-1 release candidate window

03Performing the final 'config flip' to expose stable documentation on release day