Unified Communications page: publish the approved long-form copy #220

New Issue

Closed

opened 2026-09-10 04:13:33 -05:00 by null · 1 comment

null commented

2026-09-10 04:13:33 -05:00

Owner

Levi Halford approved a change sheet for /services/unified-communications on 2026-08-28: Unified SEO + Search Sheet APPROVED 2026-08-28.md, kept in .drop/2026-08-28-levi-uc-cc-sheets/ (gitignored client material). The sheet is the spec.

What is true now. The page renders from src/data/services.js through src/pages/ServiceDetail.jsx: title "Unified Communications | Queue North", 144 words, three generic H2s ("What This Solves", "Key Benefits", "Ideal For"), and a description that runs two sentences together.

What to do.

Content in src/data/serviceContent/unified-communications.js, a leaf module under page: { seo, hero, sections, related }, rendered by the long-form branch of ServiceDetail.jsx through the shared ContentBlocks renderer.
Title Business Phone & UCaaS Solutions | Queue North, H1 Business Phone & Unified Communications Solutions, the subheading, and the 164-character description, all verbatim (not clamped).
Hero copy under the hero; both CTAs ("Request a Communications Review", "Talk With an Engineer") to /contact#contact-form.
Sections 4 to 13 as H2s, each opening with its direct answer; the 10-step migration sequence as an ol; section 13 is a list section.
FAQ (section 14) as visible h3 plus p, 7 questions. Related links with section 15's exact anchors (7 targets), plus the inline links section 10 asks for ("LAN design", "Wi-Fi").
The Quick Info card and the footer stay exactly as they are.

Traps.

Directions to the website manager are mixed into the copy: "This section is important for...", "Do not promise that every number is always portable.", "Keep this factual:", "Link naturally to:", "Avoid unsupported superlatives...". None are published; the content validator rejects them.
No FAQPage schema and no llms.txt, as the sheet says. Section ids must not start with a digit, so the 8x8 section needs an id like ucaas-8x8-implementation.
The approved subheading keeps "actually works"; owner wording wins over older review notes.
Read the sheet as raw UTF-8. The 8x8 Work and Webex screenshots are a separate issue.

Verify: the built dist/services/unified-communications/index.html has the sheet's title, description and H1 exactly (entities decoded), one h1, every H2 and all 7 FAQ questions, no sheet direction, and npm run verify passes.

Levi Halford approved a change sheet for `/services/unified-communications` on 2026-08-28: `Unified SEO + Search Sheet APPROVED 2026-08-28.md`, kept in `.drop/2026-08-28-levi-uc-cc-sheets/` (gitignored client material). The sheet is the spec. **What is true now.** The page renders from `src/data/services.js` through `src/pages/ServiceDetail.jsx`: title "Unified Communications | Queue North", 144 words, three generic H2s ("What This Solves", "Key Benefits", "Ideal For"), and a description that runs two sentences together. **What to do.** - Content in `src/data/serviceContent/unified-communications.js`, a leaf module under `page: { seo, hero, sections, related }`, rendered by the long-form branch of `ServiceDetail.jsx` through the shared `ContentBlocks` renderer. - Title `Business Phone & UCaaS Solutions | Queue North`, H1 `Business Phone & Unified Communications Solutions`, the subheading, and the 164-character description, all verbatim (not clamped). - Hero copy under the hero; both CTAs ("Request a Communications Review", "Talk With an Engineer") to `/contact#contact-form`. - Sections 4 to 13 as H2s, each opening with its direct answer; the 10-step migration sequence as an `ol`; section 13 is a list section. - FAQ (section 14) as visible h3 plus p, 7 questions. Related links with section 15's exact anchors (7 targets), plus the inline links section 10 asks for ("LAN design", "Wi-Fi"). - The Quick Info card and the footer stay exactly as they are. **Traps.** - Directions to the website manager are mixed into the copy: "This section is important for...", "Do not promise that every number is always portable.", "Keep this factual:", "Link naturally to:", "Avoid unsupported superlatives...". None are published; the content validator rejects them. - No FAQPage schema and no `llms.txt`, as the sheet says. Section ids must not start with a digit, so the 8x8 section needs an id like `ucaas-8x8-implementation`. - The approved subheading keeps "actually works"; owner wording wins over older review notes. - Read the sheet as raw UTF-8. The 8x8 Work and Webex screenshots are a separate issue. Verify: the built `dist/services/unified-communications/index.html` has the sheet's title, description and H1 exactly (entities decoded), one h1, every H2 and all 7 FAQ questions, no sheet direction, and `npm run verify` passes.

null added this to the Batch 17: Long-form Unified Communications and Contact Center pages milestone 2026-09-10 04:13:33 -05:00

null added the

labels 2026-09-10 04:13:33 -05:00

null referenced this issue from a commit

2026-09-10 05:05:25 -05:00

feat(content): publish Levi's approved UC and Contact Center pages

null closed this issue

2026-09-10 05:05:25 -05:00

null commented

2026-09-10 05:05:49 -05:00

Author

Owner

Shipped in aff8033. /services/unified-communications now serves the approved sheet's copy: 1,125 words, 10 sections and 7 FAQs, from src/data/serviceContent/unified-communications.js. Verified against the built HTML: title 'Business Phone & UCaaS Solutions | Queue North', H1 'Business Phone & Unified Communications Solutions' and the 164-character description are byte-exact from the sheet (emitted whole, not clamped); all 10 approved H2s and all 7 FAQ questions are present; no website-manager direction survived, checked against 20 phrases; no em dash, no markdown, no U+FFFD. The Quick Info box is unchanged and the footer is byte-identical to the pre-batch build. In Chromium at 320, 390, 768 and 1024: no horizontal scroll, no broken image, no console error, and all 11 section anchors deep-link correctly.

Shipped in aff8033. /services/unified-communications now serves the approved sheet's copy: 1,125 words, 10 sections and 7 FAQs, from src/data/serviceContent/unified-communications.js. Verified against the built HTML: title 'Business Phone & UCaaS Solutions | Queue North', H1 'Business Phone & Unified Communications Solutions' and the 164-character description are byte-exact from the sheet (emitted whole, not clamped); all 10 approved H2s and all 7 FAQ questions are present; no website-manager direction survived, checked against 20 phrases; no em dash, no markdown, no U+FFFD. The Quick Info box is unchanged and the footer is byte-identical to the pre-batch build. In Chromium at 320, 390, 768 and 1024: no horizontal scroll, no broken image, no console error, and all 11 section anchors deep-link correctly.