Generated 495 pages from a SQLite export
Generated 495 achievement pages across three languages from a
read‑only SQLite export, with the page address authored as data so
that correcting a sentence no longer moved the page and broke the
link.
August 2026

Situation. The company's portfolio content is authored in a separate
database — the same one that produces the CV — and the website has
to publish it as pages, in three languages, without the two copies
drifting apart. The naive approach, writing the pages by hand and
keeping them in step, fails on the first correction.

Task. The website had to generate its content from the database as a
build input, with page addresses that survive the sentences on them
being rewritten.

Action. An exporter reads the database read‑only and writes one page
per achievement per language — 495 pages — plus the taxonomy and
services data the templates need. It uses only the standard library,
so the site's build has no dependency on the generator's
environment, and the committed output means the site builds
standalone. The single most consequential decision in it concerns
addresses. The site used to derive a page's URL from the leading
words of its English statement, so correcting a sentence silently
moved the page and broke every link to it — a site whose argument
for itself is that it corrects things, charging itself a dead link
every time it did. The address is now authored as data: one row per
address per achievement, the first is current and every later one is
a retired address the site emits as a redirect. Two other traps are
recorded from the same work. A period comparison against a text
column silently matched all thirty‑two rows because of how the
database assigns type affinity across a comparison. And the language
list is now the single axis the write loop, the data files and the
queries all derive from, so adding a fourth language is one map
entry rather than a search.

Result. Four hundred and ninety‑five pages generate from one source,
correcting a statement costs nothing, and the addresses this site
has ever published continue to answer. The exporter also owns
exactly one presentation decision — how services group into themed
sections — and that is deliberate: everything else it writes is the
database's, and a group heading missing a language fails the export
rather than rendering English over translated content.

Categories:
1Frontend Engineering	/categories/frontend/	brand.engineer.company	70
1Web Development	/categories/web-development/	brand.engineer.company	70
1Databases	/categories/databases/	brand.engineer.company	70
1SQL	/categories/sql/	brand.engineer.company	70
1Data Pipelines (ETL/ELT)	/categories/data-pipelines/	brand.engineer.company	70
1Python	/categories/python/	brand.engineer.company	70
1Internationalization	/categories/i18n/	brand.engineer.company	70

Services:
1Website Development & CMS	/services/web-development/	brand.engineer.company	70
1Internationalization & Localization	/services/i18n-localization/	brand.engineer.company	70
1Data Pipeline Development (ETL/ELT)	/services/data-pipeline-development/	brand.engineer.company	70
1AI Data Readiness	/services/ai-data/	brand.engineer.company	70
1Brand, Marketing & SEO	/services/brand-marketing/	brand.engineer.company	70

hThis page on the web	URL:https://brand.engineer.company/portfolio/generated-495-pages-from-a-sqlite-export/	brand.engineer.company	70
