From your source — typically you compute them once into a sheet or JSON. SleekRank doesn't convert color values; it renders what's in the data. A small script that takes hex and produces RGB, HSL, CMYK, and contrast ratios runs once when the source updates. Open-source libraries like culori or color-convert handle the math reliably.

Yes. Use a type column (color or palette) in the source. Either share a template that conditionally renders palette swatches when present, or set up two URL patterns and templates for /colors/{slug}/ and /palettes/{slug}/ pointed at filtered subsets. Mixed approach works well: shared base template with a small conditional block for palette-only sections.

Compute them upstream against white, black, and your common foreground colors, store as columns, and inject the values into contrast cards via selector mapping. WCAG AA and AAA pass/fail labels can be calculated upstream too. SleekRank just renders the result; the math runs once when the source updates, not on every page request.

Yes. Each generated URL is added to the SleekRank sitemap. The base template is excluded and noindexed. Color queries are surprisingly competitive (named-color SERPs are crowded), but consistent on-page schema with hex, RGB, and contrast info helps rankings hold once they land.

Yes. Update the source — replace hex values, add new palette rows, deprecate old ones — and flush the cache. The next request rebuilds pages from the new values. For a major redesign, run a one-time crawl in staging to verify all pages render correctly before flipping the cache flush in production.

Yes. The base template is a normal WordPress page. Style it however you want — SleekRank only injects values into matched elements. Setting the hero background to a CSS variable (--swatch-color: #0047AB) lets your theme handle hover states, gradients, and animation while still pulling the right color from the source.

Add a mode column or duplicate rows with -dark suffixes (e.g. cobalt-blue-dark). Either approach works. The dark variant gets its own URL and contrast ratings are computed against dark backgrounds. For brand systems with paired light/dark tokens, store both in the same row and selector-map each into its own template block.

Yes. Add a type of "gradient" with from-hex, to-hex, and direction columns. Render the hero with a CSS linear-gradient using the values. Same template can handle solid colors, palettes, and gradients with a small conditional for the gradient hero.