Hospitality & Travel firm notes on company website development
{pboot:if('Context: Last week we reviewed site performance optimization with the client's IT lead. They care more about stability than buzzwords. We hit a case of payment '!='')}Context: Last week we reviewed site performance optimization with the client's IT lead. They care more about stability than buzzwords. We hit a case of payment
{/pboot:if}Context: Last week we reviewed site performance optimization with the client's IT lead. They care more about stability than buzzwords. We hit a case of payment succeeded but orders still pending. Troubleshooting started with logs on WeChat DevTools, 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 brand site launch with the client's IT lead. They care more about stability than buzzwords. Editors know the CMS well enough, but brand site launch still needs a one-page rule sheet to cut verbal rework. 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 brand site launch 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 brand site launch first. Add a field dictionary to the docs so new joiners ask fewer repeat questions. This write-up is for colleagues progressing website and CMS work. The client is in construction, roughly two hundred+ staff, based around high-tech zones. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to basic accessibility first. Prefer a go-live window outside peak traffic, and prepare the rollback package early.
Background & Goals
Last week we reviewed basic accessibility with the client's IT lead. They care more about stability than buzzwords. Editors know the CMS well enough, but basic accessibility 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 CMS publishing workflow with the client's IT lead. They care more about stability than buzzwords. We hit a case of holiday traffic spikes slowing the site. Troubleshooting started with logs on a hosting panel, then followed our reproduction steps. Next, we recommend to store backups in a separate folder with dated labels. If more features are added, scope the blast radius before scheduling.
Operations & Collaboration
The same requirement can sound different across departments; writing it down helps align decisions on multilingual website build. 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 run a real-device smoke check before go-live. If more features are added, scope the blast radius before scheduling. The same requirement can sound different across departments; writing it down helps align decisions on company website development. 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. This write-up is for colleagues progressing website and CMS work. The client is in healthcare, roughly a multi-division group, based around historic downtown districts. Editors know the CMS well enough, but search indexing diagnostics 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.
Takeaways: The same requirement can sound different across departments; writing it down helps align decisions on basic accessibility. We hit a case of mini program review rejected. Troubleshooting started with logs on Git, then followed our reproduction steps. Archive screenshots and config change IDs for this basic accessibility round so next month's retrospective stays concrete.