Give your site a design direction

Left to itself, an assistant builds the page every assistant builds. NibWP Design decides how a page should look before anything is built, and it decides it from your site rather than from a template. It is free on every install.

• Your assistant calls the design direction ability before it builds a page, section or component. You should not have to answer "what colours would you like".
• It reads what the site already has: your ACSS variables, the theme.json palette and type scale, and the colours in your logo. Where the site says nothing, it falls back to a catalogue seeded per site, so two installs never start from the same place.
• What comes back is a direction: colour roles with contrast already checked and corrected to WCAG AA, a heading and body pairing with its scale, a spacing rhythm and a line measure, shape language for radius, shadow and borders, and the section sequence that suits that kind of page.
• It also returns the generic defaults to refuse on that page, each with its reason — the centred hero stack, three equal cards in a row, one flat padding value throughout, body text run to the full width of a wide container.
• It names the builder this site uses and the tokens to express the direction in, so you get real elements and site tokens instead of pasted markup.
• The direction is remembered. Page two matches page one, which is what makes a site read as designed rather than assembled. Ask for a fresh look only when you genuinely want a different one.

NibWP Design never writes markup itself. It directs whichever builder does the work.

Full guide: How to: set a design direction