Repository navigation
Release v7.1.5
Changed
cratis-documentation-writing: when a page shows several backends, state their differences once in a table near the start, and keep a series' backend limitations in one table on its index. Adding a backend also means checking cross-product and site-level pages for single-language claims (#442)cratis-documentation-writingsite reference: site-owned pages can use the language tab macros, tabs can't sit insideSteps, the variant-docs audit covers site-owned pages, and a preview variant is labeled on the first screen of every page that shows it (#442)cratis-technical-examples: a compiling tab isn't a working tab. Check discovery, generated proxies and claimed runtime behavior, never publish failing code with a workaround in the prose, and keep id types and domain names consistent across tabs (#442)
Merge after Cratis/Documentation's site-page audit, which the site reference describes. Reviewed by a same-provider (Anthropic-only) review.
Closes #442