Automotive Services firm notes on multilingual website build

Context: This write-up is for colleagues progressing website and CMS work. The client is in property & industrial parks, roughly a hundred-person team, based around county-level cities. Editors know the CMS well enough, but search indexing diagnostics still needs a one-page rule sheet to cut verbal rework. Add a field dictionary to the docs so new joiners ask fewer repeat questions.

Delivery Approach

This write-up is for colleagues progressing website and CMS work. The client is in beauty & wellness, roughly around fifty employees, based around the Middle East. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to company website development first. Prefer a go-live window outside peak traffic, and prepare the rollback package early. The same requirement can sound different across departments; writing it down helps align decisions on image weight control. Editors know the CMS well enough, but image weight control still needs a one-page rule sheet to cut verbal rework. Archive screenshots and config change IDs for this image weight control round so next month's retrospective stays concrete.

Testing & Acceptance

Last week we reviewed channel & URL planning with the client's IT lead. They care more about stability than buzzwords. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to channel & URL planning first. Archive screenshots and config change IDs for this channel & URL planning round so next month's retrospective stays concrete. The same requirement can sound different across departments; writing it down helps align decisions on search indexing diagnostics. QA walked the main path three times on real devices and flagged edge cases around search indexing diagnostics. Prefer a go-live window outside peak traffic, and prepare the rollback package early.

Operations & Collaboration

Last week we reviewed landing page SEO basics with the client's IT lead. They care more about stability than buzzwords. Editors know the CMS well enough, but landing page SEO basics still needs a one-page rule sheet to cut verbal rework. Archive screenshots and config change IDs for this landing page SEO basics round so next month's retrospective stays concrete. Last week we reviewed channel & URL planning with the client's IT lead. They care more about stability than buzzwords. We hit a case of legacy outbound links broken. Troubleshooting started with logs on a hosting panel, then followed our reproduction steps. Next, we recommend to temporarily disable noncritical plugins and retest. If more features are added, scope the blast radius before scheduling.

Takeaways: The same requirement can sound different across departments; writing it down helps align decisions on CMS publishing workflow. QA walked the main path three times on real devices and flagged edge cases around CMS publishing workflow. Next, we recommend to have business users record a screen walkthrough. If more features are added, scope the blast radius before scheduling.