I've been working on this project for a while, and finally it looks good enough to post a small preview.
This isn't a launch post. The project has a name/domain, but not going to share it just yet. A few things are still moving around and I would rather show where it is heading than pretend it is finished.
Same posts, different front door
If you already publish through PeakD, the hard part is done. Your writing is on Hive, along with your profile and the rest of your account. The new project takes that existing content and presents it as a blog focused entirely on you and your work.
There is a main archive, a clean page for each article, and separate About and Contact pages. Post images, communities, reading details, comments, and votes are all still there, but the result feels much more like visiting an author's website than opening another social feed.
Nothing is imported into a new platform. It is still your Hive content; this is simply a different way to look at it.
 |
 |
|---|---|
 |
 |
Not a replacement for PeakD
I want to be clear about this part: the project is not meant to replace peakd.com, and I don't want it to slowly turn into a smaller copy of it either.
PeakD is where the wider Hive experience lives. It is where you can follow what is happening across the network, discover authors and communities, read Snaps, publish, interact with other people, and manage your account.
This project is deliberately much narrower. There is no global feed, no Snaps timeline, no community discovery section, and no account dashboard. It is not the place you open to see what everyone on Hive is doing. It is the place someone opens when they want to read your work.
The two should complement each other: use PeakD to participate in Hive, then use your dedicated blog as the public home for your writing. A visitor can still vote or join the comments below an article, but the blog itself stays focused on one author rather than trying to contain the whole social experience.
I may have gone a little overboard with the themes
At first I thought I would make a few themes. There are now more than ten designs in the project, so that plan went well.
They are also quite different from each other. One looks like a quiet personal journal. Another is built for photography. There is an independent magazine, a field notebook, a fairly uncompromising brutalist design, a retro pixel theme, a terminal-style theme, and a split reader that keeps the post archive beside the article.
I didn't want these to be the same layout with a new font and accent color. Each one has its own approach to navigation, archives, post cards, article pages, comments, settings, and mobile screens. Even small things such as empty states and dialogs follow the theme.
Some are still experiments, and not all of them are guaranteed to survive my next round of opinions. For now, though, this is the part of the project I have been having the most fun with.
 |
 |
|---|
Customizing it without becoming a web designer
The blog owner can open a settings panel and try changes directly on the blog. Depending on the theme, there are choices for top or side navigation, compact or wide content, list or grid archives, light and dark modes, and different accent colors.
The blog name and description can be changed there too. Once saved, those choices live in the Hive account metadata. There is no theme repository to clone and no CSS to fight at 1 a.m.—unless, like me, you are the person building all the CSS.
The aim is to give authors enough control to make the blog feel personal, without turning the setup into another project they need to maintain.
Still connected to Hive
That narrower focus doesn't make the blog separate from Hive. It is still connected underneath.
Readers can sign in with familiar Hive wallets, choose a vote weight, leave comments, and reply to other people. Those actions are broadcast to Hive, and private keys stay in the wallet where they belong.
I've also spent time on the ordinary details a public blog needs: server-rendered pages, share previews, responsive layouts, progressive image loading, and an archive that can keep going without giving up after the first page.
More later
There is still a decent list of things to finish, so I won't attach a launch date to this post and immediately regret it.
For now, this is just a preview of what I have been building. But if you have feedback or suggestions please feel free to share here or on Discord.
