Folk tales are oral-tradition stories collected from communities rather than authored. The catalog is enormous and global: Russian skazki, Japanese mukashi-banashi, West African Anansi cycles, Irish seanchai stories, Mexican cuentos, and dozens more. Each tale carries the same metadata shape: a title, a region, a language, a collector (Afanasyev, Yanagita, Lonnrot), a tale type, a set of motifs, a synopsis. The values change per tale, the fields stay constant.

SleekRank reads a folk-tale sheet and renders one URL per row at /folk-tales/{slug}/ using a base WordPress page as the template. Tag mapping handles the title, selector mappings drop in region and language, list mappings render motifs and themes, and the synopsis lands in a content block. A second page group can render region-index pages (one per region) listing every tale collected there.

A correction to a Romanized transliteration in the sheet ships to every page on the next cache cycle. Adding a newly translated Sami folk tale is one row, not a new WordPress post.

Folklore archives reward structure. A reader arriving at any folk-tale page expects the same shape every time: where it came from, who collected it, what language carried it, what happens, what motifs run through it. Search engines reward that structure too because well-organized pages surface for 'Japanese folk tales about {motif}' and '{region} folklore' queries.

The bottleneck on hand-built folklore catalogs is never the writing of one synopsis, it is the formatting drift across hundreds or thousands of tales when each passes through a separate editor session. Programmatic generation removes that drift, so the template lives in one place and every entry inherits it. Folklorists and translators focus on substance (accurate region, sensitive translation, careful attribution) and the platform handles structure.

The archive compounds in authority as new regions and oral traditions get added to the source.