Legacy web pages to USWDS, in one click

BIG-BUILD reads your old HTML straight from a Git repository, recognizes the patterns that 1990s and 2000s sites were built from, and rewrites every page as clean, accessible U.S. Web Design System markup.

Source and target live in your own GitHub repo: old pages in legacy/, results in uswds/
Ten legacy patterns mapped to ten USWDS components, from hero banners to step indicators
Section 508 / WCAG 2.1 AA fixes built in, with a before-and-after 508 score for every page
Every run is a single Git commit, plus a printable migration and 508 report
Deterministic engine: the same input always gives the same output, ready for review

How it works

From a folder of legacy pages to a modern, consistent site in under a minute.

Connect a repositoryPoint BIG-BUILD at a GitHub repo. Legacy pages and images go in legacy/, or drag and drop them in.
Detect legacy patternsFont tags, layout tables, marquees, image buttons and CGI forms are found and classified.
Rebuild as USWDSEach pattern becomes the matching USWDS component, inside a shared header, side nav and footer.
Commit and reviewAll pages land in uswds/ in one commit, with a 508 score and flags for anything a person should check.

What changes on each page

The sample site has ten pages. Each one is built around a different legacy habit, and each comes out as a different USWDS component.

<TABLE HEIGHT=220 BGCOLOR>HeroHome page banner and call to action

<INPUT onClick>, image buttonsButtonPrimary, secondary, outline, big, disabled

Row of image boxes, “More >>”Card groupWith descriptive link text

<MARQUEE>, coloured boxesAlertEmergency, success, warning, error, info

<DL><DT>Q<DD>AAccordionKeyboard and screen-reader ready

<TH> table, grey rowsTableStriped and sortable

/cgi-bin form in a tableForm controlsLabels, select, radio, checkbox

Numbered coloured cellsStep indicatorComplete, current, upcoming

Image + text news rowsCollectionHeadline, summary, date

<OL> of bold milestonesProcess listTimeline of key events

Built for large content estates

Start with ten pages, then run the same engine across thousands.

Accessibility first

Headings in order, labeled fields, scoped table headers and alt text, with anything uncertain flagged for review.

Your repository, your history

Nothing is stored outside Git. Every migration is a reviewable commit you can diff, approve or roll back.

Ready for a CMS

Clean USWDS markup is the same structure Drupal and other CMS themes expect, so import is straightforward.