SitePack 0.5.0-rc.1

Status: release candidate Date: 2026-06-12

This release candidate packages the current SitePack standard work into a reviewable public slice. It is intended for developer review before a final tag, package publication, or GitHub Release.

What Changed

SitePack now has a clearer standard surface for portable website packages:

• conformance levels for readers, validators, archives, previewers, importers and exporters;
• portable profile contracts for configuration, content, site structure, content assets, snapshots and product packages;
• extension governance for platform-specific adapter data;
• a site-map artifact and site-structure profile;
• two public site-structure examples: small-docs-site and small-blog-site;
• adapter-proof documentation showing how the same portable artifacts can map to different platform models;
• Node and PHP validator checks for declared profile requirements;
• aggregate validation through the root Makefile.

What This Gives Developers

The candidate makes SitePack easier to evaluate as a standard, not only as a collection of schemas.

Developers can now check three practical questions:

• what level of compatibility a tool claims;
• which portable profile a package follows;
• where platform-specific adapter data belongs.

This is especially important for migration and backup scenarios. A SitePack package can describe common website structure without turning Bitrix, Larena, WordPress, Drupal or another platform into the center of the format.

Compatibility Boundary

The current package examples and schemas still use spec.version 0.4.0. This release candidate records the next release scope and verification status. The final release action should decide whether the format/tool version is bumped and then update versioned schemas, examples and reference tools together.

Validation Scope

The release candidate should be accepted only when these checks pass:

PATH=/Applications/ServBay/bin:/Users/rim/.cache/codex-runtimes/codex-primary-runtime/dependencies/node/bin:$PATH make validate-all
cd sitepack-tools-node && npm audit --json
git diff --check

Not Included

This candidate does not include:

• a Git tag;
• a GitHub Release;
• npm or Composer package publication;
• production importer/exporter implementations;
• a final public article or announcement.

Recommended Final-Release Checklist

• Decide the final version number.
• Update format/tool versions consistently if a version bump is approved.
• Rerun Node and PHP validation.
• Confirm GitHub Actions.
• Create a signed tag or GitHub Release.
• Publish a short public note linking to the release notes and examples.