Background
Waymarks began as a place for personal landmarks rather than daily posts: a journey, a relationship, an album played repeatedly, or a project finally begun.
Problem
Conventional blogs flatten unlike experiences into one article feed. Waymarks needed room for long chapters, evolving projects, and shorter technical or professional notes while still feeling like one book.
Constraints
The road, mist, and open space of the original homepage already defined the site’s character. Expansion could not turn it into a card-based portfolio or let technology labels overpower the personal story. Chinese and English also needed stable relationships and clear URLs.
Approach
I used Astro content collections to build one entry model with three meanings: chapter, project, and note. Every page keeps the same cool white, forest green, rust route line, literary serif, and open dividers. Projects simply gain enough structure to explain their process.
Delivery and iteration
The first release established the bilingual static site, content routes, RSS, and Sitemap. This iteration adds a project entry point, a mixed chronicle, and combined archive filters while preserving existing chapter URLs and the original opening composition.
Result
Waymarks can now keep not only life’s turns, but also how something was understood, made real, and allowed to grow. It remains a private changelog with a broader vocabulary.
Reflection
Content architecture should not begin with the number of sections. It should begin with why these things belong to the same life. If that stays clear, technical and professional writing does not have to diminish the site’s warmth.