Best practices and recurring design decisions observed across Elementor website builds. These patterns emerge from client reviews and developer experience.
Avoid using multiple accent colors across page sections ("too Christmassy"). Pick one primary band color from the client's brand guide and apply it consistently to section backgrounds throughout the site. This reduces visual noise and keeps the eye moving smoothly down the page.
Decision point: When a client's existing color feels too gender-specific or exclusionary, revisit the brand guide for a more neutral alternative. In the [1] rebuild, pink was replaced with a muted mustard yellow from the brand guide — neutral enough to feel welcoming across genders while still on-brand.
Prefer muted, toned-down versions of brand colors for section bands. A "mustardy" yellow reads as sophisticated; a bright highlighter yellow does not. Pull the specific hex from the client's brand guide rather than approximating.
When the band color changes (e.g., from pink to yellow), revisit button and rollover colors to ensure sufficient contrast. Gray is often a safe neutral complement. Confirm the change is visually perceptible to users.
Thin, elegant fonts that match a logo may not translate well to body copy or section headers at smaller sizes — especially on mobile. Default to a bolder, more readable weight unless the client explicitly prioritizes the refined aesthetic.
Rationale: Readability serves all users, including those on phones where text renders smaller. A bolder font also tends to perform better for accessibility.
Present font changes to the client early. Frame the tradeoff clearly: thin = elegant/sophisticated, bold = readable/accessible. Most clients will prioritize readability once the tradeoff is explained.
The footer should be built once and applied consistently across all pages. Confirm with the developer that the footer is fully complete before considering any page "done." Common footer elements to verify:
Embedding a Google Map in the footer or on every page is unnecessary and adds page weight. Place the map exclusively on the Contact Us page, where it is contextually relevant.
The Contact Us page is often the highest-converting page on a site. Build it early — even before the rest of the site is complete — so that organic traffic arriving during the build has somewhere to convert. See also: [2].
Elementor is the preferred builder for client sites at Asymmetric. It is easier for developers to work in and easier to hand off to clients for self-service updates. When a project scope evolves from SEO/ads into a full rebuild, Elementor is the default choice.
Be explicit with clients about whether the site being worked on is live or on a staging environment. If the live site is receiving traffic during a rebuild, prioritize completing the Contact Us page and any high-intent pages first. An under-construction placeholder with contact information is a reasonable interim solution.
Establish a shared folder (e.g., Google Drive or media library) for client-provided images early in the project. Provide the client with a list of completed pages so they can match images to layouts. Clients should not be selecting images until page layouts are finalized — the layout determines what image dimensions and compositions will work.
For clients without a retainer, plan to teach basic Elementor editing (e.g., swapping images) so they can make minor updates independently. This reduces ongoing support burden and sets expectations appropriately.