An international education business needed two kinds of pages. Some called for a distinctive experience designed around a product. The marketing team also needed to assemble new campaign landing pages regularly, without asking a designer to rebuild every section. Our main design system gave us room for expressive layouts and interactions. In an early concept for a technical course, connected nodes and interactive sequences made a complex process visible. Pages like this depend on decisions about the product’s story and how visitors move through it. Three design system derivatives We derived a simpler system from that foundation for repeatable landing pages. It uses straightforward colour combinations, simpler layouts and basic animation. We removed complex scroll transitions and compositions that need to be tuned for every new page. The connection to the brand remains; the number of decisions an editor has to make becomes smaller. This changes where the design work happens. We design responsive sections, determine which content variations they can handle and make their purpose clear. A manager with modest design experience can then choose relevant sections, replace the content, arrange the page and check the result across screen sizes. They work with prepared choices instead of recreating the design system themselves. We brought the sections and components together in a Wix Studio showroom to see how those choices function side by side. We explain when a prepared section is enough and when a page needs its own composition in the article on reusable and individual design. One content block, two levels of design The two systems answer different needs. The main one gives a product room for a distinctive visual idea. The simplified one helps employees build recurring pages while keeping their design consistent with the brand. That relationship continues in our material on one brand across formats. A section library is one route to independent launches; the right route depends on what employees need to change. We compare the options in five approaches to landing-page production. Within the wider website and content system, this approach shows the practical value of doing the complex design thinking up front: the next page becomes easier for the team to build. Need your team to launch pages more independently? We can turn your design foundation into responsive sections and clear rules for using them in Wix Studio. Tell us what pages your team needs to make.

A landing page can give visitors a small experience of the product before they sign up. Through an interaction, they can explore something about its character, understand how it works and encounter a benefit through their own actions. At parnii.de, building these miniature product experiences is a recurring part of our communication design. In my own work, I start with a characteristic or benefit worth bringing to life. I look for a visual metaphor that expresses it, then develop an interaction in which the message and the mechanics work together. Our landing-page work for an AI content-creation course shows how this approach connects an educational offer to the experience of the page. Find the product idea the visitor can experience The starting point is the product’s substance: what it helps people do and how they take part in it. For this course, the teaching materials describe a content-production workflow that includes video editing. The learning format also gives students control over their pace. Together, those characteristics provide the basis for a section that introduces both the creative environment and the way students move through the learning material. The page still needs to explain the programme, outcomes, format and offer. Organising that information helps us identify the role an interaction can play. Here, the format section becomes an opportunity to make independent, self-paced learning tangible. The metaphor comes from the course itself. We turn the section into a miniature editing interface, borrowing the visual language of tracks, a timeline and a moving playhead. Let the interaction carry the message The section, built in Wix Studio, places a learning-interface visual behind a sequence of cards. The cards introduce video lectures, supporting text and the student’s workflow. Coloured tracks along the bottom connect these elements to the editing metaphor. Scrolling moves the playhead across the timeline and brings the cards into view. Scrolling in the other direction takes the visitor back through the sequence. The visitor controls how quickly they move, can pause on a stage and can revisit it. The heading “Learn at your own pace” gives that gesture a clear meaning. The phrase and the interaction reinforce one another: the visitor reads the promise while experiencing control over the sequence. Scrollytelling by parnii.de Three ideas come together in this one action: The editing interface introduces the course’s creative world. Its visual language relates to an activity students encounter in the programme. A familiar scroll makes the experience easy to explore. Visitors use an action they already know to discover the content, supporting the approachable feel of the course. Control over the sequence makes self-paced learning tangible. Visitors choose their pace and return to an earlier stage through their own movement. The accompanying video shows this relationship directly: progression across the tracks, the appearance of the cards and movement back through the sequence. Give the metaphor a role in the page’s story The section answers a practical question: how does learning on this course feel and work? Its position within the landing page connects that answer to the offer the visitor is considering. We structure the content, develop the visual composition and interaction, and build the section on the website. Across those stages, the product idea remains the reference point. The words explain the format; the editing metaphor introduces its atmosphere; the visitor’s action demonstrates control. The individual details contribute to that explanation. The tracks make the sequence recognisable. The playhead connects movement to progression. The cards keep the learning information readable as it appears. Forward and backward movement lets the visitor explore the relationship between the stages. This is where storytelling and scrollytelling meet. Storytelling gives the section its idea and direction. Scrollytelling lets the visitor move through that idea, with the interaction carrying part of the explanation. We explore how the content structure becomes a page in the sitemap, wireframe and CMS brief. Develop the experience from a meaningful product characteristic The same method can guide other landing pages. We identify a benefit or characteristic, choose a metaphor grounded in it and define what the visitor will do. Each choice needs a clear connection. What does the metaphor help the visitor recognise? What does their action let them experience? How does that experience support the surrounding content and the decision they are making? For this course, the answers connect editing, a familiar gesture and control over pace. Another product calls for its own idea and mechanics. The communication grows from the product and the audience’s situation. The course-page and landing-page brief looks at how those contexts shape a page. Our role as web designers is to develop that connection into a coherent experience: the story, visual language, words and interaction. The human touch lives in choosing the metaphor, giving it a meaningful role and shaping the details so the visitor can discover the idea naturally. This is one way a landing page can express the character of a product while explaining its offer. It also gives the wider website a distinctive experience grounded in what the company provides. Our website-system overview connects this work to the wider site. Is there a benefit of your product or service that people could experience through its website? We can help find the idea and develop it into a meaningful interaction within the page. Get in touch with parnii.de and tell us what you would like visitors to discover.

