Yes. Pass a sessions array in your data source with start date, end date, day of week, and time per session, and use a list mapping to render them inside the base page. Each studio page shows its current term schedule from one column rather than hand-edited HTML in the page body.

Either add a row per medium with its own slug and class details, or store mediums as an array on a single row. The URL pattern decides how the directory splits. Rows-per-medium gives each combination a unique page; arrays keep one studio profile and let rollup page groups filter on the array.

No. SleekRank renders content. Pair it with your booking plugin or external link per row for sign-ups. Many studios use platforms like Mindbody, Acuity, or Eventbrite, and a booking-url column mapped to a CTA button on the base template covers the typical workflow without SleekRank touching availability.

Use multiple page groups, each with its own base page, if mediums need very different layouts. A ceramics page that needs a kiln-firing schedule and a clay-type spec might justify its own template, while painting and drawing share one base page that handles supplies and session lists.

SleekRank caches each data source for the duration you set in the page group config. Typical values run from one hour to twenty-four hours. Clear the cache to publish edits immediately when a session shifts mid-term or a studio adds a last-minute workshop without waiting for the next refresh.

No. Copy lives in your data source or base page. SleekRank only injects values into mapped slots through tag, selector, list, and meta mappings. You control the workshop description, the supply list, and every other piece of text rendered on the page.

Either store level as an array column with values like beginner, intermediate, advanced, all-levels, or use all-levels as a single value when the class genuinely accepts every level. The level rollup page groups can filter on the array, so a beginner-friendly class still appears on the beginner-by-medium-by-city rollup.

Yes. Add a supplies column with an array of items and a kit-fee column with a number, then render them as a list and a selector on the base template. Learners often filter classes on whether supplies are included, so making the field structured rather than hidden in the description pays off in conversion and search relevance.