Opens in a new tab

our project

Walker Awning

Website Redesign & Elementor-to-Bricks Migration

An Elementor-to-Bricks rebuild with 7 service page structures, 9 market page structures, ACF-managed content and a conditional inquiry form. The project combined a redesign with checks of established URLs and essential website functionality.

Project Metadata

Client
Walker Awning
Founder / Creator
Target Market
Residential and commercial customers across South Florida, USA
Year
2026
Status
Ongoing
Duration
Core stack
WordPress, Bricks Builder, Advanced Custom Fields, Custom Taxonomies, Custom Post Types, CSS, Rank Math
Explore the ProjectDiscuss Your Website

// Delivered Structure

A Rebuild with Room to Grow

The work combined a redesigned interface with an editing system for continued publishing. These figures describe the delivered structure and verified migration work.

/01

7

Service Page Structures

Reusable Bricks structures give service content a consistent starting point.

/02

9

Market Page Structures

Who We Serve layouts organize content for different customer groups and applications.

/03

1

Custom Conditional Inquiry Form

The form displays different follow-up fields according to the visitor’s choices.

/04

9

Established Pages Restored

The client independently confirmed these pages return 200, allow indexing, use self-referencing HTTPS canonicals and appear in the page sitemap.

// Business Context

Make the Website as Useful as the Work It Represents

Walker Awning serves customers with very different projects in mind. Its website needed to explain that breadth, show relevant work and collect useful inquiry details. Behind the interface, the team needed a consistent way to create services and market pages.

Target audience

Homeowners, property managers, business owners, contractors and decision-makers at restaurants, schools and resorts exploring custom awnings, canopies and shade structures in South Florida.

A Broad Offer, Several Customer Journeys

Walker Awning designs and builds custom awnings, canopies and shade structures for residential and commercial properties in South Florida. Its completed work spans different building types, uses and customer requirements.

A visitor might begin with a particular solution, a type of property or an example of an installation. The redesigned website needed to accommodate those starting points and help visitors move toward an informed inquiry.

The client also planned to keep adding content after launch. The editing experience therefore mattered alongside the public-facing design.

Change the Design and the Publishing Foundation Together

The project involved moving an existing Elementor website to Bricks while changing its design. Recreating individual pages would only address part of the brief: the new implementation also needed a repeatable structure for services, markets and projects.

FOQIRA had to decide which information belonged in editable fields, which categories belonged in taxonomies and which layout decisions should be shared through templates. That separation would let the client create more content within a coherent system.

The inquiry process introduced another requirement. Different selections needed different follow-up questions, so the form had to adapt to the request. Existing public URLs and useful content also needed to remain accessible through the migration.

// Three Goals Behind the Technical Decisions

The redesign focused on how visitors understand the offer, how the team publishes content and how an inquiry reaches the business.

01

Make Services and Markets Easier to Understand

Give visitors distinct routes through the available solutions, the customers they serve and the work already completed. Use consistent design and photography to make those routes easier to follow.

02

Build a Content System the Client Can Use

Introduce ACF fields, taxonomies and reusable Bricks structures for services and markets. Keep editorial inputs separate from the layout rules that maintain consistency.

03

Collect Details That Fit the Inquiry

Create a custom form that responds to the visitor’s selections, revealing relevant follow-up fields for the request they are making.

// Strategy & Architecture

Define the Content Model Before Repeating the Layout

We separated the website into services, markets, projects, resources and inquiries. Each layer has a different job: explain a solution, establish its relevance, demonstrate completed work, answer a question or start a conversation.

ACF fields hold editable page information. Taxonomies organize service and market content into a consistent classification. Bricks templates and shared components control how that information is presented. This division gives the client a publishing structure while keeping design decisions consistent across pages.

The same attention to relevance shaped the inquiry form. Earlier choices determine which additional fields appear, allowing different requests to follow different paths within one form.

URL preservation was handled alongside the redesign. Existing addresses were assessed individually, so a change in the new navigation did not automatically mean removing an established page.