Marketing teams need to launch landing pages for different products, audiences and markets without bringing a designer or developer into every campaign. This overview draws on our research for one project and presents five approaches that can help companies build that capability. Each option offers a different balance of control, flexibility and required skills. The choice depends on your team’s needs, capacity and readiness. For a consistent system of communication, the foundations still need attention: a developed brand platform, reliable content prepared by the company, and clear responsibilities. See our Brand Core article and our CMS-first design article. What does the manager need to change? Changing a market and price is a different task from building a new sequence of arguments, evidence and calls to action for another audience. That distinction affects how much control the manager needs over the page. Define which changes managers can make themselves and which scenarios need to be built into the system beforehand. Five routes compared: what the manager changes, which skills it takes, and how much is prepared in advance. 1. A compact mobile landing page with Hopp Hopp is a particularly useful option for compact mobile campaigns. It is a link-in-bio service with considerably more possibilities than its name suggests. Our two reusable landing-page templates provide examples of how Hopp supports focused campaigns for mobile traffic. With a template and content ready, you can prepare a new page in hours. You don’t need coding skills, but you do need time to learn the tool. Its ready-made block layouts let your team focus on text and images. To create a block based on existing material, you can give the AI block builder screenshots as references and then customise the result. Analytics, payments and Wix business integrations make it a strong candidate for quick experiments; availability depends on the plan and setup. You can connect Hopp to your existing Wix site and use its content and business tools for your campaign pages. The essentials are a clear page structure, prepared copy and consistent brand assets. The trade-off is less freedom for bespoke layouts. The Hopp brief develops this option. 2. A library of ready-made Wix Studio sections A section library provides reusable introductions, product information, social proof, pricing and calls to action. Managers add the sections they need, arrange them and update the content. This requires basic Studio skills and an initial introduction to the editor. The page must live on a Wix Studio site. Preparation includes content structure, branding, responsive design and editing guidance. A suitably skilled team then gains extensive control over layout and content across desktop, tablet and mobile. Placeholder or outdated content needs updating, and the team must check completeness and responsive behaviour. Static content is edited in Studio. CMS-connected sections can support AI-assisted updates through MCP, which connects the chat to the content database. Clear naming, instructions and editing rules make the library usable. 3. Dynamic landing pages driven by the CMS This suits established communication patterns: clearly defined products, audiences, benefits and evidence, with recurring campaign variations. The company prepares and stores its product descriptions, audience-specific messages, market information, regional contacts, prices and promotions in the CMS. The page design is prepared in advance, including the sections and layout variations needed for different campaigns. To create a landing page, the manager defines the campaign: which product to promote, who it is for, where it runs and which price or promotion applies. The system brings the relevant content together in the prepared page design. For example, selecting a promotion adds a section with the special price and its conditions; without a promotion, the page shows the regular price and offer. Managers work within prepared scenarios. With content and responsive templates ready, our process allows page assembly in around 10–15 minutes. A manager can create the scenario through an AI chat connected to Wix CMS or enter it manually. New items start in Draft and pass through human review before publication. Our page-variants guide covers layout conditions; the CMS validation case shows checks during editing. A new campaign type may require extending the content model or design. You can also reuse the prepared design outside the CMS workflow. Converting a dynamic page into a regular static page removes its CMS connections and lets your team edit the content and layout directly in the editor, much like working with the ready-made sections in the previous approach. 4–5. Ready-made sections or a complete landing page through a Custom Wix Site App A Custom Wix Site App is an application developed specifically for the company and installed on its existing Wix sites. It gives the marketing team a reusable set of branded sections or a complete landing page, with settings for managing campaign content. Using custom elements, the app works across Wix Editor, Wix Studio and Wix Harmony. This makes it useful for companies whose sites use different Wix editors: the same app provides the prepared campaign tools across those sites. There are two ways to use it: 4. Add individual sections. The manager adds the app’s ready-made sections to a page, arranges them in the required order and updates their text and media through the app’s settings. 5. Add a complete landing page. The manager adds a prepared landing page to the site and configures its campaign content. The page structure, design and CMS connections are set up as part of the app’s development. The app’s settings give the manager control over texts, images, content selections and section order. The design of the sections is maintained within the app, so routine launches do not require the manager to work on their internal layout. A new structure or functionality requires further development; a new product that fits the existing structure can use the prepared tools. The initial work includes designing and developing the app, preparing its content connections and defining the manager’s settings. For recurring campaigns, this reduces repeated page-building work and the need to involve specialists in every launch. Both approaches are mapped in the Wix app brief. Combining the approaches These methods can coexist. A team might use Hopp for early mobile campaigns, a section library for pages requiring editorial flexibility, and dynamic pages for recurring regional offers. The useful combination follows the campaigns, content readiness and skills of the people doing the work. We explain how these choices fit the wider content system in our overview. Want your team to launch landing pages independently? We can help define the workflow, choose the appropriate Wix approach and prepare the content, design and tools it needs. Get in touch with parnii.de and tell us which pages your team needs to launch regularly.

