Most sites start with editorial notes plus public domain corpora like Project Gutenberg and the Poetry Foundation archive for older poems, with licensed sources for contemporary work. A short script normalizes each entry into one JSON object with slug, form, title, poet, year and text. SleekRank just needs consistent field names.

When you edit a poem line in the JSON, SleekRank invalidates the cached payload for that form slug. The next request to /poems/{slug}/ pulls the new row set from the file, so one corrected line touches one form library page rather than rebuilding the entire poetic forms catalog across the site.

Add an indexable boolean to the JSON entries and map it to a noindex flag in the template. SleekRank honors that flag per form, which lets you keep draft forms like cento live for internal review while telling search engines to skip them until the example set has been finalized.

If your JSON has a related_forms field with sibling slugs or a shared era, the template loops over them and links to /poems/{slug}/ for each one. SleekRank exposes the row group as a Twig variable, so you build the cross-form link graph from data instead of typing every neighbor by hand.

Page render reads the row group for the requested form from the cached file map, which is an O(1) lookup once SleekRank parses the JSON on first hit. WordPress full-page cache then takes over, so the marginal cost of more form pages stays low even across the full library set.

Yes. The index template reads the full row set, groups by form and lists every form with a link to its library page. Because both pages read the file, the index and the form pages never disagree on poem titles or poet attributions anywhere across the site at any time.

Add an era column with values like medieval or modern. SleekRank exposes it as a row field, so the form page can filter or group by era and you can later render /poems/era/{slug}/ pages from the same file by adding a second URL pattern on top of the same catalog of poems.

You delete the row or move it to a different status. The matching form page reflects the new row set on the next sync, and the catalog stays accurate without an editor opening individual posts in the WordPress admin to swap attributions or pull copyrighted text across many pages by hand.