Only if a foundation exposes a public JSON or REST endpoint, which most do not. Aggregators typically build a light middleware that scrapes or normalises foundation pages into a shared database, then expose that as a stable URL the SleekRank page group reads each cycle. SleekRank is the rendering layer, not the data acquisition layer.

Use a status column with values like open, closing-soon, and closed. Either filter closed rows from the urlPattern, or keep them live and render an archive block conditionally. The archive pattern preserves backlinks and helps applicants studying past cycles, which is common in two-year application strategies.

Yes. Map an image URL column to og:image, or pair SleekRank with SleekPixel to render dynamic cards combining host logo, stipend, and stage. Each program gets a unique social card for the times it is shared in applicant Slack workspaces, Discord servers, or department newsletters.

No. SleekRank renders pages and does not process forms, payments, or document uploads. Most fellowship pages link out to the foundation portal because applications run through proprietary systems. Use a CTA column on the database to drive the apply button per row, pointing at the foundation URL.

Yes. Add columns for cohort size, acceptance rate, average GPA, and past institution mix, 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 without bloating the WordPress install.

Use a stage column and either reference it in the urlPattern as /fellowships/{stage}/{slug}/, or run parallel page groups per stage with distinct base pages. Each group reads the same database, filtered at the data source level so URLs stay clean and indexable 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 foundation amendment, clear the SleekRank cache manually so the next render pulls fresh data from the source.

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 fellowship page can then carry a small library of applicant-side guidance that grows year over year without manual page edits.