The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
A regional timber wholesaler with decades of tradition was stuck on a legacy PHP site that demanded constant updates, security patches, and dependency fixes.
We rebuilt hilger-holz.de from the ground up in Webflow.
What changed:
— No more PHP dependencies. No more update treadmill.
— Hosting on Webflow's global CDN. Faster everywhere, secure by default.
— Strong PageSpeed scores out of the box.
— Clean on-page SEO foundation — proper headings, semantic structure, fast indexing, schema etc.
— A CMS the team can actually manage themselves.
The real win isn't just speed or rankings. It's peace of mind.
If your business runs on a site that needs constant babysitting — there's a better way.
#Webflow #WebDesign #SEO #SiteMigration #PHPtoWebflow
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Challenges
View all
Related posts
Same headline, two layouts fighting for attention.
Which one wins the first 3 seconds?
3 voted
75%
1 voted
25%
4 votes
Closed
I’m picking B. The visual details make it feel more distinctive.
The 404 was treated as a proper page rather than a fallback state.
The number is constructed as an architectural drawing. The 4 and the 0 are formed from walls at true thickness, with furniture laid out inside the resulting rooms and dimension strings running along both edges. It sits inside the same drafting system as the rest of the site rather than borrowing a display typeface.
The error message then repeats. Instead of a single dialog, identical windows cascade back across the canvas, each one carrying the same 404 notice. It reads as a system throwing an unresolved warning over and over, which is the exact behaviour Heron is built to prevent inside a model.
Error pages are never in the brief. They're a good measure of whether a team understood the product or just styled it.
Treating a 404 as an actual page instead of a dead end is such a good instinct, where did the architectural drawing idea come from, personal interest bleeding into the work?
After 6+ years of building websites, I’ve learned to ask one question early: “Who will update this after launch?”
The answer shapes the CMS, navigation, and handoff.
Fellow developers, what’s one question you always ask before starting a project?
