Service discovery depended on dense navigation
The header packed service labels, nested services, specialty content, experts, company pages, and request actions into a narrow space.
Selected work Bilingual CMS and website revamp
ParioQuantify Site Revamp
Live website redesign
I redesigned a bilingual property-services website, turning a 191-record content catalog into nine reusable CMS templates with clearer service navigation.
Project / 2026 redesignBilingual CMS and website revamp
- Role
- UX/UI designer, frontend developer and CMS implementer
- Context
- Davies North America · ParioQuantify website
- Timeline
- 2026 website redesign
01 / Overview
My contribution
Content audit, UX/UI, responsive frontend and Razor/CMS template implementation
ParioQuantify helps insurers, property specialists and legal teams assess property losses. The site needed to explain closely related services without making visitors read the entire service catalog.
I audited the content, designed the navigation and page layouts, and built the responsive templates in Razor and XHTML. The implementation had to fit the existing CMS and support both English and French content.
- Working with
- In-house cross-functional collaboration
- Scope
- Content audit, bilingual IA, responsive design, CMS implementation and migration checks
- Tools
- Tailwind CSS, Razor/C#, XHTML, JavaScript, PowerShell
191
CMS page records cataloged
The revamp catalog maps 105 English and 86 French page records.
9
Reusable page templates
Home, services, service details, content, listings, people, articles, contact, and request forms share one system.
EN + FR
Bilingual delivery
Route-aware navigation and page content support both languages through equivalent patterns.
EvidenceThe 191 records and nine templates are documented delivery counts; visitor impact has not been measured.
02 / Problem
Finding a service meant navigating a crowded menu.
Page hierarchy varied by template
Large headings and wide text blocks made the reading order unclear. Related services and next actions were easy to miss.
Responsive behavior needed explicit rules
Navigation, nested menus, long service names, request forms, and bilingual labels each needed layout rules for smaller screens.
Project context
Specialist services needed distinct routes
Audit review, appraisals, catastrophe response, dispute resolution, contents valuation, legal support, and specialty work each needed a clear navigation path that retained their sub-services.
Preserve the service catalog
The redesign needed to retain established service content and bilingual page relationships while changing how people moved between them.
Templates had to support everyday CMS work
Editors needed reusable placeholders and predictable templates for the homepage, services, expert profiles, articles, and forms, with a consistent way to maintain both languages.
Before and after
A clearer structure for service information.
I gave the service introduction a narrower reading column and placed related-service links beside it. The heading identifies the service before visitors reach the detailed copy.
Previous layoutRedesigned layout
Name the service first
The service label and heading identify the page before the visitor reaches the detailed copy. The image sits within a smaller, defined area.
Shorter lines for the introduction
The introduction moves from a wide centered block into a narrower column with a defined reading order.
Related services beside the content
A sidebar links to related services so visitors can continue without reopening the main menu.
03 / Design decisions
A service website built to be maintained.
Keep related services in reach
A visitor assessing a property loss may need more than one service. I placed related-service links beside the introduction and kept the request action in the shared navigation, giving the page a clear onward path.
Make nine templates serve the full catalog
I organized the 191 records into nine templates: home, services, service details, content, listings, people, articles, contact and request forms. Optional regions let editors vary the content within each layout.
Give both languages room on mobile
Service names and French labels need space to wrap. The compact menu and language switch sit above the service heading, while the introduction uses a single reading column.
The language switch, page heading and introduction remain in a clear sequence at a 375px viewport.
Design process
Audit the live system
I audited pages, navigation labels, service relationships, forms, expert records, metadata and bilingual content before designing the layouts.
Map content to page types
I grouped the catalog into reusable page types before building the layouts. Service detail, expert, article and request pages each needed different fields and reading priorities.
Build the templates in the existing CMS
I implemented the layouts in Razor and XHTML, with shared Tailwind styles, navigation, and scripts to check the migrated content.
Reusable patterns
Semantic design tokens
ParioQuantify purple, teal, neutral surfaces, typography, spacing, borders, and container widths are encoded once in the Tailwind theme.
Optional CMS content regions
Templates omit optional regions when they have no content, so editors do not have to work around empty sections.
Migration and QA tooling
Validation scripts check content shape, bilingual people records, migration output, and generated CSS before release.
04 / Gallery
Project images
The homepage introduces the service offer
The homepage introduces property assessment, then directs visitors to services and the request form.
05 / Outcomes
What the redesign delivered.
A published website redesign
The redesigned homepage and service pages are live, with shared navigation, bilingual content and service-request actions.
Nine templates and a bilingual content catalog
Shared styles and page structures support 105 English and 86 French CMS records.
A consistent path from service information to a request
The service template keeps a readable introduction, related services and the request action in defined places across the site.
How the work was reviewed
Before-and-after layout review
Matching service routes were captured at desktop and mobile sizes so hierarchy, content parity, and responsive behavior could be compared directly.
CMS content audit
English page content was exported and compared to source records, with structured checks for missing or mismatched regions.
Automated migration checks
People data, page records, wording, and generated CSS run through repeatable validation commands before release.
Looking back
The content inventory shaped the design more than any individual page. Different content types needed different structures, with shared navigation and editing rules.
The next evaluation should ask visitors to identify the right service and begin a request in both languages. That would test whether the revised structure helps them complete the task.