Yes. SleekRank already powers directories with thousands of rows. As long as the feed returns calls as JSON, CSV, or via REST, every row gets a URL on the configured cacheDuration. A national calls platform aggregating from arts councils across all fifty states 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 budget season, often thirty to ninety minutes, and clear the SleekRank cache manually for instant publication after a programme officer approves a new call. Pages reflect the feed value on the next request after cache expiry.

Yes. The SleekRank page is the SEO-facing brochure that surfaces the call and links out to the Submittable, CAFE, or council submission URL. The actual submission flow stays in the vendor system. Most councils use SleekRank for discoverability and Submittable for jury workflow and compliance.

Use a status column with open and closed values. After the deadline passes, the base page reads the status through a selector mapping and renders a closed banner with the submit button hidden. Keep the URL alive as a shortlist archive so backlinks from artist blogs and disciplinary newsletters survive across cycles.

Yes. Run multiple page groups, each with its own base page and urlPattern filter. Mural commissions route through one base page styled for site photos and surface specifications while sculpture commissions route through another with material safety, weight, and installation logistics blocks.

Add a shortlist column with a JSON array of artist names and link slugs. The list mapping renders shortlisted artists on each commission page after the jury phase closes, and the URL gains fresh content for SEO without rebuilding the page. The same approach handles finalist and winner stages.

Each generated page is unique by data: different title, medium, budget, deadline, agency, and site description. Use per-row metaDescription and pageTitleHtml fields to vary the heading and meta beyond the boilerplate, which keeps duplicate detection at bay across one hundred concurrent calls in a national directory.

Yes. Run a second page group keyed on budget tier with urlPattern /public-art/budget/{tier}/. The group filters the feed by tier ranges, such as under-fifty-thousand, fifty-to-two-hundred, and over-two-hundred, and renders a directory hub for each tier. Both groups read the same calls feed through different filters.