Purpose
The Technical Notes page records how the MGU website works behind the scenes. This includes components, scripts, CSS architecture, search and indexing tools, deployment behavior, local testing, and troubleshooting discoveries.
Use this section when the main value is a technical explanation rather than a public announcement or visual design choice.
What to Record
Technical notes should explain systems clearly enough that they can be repaired, extended, or reused later. They should describe the relevant file paths, scripts, dependencies, observed behavior, and fix strategy.
Useful entries may cover dynamic header and footer injection, breadcrumb JavaScript, bottom navigation, PowerShell maintenance scripts, Python utilities, SQLite indexing, Cloudflare or Netlify behavior, and local server testing.
Suggested Entry Types
Debugging notes, component explanations, script documentation, architecture decisions, deployment observations, database notes, and tool-specific lessons all belong here.
When possible, include the exact symptom, the likely cause, the tested fix, and the validation result.
Connection to the Devblog
Technical Notes turns hidden site infrastructure into readable documentation. It helps MGU remain maintainable as the number of pages, sections, scripts, and workflows increases.