A clean music theory scale catalog is straightforward to author in a sheet. Editors define each scale type once with notes, intervals, fretboard positions, and piano fingerings in JSON columns. The catalog transposes across all 12 keys via a script, then SleekRank reads the rows.

Each church mode is its own row with a parent_scale column pointing back to the parent major scale. C Ionian, D Dorian, E Phrygian, F Lydian, G Mixolydian, A Aeolian, and B Locrian all share the same parent of C major. A selector renders the relationship.

Exotic and ethnic scales live in their own rows with the same column structure. The notes array, intervals array, fretboard positions JSON, and piano fingerings JSON all behave the same way. The corpus expands as new exotic scales get added without extra work.

Each page carries a unique root, a unique mode, unique notes, unique intervals, unique fingerings, and unique audio. The shared structure is the template, not the content. Search engines treat individual scale pages as distinct entities.

Set cache duration to 86400 seconds. Scale definitions rarely change once published, and the cache duration only matters when an editor corrects a fretboard position or adds a new position pattern. Manual flushes via wp rewrite flush handle urgent edits.

Yes. SleekRank supports JSON file, CSV, Google Sheets, REST API, custom post types, and SQL queries as data source types. A music education startup could feed the page group from its own theory engine while a smaller blog maintains a sheet.

Add a root column and a scale_family column with values like major, minor, pentatonic, blues, exotic. Sibling SleekRank page groups read the same source filtered by root or by family and render per-root and per-family hubs.

Edit the fretboard_positions JSON for the row. The next cache refresh rebuilds the page with the updated position and Search Console picks up the updated lastmod. The URL stays stable so external links from technique articles continue to resolve.