Private Pro template · implemented
Relay Forge
A developer-tools landing and documentation product for a local workflow runner. The public page exposes only reviewed source-free metadata; private React, TypeScript, tests, and release files never enter this application.
Product route contract
//product/integrations/docs/changelog
State and quality contract
States: loading, empty, error, success, permission-denied, offline.
Requirements: responsive, light, dark, rtl-reviewed, keyboard-reviewed, seo-ready.
Evaluate the product fit
Relay Forge is intended for a developer tool that must move from a concise product promise into integrations, task-focused documentation, and an inspectable change history. It suits a workflow runner or similarly technical product whose credibility depends on precise setup guidance rather than invented adoption numbers.
Review whether the integration catalogue, documentation hierarchy, and changelog can be driven from maintained product records. Commands, compatibility claims, operating-system details, and examples must match a tested release. Loading and offline states should preserve access to already available guidance without pretending a remote action succeeded.
Plan keyboard-copy behavior, long code samples, narrow documentation navigation, search with no results, outdated links, and version-specific notes. Replace every demonstration command and identifier. A consuming team remains responsible for package security, telemetry disclosure, release signing, and the support path attached to its tool.
Before launch, define who owns compatibility data, documentation corrections, security notices, and release support. The deployed product should monitor failed integrations and broken documentation destinations without logging sensitive command input. Backups and rollback need to cover the site and its maintained content sources; a polished local workflow example does not prove the hosted documentation can be recovered.
Source-free preview
No public preview is published. Preview metadata remains private until release readiness and boundary review are complete.
Availability boundary
Implemented does not mean verified, release-ready, entitled, sold, or deployed. Manual browser and assistive-technology review, approved commercial terms, a protected archive, and server-side entitlement delivery remain required.