Only if those platforms expose a public JSON or REST endpoint, 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 an eligibility column with structured values for identity, career stage, or genre restrictions, then surface them through a tag mapping in the base page. Each residency page communicates eligibility clearly at the top so writers see the restrictions before reading further details.

Yes. Map an image URL column to og:image, or pair SleekRank with SleekPixel to render dynamic cards combining host name, location, and genre. Each program then has a unique social card for the times it is shared in writer Slack workspaces, Twitter threads, or MFA 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 Submittable, CaFE, or the host's own system. Use a CTA column on the database to drive the apply button per row.

Yes. Add columns for current panel members, past fellow names, sample published outcomes, and notable books from cohorts, 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 genre column and either reference it in the urlPattern as /writing-residencies/{genre}/{slug}/, or run parallel page groups per genre with distinct base pages. Each group reads the same database, filtered at the data source level so URLs stay clean per writer 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 cohort resources with an array of URLs, titles, and brief descriptions, then surface them through a list mapping in the base page template. Each residency page can then carry a growing library of writer-side guidance that strengthens its authority across application cycles.