WOW Tort: an editable cake catalogue on Webflow.

The saved first screen shows a cake being decorated, with a warm muted overlay across the image. Light typography and a rounded pale button sit above that scene. Navigation gives direct access to the catalogue, delivery, vacancies, partners and news. The composition connects the product with the act of making it, while the order action remains easy to identify against the background.

The large lettering near the lower edge gives the opening a strong graphic scale. It is a different layer from the practical menu and the short request button. In a comparable food catalogue, the important question is whether this expressive treatment leaves the product and action understandable on a phone. A dramatic crop can work as a background, but it should not make the only available example of a cake impossible to inspect.

The project records describe separate catalogue categories for signature cakes, classics, gingerbread and pastries. These are different starting points within the same business. Someone choosing a large celebration cake and someone looking for smaller sweets should not have to interpret one undifferentiated image collection. Categories give the visitor a way to narrow the subject before asking about a particular item.

A useful catalogue image also needs a relationship with its description. The photograph may illustrate a decoration, while the available flavour, weight or final configuration needs clarification. For a similar project, we would agree with the bakery which details can be selected directly and which require a conversation. The visual should invite a specific question rather than imply that every pictured combination is available for every date.

The owner’s ability to update the catalogue was a central part of the brief. That means the content structure matters as much as the first prepared set of images. A new cake needs a category, a clear name, appropriate imagery and consistent price information. When those relationships are established, adding another entry can follow an understandable process instead of becoming a small redesign each time.

The recorded catalogue supports a regular price and a separate promotional price. This gives the owner a way to manage an offer without rebuilding the product layout. The useful design question is how a visitor distinguishes the current amount from a comparison amount, and understands what the price applies to. A visual strike-through alone cannot explain whether the figure is for a whole cake, a unit of weight or a particular example.

For a comparable catalogue, we would agree price labels, units and the conditions under which the promotional field appears. A removed promotion should not leave contradictory numbers on a card and an inner page. This is a content maintenance requirement, not a claim that the project produced a measured increase in orders through discount presentation. The business remains responsible for approving the amount and the terms it publishes.

The same care applies to individual decoration. If the final price depends on a discussion, the page should explain that relationship rather than use a precise-looking number to imply a fixed offer. A visitor can still begin with an indicative product and ask for confirmation. Clarity about what is being priced helps both sides make the next conversation useful.

The project notes describe a concise form with flavour, weight, date and contact. Those fields reflect the information selected for the first request. Their presence does not prove that every additional field would cause abandonment, and the case does not claim a tested conversion lift from reducing the form. The practical objective is a request that the bakery can interpret and answer.

For a similar build, we would compare the form with the team’s actual first conversation. A field is useful when it changes how the enquiry is handled or prevents avoidable clarification. Information that requires detailed agreement may belong later. The confirmation message also deserves attention: it should tell the visitor that the request was received and explain the next step without implying payment, acceptance or a guaranteed delivery slot.

Delivery, partner information, vacancies and news are included in the recorded site structure. They serve different visitors and should not compete with the main cake-selection route. A job applicant or potential partner needs a recognisable place to begin, while a customer needs to find practical ordering information. The navigation gives these subjects names instead of expecting every visitor to use one general message.

The delivery is a Ukrainian Webflow website with an editable catalogue and enquiry form. The records do not establish an integrated payment checkout or a live production calendar, so those features are not claimed here. Nor do we publish order volume or revenue results without supporting data. The case shows a content and interaction approach that can be assessed from the work itself.

For your own bakery site, bring representative products, approved prices, delivery information and the questions your team needs to answer before accepting an order. Identify who will update new designs and promotions. These inputs let the website combine a strong visual first impression with a practical catalogue, so the visitor can move from liking a cake to asking a clear, answerable question.