The January 2025 Systm Web resolutions note mentions clearing accumulated computer gear, considering Hugo or Astro for a site rebuild, and making time for writing. The technical thread is easy to miss in a personal list. Choose one useful result that could be finished while the existing site still works.
Use a page with a job to do
For an editorial site, pick one existing article with an image, an internal link and a stable address. Copy it to a separate prototype and try the normal editing steps, from changing the headline through previewing the page on a phone. Record how the new workflow handles the old URL, title, image description and publication date. These are small checks with a clear result.
If a tool makes the layout pleasant but editing becomes cumbersome, give the editing problem its own test. Can you update two links and the image without having to rebuild your mental model of the whole site? For comparison, try the same edit on the current WordPress copy. Put both observations in a short log before deciding whether the prototype is worth extending.
Keep what the project actually needs
The next archived note considered much larger NAS storage. That juxtaposition is a good prompt to specify a real requirement. A storage project might need room for backups and reliable recovery, while a new writing project might only need a folder and a quick route from draft to published page. Estimate the storage and recovery work separately before adding hardware. Storage expansion and recovery example
Keep one dated entry for the trial containing the task, the evidence and the decision. That gives a future project a starting point even if this one stays small. If the test progresses to a real migration, work from the migration plan and account for edits made during the move.
Archive sources
The February capture of the January 1 resolutions supplies the original project ideas. The January 2 NAS note refers back to the earlier post. The prototype steps here are an editorial example.