Yes. Both json_url and json_file are supported, so a generated projections file written by your model or a hosted endpoint behind auth drives the player pages. CI can write projections.json after each model run, push it to S3 or your file system, and SleekRank consumes it on next cache flush. This is the standard pattern for sites running their own projection methodology.

Each data source has its own cacheDuration setting. Set it to match how often your model runs — typically a few hours so the Tuesday morning run is reflected before waiver-day traffic peaks. Flush manually right after a projection update if you want immediate propagation, or rely on the cache expiry for steady-state refresh. Most fantasy sites run a flush as the last step of their CI pipeline.

No. SleekRank renders pages from data your model produces. The projections themselves stay in your tooling — Python notebook, R script, third-party feed, in-house algorithm. SleekRank's job is the public publishing layer. This separation lets the model team iterate on methodology without touching WordPress, and lets the editorial team adjust page templates without breaking the data pipeline.

Yes. Use a page group per sport — NFL, MLB, NBA, NHL — each with its own JSON file or sheet and its own URL pattern like /nfl/players/{slug}/ or /mlb/players/{slug}/. Each group has its own template page, so per-sport stat fields and projection methodology are easy to handle. Multi-sport sites run this regularly with one WordPress install backing four or five sports.

Add an injury or status column to the source — 'questionable', 'doubtful', 'out', 'IR'. Map it via a selector mapping and the badge appears on every player page automatically based on the value. When the team announces a Wednesday injury report, update the column, flush the cache, and every affected player page reflects the new status within minutes. This is critical for Sunday-morning lineup decisions.

Every generated /players/{slug}/ URL is a real WordPress page added to the sitemap. The base template stays noindex'd so only the player pages compete in search. This means jalen-holloway-rb and elena-ortiz-wr each get their own indexable URL targeting the branded player query, which is where most fantasy search traffic lives.

Add a row to the source as soon as a rookie debuts or a deep-roster player gets called up. The page generates on next cache flush, the sitemap picks up the new URL, and search engines index it within days. This is much faster than building a manual page, and it matches the cadence at which fantasy-relevant news breaks during the season.

Add salary columns per DFS site — DraftKings, FanDuel, Yahoo — to the source. Each Saturday or daily slate, your data pipeline writes salaries into the same row and the player page reflects current pricing. A separate page group for /dfs/slate/{date}/ can pull cross-cutting views of the same source if you want slate-level pages alongside individual player pages.