What You’ll Produce 

• Header images for all non-blog pages 
  • One visual system, reused across page families with text variations (e.g., same technology header; text swaps: “React”, “Node.js”, etc.).
  • Exported for web (PNG/JPG/SVG as appropriate), named and organized by page reference. 
• 17 reusable blades 
  • Designed once, built as Spectra/Gutenberg components: hero variants, trust bars, services cards, step/process, case study highlight, KPIs, tech stack grid, comparison tables, testimonials, FAQs, CTA bands, contact modules, etc. 
  • Clear guidance on when/how to use each blade. 
• 25 page-type designs 
  • Desktop + mobile comps for each type; each type specifies which blades and in what order. 
  • Consistent spacing scale, grid, and type ramp. 
• Full WordPress implementation 
  • Assemble every non-blog page using Astra/Spectra to match the designs (no improvising). 
  • Wire in our internal/external links (links will be provided). 
  • Media library organized; final image weights sensible. 

Note: Accessibility and localization are not in scope right now. 

Day-to-Day 

1. Design the 17 blades and 25 page types in Figma. 
2. Produce a header image system and batch the variations (text swaps per page family). 
3. Build the blades in WordPress (Astra/Spectra) and assemble the pages according to the matrix. 
4. Drop in our approved copy and crosslinks; adjust spacing for mobile. 
5. Keep an assets + page mapping sheet up to date (we’ll provide the refs). 

Inputs You’ll Receive 

• Brand style guide (colors & typography, including Outfit). 
• Final page text for all pages. 
• Crosslinks & external links list. 
• Blog header images. 
• Creative Matrix with the 25 page types and 17 blades. 
• Sitemap with reference numbers and URLs.

Must-Have Skills

• 3 to 5+ years web/UI design and WordPress build experience (Gutenberg). Hands-on with Astra + Spectra (or very similar block libraries). 
• Figma power user: components, variants, Auto Layout, responsive thinking. 
• Strong visual craft: layout systems, spacing, hierarchy, and clean typography. 
• Asset production: creating a header image system, text-over-image treatments, and templated variations; solid image optimization workflow. 
• Comfortable with light HTML/CSS to finesse Gutenberg spacing/tables/responsive quirks. 
• Organized: can work from CSV/Google Sheets and keep manifests current. 

Nice-to-Haves 

• Batch/templated graphics skills (Figma components, Photoshop actions, or similar for rapid text swaps). 
• Light illustration/icon tuning. 
• Familiarity with Core Web Vitals hygiene (not primary right now).

Success Looks Like 

• Pages match designs 1:1 across desktop and mobile. 
• Headers feel cohesive across the site; text variations are consistent. 
• Blades are truly reusable, drop-in consistent across page types. 
• Build is tidy: predictable block structure, consistent spacing, clean media library. 
• Steady throughput against a shared page-ref checklist. 

Deliverables Checklist 

• Figma file: 17 blades, 25 page-type comps, header system, mobile variants. 
• Exported header images (all non-blog pages) with naming that matches our refs. 
• WordPress staging site with all non-blog pages implemented. 
• Short how-to: which Spectra blocks/settings map to which blades, spacing tokens, and the header text-swap process.