A website system that grows with your business
Launching a new programme, entering a new market or running a campaign rarely means adding just one page. Consider an education company with offices in several countries. It is introducing a new professional course and wants to open enrolment in one market first, with an early-enrolment price for the next intake. The course needs an accurate description, a message for the people it addresses, local prices and terms, a contact at the regional office, a page layout — and someone to keep all of it current after launch.
When every launch begins by copying the last page, these decisions end up scattered across the site. A few months later, nobody is sure which course description is correct or which price is still valid.
We are web designers who work directly with founders and their teams, and we design websites as connected systems. Brand decisions guide the content; a structured content model feeds the pages; a design system gives them a consistent form; and the team has a clear process for making changes. Below, we follow this launch through each stage of that work.
Deciding what the website needs to say
1. Mapping the web presence
We begin with an audit of the existing sites and pages. What belongs on the main site? What varies by country? Which information belongs in the course catalogue, a campaign landing page or the learning platform?
In our example, the audit might reveal that the course description already exists in three versions: on the main site, in a PDF brochure and on an older regional landing page. It also shows the path a visitor should take: from an advertisement to the new landing page, then to enrolment or a conversation with the regional office. Each site and page gets a defined job, and the paths between them become explicit.
2. Agreeing on the promises behind the copy
A page cannot resolve an uncertain offer with better wording. If the three descriptions disagree about who the course is for or what participants will be able to do afterwards, the company has to decide what it can actually promise.
We separate facts that need correcting, explanations that need improving and decisions that belong to the founder or product owner. Those decisions go into the Brand Core: the agreed foundation that sets out whom the company serves, what it offers, the promise it makes and the evidence behind it. The new landing page and the next campaign in another market then draw on the same answers. We describe how a content review leads to this work in our Brand Core article.
Structuring content and design
3. Modelling content for reuse
Next, we decide which content is shared and which belongs to a particular context. The course description serves every country. The early-enrolment price applies only in the launch market and only until a set date; the regional contact belongs to that market alone.
We model this information as connected collections in Wix CMS before designing any page around it. A landing scenario then records the choices for one campaign: the programme, the audience, the market and branch, the price, any promotional offer and the visual brand profile. The page retrieves its content from those records instead of keeping its own copies, so a corrected course description appears everywhere it is used. CMS-first design explains the model and the editing work behind it.
4. Designing for distinction and repetition
The course's main product page may deserve its own composition, perhaps even an interaction that lets visitors experience something of the course before they enrol. Campaign pages like the new landing page need a smaller set of choices that the marketing team can apply confidently. Both should clearly belong to the same brand.
We therefore work on two levels: a main design system with room for expressive layouts, and a simpler one derived from it for repeatable sections in Wix Studio, with straightforward colour combinations, layouts and motion. Routine pages become easier to assemble without every page collapsing into the same template. Our two-level design-system approach explains the distinction.
Making launches routine
5. Choosing how the team launches pages
"Let the team launch landing pages" can mean different things. One manager only needs to change the price and the office; another needs to arrange prepared sections in a new order; a third needs a new sequence of arguments for an unfamiliar audience. These tasks call for different degrees of freedom.
In the Wix ecosystem, we see five routes: a compact mobile page built with Hopp, a library of Wix Studio sections, dynamic pages driven by the CMS, and two routes based on a custom Wix site app — one supplying individual branded sections, the other a complete landing page. The right choice depends on what changes, how often it changes and which skills the team has; we compare the routes in our guide to independent landing-page launches. A recurring offer such as an early-enrolment campaign suits dynamic pages: a single field on the scenario determines whether the page shows its standard layout or a promotional version with the special price and conditions.
6. Putting the rules where the team works
To work independently, managers need understandable fields, clear choices and feedback at the moment something goes wrong.
In our landing workflow, every new scenario starts as a draft. If the manager preparing the page selects an office from another country by mistake, a note in the CMS reports that the branch belongs to a different market. Missing selections, such as a price or an audience, are flagged in the same way. The manager corrects the draft, reviews the page and approves publication. The checks make agreed rules visible; the decision stays with a person. The CMS validation case shows the setup in detail.
7. Planning the team's workload
A new workflow changes responsibilities. Someone has to maintain the shared course facts, check each campaign, handle exceptions and learn the tools. AI can speed up parts of this work — a manager can draft a scenario through an AI chat connected to the CMS, for instance — but someone still has to review what it produces and decide what to trust.
Alongside the system, we therefore discuss three questions with the founder and team: what improves for the business, what improves for the people doing the work, and how roles, authority and learning time change. Faster launches should not quietly become unrecognised extra work. Our article on the founder and team takes this further.
Proving it on one launch
8. Building a pilot, then expanding
A system becomes concrete when it handles a real launch. In our example, that means one course, one audience and one market: the new course, presented to its first audience in the launch market. We prepare its content sources and page design, create the scenario, test both the standard and promotional versions, and ask the people who will maintain the page to use the workflow themselves.
Then we look at what took time, what needed correcting and what remained unclear. The answers shape the next step: another page variant, clearer CMS guidance or a different way to assemble pages before the course opens in the next market. The goal is a web presence that changes with the business while its content, design and responsibilities remain easy to understand.
Planning a new programme, market or campaign? Tell us what you are launching and where, and we will suggest where to start: mapping your web presence, structuring the content or designing the Wix workflows your team will use. Get in touch with parnii.de.
