Yes, if the source exposes JSON, CSV, or a REST endpoint your WordPress server can reach. SleekRank does not integrate with proprietary arts platforms directly. Most aggregators build a middleware layer that ingests institution pages and curated submissions into one normalised JSON feed, then point a SleekRank page group at that feed for rendering on the configured cacheDuration.

Use a status column and either drop closed rows at the urlPattern level so they fall out of the sitemap, or hide the submit CTA via a conditional in the base page while keeping the URL alive. The second pattern preserves accumulated backlinks and lets the URL flip back to open when the next edition opens, which works well for annual residencies and recurring magazine issues.

Yes. Map an image URL column to og:image, or pair SleekRank with SleekPixel to render dynamic call cards combining medium, deadline, and stipend. Configure the meta mapping in the page group and each call gets a unique social card for the times the URL is shared in artists Slack groups or Instagram stories during peak submission windows.

No. SleekRank renders pages and does not process submissions, fees, or portfolio uploads. Use a selector mapping to link to the institution's submission portal, often Submittable or a custom intake form. Most aggregators link out to keep the official channel as the source of truth and avoid handling artist portfolios on the directory side.

Yes. Add a medium column and reference it in the urlPattern as /open-calls/{medium}/{slug}/, or run parallel page groups per medium if base page layouts need to differ between photography, painting, and digital art calls. Each group reads the same feed but applies different filters and templates, keeping URLs distinct and rankable per medium cluster.

Edit the feed or sheet and clear the SleekRank cache. Pages reflect the new values on the next request. For institutions that update stipend amounts or deadline extensions mid cycle, set cacheDuration low during peak submission windows so changes propagate without manual flushes. The trade off is more frequent fetches from the data source under traffic load.

Yes. Add columns for juror rosters and selection criteria, then surface them through list mappings in the base page template. Juror names attract serious submitters who research panels before entering, and clear selection criteria reduce mismatched submissions, which improves the artist-to-institution fit and saves both sides time during the review process.

Store early, regular, and late fee columns separately and map them through tag and selector mappings in the base page. The page renders the current fee tier dynamically based on the deadline window, which helps artists plan their submission budget across multiple calls within the same season without missing early bird discounts.