A useful portfolio changes as the work changes. For me, that means connecting my background in development, SEO, and testing with the applications and AI tools I am exploring now.
This website began as a custom WordPress portfolio. Its personal logbook idea still fits: a place for projects, notes, and milestones, rather than a page that needs to be rewritten whenever something moves forward.
Make room for the process
Projects have a status: Planned, In progress, or Completed. A status needs context. For an application, that might include what already works, what remains to be built, and where someone can see the code or try a demonstration.
The current portfolio project explains its publishing architecture and migration work. Future projects can use the same structure while keeping the details specific to the problem they address.
Keep information in one place
The new direction stores content and code together in GitHub. A project’s title, description, technologies, and body have one source. Page templates can use those details on both a project listing and an individual project page.
This makes a practical difference to updates. If I change a project’s description, I want that edit to reach every place that uses it. Repeated manual edits are easy to miss, especially as the website grows.
Publish when there is something to share
The notebook is intended for material connected to my own work: a decision, a question, a problem, or a lesson. It does not need a daily article quota.
New project updates will come from my instructions or from releases in a repository I have selected. That gives each update a clear source and keeps the website connected to actual activity.