Review Your Report

Before anything is built, your design system is catalogued and a build plan is made. The few decisions that matter are asked right in the report. This is the report for this very site: read it, answer its ten decisions and submit it.

0 of 10 answered
FrameWorkerNovember 17, 2026
Pre-build design assessment

FrameWorker

Pixel perfect development in days


We reviewed every drawn page as one system, measured what is already consistent, and wrote down the few decisions that make it buildable once and reusable everywhere.

#007bff#0a0f1c#e6f2ff#ffffff

Prepared by FrameWorker · 4 page designs reviewed

Cover1 / 8
FrameWorker · Pre-build assessment

Executive summary

Eight systems were measured across the four drawn pages. Four are adopted exactly as drawn. The other four come down to the ten decisions in the margin, each one answered with a box.

TypeSandor and Arabesca adopted as drawn; the wordmark’s face need not load; the hero keeps its own two sizesDecisions 4 and 5
ColorBrand blue, ink, paper and the grid rule adopted; one soft grey sits below AADecision 9
SpacingThe 40px cell throughout; two section gaps off the grid; one named exception inside panelsDecisions 6 and 7
RhythmAdopted as drawn: the body line of 26px, headlines at 1.1
CornersNone. Squared throughout, adopted as drawn
ShadowsNone. Flat throughout; the focus ring is the one allowed
ImageryLine drawings and two portraits, adopted as drawn
NavigationThree linked pages undrawn, one menu link to settle, two states to addDecisions 1, 2, 3 and 10
5StandardizationsValues we tidy onto one set. Nothing moves more than a cell.
1AccessibilityOne contrast pair below AA, with a fix that keeps the look.
4Gaps to fillThings the designs don’t show yet. We propose a default for each.

Check one box per decision → sign the last page → we build the system once and every page rides it.

Executive summary2 / 8
FrameWorker · Pre-build assessment

Your decisions (1 of 5)

GapDecision 1 of 10

Add the three pages that are linked but not drawn?

The nav links Pricing and the footer links Privacy and Terms. None of the three has a design.

What you drew4 pagesHome, Your CMS, Hosting, About
What we’d build4 + 3Pricing from the inner-page template; Privacy and Terms as plain text pages
If you approve
We build the three from the inner-page template and you fill the copy in the CMS.
If you keep it as drawn
You send designs for the three before the build starts.

Applies to Pricing, Privacy and Terms.Never changes The four pages you drew.

GapDecision 2 of 10

Does “How it works” open a page or scroll the home page?

The header links How it works, Your CMS, Hosting and About. How it works has no page; the home page has the section.

What you drew4 linksOne of them to a section of the home page
What we’d buildAn anchorHow it works scrolls the home page to its steps
If you approve
How it works scrolls to the steps on the home page; a page can follow later.
If you keep it as drawn
You draw a How it works page and the link goes there.

Applies to The one header link.Never changes The header’s layout, wordmark and Contact button.

Your decisions (1 of 5)3 / 8
FrameWorker · Pre-build assessment

Your decisions (2 of 5)

GapDecision 3 of 10

The same footer on every page: the copyright line and two legal links?

The footer is drawn once, on the home page: © FrameWorker, Privacy Policy, Terms and Conditions.

What you drew1 of 4The footer appears on the home page only
What we’d buildEvery pageOne footer, editable once, on all of them
If you approve
The home page’s footer becomes the one footer, editable once in the CMS.
If you keep it as drawn
You draw the footer for the other pages.

Applies to The footer on every page.Never changes The home page’s footer as drawn.

StandardizeDecision 4 of 10

Load three typefaces, not four?

Sandor on headlines, Arabesca on the one script word, a mono on body text, and Rawest on the wordmark only.

What you drew4 facesSandor · Arabesca · the mono · Rawest (the wordmark)
What we’d build3 facesThe wordmark ships as drawn outlines; Rawest is not loaded
If you approve
The wordmark is an SVG of its outlines; three font files load, not four.
If you keep it as drawn
Rawest is loaded on every page for the one word.

Applies to The wordmark.Never changes Every headline, the script word and the body text.

Your decisions (2 of 5)4 / 8
FrameWorker · Pre-build assessment

Your decisions (3 of 5)

StandardizeDecision 5 of 10