A course landing page can follow the same structure across campaigns until a promotion changes the message. A discounted offer needs its own section for the price and conditions; a standard page does not. Wix Studio page variants let a dynamic item page use different layouts according to a rule on its CMS items. 1. Define the condition in the content model Create a collection whose items represent the pages or campaign scenarios. Each item can select its product, audience, market, price and optional offer from prepared content. Add a simple field such as With Offer to say whether that scenario uses the promotional layout. The distinction matters: a reference to an Offer record can supply the promotion’s content, but page-variant rules cannot use reference fields. A direct field on the page’s own collection gives the layout a condition it can evaluate. For more on planning these relationships, see CMS-first design. 2. Design the standard page Create a dynamic item page in Wix Studio with a variable in its URL. Connect the page to the collection and design the regular version: relevant product and audience content, regional details, standard price and call to action. This is the original layout. Items that match no variant rule will use it. 3. Add the promotional variant Add a page variant by duplicating the standard design. Give the promotion its own section for the offer, price and conditions, then set its rule to With Offer = true. Both layouts use the same dynamic page and its dataset; the rule determines which layout an item receives. Wix Dynamic Page Variants This keeps the difference in the page design, where it belongs. A manager chooses the campaign and its offer in the CMS instead of deciding how to rebuild the page. If managers enter those choices themselves, our CMS validation case covers how to flag incompatible selections. 4. Check both paths Preview one item with an offer and one without it. Check the content, layout and responsive behaviour in each state, then review the pages before publication. The two variants share the original page’s URL pattern and SEO settings, so plan those at the dynamic-page level. Two page layouts based on one Dynamic Page One content model can now support two distinct landing-page layouts without duplicating the whole page for every campaign. For a comparison with other ways of launching pages in Wix, see five approaches for marketing teams. Want your team to launch campaign pages from structured content? We can design the CMS model and page variants around the choices your campaigns actually require. Get in touch.

