OM Defence Systems: improving the structure of a Webflow site.

A website can look coherent while its internal structure makes ordinary changes difficult. In this project, the starting point was an existing design that needed to remain recognisable. Replacing it with a new visual concept would not have answered the core request. The work concerned how the pages were assembled, how styles were named and reused, and whether interactive elements opened the correct content.

The saved first screen uses a dark background with red imagery, a large white headline and a light call-to-action. A compact header separates product navigation from the newsroom, careers and contact. Those visible choices establish a particular presentation. Preserving them meant treating the existing site as a reference during the rebuild, rather than assuming that every internal improvement should produce a visibly different homepage.

For a comparable project, the initial review should identify which parts are approved and which defects need correction. Otherwise the word redesign can hide two different tasks: a visual change and an implementation repair. OM Defence Systems illustrates the second kind. Its main value as a portfolio example is the ability to work within an existing presentation while making the underlying structure more understandable.

The project records describe renaming close to three hundred classes into a consistent system. The number indicates the extent of the recorded cleanup; it does not by itself measure quality. A meaningful name helps another editor or developer understand what a style belongs to. The more important question is whether its use remains consistent across components, pages and responsive states after the renaming.

A class may affect more than the element currently visible on screen. It can be shared by several cards, nested within a component or referenced by an interaction. For a similar refactor, changing names should therefore be paired with checking their relationships. Otherwise a tidy-looking style list can conceal new differences between pages. This is why structural cleanup deserves a review of representative templates rather than a quick look at the homepage alone.

The system also needs boundaries. A shared rule should represent something genuinely shared, while a specific variation should remain identifiable. Combining unrelated sections under one name makes later edits unpredictable. Creating a different class for every nearly identical element produces another kind of maintenance burden. The useful outcome is a set of patterns that a successor can understand and apply with reasonable confidence.

The recorded delivery includes CMS collections for the newsroom and careers. These areas contain information that changes independently of the principal page layouts. A new article or vacancy should use an agreed content structure rather than require rebuilding the surrounding design. The distinction is useful for a team that needs to publish updates while keeping the overall presentation consistent.

CMS fields do not remove editorial responsibility. Titles, dates, descriptions, images and publication status still need an owner. For a similar company website, we would agree which fields are required, who approves the content and how outdated entries are handled. Those decisions prevent an editable section from becoming a collection of incomplete records. They also make handover more concrete than simply giving someone access to the editor.

News and vacancies should not be forced into one identical model just because both are collections. A vacancy can need role-specific information and an application route; a news item has its own reading context. The implementation should reflect the content actually being maintained. In this case, the relevant result is that both sections were included in the recorded CMS scope, not a promise that every future change will be possible without technical help.

The original delivery records a pass over titles and page structure. Those elements help a website describe its content consistently. They belong in a structural rebuild because a corrected interface should still expose meaningful page information. However, preparing titles does not establish search demand, guarantee indexing or show that a page has gained positions. Those outcomes require separate observation of the published site.

For a similar refactor, the address map should be checked alongside the page content. Keeping an existing design does not automatically preserve every route, and a visually correct page can still have a broken internal link. An acceptance list should therefore include important addresses, navigation destinations and page descriptions. We would base that list on the actual site being changed, rather than claim that a generic SEO checklist proves business growth.

OM Defence Systems is relevant when a company already has a visual direction but its website is difficult to maintain or contains inconsistent interactions. The recorded result combines class cleanup, corrected assets and modal routing, CMS work and page-structure preparation within Webflow. These are concrete implementation tasks that can be scoped and reviewed without replacing the company's identity.

We do not publish a measured increase in enquiries or an independent assessment of the company's products here. For a similar project, bring access to the existing site, a list of recurring editing problems and examples of the presentation that should remain. That makes it possible to distinguish necessary repairs from optional visual changes and agree a reviewable scope before the site is rebuilt.