# Showcase Design Benchmark

This note records the design references used to shape the product page.
It is intentionally about page strategy and information architecture, not visual
copying.

## References

- [Evidence](https://evidence.dev/): product-focused data-app positioning,
  strong emphasis on polished data products, version control, validation, and
  testing.
- [Observable Framework](https://observablehq.com/framework/): command-line
  first data-app positioning, local preview, static output, source control,
  unit testing, and CI/CD as part of the product story.
- [Grafana](https://grafana.com/): strong hero, proof surfaces, ecosystem
  positioning, and trust signals around secure and open foundations.
- [GitHub Docs: status badges](https://docs.github.com/en/actions/how-tos/monitor-workflows/add-a-status-badge):
  repository health signals should be visible from the README.

## Applied Principles

- Lead with a product identity instead of a project explanation.
- Show a product interface immediately in the first viewport.
- Turn quality gates into visible trust signals.
- Separate reusable core behavior from local adapter details.
- Present human-readable outputs and automation-ready contracts together.
- Present code, configuration, outputs, and release checks in one developer
  surface instead of scattering them across separate notes.
- Keep roadmap language focused on reusable core maturity.

## Non-Goals

- No copied brand visuals, logos, testimonials, claims, or customer proof.
- No fabricated usage numbers, teams, companies, or security certifications.
- No workbook names, screenshots, source paths, or business records from a
  specific internal workflow.