Yes. SleekRank already powers directories with thousands of rows. As long as the feed returns residencies as JSON, CSV, or via REST, every row gets a URL on the configured cacheDuration. A global platform aggregating from hundreds of foundations imposes no extra load because the base page is the same across every URL.

They appear as quickly as cacheDuration allows. Set the cache low during peak application season, often one to four hours, and clear the SleekRank cache manually for instant publication after a coordinator approves a new cycle. Pages reflect the feed value on the next request after cache expiry.

Yes. The SleekRank page is the SEO-facing brochure that surfaces the programme and links out to the Submittable or Slideroom application URL. The application stays in the vendor system. Most foundations use SleekRank for discoverability and the vendor for jury workflow.

Use a status column with open, closed, and notified values. The base page reads the status through a selector mapping and renders the appropriate banner with the apply button hidden. Keep the URL alive across the full year so backlinks from arts newsletters survive past each cycle close.

Yes. Run multiple page groups, each with its own base page and urlPattern filter. Writing residencies route through one base page styled for sample-work submission requirements while visual arts route through another with portfolio-image upload guidance and studio specifications blocks.

Add an alumni column as a JSON array of past-resident slugs and names. The list mapping renders the alumni gallery on each programme page, growing year over year as the feed accumulates. The same approach works for past-cohort show links and exit-interview archives.

Each generated page is unique by data: different title, discipline, stipend, length, host venue, deadline, and selection criteria. Use per-row metaDescription, pageTitleHtml, and selectionNotes fields to vary the heading and meta beyond boilerplate, which keeps duplicate detection at bay across hundreds of programmes.

Yes. Each foundation submits programmes via a shared sheet or its own JSON feed, and SleekRank can run separate page groups per foundation or merge into one master group. National platforms typically run a nightly middleware export that normalises field names across foundation feeds before SleekRank reads the merged sheet.