• Ops
  • 2026-09-28
  • 1724 views

Company website guide: product-site information architecture for property & industrial parks

Context: The same requirement can sound different across departments; writing it down helps align decisions on image weight control. We hit a case of holiday tr

Context: The same requirement can sound different across departments; writing it down helps align decisions on image weight control. We hit a case of holiday traffic spikes slowing the site. Troubleshooting started with logs on Git, then followed our reproduction steps. Add a field dictionary to the docs so new joiners ask fewer repeat questions.

Testing & Acceptance

Last week we reviewed static asset caching 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 static asset caching first. Next, we recommend to compare staging vs production configuration diffs. If more features are added, scope the blast radius before scheduling. Last week we reviewed inquiry form conversion path with the client's IT lead. They care more about stability than buzzwords. QA walked the main path three times on real devices and flagged edge cases around inquiry form conversion path. Archive screenshots and config change IDs for this inquiry form conversion path round so next month's retrospective stays concrete. The same requirement can sound different across departments; writing it down helps align decisions on company website development. Editors know the CMS well enough, but company website development still needs a one-page rule sheet to cut verbal rework. Archive screenshots and config change IDs for this company website development round so next month's retrospective stays concrete.

Background & Goals

This write-up is for colleagues progressing website and CMS work. The client is in finance & tax consulting, roughly two hundred+ staff, based around East Asia. QA walked the main path three times on real devices and flagged edge cases around basic accessibility. Add a field dictionary to the docs so new joiners ask fewer repeat questions. Last week we reviewed product-site information architecture with the client's IT lead. They care more about stability than buzzwords. We hit a case of metrics not matching finance numbers. Troubleshooting started with logs on Flutter, then followed our reproduction steps. Prefer a go-live window outside peak traffic, and prepare the rollback package early. Last week we reviewed multilingual website build with the client's IT lead. They care more about stability than buzzwords. Editors know the CMS well enough, but multilingual website build still needs a one-page rule sheet to cut verbal rework. Next, we recommend to require a change request for any scope change. If more features are added, scope the blast radius before scheduling.

Operations & Collaboration

Last week we reviewed CMS publishing workflow with the client's IT lead. They care more about stability than buzzwords. Editors know the CMS well enough, but CMS publishing workflow 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. Last week we reviewed static asset caching with the client's IT lead. They care more about stability than buzzwords. We hit a case of captchas frequently failing to load. Troubleshooting started with logs on SSL certificates, 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. Last week we reviewed landing page SEO basics with the client's IT lead. They care more about stability than buzzwords. QA walked the main path three times on real devices and flagged edge cases around landing page SEO basics. Add a field dictionary to the docs so new joiners ask fewer repeat questions.

Takeaways: This write-up is for colleagues progressing website and CMS work. The client is in manufacturing, roughly about thirty people, based around high-tech zones. QA walked the main path three times on real devices and flagged edge cases around basic accessibility. Prefer a go-live window outside peak traffic, and prepare the rollback package early.


Tags:
  • website