Kindergarten reading instruction breaks into a tidy list of foundational skills. Letter recognition, beginning sounds, rhyming, sight words, blending CVC words, segmenting phonemes. Each skill has the same teaching shape: a definition, a small set of examples, a visual or word list, and a handful of practice items. The structure is identical across skills; the letters, sounds, and word lists are what change.

SleekRank reads a reading skills sheet and renders one page per row at /reading/kindergarten/{slug}/. Tag mappings push the skill name into the H1 and the standards code into a badge. List mappings handle the examples array and the practice-items array. Selector mappings inject the visual reference (alphabet chart, ten frame, word list) and the recommended duration into fixed slots. Early-childhood literacy specialists maintain the sheet directly.

The sample data for this group shows the pattern: letter-recognition (CCSS RF.K.1.D, 6 examples), beginning-sounds (RF.K.2.A, 5 examples), rhyming (RF.K.2.A, 5 examples), sight-words (RF.K.3.C, 4 examples), blending-cvc (RF.K.2.D, 5 examples). Each row becomes its own indexable URL.

Kindergarten reading is the cleanest case for a per-skill template. Every skill has the same teaching backbone, the variation between skills is small and tightly structured, and the audience (parents, kindergarten teachers, intervention staff) lands on a specific skill via search rather than browsing a long index. Hand-building each skill as a separate WordPress page produces a corpus that looks consistent for the first five pages and then drifts.

Phonics visuals render at different sizes. Sight-word lists are formatted three different ways. Standards code badges look slightly different on different pages because different team members made them.

Literacy specialists, who are not WordPress editors by training, get blocked on a developer for every batch of new skills. Treating skills as data fixes both problems. The sheet matches the way kindergarten scope-and-sequence documents already work.

The WordPress site reads that sheet and renders consistent pages. New skills ship the day the team updates the sheet, and a fix to the visual-display block applies to every page at once on the next cache cycle.