Only if those platforms expose a public JSON or REST endpoint your WordPress server can pull, which is rare. Aggregators typically maintain a curated database by tracking program pages directly, then point a SleekRank page group at that database for rendering. SleekRank is the rendering layer, not the data acquisition layer.

Use a funding-type column with values like fully-funded, partial, self-funded, and work-study, then surface it through a tag mapping in the base page. The data drives both visible copy and structured metadata so applicants and search engines understand the financial structure at a glance.

Yes. Map an image URL column to og:image, or pair SleekRank with SleekPixel to render dynamic cards combining host name, location, and medium. Each program gets a unique social card for the times it is shared in artist Slack workspaces, Discord servers, 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 square footage, kiln access, press access, accommodation type, and meals included, then surface them through selector or list mappings in the base page template. The data lives in your database and the page renders the references on demand.

Use a medium column and either reference it in the urlPattern as /artist-residencies/{medium}/{slug}/, or run parallel page groups per medium with distinct base pages. Each group reads the same database, filtered at the data source level so URLs stay clean per practice 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 alumni 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 exhibitions, grants, and gallery placements that strengthens its authority over time.