– or how it turned into seven subpages and a drone slider
A story based on real events (with a touch of imagination)
Before I begin, let me clarify something.
The story you’re about to read didn’t happen exactly this way. It’s a blend of several real projects, calls, emails and meetings. Some facts, some exaggeration — but if you’ve worked in this industry even briefly, you’ll quickly recognise it could all have happened… and probably does, regularly.
It Was Supposed to Be Simple — So, HTML to Start
When the client presented their first idea — one page, no frills — the obvious choice was to build a static HTML site.
Simple, fast, lightweight. No need for a database, no complex setup, no ongoing maintenance.
A project you could launch and forget — it runs quietly in the background, requires no updates, and carries minimal risk of failure.
From One Page to a Full Website
“Mr Paweł, I just want a simple page. One tab, nothing fancy.”
I listened, nodded, and made notes: simplicity, single page, no extras.
I already had a clean and aesthetic concept forming in my mind — one that would meet the client’s expectations.
But after just a few minutes of conversation, the list started growing:
- a photo gallery — because the offer deserves to be seen,
- a contact form — since nobody really wants to call these days,
- an English version — so foreign clients can find their way around too.
When Simplicity Is No Longer Enough
As the conversation developed and the list of needs expanded — gallery, form, language version, dynamic content —
it became clear that a pure HTML site simply wouldn’t cut it.
The “one-page business card” was slowly evolving into something much more: a platform that didn’t just inform but engaged users, adapted to changes and allowed for growth.
That’s when I suggested switching to WordPress — a solution that matched the project’s actual expectations.
A CMS brought flexibility but also new challenges:
the need for updates, security, ongoing maintenance, and content management awareness.
This wasn’t change for the sake of change — it was a response to real needs.
WordPress? Why So Complicated?
Seeing the project expand, I proposed a tried-and-tested solution: WordPress.
I explained it was flexible, user-friendly and would allow the client to manage the site independently later on.
I also honestly mentioned that there’s a lot of documentation available — and yes, I’d send it over — but it takes time to go through it.
So I offered something better: a tailored user manual prepared specifically for their website.
“This WordPress documentation is free, right?” the client asked.
“Yes, fully available online.”
“Well, I’ll read it myself if needed.”
And just like that — another helpful service was turned down.
Administrator or Editor? Why Bother…
Just in case, I suggested creating an editor-level account — one limited to content editing.
No access to plugin settings, themes or crucial options.
I explained that this was safer, especially for someone who doesn’t work with WordPress daily.
The response?
“But that’s extra, right?”
“Yes, it requires custom setup.”
“Then I’ll just be careful.”
I mentally noted: carefulness on one’s honour.
Monthly Support? Nothing Will Happen Anyway
My last suggestion was routine:
monthly website management — updates, backups, security, uptime monitoring.
So the site wouldn’t just launch, but stay stable, safe and ready for future technology changes.
“That’s another fee?”
“Yes, it covers ongoing maintenance.”
“Nah, no need. If something breaks, we’ll deal with it then.”
Problems Came Sooner Than Expected
At first, everything looked great.
The site worked, the client was happy, the gallery sparkled in the sun, and the drone slider was dazzling.
Until it wasn’t.
The first issues appeared two weeks later:
- “I changed something in the gallery, and now nothing shows up.”
- “The English version disappeared.”
- “The form isn’t working.”
- “The site broke after a theme update.”
Each of these had one thing in common —
they were direct results of earlier decisions: skipping support, refusing documentation, declining maintenance.
What This Story Really Shows
There’s one key takeaway I hope you remember.
It’s not that the project grew — that’s natural, and that’s fine.
It’s not that the client changed their mind — we all want the best for ourselves.
It’s about understanding that as a project grows, so does the workload and responsibility.
Some things — like website security, stability, and ease of management — don’t happen “on their own”.
They require work, attention, and often additional investment.
A Project Is a Journey — And Journeys Require Planning
Every web project — even one that starts with “just one tab” — is a journey.
From idea to execution, from rough concept to solid solution, from minimal to ambitious.
And like every journey, it helps to have a plan.
To know your destination, your resources, and what you’ll do if you hit a curve in the road.
With clear agreements, open dialogue and mutual understanding, that journey can be safe and even enjoyable — for both client and developer.
Because changing needs aren’t a problem.
Problems start when we pretend nothing needs to change — not the plan, not the scope, not the budget.
So, if you’re a designer and hear someone say they “just need a simple one-page site” — smile.
It could be the start of a brilliant story.
And if you’re the client, remember — growing a project is perfectly normal.
Just be prepared for it and treat it as part of the bigger plan, not a complication to avoid.