---
title: "I updated teqfw.com with Codex"
description: "The site runs on TeqFW. I worked on the page with Codex using ADSM. The update required a lot of context, specifications, code, templates, and static assets."
date: 2026-05-01
display_date: "May 1, 2026"
image: "/img/blog/2026/20260501-02-teqfw-site.png"
image_alt: "I updated teqfw.com with a Codex agent"
---

# I updated teqfw.com with Codex

<zoom-img src="/img/blog/2026/20260501-02-teqfw-site.png"
        alt="I updated teqfw.com with Codex" width="100px"></zoom-img>

I updated my [teqfw.com](https://teqfw.com/) site, starting with
        the home page and the related materials.

The site runs on **TeqFW**. A Codex agent assembled the page code, copy, layout, and markup.

The work was done together with the Codex agent using my ADSM method,
        `Agent-Driven Software Management`.

The source material for this update came to:

`440 KB` - project context, that is, documentation;

        `512 KB` - TeqFW and SSR site specifications;

        `77 KB` - application code for processing templates with Nunjucks;

        `80 KB` - template text, that is, markup and pages;

        `160 KB` - static assets, including images.

The practical takeaway is simple: with this kind of workflow, documentation needs to outweigh code by a
        noticeable margin. That gives the agent a clearer frame and makes it easier to build the result step by
        step.