HLDD Builder
A web app I built where a client signs in and builds a High-Level Design Document section by section.
- Block types to build with
- 24
- Guided prompts built in
- 9
Next.js, Supabase, Python, python-docx, Vercel
A High-Level Design Document (HLDD) is the plan an eLearning course is built from. A developer builds the course from it, which means every field they need has to be there, labelled, with the designer’s words sitting against the labels. I wanted the outline locked, so that two designers could not hand over two different documents. The HLDD Generator, an earlier tool of mine, drafts the document from interview notes. The HLDD Builder is where a designer writes it themselves.
What I built
In the Builder the screen is the document. The printed template is already a labelled form on paper, and the app makes that paper live. There is no separate form to fill in and no preview to check afterwards. What a designer types is what prints.
- Seven steps
- The designer sets up the course, writes the objectives, builds the outline, fills the blocks, lists the files, writes the takeaways and exports. The export is one Word file on the template, and a PDF that holds the same document.
- 24 blocks
- A block is one thing on the learner’s screen: a paragraph, a set of tabs, an accordion, a knowledge check, a scenario. The designer picks the block first and then types into its fields, because the block decides what the fields are. Each block shows a drawing of how it looks on screen, so they are choosing a shape rather than a code.
- AI as a co-author
- A new course opens on a prompt for Microsoft Copilot. The designer attaches their source documents, and Copilot interviews them through seven checkpoints and waits at each one. What comes back fills the overview, the objectives, the outline and the blocks in one pass, and the designer sees what will fill before anything does. After that, every part of the document has its own prompt button, nine prompts in all.
- Accounts
- Every designer signs in and sees only their own courses. Sign-up needs an invite code, and the database checks it, which means the rule holds even if somebody goes around the app.
Why the warnings never stop the designer
The Builder counts what is still open: an empty field, an objective that no block covers, an objective that starts with “understand” (flagged because you cannot watch a person understand). The count in the corner is a list the designer can click, and every entry takes them to its row. The export always runs and says how many items were still outstanding.
Nothing a designer writes is thrown away either. If they change a block’s type after writing the copy, the row keeps what it can. Anything with no home in the new block waits at the foot of the row until they place it or discard it.
What it delivers
The Builder went live on 9 August 2026 with accounts for two people on a client’s learning team. Nine days later the first designer from outside the project took it from start to finish and found seven defects, and all seven were fixed in that round. The following night a full course came out as a Word file with all 19 overview rows and all four objectives character for character as they had been written. In November a colleague asked what it would take to use the Builder for technical maintenance courses. The 24 blocks stay as they are, and only the guidance around them changes.
