For a long time , thought having a personal website was unnecessary
There were already plenty of places to write. Social media was faster. Publishing somewhere else was easier. I could post a thought, share a photograph, or write something and have people see it almost immediately.
So why build a website?
The answer became clearer the more time I spent online.
I wanted a place that was mine.
Not a profile. Not a feed. Not a page designed around someone else's algorithm.
A place where I could collect the things I make, the places I visit, the ideas I find interesting, and the things I am still trying to understand.
So I started building.
I wanted something simple
I didn't want the website to do everything.
I didn't need hundreds of features, complicated animations, endless categories, or a dashboard full of statistics.
I wanted someone to arrive and immediately understand what the site was about.
There would be writing.
There would be photographs.
There would be things I had built.
There would be ideas I wanted to explore.
And there would be things I simply found interesting.
That was enough.
The funny thing about wanting something simple is that making it simple isn't always simple.
Every decision creates another decision.
What should the homepage show?
How should articles look?
Where should images live?
How should content be organized?
What happens when something breaks?
How much control should the editor have?
What should happen behind the scenes?
A small website can contain surprisingly complicated problems.
Things broke
Of course, building it wasn't as smooth as I imagined
Things broke.
For someone not from IT background, it was difficult. It was frustrating.
But all thanks to milestone of the Era, My partner on this development.
My teacher Mr AI Bahadur.
A website isn't finished just because it looks finished.
There is a difference between something that works when everything goes right and something that can handle things going wrong.
That distinction became one of the most valuable things I learned while building this site.
Building teaches differently
There are things you can understand intellectually without really understanding them.
Security is one of them.
It is easy to think about security as a checklist:
Use a strong password.
Validate input.
Sanitize HTML.
Check uploaded files.
But when you build something yourself, those ideas stop being abstract.
An article editor accepts information from a browser.
An image uploader accepts files from a user.
A database stores information that will later be displayed to someone else.
A single assumption can move through all of those layers.
Suddenly, "just make a simple website" isn't quite so simple.
Building it myself made me appreciate the invisible parts of software.
The parts nobody sees when everything works.
I also learned that ownership matters
There is something satisfying about writing something and knowing exactly where it lives.
When I publish something here, it isn't disappearing into a feed.
It becomes part of an archive.
A thought from today can still be here years from now.
A photograph can sit beside something I wrote months earlier.
An old idea can become interesting again because I have changed since I wrote it.
That is one of the reasons I like personal websites.
They are not just publishing tools.
They are records.
A website can slowly become a map of a person's interests.
You can look back and see what you cared about, what you were learning, what you were building, and what you were trying to figure out.
That is much more interesting to me than chasing the next post.
The website is allowed to change
I don't expect this site to stay exactly the way it is today.
It will change.
The design will probably change.
The writing will change.
The things I am interested in will change.
Some sections may disappear. New ones will probably appear.
There may be articles here that I eventually disagree with.
That's okay.
A personal website doesn't have to be a finished representation of a person.
It can be a work in progress.
In fact, I think that is part of the point.
I want this site to reflect where I am now, rather than pretending I already know where I am going.
Why not just use social media?
I still use the internet in all the usual ways.
Social platforms are useful. They are good for discovering people, sharing things quickly, and having conversations.
But I don't want them to be the only place my work exists.
Feeds are designed for what is new.
Websites are good at keeping what is old.
That's an important difference.
A post on a feed has a short life.
An article on a personal website can sit quietly for years and still be discovered.
I like that.
Not everything needs to be optimized for immediate attention.
Some things are worth making simply because you want them to exist.
What I want this place to become
I don't have a perfect plan for this website.
And I don't think I need one.
For now, I want it to be a collection of things worth keeping.
Things I have learned.
Things I have built.
Places I have been.
Ideas I keep returning to.
Experiments that taught me something.
Photographs that remind me of a particular moment.
Books, websites, tools, and people that made me curious.
Some of these things will be useful.
Some will be personal.
Some may simply be interesting.
I don't want every article to have a lesson.
Sometimes noticing something is enough.
The point isn't the website
After spending so much time building it, this is probably the most important thing I learned:
The website itself isn't really the project.
The project is everything that happens because the website exists.
Writing more.
Paying closer attention.
Learning new things.
Making things.
Documenting them.
Looking back.
Thinking more carefully.
The website is just the place where those things meet.
And maybe that's the best reason to build a personal website.
Not because you need another place to publish.
Not because everyone needs a personal brand.
Not because having your own domain automatically makes your work more important.
But because sometimes it is worth creating a small corner of the internet that belongs to you.
A place where you can leave something behind.
This is mine.