Five Layers, Each with a Clear Role

The content model separates what Walker Awning offers, who it serves, the work it has completed, supporting information and the inquiry process.
ServicesMarketsProjectsResourcesInquiry Form

Structured Service Content

Service pages explain individual solutions. ACF fields provide editable information, taxonomies organize the content and Bricks structures provide consistent presentation.

Key Schema / Data Fields:
ACF-managed service content
Service classification through taxonomies
Reusable Bricks page structures
Supporting images and calls to action

A Different View of the Same Business

Market pages explain the offer in the context of a customer group or application. Their own content structure keeps the message focused on the audience.

Key Schema / Data Fields:
Who We Serve content
Market classification through taxonomies
Audience-specific descriptions
Reusable market page structures

Evidence Visitors Can Explore

Projects provide a dedicated place for completed work. A project content type, categories and portfolio filtering help organize and present that evidence.

Key Schema / Data Fields:
Dedicated project content type
Project categories
Filterable portfolio listing
Reusable project presentation

Useful Content Retained Through the Rebuild

Existing articles and resource pages remain part of the visitor journey. Migration checks account for their established URLs and distinct informational purpose.

Key Schema / Data Fields:
Existing article content
Resource listing
Established URL preservation
Relevant internal links

Follow-Up Fields That Match the Selection

A custom form adapts as visitors choose options. Conditional visibility reveals the fields relevant to those choices, supporting different inquiry paths within one interface.

Key Schema / Data Fields:
Selection-dependent field visibility
Different follow-up fields by choice
One form for multiple inquiry paths
Context for the initial conversation

// How the Publishing Layers Work Together

Content Model

Services & Markets

Organization:
Taxonomies classify content
Editorial input:
ACF fields hold page information
Presentation:
Bricks templates render the layout

Design Approach

The redesign gives project photography a prominent role and uses a clearer hierarchy for service information, market content and calls to action. Visitors can explore what Walker Awning builds and see how that work relates to their own needs.

Shared typography, spacing, colors and component styles give the pages a consistent visual language. The CSS variables were reworked to support the new design, and responsive layouts carry the same hierarchy onto smaller screens.

Service and market pages share design patterns while serving different editorial purposes. A service explains a solution; a market page explains its application for a particular audience. Treating them separately makes both the writing and the layout more focused.

Development Approach

FOQIRA rebuilt the Elementor implementation in Bricks and introduced reusable structures for services, markets and project content. The client verified that the rebuilt pages continued to render through Bricks after Elementor frontend assets were removed.

ACF provides the editing fields, while taxonomies provide the classification needed to organize services and markets. Bricks uses that structured content in reusable layouts, keeping content entry separate from presentation. A dedicated project content type and project categories support the portfolio and its filtering interface.

The custom inquiry form uses conditional visibility: a visitor’s selection determines which follow-up fields appear. This supports different inquiry paths without creating a separate public form for every case.

Implementation also covered shared CSS, responsive navigation, link and CTA checks, form testing and post-launch SEO verification. Follow-up production work preserved the content the client had already added after launch.

// interface & system gallery

Platform Interface Gallery

Explore actual high-resolution interface views of the custom WordPress Bricks platform. 

Walker Awning homepage with architectural shade messaging, company photography and quote request buttons.
Walker Awning project cards showing installation photographs, locations, categories and project descriptions.
WordPress project editor showing custom fields for location, short description and award, alongside Project Types categories.
Quote request form with Homeowner selected, showing project type, timeline and project photo upload fields.
Quote request form with Business or Property Manager selected, showing project scope, property type and timeline fields.
Mobile PageSpeed Insights report showing scores of 93 for performance, 95 for accessibility, and 100 for best practices and SEO.

// Key Solutions

The Decisions That Make the Rebuild Work

sol_01

A Redesign Rebuilt in Bricks

FOQIRA implemented the new design in Bricks, with shared components, reworked CSS variables and responsive layouts. This established a common presentation layer for the rebuilt website.

