feat: Umami/ntfy 可观测性栈与 WordPress AdSense 部署

deploy/wordpress/content/posts/batch2/27-client-communication.html

@@ -0,0 +1,18 @@
+<p>Clear client communication is a competitive advantage when your timezone and workspace change weekly. Templates reduce emotional labor and missed expectations.</p>
+
+<h2>Core templates to keep</h2>
+<ul>
+  <li>Kickoff: working hours, response SLAs, tools, and escalation path</li>
+  <li>Weekly update: progress, blockers, next decisions needed</li>
+  <li>Travel transition: dates, overlap hours, backup connectivity</li>
+  <li>Incident note: outage or delay with ETA for the next update</li>
+</ul>
+
+<h2>Write for async first</h2>
+<p>Assume recipients will read without a meeting. Put decisions and deadlines at the top. Attach links, not mysteries. Ambiguity creates meetings; clarity removes them.</p>
+
+<h2>Timezone etiquette</h2>
+<p>State your overlap window in the client’s timezone. Avoid “ASAP.” Replace it with a timestamp. Professional boundaries are easier to respect when they are specific.</p>
+
+<h2>Keep a living doc</h2>
+<p>Store templates in one note and improve them after each awkward thread. Your future self in another airport will thank you.</p>