A trigonometry lesson centers on an identity, a unit-circle fact, or a model (law of sines, law of cosines, double-angle, sum-to-product). Each has a statement in LaTeX, a small proof sketch, a graph, two or three worked examples, and a set of practice problems. The shape repeats across the entire course, which is what makes a per-lesson template earn its keep.

SleekRank reads a trigonometry sheet and renders one WordPress page per row at /trigonometry/lessons/{slug}/. Tag mappings carry title and topic, selector mappings inject LaTeX through one MathJax or KaTeX block and embed Desmos graphs, list mappings handle examples, practice problems, and related identities, meta mappings carry description and LearningResource JSON-LD.

Teachers and curriculum writers edit the sheet directly. A new identity is a new row. Adding a Desmos visualization to an existing identity is one cell. The base lesson template is noindexed, each generated URL enters the sitemap, and cache duration is set per source so an early-week edit reaches students by class time.

Trigonometry is one of the most structured pieces of high school and early college math. The identities are countable, the unit circle is finite, the laws are named, and the proofs follow a small number of patterns. That clean structure is exactly what hand-built page systems fail to preserve.

By the time an instructor has written thirty trig pages in Gutenberg, the LaTeX renderer config has drifted, the Desmos iframes are inconsistently sized, the proof sketches vary in depth, and the related-identity cross-links have rotted as lessons were renamed. Search intent is direct. Students search for the specific identity, the specific law, or the specific worked-example query, and a focused per-identity page wins the click over a long survey page.

The data is tabular and modest. One identity statement, one proof sketch, one Desmos URL, two to three worked examples, ten to fifteen practice problems. Everything else is layout.

Once the sheet is the source, math teachers own the content, the web team owns the rendering, and the corpus stays consistent across semesters and instructors. Pair with SleekPixel for OG cards that carry the identity name and topic, and the course site grows with the curriculum rather than behind it.