Skip to content
Tutorials Center
My learning

Topics

Lesson 9 of 37 ยท Concepts and Setup

Brand Setup: Colors, Fonts and Assets

Set up a site's brand foundation first: color palette, contrast checks, fonts, image formats and sizes, naming and a style guide, then apply it with site themes, variables and swatches.

A site feels professional when colors, fonts and images behave consistently. The way to get there is to decide the brand foundation once, store it in the builder's central places, and then reuse it everywhere. Both tools support this: Wix has site design settings for fonts and colors, and Webflow has swatches, variables and classes. When the foundation is set up first, a rebrand later takes minutes, not days.

This lesson shows how to choose a palette, test contrast for accessibility, pick and load fonts responsibly, and prepare image assets that do not slow your pages. Stand-in programs let you compute things like contrast ratios and image sizes, which the builders only show you indirectly.

Define a palette

A practical palette has roles, not just colors.

Role Purpose Example
Primary Main brand color, buttons, links A strong blue
Secondary / accent Highlights, secondary buttons A warm orange
Neutral dark Body text, headings Near-black
Neutral light Backgrounds, cards Off-white
Feedback Success, warning, error Green, amber, red

Keep it small: one or two brand colors plus neutrals is enough for most sites. Write the colors as hex values (such as #1d4ed8) in a shared note.

Apply the palette in the builder by defining it centrally:

  • Wix: set the site's color palette in the site design area, so elements can reference theme colors. Changing a theme color then updates every element that uses it.
  • Webflow: create swatches or variables (color variables in the Variables panel) and use them in the Style panel instead of typing raw hex values. Variables can also hold sizes and fonts, and they can be switched in modes, such as light and dark.

Contrast: the accessibility basics

Text must be readable. The web accessibility guidelines (WCAG) measure this with a contrast ratio between text and background: at least 4.5 to 1 for normal text and 3 to 1 for large text (roughly 24px regular or 19px bold) at the AA level. Light grey on white fails for many people, even if it looks elegant on your monitor.

The ratio is computed from the relative luminance of each color. You never need to do it by hand: this stand-in does the arithmetic so you can check any palette pair before you commit to it.

JS Stand-in: WCAG contrast ratio checker

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Notice how the light grey on white and white on orange pairs look fine at a glance and still fail the normal-text test. Always check button labels, placeholder text and text over images.

Choose and load fonts responsibly

Fonts carry personality, and they also cost bytes. Guidelines:

  1. Use two families at most: one for headings, one for body text (or just one family in several weights).
  2. Prefer fewer weights. Each weight and style is another file. Regular and bold usually suffice.
  3. Check licensing. Webflow offers Google Fonts and lets you upload your own licensed fonts; Wix provides a font library and lets you upload fonts too. Uploading a font you do not have rights to is a legal risk.
  4. Provide fallbacks. The browser shows a fallback font while the custom font loads, so choose a fallback with similar proportions.
  5. Test readable sizes. Body text around 16px or larger is a good baseline.

The fonts also appear as variables or text styles. In Webflow, set the base font on the body and let everything inherit. In Wix, define the theme's text styles (heading levels and paragraph styles) and apply them rather than formatting each text box by hand.

Prepare image assets

Images are usually the heaviest part of a page. Prepare them before upload.

Format Best for Notes
JPEG Photographs Good compression, no transparency
PNG Graphics needing transparency Large for photos
SVG Logos, icons, simple illustrations Scales perfectly, tiny files
WebP / AVIF Modern general use Smaller than JPEG at similar quality; builders often convert for you

Practical rules:

  • Resize to about twice the displayed width at most (for sharp high-density screens), not to the full camera size.
  • Compress photos to a quality that still looks good, usually well below the original.
  • Give every image a meaningful alt text describing its content or purpose.
  • Use SVG for the logo.
  • Name files descriptively before uploading.

Estimate image weight

A rough estimate shows why resizing matters. The stand-in calculates the raw (uncompressed) pixel data size and a rough compressed size using an assumed bits-per-pixel figure. It is an approximation to build intuition, not a prediction.

JS Stand-in: image weight estimator

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The camera original is dozens of times heavier than a properly sized thumbnail, even though the thumbnail may be shown at a tiny size. Builders create several sizes of an image for you (responsive images), but they still need a sensibly sized source.

Build a one-page style guide

A style guide records your decisions: palette with roles and hex values, font families and weights, text sizes for each heading level, button styles, spacing scale, logo rules and image style. Webflow users often build a hidden style guide page inside the project that shows every heading, paragraph, button and form element. Wix users can do the same on a draft page. This page becomes a visual test: if you change a variable and the style guide page looks wrong, you caught a problem before it spread.

Generate a tint scale

Hand-picking lighter and darker versions of a color is slow. The stand-in below mixes a base color toward white and black to create a consistent scale, a technique often used for hover states and backgrounds.

JS Stand-in: generate tints and shades

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Common mistakes

  • Using five near-identical blues because each was picked by eye.
  • Putting text directly over a photo without checking contrast.
  • Uploading uncompressed camera photos.
  • Applying fonts element by element instead of in the site-wide text styles.
  • Forgetting alt text and meaningful file names.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What minimum contrast ratio does WCAG AA require for normal-size text?

    AA requires 4.5:1 for normal text and 3:1 for large text.
  2. 2. Which format is best for a company logo that must stay sharp at any size?

    SVG is vector-based, so it scales without losing quality and is usually very small.
  3. 3. Why define colors as variables or theme colors instead of typing hex values everywhere?

    Central definitions turn a rebrand into a small edit and keep the site consistent.
  4. 4. What is a sensible limit for font families on a site?

    Fewer fonts and weights mean fewer downloads and a more consistent look.

Summary

  • Set up a small, role-based palette, one or two font families and a style guide before building pages.
  • Store brand values centrally: site design settings in Wix, swatches and variables in Webflow.
  • Check contrast (4.5:1 for normal text), and never rely on how colors look on your own screen.
  • Resize and compress images, prefer SVG for logos, and always write alt text.
  • Fewer fonts and weights make pages faster and more consistent.

Next: Classes and the Box Model in Webflow