Property & Industrial Parks firm notes on CMS publishing workflow

Context: This write-up is for colleagues progressing website and CMS work. The client is in textile & apparel, roughly two hundred+ staff, based around new urban centers. Editors know the CMS well enough, but search indexing diagnostics still needs a one-page rule sheet to cut verbal rework. Next, we recommend to document the reproduction path in a shared sheet. If more features are added, scope the blast radius before scheduling.

Testing & Acceptance

Last week we reviewed product-site information architecture with the client's IT lead. They care more about stability than buzzwords. Editors know the CMS well enough, but product-site information architecture still needs a one-page rule sheet to cut verbal rework. Prefer a go-live window outside peak traffic, and prepare the rollback package early. Last week we reviewed inquiry form conversion path with the client's IT lead. They care more about stability than buzzwords. We hit a case of mini program review rejected. Troubleshooting started with logs on Redis, then followed our reproduction steps. Archive screenshots and config change IDs for this inquiry form conversion path round so next month's retrospective stays concrete.

Delivery Approach

This write-up is for colleagues progressing website and CMS work. The client is in agritech, roughly a hundred-person team, based around free-trade zones. Editors know the CMS well enough, but inquiry form conversion path 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. The same requirement can sound different across departments; writing it down helps align decisions on product-site information architecture. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to product-site information architecture 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 static asset caching. We hit a case of CMS image uploads over-compressed. Troubleshooting started with logs on approval workflows, then followed our reproduction steps. Add a field dictionary to the docs so new joiners ask fewer repeat questions.

Operations & Collaboration

This write-up is for colleagues progressing website and CMS work. The client is in finance & tax consulting, roughly a multi-division group, based around coastal tech hubs. QA walked the main path three times on real devices and flagged edge cases around channel & URL planning. Archive screenshots and config change IDs for this channel & URL planning round so next month's retrospective stays concrete. Last week we reviewed site performance optimization 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 site performance optimization first. Archive screenshots and config change IDs for this site performance optimization round so next month's retrospective stays concrete.

Takeaways: 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.