Wherever the people maintaining it prefer. Google Sheets and Notion are common because non-developers can edit them in place. CSV, JSON URLs and files, and REST APIs all work too. For convention organisers running a guest list, Notion's property typing helps keep style tags consistent across dozens of guest artists. For studios with an internal admin tool, a JSON endpoint exposing the roster is often cleaner than maintaining a parallel sheet.

Yes. Add a booking column with values like open, waitlist, or closed and map it onto the rendered page through a tag or selector mapping. The badge appears on the profile, every style rollup the artist participates in, and the city rollup from one column edit. Set a short cache duration if booking status changes weekly so the public pages stay accurate without waiting for a manual flush.

SleekRank can map any image URL field into img tags on the page through selector mappings. It does not host or generate galleries on its own. Reference portfolio image URLs from a column or array column in the source, or link out to the artist's external portfolio site through an anchor. For OG images, pair with SleekPixel to render dynamic cards or map og:image to a hosted preview URL per row.

Yes. If an artist works in two styles like fineline and ornamental, list both in the styles array column and let multiple style page groups pick them up through filtering. The same row contributes to /tattoo-artists/fineline/{city}/ and /tattoo-artists/ornamental/{city}/ from one source. Style range is common; the directory should match how artists actually market themselves rather than forcing a single primary style choice.

Each data source has a configurable cache duration per page group. Flush the cache when you make a change and the next request rebuilds the page. For a studio adding a new resident artist, the workflow is: add the row, run wp rewrite flush so the new URL is routable, flush the SleekRank cache so the page populates. New cities work the same way: add city-tagged rows, flush rewrites, flush cache.

No. SleekRank only generates the pages defined by your page groups and only replaces content within mapped tags, selectors, lists, and meta on those pages. Other pages on the site are completely untouched. The base page itself is also auto-noindexed so only the per-artist URLs compete in search; the base remains a normal WordPress page in your admin for editing.

Yes, with an array column for upcoming conventions. Render it through a list mapping on the artist page, and have the convention's own /conventions/{slug}/ page group pull guest artists by filtering rows where the conventions array contains the convention slug. The same data drives both the artist's tour schedule on their profile and the convention's guest list page.

Store cities as an array column instead of a single value, then let the city rollup page group filter rows where the array contains the URL parameter. The artist appears on every city rollup they list, and their profile shows all current studios via a list mapping. Travelling artists no longer need duplicate rows in the source, and updating a guest stint is a single array edit.