First Progress – From Chaos to Structure

After an intense week working on Project Angmar, things are finally starting to fall into place.
The last few days have been all about cleaning, organizing, and documenting — and it feels incredibly rewarding.

🚀 A Quick Status Update#

The project now builds smoothly both locally and on Vercel.
Every component has been reviewed, documented, and properly structured.
And the blog you're reading right now? It's no longer a placeholder — it actually works!

🧠 From Chaos to Order#

The first few days were mostly spent fixing my own mess.
I ran into everything from import conflicts and broken CSS comments, to React hooks being used on the server side by mistake.

The solution was to clearly separate server and client components, and gather all global state under a single Providers file.
That made useI18n and theming finally work reliably.

This small structural change solved several issues at once — and taught me a lot about how Next.js 15 actually expects things to be built.

🧩 Documenting Every Component#

One of my main goals was to make the codebase clean and professional.
I went through and documented over 50 component files, adding clear headers, purpose descriptions, and feature summaries.

It might seem small, but the difference it makes is huge — especially as the project grows.

💅 Global CSS & Theme Cleanup#

I spent a lot of time cleaning up globals.css and organizing all the Middle-Earth–inspired themes (Valinor, Rohan, Lothlórien, and more) to work smoothly in both light and dark modes.

The result is a far more stable foundation where every color and effect is structured around --color-* tokens.
It gives me full control — and makes it much easier to add or tweak themes later on.

✨ Refining the Hero & FeatureGrid#

I also improved the Hero section with better typography, contrast, and theme responsiveness.
At the same time, I expanded the FeatureGrid from six to nine cards and rewrote them to reflect what I actually prioritize as a developer:

• Clean, consistent UI
• UX first
• Design tokens and theming
• Scalable structure
• Performance
• Code quality
• Multi-language support
• Content-driven design
• Continuous learning

These feel more genuine — and together they paint a better picture of how I think when I build.

📝 Blog & Content#

I removed all placeholder blog posts and replaced them with real ones:

• Welcome to Project Angmar – the introduction
• This one – the first actual progress update

My plan is to use this blog more like a development diary than a showcase.
Short, honest reflections — about what's working, what's breaking, and what I'm learning along the way.

⚙️ Technical Lessons#

The past days have been packed with small but valuable insights:

• Next.js 15 enforces a strict boundary between server and client components
• MDX + Turbopack works well, but only with static import mapping
• Good documentation drastically reduces errors
• Systematic work beats speed — fix one thing at a time, not everything at once

📈 What's Next#

The next goal is to fill the portfolio with real projects and showcase components.
I'll also write more about how I use Tailwind tokens, and share what I learn from real school and personal projects as I go.

After many hours of debugging, organizing, and restructuring, the project finally feels mine.

The code is clean, the themes play nicely — and the blog is alive.

Not bad for two intense days in Angmar.

This entry reflects the work done between October 10-12, 2025
Next up: Portfolio projects and real-world component showcases