A website brings a company’s strategic decisions into public view. It needs to explain who the company serves, what its products offer, why those offers matter and what supports their promises. When the business operates across several products or markets, those answers also need a clear relationship to one another. Preparing the content makes that relationship visible. A course description, regional homepage and campaign landing page may each sound convincing on their own, while presenting different expectations of the same company. Reviewing them together shows which differences serve a particular audience and which require a decision. This is where content preparation can lead to work on the Brand Core: the agreed foundation that guides the company’s positioning, promises and communication. 1. Identify the decisions behind the wording A request to revise a paragraph can contain several different questions. Is the information current? Does the wording explain the offer clearly? Has the company agreed on what it wants to promise? These questions need different actions. A factual error needs correction. An unclear explanation needs editing. An unsettled product promise needs a decision from the people responsible for that product. One paragraph can hide three different tasks: correct a fact, edit an explanation, or decide on a promise. For example, consider a course promoted around practical professional skills. To communicate that promise, the page needs to explain what students practise, what they produce and how their work is assessed. A description of the topics alone leaves those questions unanswered. The team therefore needs to establish what the course actually provides, which outcomes it can support and what evidence it can show. The copy can then express those decisions accurately. This gives the content review a useful purpose: identify the questions that must be answered before the website can communicate a consistent offer. 2. Use the existing materials as evidence We collect the website copy, product descriptions, campaign pages, sales materials and relevant internal documents. We compare how they describe the same audiences, products and outcomes. Each important statement needs a source and someone who can confirm it. We distinguish confirmed facts, working assumptions and missing information. A promise repeated across several landing pages still needs supporting evidence. This review also separates company-wide statements from local conditions. The group may share an educational approach, while prices, enrolment routes, contacts and available support vary by market. Those differences need to be recorded so the team knows where each statement applies. The facts-and-assumptions brief develops this review method. In our work on a multi-market EdTech project, collecting and updating content for regional websites led to a decision to work on the Brand Core. The project needed a shared foundation for preparing content across its products and markets. We prepared a collaboration framework connecting that foundation to product descriptions, regional communication and the planned CMS. It organised the questions, sources and decisions the team needed to work through. This is the part of the process the example illustrates: turning a content problem into a structured brief for company decisions. 3. Define what the Brand Core needs to resolve We use Brand Core to mean the company’s agreed purpose, mission, audiences, promise, principles, distinctive approach and voice. Each part has a practical role in the website. The mission explains what the company does and for whom. Audience priorities guide which problems the pages address. The promise defines the result the company stands behind. Its distinctive approach explains how it delivers that result. Evidence gives the reader a reason to believe it. Values need to be visible in how the company delivers its offer. For an education business, a practical approach to learning needs a concrete explanation: how students apply what they learn through course assignments, what feedback they receive from instructors and how their work is assessed. These details show prospective students what the approach means for their learning experience and give the team a clear basis for communicating it. For a business working across several markets, the same process defines what remains common and what needs local adaptation. A shared mission can guide different offers; each market still needs its own accurate explanation of how that offer works. The result is a set of decisions the team can use when preparing the next product page or campaign. 4. Give the team a clear way to make those decisions Our framework starts with prepared questions and source material. The founder, product lead and marketing team contribute their perspectives; the review makes differences visible before the group chooses a direction. We organise the discussion around specific decisions: the priority audience, the promised result, its supporting mechanisms and the boundaries of the offer. We prepare alternatives with their consequences, so participants have something concrete to assess. The company’s decision owners choose the direction and confirm product facts. As web designers working directly with the founder and team, we structure the process, prepare the questions and options, facilitate discussion and document the agreed decisions. The result is a shared brand foundation: a clear account of whom the company serves, the value it offers, the promise it makes and the evidence behind it. This foundation gives the team a consistent basis for developing product descriptions, website structure, design and marketing communication. We explore this collaboration in the founder-and-team brief. The record shows what is agreed, who approves it and what still needs information. An open question receives a responsible person and a next action. Once the decision is made, the wording can be finalised around it. 5. Carry the decisions into the website The agreed foundation becomes useful through the materials the team works with: product descriptions, audience messages, supporting evidence, regional information and guidance for writing. We then map that content to the site. The page structure determines how the visitor encounters the offer. The CMS records its sources and relationships. Design gives the information hierarchy, emphasis and a coherent visual expression. See the Brand Core communications brief and our CMS-first design article. Brand Core decisions become fields the team fills in for each audience. When a new campaign starts, the team can return to those sources and decisions, adapt the message for its audience and prepare the appropriate page. The wider system of websites, landing pages and content workflows builds on this foundation. Our website-system overview connects these parts. If preparing your website content repeatedly brings up questions about your audience, offer or promise, we can help review the materials, structure the decisions and develop a shared foundation for the site. Get in touch with parnii.de and tell us which questions keep returning during content review.

As part of a wider project to centralise marketing content for an international education business, we developed a workflow that would let the marketing team prepare landing pages without involving a designer or developer in every launch. The challenge was to preserve consistency across the decisions behind each page: the programme being promoted, the audience it addressed, the market, the regional contacts and the commercial terms. Making these decisions available in a CMS also meant defining how they related to one another and helping the team recognise incompatible selections. The workflow assumes an established Brand Core and a structured source of truth for the content. Within that framework, a manager can create a landing scenario through an AI chat or directly in the CMS. Every new item starts as a draft. Automated checks support the process; a person reviews the content and resulting page before publication. First, define what a landing page needs The company operated across several markets and time zones. Its content included course information, regional contacts, prices and commercial terms. It also included audience needs: what people wanted to achieve, what held them back, and which benefits or evidence mattered to them. We organised this information into connected CMS collections. A landing scenario then selected the relevant building blocks: Programme: the course and its supporting content. Persona: the audience, its needs and the message to emphasise. Market and branch: the regional context and company contacts. Price and optional offer: the applicable commercial information. Brand profile: the visual rules for the scenario. The scenario connected these records so the page could retrieve the relevant content without the manager copying it into each new landing page. A developed Brand Core is a prerequisite: the company’s mission, values, positioning and promise guide the content that enters the system. Product facts, audience insights and evidence need to reflect those decisions. We explore this preparation in our Brand Core article and our CMS-first design article. Turn those choices into a page In the prepared workflow we developed, a manager could describe a campaign in an AI chat connected to Wix CMS through MCP — a connection that lets the chat work with the CMS. The prompt created a draft landing scenario using the existing content and page setup. Publication remained a separate step, following human review. These choices can also affect the page’s layout. For example, a campaign with a promotion can show a dedicated offer section with the discounted price and conditions. A campaign without a promotion uses the standard layout. The manager selects the offer in the CMS; the page uses the prepared rules to display the appropriate version. Wix Studio supports this through page variants. We explore how to design those versions in our page-variants guide. With the content, templates and connections already prepared, a manager could assemble a landing page in around 10-15 minutes, then complete the final review before publication. The content modelling and design work happened beforehand. We compare other approaches, suited to different stages of company readiness, in our guide to independent landing-page launches. Support the manual route too A manager could also create a draft directly in the CMS, selecting the same connected records manually. We added Wix data hooks — code that runs around database operations — to check the scenario when it was added or updated. The checks wrote explanations into a separate Validation Notes field. For example, if the selected branch belonged to a different market, the field displayed: The selected Branch belongs to a different Market. The manager could see the mismatch and correct the selection. Missing information was also surfaced, such as an unselected programme, persona, price or brand profile. We added Wix data hooks — code that runs around database operations — to check the scenario when it was added or updated. The checks wrote explanations into a separate Validation Notes field. These checks made previously defined rules visible at the point of work. The manager could correct the draft, review the content and resulting page, and approve publication once the scenario was ready. Automated validation was one part of that review. The next step: from landing page to advertising brief The next step: from landing page to advertising brief (AI-generated image) The same agreed content can also support the advertising materials that bring people to the page. The next step is to make publication of the reviewed landing page the starting point for preparing a creative brief and production specifications. The brief would bring together the audience, message, offer, evidence and brand guidance; the specifications would define the required formats and assets. These documents would then go to an external production system. We have already tested the onward connection using Wix CMS, Wix MCP, ChatGPT and ElevenLabs MCP to create advertising materials from the structured campaign context. I submitted the experiment to an ElevenLabs Challenge, where it received an Honorable Mention. The workflow and its results are the subject of a planned case study. Victor Anferov, parnii.de What makes this possible Before introducing this workflow, a company needs a developed Brand Core, reliable content, a clear model of how its records relate and agreed templates. It also needs people responsible for maintaining the information and reviewing each landing page before publication. The checks can then reflect actual business rules: which branch serves which market, which price applies, and which information a scenario needs. Want your marketing team to launch landing pages independently? We can help structure your content, build the Wix CMS and dynamic templates, and add checks that guide your team through each launch. Get in touch with parnii.de and tell us which products and markets your team works with.

