An anonymised website-build account
From supplied Figma designs to a finished website
A web-development team used Beyond Better to turn supplied design images and owner-provided public copy into a website, while people remained responsible for every decision that went live.
An anonymous account of a specific project
This story concerns an established web-development team working on a website for a financial-services business. The business, its owner, the team, and the site are intentionally not identified. This is not an endorsement by them or a named customer story.
The project began with Figma design images and public-facing text copy supplied by the owner. The team used BB as part of its normal iterative building process, applying its own web-development experience and judgement as it worked from the supplied material.
How BB fit into the build
The tool supported the implementation work; it did not replace the people making design, content, and publication decisions.
1. Start with supplied material
Design images and public copy
Figma design images set the visual direction. The owner supplied the public text copy, which gave the team source material to review and place in the site.
2. Build and refine iteratively
Implementation with human judgement
BB generated HTML, CSS, and JavaScript for the application. The team reviewed the work, made iterative refinements, and used its standard web-building experience to decide what to retain or change.
3. Make final owner-led updates
Minor iterations after the build
The owner was able to use BB for minor final iterations, including copy changes and final image replacements, while retaining control over what was approved for publication.
A Fresh application, deployed through Deno Deploy
For this project, the generated HTML, CSS, and JavaScript formed part of a Deno Fresh application. The finished site was deployed to Deno Deploy.
These are implementation details of this build, not a recommendation or requirement for every project. The people responsible for a site still choose its architecture, hosting, and release process.
People stayed accountable
- • The owner provided the public text and approved final content changes.
- • The web-development team reviewed generated material and made design and implementation decisions.
- • The people responsible for the site remained responsible for its accuracy, publication, and any obligations that applied to it.
What this project reported
From the supplied Figma designs to the finished site, this project took a couple of days. The account contrasts that with the multiple weeks it might otherwise have taken for this particular project.
The owner’s development cost was a few hundred rather than a few thousand. That comparison is an account of this build’s circumstances, scope, and decisions; it does not predict costs, timing, or results for another project.
Generated material still needs meaningful human review. Before publication, responsible people need to check the design, public copy, facts, images, technical implementation, and anything else required for their own site.
Bring your website project into the build process
Start with the materials you have, work through the implementation, and keep people responsible for the decisions that matter.