The problem
A personal website has to introduce its owner quickly while leaving room for work that needs explanation. An early portfolio can also blur together examples, prototypes and completed work. This site needed a clear professional introduction, accessible project links and an explicit boundary around private family research.
Role and scope
Michael is the site owner and editorial decision-maker. The implementation is AI-assisted. This account describes the site’s observable content and structure, not a claim of sole authorship of every line of code or a measured improvement in conversion.
Design decisions
Start with a short professional introduction
The opening describes Microsoft 365 administration, software connections and technical communication in plain language. The longer background sits in an expandable section. A visitor can get the basic introduction immediately and choose whether to read more. [1]
Make project types easy to distinguish
Mosaic Together has its own playable-project card and direct game link. Before this expansion, the two case-study cards were explicitly labeled draft outlines and included Status and Evidence fields. The revised section replaces those placeholders with detailed accounts and retains visible scope and evidence information. [2]
Keep personal and professional boundaries visible
The family-history section states that private research stays unlinked and only specifically approved public material belongs there. That boundary is part of the page itself. It lets the site introduce a personal interest without exposing the underlying private collection. [1]
Use a small, inspectable implementation
The site is static HTML and CSS. Native disclosure controls provide expandable content without an additional script. The source includes a skip link, visible keyboard-focus styles, semantic headings and layouts that change from two columns to one on smaller screens. These are implemented features; they do not by themselves establish full accessibility conformance. [2]
What can be verified
The delivered artifact is the website itself: a profile, project navigation, detailed case-study pages and a contact link. The implementation makes the distinction between a project’s purpose and its supported result visible to the reader. No analytics study, user research, usability score or business-impact measurement is claimed.
The lesson
Progressive disclosure is useful when the short version remains accurate. A project card should say enough to set expectations; the full account should explain the problem, choices, evidence and remaining limits. Keeping those layers consistent is an editorial task as much as a layout task.
Sources and scope
[1] Michael Oakes homepage — the profile, professional focus and public family-history boundary are directly inspectable.
[2] Implementation review, November 5, 2026: the saved version-7 HTML and matching Notion layout records were inspected before this expansion. The current page exposes the resulting structure. These records support the design history, not performance or accessibility certification.