dardo
ESLet’s talk ↗

Inside the studio

Inside Dardo’s website: from content to a received inquiry

A working example of how we connect a multilingual publication, browser tools and project intake. Explore the actual components of this site and the decisions behind them.

01

Content that is available before interaction

Dardo’s editorial pages are generated as HTML with Astro. Services, project notes, articles and country guides share a content model, but each page has its own purpose and related next steps. The English and Spanish versions link to their equivalents, and the sitemap lists the public publication rather than internal experiments.

02

Tools that preserve the decision

Country guides connect to a timezone planner and a downloadable checklist. The budget planner keeps the selected market in the shareable scenario. Naming and industry worksheets prepare an editable brief that can continue into a project inquiry. The tools work in the browser and do not require an email to download a result.

03

A receipt that represents something

The inquiry form sends to a Cloudflare Worker and shows success after a record is stored in a private D1 database. Repeated attempts with the same receipt are deduplicated. The inbox separates new, qualified, won and test inquiries so implementation checks do not masquerade as customer demand. This describes the system; search rankings and client outcomes require their own measured evidence.

From an idea to something real

Make your next
move matter.

Start a project ↗Explore the project planner →