Curation

How entries get curated

Six steps from a discovered URL to a verified registry entry — the same checklist the build pipeline enforces, in the same order.

300 resources under curation 0% reviewed or tested 38 categories · 13 stages

The pipeline as a checklist

Six steps, no shortcuts

Each step has a dedicated reference doc and an enforcing build stage. Skipping one is a build error, not a style choice.

Step 01

Candidate resources are found from sources with recorded authority — standards bodies, official vendor docs, established communities.

Step 02

A curator writes the YAML record against the canonical model: one category, provenance, security flags, learning objectives, relationships.

Step 03

Every license is checked against the catalogue. Proprietary and non-reproducible sources are linked and summarised only — never redistributed.

Step 04

Quality (per-component rubric), completeness (16 canonical fields) and trust (verification − flags − staleness) are computed by the build.

Step 05

Entries land at community, then are promoted to reviewed (source/license/docs checked) and tested (install + example run). Re-checked every 180 days.

Step 06

The pipeline regenerates registry, search index, graph and stats; the site reads only those artifacts. A failed validation halts the build.

Current state

Of 300 resources, 0 have been reviewed or tested (0%). The remaining 300 are community finds awaiting a curator check.

0 entries