A site where launch was
just the start
Websupport is the largest hosting provider in Slovakia. We built its new website during the 2020 rebrand and have kept developing it ever since.
The website handles dozens of services, configurators and four markets. It changes every month, depending on what Websupport needs.
4
markets · SK, CZ, HU and SE
60+
custom Gutenberg blocks
2020
start of the project and the partnership
12–15
people on the team during the busiest phase
A website built with a new brand
Websupport was going through a complete rebrand. The new visual identity did not arrive all at once: the design team delivered it in parts, and we implemented each one as it came.
While we were finishing the first subpages, others were still being designed. Development ran in parallel cycles, and new designs kept bringing requirements that made us revisit technical decisions too.
So the first launch did not mean a finished website. What went live were the parts needed for the rebrand and the related campaigns; further content was added step by step.
New brand and new website, built together.
A large website, simple to manage
The website covers dozens of hosting, cloud and server services, each with its own parameters and configurations. Add to that price lists, configurators, a hiring section and an extensive menu.
The subpages also differ a lot visually. The website uses different layouts, component variations and even light and dark modes depending on the type of product.
We needed a system that carries this complexity in the background and stays simple to manage day to day.
Complexity stays in the background.
More than 60 custom Gutenberg blocks
We built the admin around custom blocks that the editorial team uses to assemble new pages.
Each block carries settings and variations for product and content pages. Together they form a system that lets the website grow without starting from scratch.
Editors assemble a new page without a developer.
Product data is not entered by hand
Websupport manages its products in an internal system, so the website does not store prices and configurations a second time in WordPress.
Internal system
products, prices and configurations in one place
API layer
gives the website access to data from the internal API
websupport.sk
product cards, price lists, configurators
The solution later proved portable. We reused the foundation built for Websupport on the Active24 website (another hosting brand in the same group).
Product data lives in one system. The website only reads it.
The website and sales app work as one product
Websupport’s sales app is part of the website. It uses the site’s header and footer and loads into the content area, so users experience it as just another page.
The website also passes on what the user has chosen: the product, configuration, domain and service parameters. The order continues without losing context.
Anyone choosing hosting or a server should have a simple, clear process in front of them.
Customers can't see where the site ends and the app begins.
One login across systems
Login is not handled by WordPress. The website is part of Websupport’s wider user environment, so the login layer sits outside it.
A logged-in user may see different prices or content on the website depending on their account. The same login works in the sales app and in the customer admin, so WordPress is just one part of a bigger whole.
From three markets to four.
Without a rebuild.
We started with Slovak and Czech versions, then added Hungarian. Today the website also runs in Sweden.
Slovakia
Czechia
Hungary
Sweden · Swedish and English
The original three markets ran as separate single-language websites within one multisite. The Swedish market needed two languages, so we extended the architecture to support that model too. Adding a new market is now mainly a matter of configuration and content.
A new market is configuration, not a new project.
One system, very different pages
Hosting, VPS, cloud and servers have different visual modes: part of the website is dark, while other products switch to light.
We needed a system flexible enough to handle different situations without a pile of templates, and without turning into an uncontrollable mix of exceptions.
Performance does not end at launch
On a website this size, performance cannot be solved with a single optimisation before launch. We monitor Core Web Vitals, loading and technical health on an ongoing basis.
So after launch we keep working on the details that affect the website’s speed and stability. Performance is part of our long-term care for the project.
A large website is not finished on launch day.
A large project on time, with a changing brief
Design was happening in parallel with development, requirements were added during implementation, and deadlines were tied to the rebrand and marketing campaigns.
We kept revisiting technical decisions and adjusting the scope so work could continue without blockers. It was live agile development with large teams on both sides. We hit the launch date, and in the process built the foundation we have been building on ever since.
“I very much enjoyed working with Webikon. Communication was always prompt, and even when there was a misunderstanding, there was always a willingness to find a systematic solution.”
We have worked on Websupport continuously since 2020
After the first launch came new features, larger development projects, and everyday changes, fixes and support.
During the biggest phase of development, 12 to 15 people worked on our side. Websupport had a team of a similar size on the project.
Dedicated project manager
Regular status calls with the Websupport team on the current state and next priorities.
Tasks in a shared system
Websupport’s project team enters tasks directly into our system, and our developers work through them as they come in.
Development, not just upkeep
We know the solution in depth, so we don’t build each new feature from a blank slate.
Years on, there is still plenty to build.
A technical foundation that grows with Websupport
The original implementation grew into a website with its own component system, a connection to internal data and an architecture ready for more markets and languages.
Websupport needed more than a supplier for a new website: a partner who would know the solution, take responsibility for it and keep developing it.
Technical solution
We choose technology to fit the project, not the other way round. These decisions have carried a large website since 2020 without it ever needing to be rebuilt from scratch.
Website foundation
WordPress multisite
Four markets in one installation. Each one manages the content it needs on its own.
60+ custom Gutenberg blocks
Blocks with settings and variations for product and content pages.
Light and dark mode
Visual modes by product type, within one component system.
Data and integrations
Custom WordPress plugin
It talks to the internal API and supplies the website with products, prices and configurations. The same foundation later served the Active24 website too.
Connection to the sales app
The app loads into the website and picks up the selected product, configuration and domain.
Single login
The login layer sits outside WordPress and is shared by the website, the sales app and the customer admin.
Operation and development
Core Web Vitals
We monitor and optimise performance and technical health on an ongoing basis.
Continuous development
A dedicated project manager, regular status calls and tasks in a shared system.
Architecture for new markets
Single-language and bilingual websites within one multisite. A new market is added through configuration.
More long-term partnerships
A live website needs a team that knows it.
Websupport has a website that changes every month, and a team that has known it since the first line of code. Tell us what you’re planning for yours.
No-obligation consultation.
We reply within 24 hours.