Only if a portal exposes a public JSON or REST endpoint, which most do not. Aggregators typically maintain a curated database by scraping or normalising program pages, then expose it as a stable URL the SleekRank page group reads each cycle. SleekRank is the rendering layer, not the data acquisition layer.

Use an application-window column with a label like rolling, plus a next-review-date column for context. The base page can render rolling status differently from cycle-based windows so applicants understand when to apply. Edit the row when the host posts a new review window and the change flows through the next cache cycle.

Yes. Map an image URL column to og:image, or pair SleekRank with SleekPixel to render dynamic cards combining host name, location, and discipline. Each program then has a unique social card for the times it gets shared in artist Slack workspaces or department mailing lists.

No. SleekRank renders pages and does not process file uploads, payments, or applications. Most residency pages link out to the host portal because applications run through SlideRoom, Submittable, or the host's own system. Use a CTA column on the database to drive the apply button per row.

Yes. Add columns for studio specs, room counts, accessibility notes, and amenities, then surface them through selector or list mappings in the base page template. The data lives in your database and the pages render the references on demand.

Use a discipline column and either reference it in the urlPattern as /residencies/{discipline}/{slug}/, or run parallel page groups per discipline with distinct base pages. Each group reads the same database, filtered at the data source level so URLs stay clean per applicant audience.

As fast as your cacheDuration allows. Set a tight cache during open cycles, often two to six hours, so edits land quickly. For instant updates after a host posts a cycle change, clear the SleekRank cache manually so the next render pulls fresh data.

Yes. Add a column for notable alumni or sample outcomes with an array of names, years, and project links, then surface them through a list mapping in the base page template. Each residency page can carry a growing record of cohort results that strengthens its authority over time.