For founders and leaders of small, established teams, AI opens up possibilities across the creative process—from the first idea to production and evaluation. Understanding where it can help requires a view of how the whole team works. I see a growing role for an external partner who combines a fresh perspective with a deep understanding of the business. Someone who follows the work, notices duplicated effort, slow handovers and the context people carry in their heads, then helps choose tools that address those specific problems. The purpose is to make the team’s work easier and more meaningful while creating room for the business to grow. Every new tool also asks something of its users: learning, switching attention, checking outputs and making decisions. Individual tasks can become faster while the overall mental workload increases. Giving someone several additional responsibilities and calling it efficiency leaves that cost out of the picture. A single task gets faster, but learning, switching attention, checking and deciding add to the day. A useful starting point is a shared conversation: What improves for the business? Faster launches, better quality or the ability to explore ideas the team previously lacked time for? What improves for the people? Which repetitive tasks disappear? Where do they gain autonomy or time for work that uses their skills? What changes in the role? Agree on responsibilities, decision-making authority, learning time and how added responsibility is recognised. Three questions to answer together with the founder and the team before choosing a tool. We explore how to structure those decisions with the founder and team. Giving marketing managers the ability to launch landing pages independently, for example, means preparing both the tools and the conditions in which people can use them confidently. That partner’s work continues through the transition: trying tools on a real task, redesigning the workflow, helping people learn, evaluating results and adjusting what causes friction. Management gains a partner it can rely on; the team gains someone who keeps its experience and capacity in the conversation. As web designers, we bring this perspective to websites and the content processes around them. We look at the complete journey, including the checking and coordination between individual tasks. Want to explore where AI could help your team’s website and content work? We can map the process with you, identify a useful pilot and support the transition. Tell us what you would like to improve.

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. The method at a glance: four phases, eight steps, and the article in this series that covers each step in depth. 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.

