BUILD NOTES / OCTOBER 2026
Site structure, AI collaboration, and lessons learned.
Each revision has been an opportunity to learn how to specify changes, evaluate the output, and keep the site useful as the content grows.
Organizing the site for faster reading
Give each page a clear job.
As experience narratives and project notes accumulated, the site became harder to scan. I separated professional experience from About, shortened the Home page, and moved detailed project work into the Dev Log.
- Home: a short introduction, selected evidence, current projects, and the kinds of work I am seeking.
- Work Experience: reverse chronological history, education, and expandable examples from Flow, HoloLens, Halo Infinite, and Litesprite.
- About: how I think and work, a little personal context, and contact details.
- Dev Log: project summaries first, with implementation notes and learning available when the reader wants more detail.
Other revisions made names more straightforward, aligned shortcut links with the experience order, and preserved direct links into longer examples. These are implemented design choices, not evidence of a measured improvement in recruiter behavior.
ChatGPT Sites: useful features and limits
Useful features, with review still required.
In this project, Sites has supported conversational page creation and revision, multiple pages, shared styling, expandable sections, internal links, and publication. That makes it practical to turn an idea or feedback into a working revision and refine it further.
Limits I have encountered in the process
- More content can weaken the result. Repeated additions created a need to simplify the page structure and decide what belongs in the first reading pass.
- Generated wording still needs evidence. I need to check dates, ownership, outcomes, and whether a capability is implemented, partially tested, or only planned.
- A change can affect other pages. Renaming projects, moving education, or changing chronology also requires checking navigation, repeated summaries, and existing links.
- Publication is not the same as validation. A deployed version still needs visual and usability review. Audience settings also need to match how I intend to share it.
These are observations from building this site, rather than a comprehensive benchmark of Sites. The current portfolio presents experience and project evidence; it does not run the job tracker or the Telegram assistant.
A clearer way to collaborate with AI
Specify the purpose of a change, identify the pages it affects, provide the source facts, and review the result against those requirements. Small, focused revisions make it easier to notice drift and preserve a consistent voice.
Next checks: usability, mobile layout, and access
Test the reading path.
The next useful check is whether someone unfamiliar with my work can quickly identify my relevant capabilities, find a supporting example, and locate contact information. Mobile readability, navigation, and visitor access also need review.
Keep new updates concise and tied to actual work. Record usability feedback before claiming that a layout change improves engagement or job-search outcomes.
Technologies: ChatGPT Sites, generated HTML, CSS, and JavaScript. Learning focus: requirements, information architecture, AI collaboration, content validation, and publication boundaries.