At first, the front page was enough.
That worked when there were only a few pieces and everything still fit in one view.
One page could hold everything.
Then the writing kept coming.
Not because I suddenly wanted more pages.
Because the front page started doing too many jobs at once.
It was trying to be an entrance, an archive, a category map, and a reading queue at the same time.
That works for a while.
Then it starts to blur.
What Actually Broke
The problem was not that there were too many articles.
The problem was that the structure stopped matching the way the site was being used.
Build started filling up faster than everything else.
New pieces kept pushing older ones further down.
The front page still worked as a way in.
It stopped working as the whole system.
So the archive had to become real.
Not a CMS.
Not a database.
Just a more honest static structure.
The front page now shows the newest pieces and smaller previews.
The sections have their own pages.
The archive has its own page.
The writing did not change.
The site just stopped pretending one page could carry all of it forever.
Why It Matters
This is the same pattern as the rest of the system.
Nothing changed just to look cleaner.
The structure changed because growth exposed a limit.
It is easy to confuse simplicity with flatness.
They are not the same thing.
A system can stay simple and still gain depth.
Sometimes depth is what allows simplicity to survive.
If everything stays on one page for too long, the cost does not disappear.
It just gets pushed somewhere else.
Into browsing.
Into memory.
Into friction.
The Other Fix Hiding Inside It
There was another correction inside this one.
The upload flow had to grow up too.
Once the site had real section pages and subpaths, the old FTP assumptions stopped being good enough.
The upload script had to understand the new depth too.
Same lesson.
When the project gets more real, the tools around it have to get more exact.
Not more bloated.
More exact.
Status
The front page is not the whole site anymore.
Good.
That means the archive exists as a real layer now, not just as whatever still happens to be visible after scrolling.
The project has more depth than it had yesterday.
And it is still just HTML.
— Dennis Hedegreen