When a company promotes several products to different audiences and markets, its website needs to support those variations. Product facts, audience-specific messages, regional contacts and commercial terms all have to reach the right page. The marketing team also needs a clear way to maintain that information and prepare the next campaign. CMS-first web design starts by organising this content and the relationships between it, then uses that structure to develop the pages and the team’s editing workflow. CMS stands for content management system. In this approach, it becomes the working source for the information your website displays. For a founder, the practical question is: how should the site be designed so the team can keep its content accurate and use it across new pages? 1. Start with the work your team needs to do Before defining fields or page layouts, we identify the recurring tasks. Does the team need to introduce new products, adapt an offer for another audience, change regional contacts or launch a promotion? Each task tells us which information stays shared and which needs its own version. A product description can serve several campaigns. The message explaining its value to a particular audience needs to reflect that audience’s priorities. A price belongs to defined commercial conditions; a regional contact belongs to the market it serves. These distinctions rely on agreed business decisions. The company needs to know what it offers, who it serves, what it promises and which evidence supports that promise. A developed Brand Core gives this work a consistent direction. We explain how that foundation enters everyday communication in the Brand Core communications brief. The result of this first step is a practical content inventory: the information the site needs, its source, where it is used and who maintains it. 2. Give the content a structure the team understands We then group related information and define how the groups connect. In Wix CMS, a collection holds a set of records, such as products or regional offices. Each record has fields for its details. A reference links a record to information stored in another collection. For example, a campaign can refer to an existing product and regional office. The team selects those records when preparing the campaign, so their details can be retrieved without being copied into every new page. Our landing-page workflow for a multi-market EdTech project provides a concrete example. A landing scenario connects seven sets of information: the programme, Persona, market, regional branch, price, optional promotion and visual brand profile. The scenario records the choices for one campaign. The connected records hold the content those choices require. This gives the manager a clear task: select the programme and audience, choose the market and its contacts, then select the applicable price and promotion. Shared information has a defined source. Audience-specific messages and local commercial terms retain their own context. We explore the full educational content model in the educational CMS brief. 3. Design how that content becomes a page The content structure informs the design. We decide which information appears first, how the page explains the offer, where it presents evidence and how it leads to the next action. We connect the page’s text, images and other relevant elements to their CMS sources. In Wix, a dynamic item page uses a prepared design to display the content for a particular record at its own URL. The same design can therefore serve multiple campaigns. The designer also prepares the variations those campaigns need. A landing page with a promotion can include a special-offer section showing the promotional price and conditions. Without a promotion, it presents the regular offer. The manager’s selection determines which prepared version the visitor sees. Visual exploration and content modelling develop together. Testing real content in the layout reveals whether the model supplies everything the page needs. A longer audience message, several pieces of evidence or different price conditions can each affect the composition. This step produces both a usable page design and a clear map of where its content comes from. The same source information can also support a compact campaign page or a fuller product page, with each presenting the detail its reader needs. See the sitemap-to-CMS brief and our page-variants guide. 4. Make editing and publication part of the design The team’s interface needs as much thought as the visitor’s page. Managers need understandable field names, instructions and a clear distinction between changing shared information and configuring one campaign. Changing a shared product description affects the connected pages that use it. Selecting another price for a campaign changes that campaign’s offer. The editing process should make the scope of each action clear. In our landing workflow, a new scenario starts as a draft. The system checks the selected records and highlights missing or incompatible information. The manager corrects the selections, reviews the resulting page and approves publication. Our CMS validation case shows this process in detail. Content owners maintain product facts, messages and commercial terms. Designers and developers prepare the display rules and extend the system when a new campaign needs a different structure. This division gives the team autonomy within a process it understands. CMS-first brings content, design and responsibility into the same project. The work creates a site that can support regular updates and prepared campaign variations, with a clear route for introducing new requirements. Our wider guide explains how this fits into a managed system of websites and landing pages. Does your team regularly update products, offers or campaign pages? We can help organise the content, design the Wix CMS and page templates, and prepare an editing workflow around the work your team needs to do. Get in touch with parnii.de and tell us what changes most often on your site.

Looking for CMS in Wix Harmony and finding instructions for a different Wix editor? That’s where things get confusing. In Harmony, the route starts with a repeater. This short video shows where to find the controls, connect a collection and open it to manage your content. It uses official Wix Harmony screenshots. Watch the guide on YouTube Add a repeater In the Harmony editor, open + Add → Elements → List → Repeaters. Choose a repeater and drag it onto your page. A repeater displays several items using the same layout: a row of project cards, for example, each with its own image and text. A collection holds the content those cards use. The starting point is under List → Repeaters in the Harmony editor. Screenshot: Wix Help Center. Connect a collection Select the repeater and choose Connect Collection. Create a new collection, or select an existing one if it already contains the content you want to display. This is the step that is easy to miss when you are looking for a separate CMS button. Adding an element that uses collections brings CMS into the site. Choose a new or existing collection, then connect it. Screenshot: Wix Help Center. Open the full collection Select the connected repeater and choose Manage Items → Open collection. The Open collection link sits at the bottom of the panel. You can also click the collection name near the top. Manage Items gives you a route to the full collection. Screenshot: Wix Help Center. What if the option is missing? Wix is rolling out CMS functionality in Harmony progressively. If the controls are missing, the feature may not be available in your account yet. These steps describe the documented workflow for accounts where it is available. Official guide: Adding and Setting Up Repeaters in Wix Harmony What’s New with the CMS in Wix Harmony

