Building a home for my learning
I made a small personal site so that side projects and the lessons behind them have a place to live.
Why I built this
I wanted a place to keep the details that tend to disappear once I move on to the next thing. Building and experimenting often teach me the most while I am in the middle of them, but those lessons fade quickly if I do not write them down. I wanted a personal notebook for the small discoveries that come from making things.
The important constraint was that publishing had to feel light. If writing a post meant fighting a complicated editor or redesigning a page, I would probably avoid it. I wanted to be able to finish a weekend experiment, open a Markdown file, and leave a useful record while the context was still fresh.
What I built
Today I built the foundation for that space: a static personal website with a notes index and individual post pages. The site uses Astro and supports both Markdown and MDX, so an ordinary note can stay simple while a more involved post can grow when it needs to.
I also set up a small publishing workflow. Posts have a title, short description, date, tags, and a draft setting. Drafts stay out of the public site, which gives me room to write unfinished thoughts without accidentally publishing them. There is a starter command and an MDX template so each new note begins with the same basic shape.
I connected the project to GitHub and Cloudflare Pages, then connected my domain so the site can live at a stable address. I added my GitHub and LinkedIn links as the first personal details on the site. The rest of the content can grow at the pace of the work itself.
What I learned
The biggest lesson was that a personal site does not need to begin as a complete biography or a polished collection of case studies. It can start as a useful system for paying attention. A small structure makes it easier to return: one place for projects, one place for notes, and a low-friction way to add the next thing.
I also learned that deployment is less mysterious when it is broken into small steps. The site build, the GitHub repository, the hosting project, and the domain each have a separate job. Once those pieces are connected, updating the site is mostly a matter of changing the source and pushing a commit.
For future posts, I want to keep the writing honest and repeatable. Each note will explain why I built something, what I built, and what I learned. That should make the archive useful to readers, but more importantly, useful to the version of me who comes back to it later.
Next time
The next step is to publish this note once I have given it a final read. Then I can let the site become a record of what I am actually making, one weekend at a time.