Why this matters
A personal site changes shape when it can be updated by both a human and an agent. The important point is not automation for its own sake. The point is to make judgment, review, and publishing cadence easier to maintain over time.
The site needs to hold ideas, projects, source trails, drafts, and release decisions in one understandable surface. Once those parts exist, OpenClaw can help refresh or prepare content without taking control away from the editor.
Working model
- Articles stay in explicit draft, review, published, or archived states.
- OpenClaw can propose refreshes, summaries, and source checks.
- Publication remains a deliberate action with rollback and audit history.
- Public pages should use the same content shape that the future API will expose.
Product direction
The website should behave like a small publishing system before it becomes a full management product. Static content files are enough for the first step because they force the content model to stay visible, inspectable, and version controlled.
The next layer is an admin surface where a human can assign a content job, inspect the result, talk through uncertainty, and publish only after the reasoning is clear.