A small experiment in context, with a font I recently made. Embrace the spirit of discovery with this bold pink lettering against a dark green background, urging everyone to "Stay Curious." Put “Stay curious.” on a green poster in pink letters and I hear an invitation. Put it over a road disappearing into fog and I start wondering whether curiosity is a good idea. An atmospheric, monochrome study invites the viewer to embrace curiosity on a quiet, winding road beneath bare trees, blending mystery and familiarity. The words are identical. So is the font. But the road gives the invitation somewhere to lead, and very little information about what might be waiting there. Suddenly, those soft letters feel a little less reassuring. The font and words stay the same. Colour, imagery, scale and spacing change the reading Kirill Hi. I design for the web and experiment with type, code and motion. Sometimes a small detail turns into a project of its own. This font started that way. Finding the edge I tried this with Parnii Biotic, a display font I recently made using Plus Jakarta Sans as an open-licensed starting point. The original idea was a small family for web layouts: something expressive for headlines, something quieter for subheadings, and a cut for smaller text. I wanted to see how much character could come from the letters themselves. Plus Jakarta Sans ExtraBold — the open-licensed starting point. Parnii Biotic Display — the derived font, at the same type size and baseline. Metaballs were an early reference: soft forms that appear to pull towards each other and gather into larger shapes. I was interested in the tension around their edges. The letters should feel organic, as if they had settled into place but might still move a little. On the bright poster, that softness reads as playful. Against the fog, the uneven outline starts to feel unfamiliar. There is enough weight to hold the composition, and enough irregularity to leave its mood open. The rounded forms can be friendly without making every setting feel childish. The irregularity is part of the exported contours. These are two letters from the final font, enlarged without additional effects. Getting there took a few wrong turns. Rounding the corners made the original font look softer, but the result felt too tidy. A regular wave introduced a pattern I kept noticing. Smaller fluctuations along the edge were more interesting: a swelling here, an indentation there. I had to keep putting them into words to see whether they worked. A headline has to work on a page A letter enlarged on a blank canvas can be convincing. A headline on a page asks more of it. The spacing starts to matter, the surrounding text competes for attention, and the same contour may barely register at a smaller size. The subheading needed to be judged as a subheading. Looking at everything large was hiding useful information. A scale check, not three separate cuts: the same Display font at 72, 32 and 16 px, paired with Arial. Sizes refer to a 1000 px-wide view; smaller screens scale the whole sheet. I moved between browser experiments, a small Python tool and installed font files until the processed contours travelled with the font. That made the two posters a useful comparison: I could keep the letterforms fixed and change the world around them. The same forms, in motion The display cut became the focus because it held the organic quality most clearly. In the motion study, those same fixed letterforms lift, rotate and settle. The gentle timing adds another layer of playfulness. Change the pace and the surrounding scene, and there is another direction to explore. Actual letterforms from the font, animated through position, rotation and scale. 15 seconds, no audio. This is what keeps me interested in web design. A photograph changes how a line of copy sounds. A type choice changes how much space a section needs. Movement changes where attention goes next. The impression comes from how those decisions work together, and each adjustment can make me reconsider the others. Having a direction helps me decide what to keep; knowing the tools gives me ways to try it. Sometimes that means changing the layout. Sometimes it means writing a small tool or taking the same words into a completely different setting. I still like both “Stay curious.” posters. I would follow the invitation in one of them a little more cautiously. Sources and licence Parnii Biotic Display is a modified font based on Plus Jakarta Sans, by The Plus Jakarta Sans Project Authors, and is released under the SIL Open Font License 1.1. Original copyright notices and the full licence are included with the font. Original project. Atmosphere-study photograph by Keagan Henman on Unsplash. Cropped and colour graded; lettering composed in Python using the released Parnii Biotic Display font. View the source photograph.