Headlines on one scale from 64px, stepping by 1.25?

Headlines are drawn at 120, 72, 64, 52, 40, 32, 26 and 22px. All but the hero’s two sit on one ladder.

What you drew8 sizes120 · 72 · 64 · 52 · 40 · 32 · 26 · 22
What we’d build6 + 2The ladder 64 · 52 · 40 · 32 · 26 · 22, the hero’s 120 and 72 named as its own
If you approve
Six headline steps on one scale; the hero keeps its two sizes as the one exception.
If you keep it as drawn
Every headline size becomes a setting of its own.

Applies to Every headline on every page.Never changes The hero headline and the body text.

StandardizeDecision 6 of 10

Put the space between sections on whole 40px cells?

Sections sit 80, 120 and 160px apart, except two at 100 and one at 60.

What you drew5 gaps60 · 80 · 100 · 120 · 160px
What we’d build3 cells80 · 120 · 160px, every one on the grid
If you approve
The three off-grid gaps move to the nearest cell, at most 20px each.
If you keep it as drawn
All five gaps are built as drawn.

Applies to The space above and below every section.Never changes The space inside sections.

Your decisions (3 of 5)5 / 8
FrameWorker · Pre-build assessment

Your decisions (4 of 5)

StandardizeDecision 7 of 10

Keep the panel’s 30px inner padding as the one off-grid value?

Boxes use 20 and 40px inside, the cell and its half. The contact panel and the form fields use 30px.

What you drew20 · 30 · 4030 appears in two places
What we’d buildNamed30px kept, named “panel padding”, used nowhere else
If you approve
The 30px stays, as one named value the panels share.
If you keep it as drawn
The panels move to 20 or 40px like every other box.

Applies to The contact panel and the form fields.Never changes Every other box and its padding.

StandardizeDecision 8 of 10

One column of 1200px, thirty cells, that rounds down to whole cells on smaller screens?

Every page is drawn at 1200px. On a 1280 screen the column would land between grid lines.

What you drew1200pxOne width on every page
What we’d build30 cells1200 capped; below that, the width rounds down to whole 40px cells
If you approve
The column is always a whole number of cells, so every box lands on a grid line.
If you keep it as drawn
The column is a plain 1200px; the grid is not guaranteed to line up on small screens.

Applies to The content column on every page.Never changes The hero’s script word, which bleeds to the column edge.

Your decisions (4 of 5)6 / 8
FrameWorker · Pre-build assessment

Your decisions (5 of 5)

AccessibilityDecision 9 of 10

Darken the soft grey used for the ledes and the footer?

The soft grey on white measures 4.2:1. The AA rule for small text is 4.5:1.

What you drew4.2 : 1The soft grey on paper — just below AA
What we’d build5.3 : 1One step darker on paper — passes AA
If you approve
The ledes, captions and footer links use the darker grey and pass AA.
If you keep it as drawn
The grey stays as drawn and the site does not meet AA for small grey text.

Applies to Ledes, captions, footnotes and the footer.Never changes Body text and headlines, which are ink.

GapDecision 10 of 10

Add focus and disabled states for the buttons and the contact form?

Buttons and fields are drawn at rest and on hover only. The system allows no shadows except a focus ring.

What you drew2 statesRest · hover
What we’d build4 statesRest · hover · focus (a 2px brand-blue ring) · disabled (40%)
If you approve
Focus is the one ring the system allows; disabled is 40% opacity. Both squared, like everything else.
If you keep it as drawn
You draw the focus and disabled states before the build.

Applies to Every button, link and form field.Never changes The rest and hover states you drew.

Your decisions (5 of 5)7 / 8
FrameWorker · Pre-build assessment

Sign-off

Every decision above has a box. When all 10 are checked, sign here and the build starts from this report. Anything you want changed later is a change to the report, never a surprise in the build.

  1. Site architecture
  2. Header menu
  3. Footer menu
  4. Typefaces
  5. Text sizes
  6. Space between sections
  7. Space inside components
  8. Content width
  9. Light backgrounds
  10. Focus and disabled states
Sign-off8 / 8

A real report carries the full catalogue too: every colour, type step, corner and gap measured from your file, the page map and the block build plan. The decisions are the part that needs you.