Read the background material behind the tools so you can choose formats, compare palettes, and move from quick experiments to implementation-ready decisions.
These articles are designed for people who need more than a single tool result. They explain why one format is easier to maintain than another, how to judge extracted colors before using them in a UI, and what to check before saving a value into CSS, a token file, or a design handoff.
Learn the tradeoffs between HEX, RGB, RGBA, and 8-digit HEX. This guide explains when each format is easier to read, when transparency should be encoded directly, and which mistakes tend to happen during design-to-code handoff.
Understand how to turn extracted colors into practical UI decisions. This guide covers how to assign roles to palette colors, where contrast checks fit into the process, and when a palette needs refinement before it becomes part of a system.
Review how hexadecimal notation maps to red, green, and blue channels so you can explain conversions clearly during development and handoff.
Read the HEX and RGB guideCompare the two most common transparency-friendly CSS formats and decide which one is easier for your team to read, store, and review.
Read the alpha format guideLearn a practical contrast review workflow for text, overlays, and accent colors before you ship palette decisions into a live interface.
Read the contrast guideRead when alpha-enabled HEX values are a good fit for reusable tokens and when a more explicit format is easier for review.
Read the 8-digit HEX guideLearn how to turn raw converted or extracted values into token names that stay understandable as a project grows.
Read the naming guideUse a practical checklist before moving values from design tools, browser inspection, or brand references into implementation.
Read the handoff checklistStart with the format overview, then read the HEX and RGB guide, and finish with the RGBA versus 8-digit HEX article if transparency is involved.
Start with the palette workflow guide, then review the contrast basics and token naming article before saving final implementation values.
Open the design handoff checklist after choosing your final format so the stored values remain easier for teammates to review and reuse.
Use the directory page for a full overview of the tools, guide articles, and policy pages without leaving the public site structure.
Read a guide first if you are still deciding which format or palette direction you actually need. Context saves time before you start copying values.
Use the tool for the fast conversion or extraction step, then come back to the article when you need a more durable implementation choice.
Treat the final step as documentation. The tool helps you move quickly, while the guide helps you store the result in a way your team can understand later.
If you already know what you need, jump directly into the interactive pages and come back to the guide library whenever you need more context.
Tools are good at producing answers, but guides are better at explaining decisions. Static pages make the site easier to understand before JavaScript runs, give search engines more context, and help visitors judge whether a tool fits their workflow.