For a long time, I published most of my articles on DEV.to.
Not because I had some big strategy behind it.
I simply didn't have a website of my own.
DEV.to was convenient. I could write something, publish it, and put it in front of other developers.
But eventually I started thinking:
What if I had my own place for all of this?
My projects.
My articles.
Things I've built.
Things I've broken.
Things I've learned.
So I decided to build one.
Meet Devlogr 🚀
Devlogr is my personal developer portfolio and blog.
👉 https://www.devlogr.run.place/
The idea is pretty simple:
A place where I can document what I'm building and learning, while also having a home for my projects and developer profile.
The name comes from Dev + Log.
Basically, a log of my journey as a developer.
What does it have?
I wanted it to be more than just a page saying:
"Hi, I'm a developer. Here are my skills."
So I built it around the things I actually want to show.
📝 Articles
This is where I'll be writing about things I build, problems I run into, experiments, lessons learned, and whatever else seems worth documenting.
I'll also be moving some of my older articles here.
🚀 Projects
My projects have their own place instead of being buried somewhere in a GitHub profile.
The goal is to show not just what I built, but eventually more about why I built it and what I learned from it.
🐙 GitHub integration
I also wanted my projects and GitHub activity to connect naturally with the site instead of manually updating everything every time.
So parts of the site use GitHub data to keep things more dynamic.
🔍 SEO
Since this is my own website, I didn't want it to just exist at a URL that nobody can find.
So I also spent time making it properly SEO-ready:
- Dynamic page metadata
- Canonical URLs
- Sitemap
- robots.txt
- Open Graph previews
- X/Twitter cards
- Structured data
- Article metadata
- Semantic HTML
- Image optimization
- Internal linking
- Mobile optimization
- Crawlability and indexability
There is obviously still a lot to learn about SEO, but I wanted to start with a solid foundation.
Why not just keep using DEV.to?
I'm not stopping.
I actually think platforms like DEV.to are great for reaching other developers.
But there's a difference between having an audience somewhere and having a home of your own.
So I'm thinking about it like this:
Devlogr → my home
DEV.to → distribution/community
I'll continue sharing articles on DEV.to, but Devlogr will be the original home for my writing.
That also means I can experiment with the website however I want.
No waiting for someone else's feature.
No worrying about how the platform changes.
It's mine.
Building it was also the point
One of the reasons I wanted to build Devlogr was simply to learn.
There are plenty of things I could have used an existing solution for.
But building it myself meant I had to think about:
- Architecture
- Routing
- Content management
- UI/UX
- SEO
- Performance
- Deployment
- Security
- Integrations
- And all the weird little problems that appear once something is actually running.
And honestly, those problems are probably more valuable than the finished website.
Because every time something breaks, there's something new to learn.
What's next?
Devlogr is definitely not "finished."
I want to keep improving it as I use it.
Some things I'd like to explore:
- Better article discovery
- More project details
- Improved search
- More developer-focused features
- Better analytics
- More integrations
- And probably a bunch of ideas I'll come up with after using it for a while 😅
For now, though, I'm happy to finally have a place of my own.
So... welcome to Devlogr 👋
I started it because I didn't have a developer website.
Now I do.
And from here, I'll be documenting what I build, what I learn, and occasionally what I completely break.
Building. Breaking. Learning. Repeat.
👉 Devlogr: https://www.devlogr.run.place
👉 Github source code: https://github.com/DeveloperPuneet/Devlogr
If you're also building your own little corner of the internet, I'd love to hear about it.
Top comments (0)