Add a refines column with the slug of the parent pattern when the new entry is a specialization (CQRS refines Command Query Separation, for example). A list mapping renders Refines and Refined by sections on each page. Pattern composition relationships stay explicit and bidirectional through the same slug column on both ends.

Yes. Add an adrs array column holding URLs or slugs to ADRs that adopted or rejected the pattern. A list mapping renders Related decisions on each pattern page. Engineering wikis especially benefit because architects can trace where a pattern decision was made and why, without manually keeping that index up to date.

Add a qaw_scenarios array of objects with attribute name and scenario string. A list mapping renders a Quality scenarios table on each pattern page. Patterns can then be queried by the quality they primarily address (latency, availability, modifiability), which is the core decision lens in QAW-driven architecture practice.

Add a maturity column with values like emerging, mainstream, specialized, legacy. Conditional Twig in the base template renders a maturity badge per pattern, and a meta mapping puts the badge into the Open Graph image. Readers see at a glance whether a pattern is a safe default or a frontier choice for their context.

Yes. Run two SleekRank page groups against the same sheet, with a visibility column that conditional mappings respect. Internal patterns marked private are excluded from the public render via a filter on the page-group data source. One sheet, two sites, two URL families, zero risk of confidential patterns leaking publicly.

Google treats them as TechArticle content with software-engineering entity context. Structured data plus consistent semantic markup tends to surface architecture pattern pages well for query like X pattern trade-offs or when to use Y pattern. SleekRank handles the schema baseline; the catalog still has to compete on content quality for serious ranking.

Render diagrams from a structured source like PlantUML or Mermaid stored in a diagram_source column. A build step converts each source to SVG and writes the SVG URL back into the sheet. The base page renders the SVG via a selector. Refresh the entire catalog's diagram style by updating the PlantUML theme once.

Yes. Add a recommended_stacks array of objects with stack name and rationale string. A list mapping renders a Recommended stacks block. Microservices on Kubernetes, event sourcing with Kafka and a relational read store, hexagonal architecture in Go with explicit ports. Each pattern page lists the canonical implementations engineers actually use.