pl8ypus
Systems / Segunda Escolha

Build 14 / Bilingual website delivery

Two languages.
One maintainable website.

A Portuguese and English communications website, organised into editable source pages, shared assets, explicit routes, and a repeatable Cloudflare Pages build.

Live bilingual website Portuguese / English Static HTML Node build Cloudflare Pages

Published 26 October 2026 · Repository evidence through 9 October 2026

Greg's take

Publishing is only part of the job.

A website also needs to make sense to the person who edits it next. With two languages and a growing page set, that means knowing which file owns each URL and which assets are shared.

The October work organised the existing production pages into an editable repository and a repeatable build. It creates a practical handover: change the source, preview the result, then publish the generated output.

The system

How the pieces fit together.

Content

Two language routes

Portuguese is the default experience, with English under /en/. Both public homepages were reachable during the 26 October website review.

Source

Editable pages and shared assets

Named HTML files hold page content. Shared styles and scripts live together, while routes.json maps each source file to its published destination.

Delivery

A small build pipeline

A Node build produces dist for Cloudflare Pages. The repository requires no dependency installation for this build, and the local preview uses the same generated output.

Build journey

From the first useful slice to the latest change.

01 / Starting point

Work from the available production pages

The repository records that the editable HTML came from the v10 production distribution. The original generator was not supplied, so the maintainable source is the recovered page set and shared assets.

02 / October organisation

Make the editing path explicit

The 9 October commit introduces the editable website structure and Cloudflare Pages build. Source-to-route mapping keeps filenames and public addresses connected without editing generated output.

03 / Public delivery

Verify both language entry points

The Portuguese homepage and /en/ returned successful public responses on 26 October. The site includes language navigation and a contact lightbox. This review did not submit a contact form or verify message delivery.

Evidence and limits

A live delivery with a clearer maintenance path.

The repository documents the source layout, route mapping, build command, preview command, and Cloudflare Pages output directory. Public checks confirm that the Portuguese and English entry points are reachable. These checks establish website availability, not commercial results or the accuracy of every content claim.

Current limits

Email configuration is explicitly deferred in the repository. Contact-form delivery and the full bilingual content set were not revalidated in this review. References or examples on the agency website are not treated here as evidence of client relationships or delivered business outcomes.

Source review: committed implementation and project records at 61d3018f, reviewed 26 October 2026. Private source, operational data, and credentials are not published with this story.

What the build taught us

The next step follows the evidence.

The result is a public bilingual site with an understandable editing and publishing workflow. The next maintenance work is content parity, route checks, and end-to-end contact verification.

Build something useful

Have a workflow that needs this kind of care?

Start with the problem, the constraints, and what a useful result would look like.