Wix Website
created for you

In Wix Studio, layouts are designed visually. What matters is not just the freedom to position elements. Text, images, navigation and user journeys must also work together effectively at narrower widths. A layout that looks elegant on a large screen can become cramped or confusing on a phone. That is why we plan spacing, order and flexible sizing from the outset. The simplified design canvas illustrates this relationship without recreating the real interface.

Select text, an image or a button and move the element using the arrows. Your choice of device changes the available workspace. In a real project, we also set sensible limits: text needs enough width to remain readable, a button must remain accessible, and important content must not be visible only on desktop. Responsiveness therefore means more than shrinking a finished page. We review the hierarchy of your information and test the design with both short and longer content.

Recurring content can be organised into collections. Rather than recreating each team member, service or article on a separate page, suitable fields are defined. A shared layout can then generate dynamic pages from them. This makes maintenance easier when the content structure is stable and clearly defined. The demo uses three fictional entries and runs entirely in your browser. The title, category, description, image and status update the preview immediately.

For your project, we review which details are genuinely needed and who may edit them. Required fields, clear field names and well-organised images help with future work. Publication status and permissions need to be configured deliberately; a CMS does not automatically make private information secure. Before handover, we test the planned editing workflows with typical content. If the structure expands later, we review the effects on existing records, navigation and dynamic pages together.

An appointment website needs more than a calendar. Visitors need to know what a service includes, which details are required and what happens after an enquiry. Wix Bookings can support different booking workflows; availability, rules and the required plan are checked separately. We distinguish between a binding booking and a non-binding enquiry. This decision affects the wording, form fields and confirmation. The preview only provisionally selects a demo appointment.

For the real setup, we discuss services, duration, staff allocation and organisational constraints. Cancellations, rescheduling and notifications are also part of the process. We avoid unnecessary required fields to keep getting in touch straightforward. Before a booking feature goes live, we test the planned workflows and the feedback shown to users. The demo does not send an email, create a customer record or reserve a time slot. Your entries disappear when you reset or leave the page.

A multilingual website needs consistent content and clear ways to navigate between languages. Headings alone are not enough: navigation, buttons, descriptions and contact information must align. Wix Multilingual offers language management options; we check support for specific business features and CMS content against your intended scope. In this local preview, German, English and French switch independently of the language of the Widmer & Kunz website. The displayed URL path changes too.

Before implementation, we define which pages should be available in which languages and who approves translations. Incomplete language versions are not presented as finished content. For search engines, we consider each version’s page structure, titles and language associations. Translation is also a content task: offerings, terminology and calls to action must suit the target audience. Automated assistance can be useful, but it does not replace subject-matter and language checks.

When standard features are not enough, custom workflows can be implemented with Velo and suitable interfaces. However, a conditional form field, a calculation or targeted processing of CMS data needs a clear specification. We first describe which inputs are allowed, how they are validated and what feedback should follow. The required functions are then programmed and tested. The schematic preview shows how the workflow changes with your selection.

Additional features bring responsibility. Data access, error handling, notifications and ongoing support all need to be considered. An automated email does not become a reliable process simply through a visible checkbox. We assess which solution is possible within Wix and where an external service might be useful. The demo only shows a workflow state. It does not run any code on your Wix account or change any data or permissions.