A geometry lesson on the Pythagorean theorem has the same teaching shape as a lesson on congruent triangles or properties of parallel lines: a topic name, a one-paragraph definition, a diagram, a set of given conditions, a proof sketch, and a few worked examples. The structure is identical across topics; the diagrams, conditions, and worked examples are what change.

SleekRank reads a geometry lessons sheet and renders one page per row at /geometry/lessons/{slug}/. Tag mappings push the topic name into the H1 and the unit label into a badge. Selector mappings inject the diagram image URL and the LaTeX statement into MathJax slots. List mappings handle the conditions array and the worked-examples array. Geometry teachers maintain the sheet, the WordPress site stays in sync without anyone touching the editor.

The sample data for this group shows the structure: pythagorean-theorem (right-triangles unit, 3 examples), congruent-triangles (triangles unit, 4 examples), parallel-lines-transversal (lines and angles unit, 4 examples), circle-theorems (circles unit, 5 examples), area-of-polygons (area and perimeter unit, 4 examples). Each row becomes its own indexable URL.

Geometry teaching is the textbook case for a per-topic template. Every theorem has the same backbone: a statement, conditions, a diagram, a proof sketch, and worked examples. The variation between topics is small and structured.

Hand-building each topic as its own WordPress page produces a corpus that looks consistent for the first ten pages and then drifts. Diagrams render in different sizes. LaTeX is configured slightly differently on different pages.

Worked examples get uneven depth as different authors contribute. Conditions and hypotheses sometimes appear before the statement, sometimes after, depending on who wrote that particular page. Treating topics as data fixes both problems.

The sheet matches the way curriculum scope-and-sequence documents already work. The WordPress site reads that sheet and renders consistent pages. New topics ship the day the curriculum team updates the sheet, and a fix to the worked-examples block applies to every page on the next cache cycle.

The geometry teacher does geometry teaching; the web team owns rendering.