The Day MonkModern Went Live
A field note on building, breaking, doubting, and finally seeing an idea become real.
The Day MonkModern Went Live
Today, MonkModern is live.
After weeks of building, changing, fixing, testing, breaking things, restoring things, and trying to understand what was actually happening behind the screen, the website finally opened on its own domain:
monkmodern.com
It looks like one simple sentence.
But anyone who has ever built something from almost nothing knows that the final moment never carries the full weight of the process.
A website going live sounds clean from the outside.
A domain opens. A homepage appears. A logo sits at the top. Pages load. Buttons work.
But behind that clean surface, there is usually a long, messy, emotional, very human story.
And MonkModern had that story.
It did not begin as a finished vision
When I first started working on the website, I thought I was simply building a place to publish my thoughts, articles, and reflections.
At that time, MonkModern was still taking shape.
It was connected to my personal journey, my writing, my monkhood years, my inner experiments, and my desire to share something meaningful.
But slowly, while building the website, the idea itself started evolving.
MonkModern was no longer only a blog.
It became a space for clarity.
A space for people navigating difficult questions.
Should I continue this path?
Should I marry this person?
Should I quit this job?
Why am I exhausted?
Why am I confused?
Why do I keep repeating the same mistakes?
Why does life feel directionless even when everything looks normal from outside?
The website forced the idea to become sharper.
That is one thing I learned during this process:
Sometimes we do not fully understand what we are building until we begin building it.
— Hitesh Mandavi
The act of creation reveals the idea.
The building process was not peaceful
There is a strange fantasy around building something.
From outside, it looks creative, exciting, and inspiring.
And yes, sometimes it is.
There are moments when you feel a sudden rush of energy.
You see a page taking shape.
A section looks beautiful.
The logo finally feels right.
The homepage starts speaking the language you wanted.
In those moments, building feels magical.
But then something breaks.
A page goes blank.
An image gets cropped badly.
The mobile layout behaves differently.
A form stops saving data.
The article spacing looks wrong.
The deployment fails.
The domain does not connect.
The website shows an error instead of the homepage.
And suddenly, the same project that gave excitement begins to create frustration.
There were moments when I felt motivated.
There were moments when I felt demotivated.
There were moments when I got excited again.
There were moments when I almost lost interest.
That is the emotional truth of building.
It is not a straight line.
It is more like walking through fog while carrying a picture in your mind that nobody else can fully see.
The clean website hides the messy middle
When someone opens MonkModern now, they will see the final surface.
They may see the logo, the dark design, the mountain background, the Journal, Field Notes, Resources, Start Here, About, and Consultation pages.
But they will not see the messy middle.
They will not see the WordPress experiments.
They will not see the Astra theme confusion.
They will not see the design changes.
They will not see the post publishing errors.
They will not see the struggle with slugs and Markdown files.
They will not see the backend setup.
They will not see the Supabase tables.
They will not see the GitHub confusion.
They will not see the deployment mistake.
They will not see the 403 error.
They will not see the moment when the site was technically deployed, but still not working properly.
And that is the nature of most meaningful work.
The final thing looks simple because the complexity has been absorbed into the process.
A clean result is often the visible form of invisible struggle.
One of the biggest lessons was technical clarity
At one stage, the website was ready locally.
The design was working.
The forms were connected.
The pages were loading.
But deployment became its own challenge.
I thought connecting GitHub to Hostinger would be enough.
But the first deployment went through the wrong path.
The site was treated like a normal static or shared-hosting website. It was deployed into the regular website folder, but MonkModern was not just a static website.
It was built with Next.js.
That means it needed a Node.js environment, because the website had server-side form routes for newsletter signups, resources, and consultation requests.
This was the key technical lesson:
A modern website is not only about design.
It is also about architecture.
The website code was in GitHub.
The backend data was in Supabase.
The hosting was on Hostinger.
The live domain was monkmodern.com.
Each part had a role.
GitHub stored the code.
Hostinger ran the website.
Supabase stored form submissions.
The domain connected people to the final site.
Once I understood this clearly, the confusion reduced.
And this is probably how I would explain it to someone simply:
A website is like a house.
The design is how it looks.
The code is how it is built.
The database is where important information is stored.
The hosting is the land where the house stands.
The domain is the address people use to visit it.
If any one of these is wrongly connected, the house may exist, but people may still not be able to enter it.
The backend made the website feel real
Before the backend was connected, the website felt like a beautiful place.
But after the forms started saving data, it became functional.
That was a different feeling.
The newsletter system started saving emails.
The resources page started collecting access requests.
The consultation form started storing real consultation requests.
That was the moment MonkModern stopped being only a presentation and became a working system.
This matters because a website is not only a digital brochure.
A real website should do something.
It should help people enter your world.
It should collect interest.
It should guide visitors.
It should create a relationship.
It should become the beginning of a conversation.
For MonkModern, that conversation begins with clarity.
Building taught me patience more than technology
Yes, I learned technical things.
I learned about Next.js, GitHub, Hostinger, Supabase, environment variables, deployment settings, Node.js apps, build commands, and domain connection.
But the deeper lesson was not technical.
The deeper lesson was patience.
There were many times when the solution was not immediately visible.
And that is uncomfortable.
When something breaks, the mind wants quick closure.
But building does not always give quick closure.
Sometimes it asks you to stay with the problem.
Look again.
Try again.
Understand the structure.
Ask better questions.
Separate emotion from the issue.
That itself is a MonkModern lesson.
Clarity does not always come before action.
Sometimes clarity comes because you keep acting through confusion.
The emotional moment matters
When the website finally opened on monkmodern.com, it was not only a technical success.
It felt emotional.
Maybe even a little dramatic.
Joy, relief, happiness, exhaustion, and almost tears — all together.
Because I knew what went into it.
The site was not created in one smooth flow.
It was created through resistance.
And that is why the final moment felt different.
When you build something casually, the result feels casual.
When you build something through difficulty, the result carries weight.
MonkModern going live felt like proof that the idea survived the process.
This is only version one
The website is live, but it is not the end.
It is the beginning.
There will be more articles.
More field notes.
More resources.
More frameworks.
More tools.
More clarity systems.
More experiments.
More refinements.
But now there is a foundation.
Before this, MonkModern was scattered across thoughts, notes, conversations, drafts, and ideas.
Now it has a home.
That matters.
Because a home gives continuity to an idea.
Final reflection
Today, MonkModern is live.
Not perfect.
Not complete forever.
But alive.
And maybe that is the real milestone.
Not that everything is finished.
But that something meaningful now exists outside the mind.
An idea has taken form.
A private vision has become a public space.
A long inner journey has become a digital home.
This is the first field note after launch.
And it feels right that the first note is not about success, productivity, or motivation.
It is about the real process of building.
Because building anything meaningful is rarely clean.
It is messy.
It is emotional.
It is technical.
It is tiring.
It is beautiful.
And sometimes, after all the confusion, one day the page finally opens.
MonkModern is live.
Share this article