A Now Page for a Personal Website - Sharing What Matters at This Moment

A personal website can explain who we are, archive what we have made, and point visitors toward our best work. Yet those polished pages often miss a smaller, more human question: what has our attention right now? A now page answers that question with a dated snapshot of current projects, interests, routines, and priorities.

I think of it as the note stuck to a refrigerator door rather than a permanent plaque on the wall. It does not need to summarize an entire life. It only needs to be honest about the present, useful to people who care, and simple enough that updating it never becomes another abandoned project.

What a now page actually is

A now page is a public page, usually available at /now/, that describes what its author is doing or focusing on during the current season. The idea was popularized by Derek Sivers and has since been adopted by many people with personal websites. Unlike an About page, which tends to change slowly, a now page is deliberately temporary.

An About page might say that you are a developer, writer, or home-server enthusiast. A now page can say that you are migrating backups to restic, reading about small web communities, learning German, and trying to walk before breakfast. Those details provide context without requiring a stream of daily posts.

The format sits somewhere between a status update and a journal entry. It is calmer than social media because there is no algorithm demanding frequent activity, and more current than a biography because old priorities can be replaced without rewriting your identity. Visitors see one considered snapshot rather than hundreds of disconnected fragments.

Why the page belongs on a personal website

Personal websites are valuable partly because we control their pace. A now page strengthens that quality. Instead of filling a profile for a platform, we choose what deserves attention and how much context to give it. There are no required fields, engagement counters, or prompts asking us to post again.

It can also make conversations easier. A friend may discover that you are experimenting with a tool they use every day. A reader may recommend a book related to your current research. A potential collaborator can understand what kinds of work fit your available energy. The page becomes a small conversation starter, not a performance dashboard.

There is a benefit for the author too. Writing down current priorities forces a gentle review. If the list contains twelve supposedly important projects, it reveals the problem immediately. Like packing a small bag for a weekend trip, limited space makes us decide what we actually need.

What to include, and what to leave private

There is no mandatory template, but a useful page usually covers three to six areas. You might mention work in progress, something you are learning, a recent change in routine, media you are enjoying, or a question you are exploring. Short explanations are better than unexplained lists because they show why each item matters.

A practical structure could include:

• Building: one or two active projects and their present stage.
• Learning: a skill, subject, or experiment receiving focused attention.
• Reading or listening: selected media that genuinely shapes your thinking.
• Living: a safe, broad note about routines, place, or personal priorities.
• Pausing: work you intentionally stopped, which can be as informative as active work.

Public does not mean complete. Avoid publishing a precise daily schedule, a live location, private health details, client information, or anything that could compromise another person. “Spending more time with family” communicates enough; names, addresses, and travel dates usually do not. Treat the page like a postcard sent openly, not a private diary left unlocked.

A small semantic HTML example

The implementation does not require a framework, database, or special widget. Plain semantic HTML is durable and accessible. A minimal page might look like this:

<main>
  <article>
    <h1>Now</h1>
    <p>A snapshot of what has my attention right now.</p>

    <h2>Building</h2>
    <p>Improving my personal publishing workflow and its backups.</p>

    <h2>Learning</h2>
    <p>Studying accessible design beyond automated test scores.</p>

    <h2>Reading</h2>
    <p>Essays about maintenance, ownership, and the small web.</p>

    <p><small>Last updated: <time datetime="2026-08-13">13 August 2026</time></small></p>
  </article>
</main>

The <time> element gives the visible update date a machine-readable value. That date matters: it tells visitors whether they are seeing a fresh snapshot or an old one. The page can remain useful when stale, but it should not pretend to describe “now” without revealing when now was.

Add the page to your main navigation only if it is central to the site. Otherwise, a link from the About page or footer is enough. The predictable /now/ path helps people who already know the convention, while descriptive link text such as “What I am doing now” helps everyone else.

Designing an update rhythm that survives

The most common failure is not bad design; it is an update process that asks too much. A weekly schedule may sound disciplined, but many lives do not change meaningfully every seven days. Monthly, every six weeks, or whenever your main focus changes can all work. Choose a trigger you can remember.

I prefer placing a recurring reminder on the first weekend of each month. The reminder is an invitation, not a deadline. I read the page, remove claims that are no longer true, adjust the date, and stop. A useful update can take ten minutes. If nothing has changed, changing only the date would be misleading, so I leave it alone.

Keep the editing path short as well. If publishing requires opening five services and rebuilding a complicated application, the page will age quickly. A single Markdown or HTML file in the same repository as the website is often ideal. The best content workflow resembles putting a book back on a nearby shelf: there is little friction between intention and action.

Archive old snapshots without creating clutter

Replacing the page discards a small piece of personal history. Over time, those snapshots can reveal changing interests and long-running themes more clearly than a calendar does. Consider saving each previous version under a dated archive, such as /now/2026-07/, before updating the current page.

An archive does not need prominent navigation. A simple “Previous updates” link near the bottom is sufficient. If maintaining separate URLs feels heavy, keep older versions in your Git history instead. The purpose is reflection, not building another content machine.

Be careful when archiving sensitive context. Information that felt harmless for one month may become revealing when combined across years. Review old snapshots occasionally, and remove details that no longer belong in public. Ownership includes the freedom to revise or delete.

A page about attention, not productivity

A now page can easily turn into a public checklist designed to prove that we are busy. That misses its most interesting quality. Rest, family, uncertainty, and deliberate pauses are valid parts of the present. “Reducing side projects” can be more honest and useful than inventing another impressive heading.

Write in ordinary language and resist turning every hobby into a measurable goal. The page should sound like an answer you would give a thoughtful friend over coffee. That voice makes it personal without making it confessional, and specific without becoming a résumé.

Conclusion

A now page is one of the smallest useful additions to a personal website. It provides fresh context, encourages better conversations, and creates a lightweight record of how attention changes over time. Start with three sections, add a visible update date, protect private details, and choose a maintenance rhythm that fits your real life.

If you already maintain a now page, what makes you remember to update it? Share your approach in the comments, or send this article to someone whose personal website deserves a little more of the present.