The Architect’s Guide to HIPAA on Wix A comprehensive deep-dive into regulatory frameworks, technical implementation strategies, and risk management for healthcare web deployment. 1. Introduction: The Convergence of Low-Code and Regulation The digital transformation of the healthcare sector has precipitated a fundamental conflict between the need for agility in web deployment and the rigid, absolute mandates of data privacy laws. In the last decade, the democratization of web development through 'low-code' platforms has enabled private practices to deploy sophisticated digital presences without overhead. However, Wix has historically occupied a contentious position within this ecosystem. For years, the prevailing consensus among HIT compliance officers was that Wix represented an unacceptable risk for any entity handling Protected Health Information (PHI). This assessment was predicated on a lack of granular data controls and the absence of executing Business Associate Agreements (BAAs). Today, however, the landscape has shifted. Wix now exists in a superposition of compliance states: it is simultaneously a non-compliant liability for the uninformed user on a standard plan, and a robust, BAA-backed secure environment for the enterprise subscriber. This duality presents a unique challenge for architects who must navigate a complex matrix of feature sets to achieve a defensible compliance posture. 2. The Regulatory Landscape: Deconstructing HIPAA for SaaS To effectively architect a solution on Wix, one must first understand the specific regulatory pressures that define 'compliance' in the context of a hosted Software-as-a-Service environment. HIPAA is not a monolithic statute but a layered framework of rules that have evolved to address the realities of digital information. The Privacy Rule defines PHI broadly. On a Wix website, PHI is generated the moment a user interaction moves beyond anonymous browsing. A name and an email address submitted via a 'Contact Us' form constitute PHI if the context implies a patient-provider relationship. Furthermore, if a Wix website stores form submissions in its internal database (Content Manager), that database becomes part of the 'designated record set,' imposing a legal obligation to be able to retrieve, export, and amend that specific data point upon patient request. The Security Rule acts as the technical operationalization of the Privacy Rule. It mandates specific administrative, physical, and technical safeguards. For a cloud platform, the critical deficiency in standard plans is often the lack of 'read-access' logging. While standard plans log design edits, they rarely log which admin viewed a specific patient's form submission, a key requirement for HIPAA audits. The Omnibus Rule & The BAA Mandate The 2013 Omnibus Rule was a watershed moment for cloud computing. It clarified that web hosts are 'Business Associates' if they have persistent access to data—even if encrypted. Therefore, Wix is a Business Associate. A Covered Entity cannot legally use Wix to store PHI unless Wix enters into a Business Associate Agreement (BAA). This contract sets the rules of engagement: it legally binds Wix to report breaches to the Covered Entity and to honor data subject requests. Without a signed BAA, using the platform for PHI is a violation of federal law, regardless of technical security measures. 3. The Wix Architecture: A Comparative Analysis The platform essentially operates as two distinct products: the mass-market consumer platform and the gated, compliance-ready enterprise environment. Understanding this dichotomy is essential for cost-benefit analysis. The Standard Infrastructure (Non-Compliant) The standard tier includes plans like 'Core' and 'Business'. On these plans, Wix explicitly states it will not sign a BAA. The Terms of Service likely contain a specific clause prohibiting the storage of PHI, effectively transferring all liability to the user. Critically, support agents for standard plans often possess 'break-glass' tools that allow them broad visibility into site data to resolve technical issues rapidly. While excellent for uptime, this access model is incompatible with HIPAA's strict 'Minimum Necessary' standard for data access. The Enterprise Infrastructure (Compliant-Ready) Navigate to Dashboard > Privacy & Cookies > HIPAA. The 'Sign Now' button is your first step to legal compliance. The 'Business Elite' and Enterprise plans introduce a 'PHI Protection' mode. This is not merely a legal label but a technical reconfiguration. It likely triggers a migration or configuration change that isolates the site's data or applies stricter encryption keys. The 500% price differential pays for legal overhead, segregated infrastructure, and liability absorption. By signing the BAA, Wix accepts a portion of the financial and legal risk associated with a data breach, which justifies the higher recurring revenue. → Read Official Documentation 4. The Hybrid 'Workaround' Model: Compliance for the Mass Market For the vast majority of private practitioners, the cost of enterprise plans is prohibitive. This creates a market reality where compliance must be achieved on the standard infrastructure. This is the 'Hybrid Route,' where Wix acts solely as a presentation layer, and all PHI handling is offloaded to compliant third-party vendors. In this model, the Wix site is conceptually treated as a public billboard. It contains no interactive data collection that touches Wix servers. You must disable native forms, comments, and member areas to prevent accidental data leakage. The iFrame Integration Strategy To collect patient intake forms without breaking the law, the architect must select a specialized vendor that signs a BAA for lower-cost tiers (e.g., Hipaatizer, JotForm, or Cognito Forms). These vendors provide embed codes (iFrames) that are placed inside the Wix site. Technically, when a patient types into this form, the data flows directly from their browser to the vendor's encrypted cloud, bypassing Wix's servers entirely. The Wix backend never 'sees' the data. This effectively removes Wix from the chain of custody, negating the need for a Wix BAA. Operational Risks and Discipline The Hybrid model is fragile. It relies on strict human discipline. A staff member might accidentally add a standard Wix 'Subscribe' form to the footer, creating a data leak. Unlike the Enterprise mode, the standard dashboard does not prevent this. Furthermore, practices must be wary of 'email links'. A simple 'mailto:doctor@clinic.com' link is dangerous because standard email is not encrypted. Practices must use HIPAA-compliant email providers (like Google Workspace with a BAA) and discourage patients from sending sensitive info via email. 5. Native Compliance: The Enterprise Pathway For organizations that select the Business Elite plan, the 'Native Compliance' pathway allows the use of Wix’s built-in tools. The activation mechanism is a distinct workflow within the Wix Dashboard. The 'Activate PHI Protection button. WARNING: This may break non-compliant third-party apps installed on your site. Upon clicking 'Activate PHI Protection,' the system enforces a whitelist. It scans installed applications against an internal database of compliant apps. Non-compliant apps are sandboxed or removed. This automated enforcement is a significant administrative safeguard, preventing human error in app selection. Behind the scenes, this likely enables the 'PII' flag globally for the site's data collections, ensuring that all subsequent data writes to the Content Manager are encrypted with a site-specific key. → Read Official Documentation Managing Data Subject Rights Dashboard > Privacy & Cookies > Visitor Data. Use 'Data request' to export user records for HIPAA/GDPR fulfillment. A compliant system must be able to respond to patient requests. The Native Route integrates DSR management into the dashboard. If a patient requests a copy of their data, the 'Visitor Data' tab allows the admin to query by email or phone number and aggregate data from Wix Stores, Bookings, and Forms into a portable format. However, the platform emphasizes verifying the requestor's identity before submission. A malicious actor might impersonate a patient to request a data dump. The platform provides the tool, but the process of verification remains a manual responsibility of the practice.