# 000005 - Website & documentation architecture *Document code: LES-JOUR-000005 | Phase 0 | 12–18 May 2026* *** Week 2 was infrastructure and planning — end to end. No modules were built. No code was written. No data flowed through any system. By almost every conventional measure of project progress, the week produced nothing. By every measure that actually matters for a five-year enterprise architecture programme, it produced an enormous amount. This distinction is worth sitting with. The instinct in any ambitious technical project is to build. To write code, deploy resources, create things that can be shown and demonstrated. Infrastructure, documentation architecture, governance frameworks, decision records — these feel like overhead. They feel like the work that happens before the real work begins. The assumption embedded in that feeling is wrong, and recognising it is one of the more important things that happened this week. A system built on a clear foundation is built once. A system built without one is built twice — the second time to fix what the first time got wrong. Week 2 was the investment in building it once. *** ## What Was Built The NikiDigitals website went from a single homepage to a complete six-page professional presence — built, styled, fully responsive across desktop, tablet, and mobile, and cross-linked across all four portfolio layers. The brand identity was formalised: Navy Night as the primary tone, Circuit Blue as the accent, Syne Bold for headings, DM Sans for body. The contact form was configured with authenticated SMTP email delivery confirmed. A portfolio that existed in fragments became a functioning unified system. The documentation architecture was significantly matured. Sixty-six architectural decisions were formally recorded across three dated ADR files. The master decisions table was restructured into a dedicated decisions index — scalable, searchable, and version-controlled. The project plan reached version 2.3. The master roadmap reached version 3.9. The GitBook Vision & Strategy section was fully populated with nineteen sub-pages across the project plan and roadmap — each written as a standalone document for a professional reader who arrives without prior context. Two new repositories were established — LES-DASH for the dashboard layer and LES-demo-data for synthetic data generation — bringing the confirmed repository set to eighteen. The diagramming standards were formalised: C4 Model for system architecture, BPMN 2.0 for process flows, ERD for data models, Azure Architecture icons for infrastructure, all in draw\.io. Security foundations were laid — Bitwarden adopted as the password manager, the Azure Tenant ID secured, and a secrets register created and committed to GitHub. The learning methodology was formalised. Every new technology or concept follows a five-step progression: Study, Discuss, Sandbox, Review, Apply. Sandbox projects are not throwaway practice — they are committed to GitHub as standalone portfolio evidence of the learning journey. No concept is implemented in LES until the Review step is complete. *** ## What Was Decided Two standing instructions were added to the mentor protocol that will govern every learning session for the remaining four years and eleven months of this project. The first: one journal entry per week, written at end of week, consolidating all sessions across all days. The week is the unit of reflection — not the session, not the day. The second is more significant. All learning questions are answered at global expert depth. The target is not practitioner-level understanding. It is not the understanding required to complete a deliverable or pass an examination. It is the deepest possible understanding of the subject that exists. This standard is set once and never lowered. The habits of understanding formed in Phase 0 determine the quality of everything built in Phases 1 through 5. *** ## The Observation That Defined the Week Most people skip this step. Infrastructure, planning, documentation architecture, governance frameworks, decision records — these are the parts of a serious project that are invisible to the outside world and genuinely difficult to sustain without a clear understanding of why they matter. The temptation is to move past them quickly, to reach the parts that feel like building. The projects that do that are the ones that get rebuilt. Phase 0 is close to complete. The foundation is not a plan. It is in place. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://nikidigitals.gitbook.io/les/10-the-journey/session-journal/000005-website-and-documentation-architecture.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.