sol_02

ACF and Taxonomies for Services and Markets

Structured fields hold editable information, while taxonomies organize service and market content. Reusable Bricks structures let the team create pages within an established design.

sol_03

A Custom Form with Conditional Fields

The inquiry form responds to the visitor’s choices. Relevant follow-up fields appear according to the selected options, allowing different requests to follow different paths within the same form. This keeps the questions tied to the inquiry and gives Walker Awning more specific context for its response.

sol_04

Content Preservation During Migration

Established pages and legacy routes were reviewed individually. Useful content was restored at its original URLs, and relevant redirects were checked for a direct 301 followed by a working destination.

// What Changed

From the Brief to a Working System

Design and Builder

before

The existing website used Elementor. The brief called for a design change alongside a move to Bricks.

after

A redesigned interface implemented in Bricks, with shared styling, reusable components and responsive layouts.

Business Benefit:

The new design has a consistent technical foundation for future pages and maintenance.

Service and Market Publishing

before

The rebuild needed a defined way to create and organize services and market pages.

after

ACF fields, taxonomies and reusable Bricks structures separate editable information, classification and presentation.

Business Benefit:

The client can populate new content within the established structure instead of starting each layout from scratch.

Inquiry Collection

before

The brief required different follow-up fields for different visitor selections.

after

A custom inquiry form reveals relevant fields according to the chosen options.

Business Benefit:

Visitors can supply details suited to their request, giving the team context for the first conversation.

// Technical Implementation

Content, Presentation and Form Behavior with Defined Responsibilities

WordPress provides the publishing environment. ACF holds editable information, taxonomies classify services and markets, and Bricks controls their presentation. Dedicated project content supports the portfolio. Each part has a defined responsibility, making the implementation easier to understand and extend.

The form adds a behavioral layer. User selections control the visibility of follow-up fields, so the interface adapts to the inquiry. Relevant questions appear as the visitor makes choices, supporting multiple request paths within one interface.

Shared CSS variables and styles support the redesigned interface. Migration checks cover page availability, redirects, indexing directives, canonicals and sitemaps, alongside the visual and functional review.

WordPress

Publishing Platform

The content management foundation for services, markets, resources and projects.

Bricks Builder

Presentation Layer

Reusable page structures, components and responsive implementation of the new design.

Advanced Custom Fields

Content Inputs

Structured editing fields for service and market information.

Custom Taxonomies

Content Classification

Organization of services and markets through defined categories.

Custom Post Types

Project Portfolio

Dedicated project entries for presenting and organizing completed work.

Conditional Inquiry Form

Custom Interaction

Selection-based visibility reveals different follow-up fields within one form.

CSS Variables & Shared Styles

Design Implementation

Reworked variables and reusable styling support consistency across the redesigned site.

Rank Math & Search Console

SEO Migration Review

Metadata, indexing controls, sitemap configuration and URL inspection support verification.

A Publishing Workflow the Client Can Continue Using

The Walker Awning team began adding content after the core site went live. The reusable structures gave that work a defined place: editorial information goes into fields, classification is managed through taxonomies and the templates maintain the presentation. The rebuild supports continued publishing alongside the company’s day-to-day work.

Edit content through structured fields
Organize services and markets through taxonomies
Reuse the design through Bricks templates

// Project Scope

Redesign, Builder Migration & Custom WordPress Development

+ Advanced Custom Fields
+ Bricks Builder
+ CSS
+ JavaScript
+ PHP

// Collaboration

Project Team & Responsibilities

Strategy
FOQIRA Studio
UX/UI Implementation
FOQIRA Studio
WordPress & Bricks Development
FOQIRA Studio
Content
Walker Awning team

[ Planning a Similar Rebuild? ]

Your Next Website Should Be Easier to Use—and Easier to Manage.

If your Elementor website needs a new design, a clearer content structure or a more useful inquiry process, we can help plan the move to Bricks. Tell us what needs to change and what your existing website needs to keep.
close