feat(platform): update Build and Compute page copy

[felixwidjaja]

Summary

• Build hub (/platform/build): new hero title and subtitle; Compute card drops the "Coming Q3 2026" badge, gets the new description and a "View documentation" button; Object Storage says "Global, low latency access" instead of "10+ global regions".
• Compute page (/platform/compute): new "Isolated. Fast. Private." headline, subtitle and six-item checklist; sandbox use case swaps the checkpoint and 100K items for "Private by default networking with Galactic VPC"; AI agents use case drops all GPU references (description, bullet, terminal sample).
• Features tabs hidden: the "Virtual machines that are tiny and mighty" section is removed from the page and its markdown export, since only one tab has real content. The component and data are kept for later.
• Meta copy: search and social titles/descriptions for both pages updated to match; "network edge" changed to "edge" in the homepage blurb, its markdown export, and llms-full.txt.

Notes

• The rendered Compute hero (rotating "Build ephemeral databases…" headline and description in data/compute.ts) is unchanged.
• llms.txt still says Datum Compute is "coming but not yet available"; needs a decision on whether Compute is live.
• Object Storage keeps its "Coming soon" badge and "View enhancement" button.

Test plan

• astro check, ESLint, Prettier pass
• /platform/build and /platform/compute reviewed locally
• "View documentation" link (/docs/compute) resolves
• Preview shows no features tabs section on /platform/compute

[github-actions]

🔎 SEO & Meta Review

Analyzed 1 of 97 built HTML pages (mode: changed-only).

📊 Score summary

Metric	Value
Overall score	🟢 100 / 100
Pages analyzed	1
Title issues (missing or >70 chars)	✅ 0
Description issues (length out of 70–160)	✅ 0
Canonical missing	✅ 0
H1 issues (0 or >1)	✅ 0
Noindex on built pages	✅ 0
og:image missing	✅ 0
JSON-LD invalid	✅ 0
Pages with missing alt text	✅ 0
Broken internal links	✅ 0
Redirect chains	✅ 0

No previous audit found — trend will appear next run.

---

SEO Review — datum.net (1 page analysed)

1. Summary

The single page analysed is broadly well-structured with no critical blockers. Two moderate issues need attention: the meta description is slightly short of the recommended floor, and the JSON-LD schema types do not match the page's content type.

---

2. Critical Issues

Issue	Count	Detail
Short meta description (<70 chars)	0	—
Description below recommended 130-char target	1	120 chars — just under the 130-char soft floor
Missing/wrong canonical	0	—
Duplicate or missing title	0	—
noindex on production page	0	—

No hard critical issues found. The description length is the closest concern (120 chars vs. recommended 130–160).

---

3. Improvements

JSON-LD schema coverage

• 1 page uses only Organization + WebSite types. A product/feature landing page like /platform/build should also include a WebPage (or SoftwareApplication) type to give crawlers richer structured context. Add a WebPage block to the shared page schema emitted in the relevant layout (likely src/layouts/PlatformLayout.astro or equivalent).

og:description vs. meta description inconsistency

• 1 page: the og:description ("Deploy and scale apps & agents instantly on fully isolated virtual machines." — ~76 chars) is significantly shorter and less informative than the meta description (120 chars). Align them or use the full meta description as the og:description for consistent social previews. Update the Open Graph tag in the page's front-matter or layout head component.

---

4. Per-page notes

• /platform/build — Meta description is 120 chars, just below the 130-char recommended floor, reducing snippet real-estate in SERPs. og:description is also much shorter (≈76 chars) and omits key differentiators ("cold starts under 10ms", "microVMs").

  • 💡 Fix: Expand the meta description to 135–155 chars, e.g.: "Securely deploy and scale apps and agents instantly on fully isolated microVMs at the edge. Cold starts under 10 ms — built for AI workloads." (141 chars). Reuse this string (or a close variant) as og:description in the page's <head> block.

• /platform/build — JSON-LD only declares Organization and WebSite types; no WebPage or SoftwareApplication entity describes the page itself, limiting rich-result eligibility.

  • 💡 Fix: Add a WebPage JSON-LD block (with name, description, url, and isPartOf pointing to the WebSite entity) in the layout responsible for platform pages (e.g. src/layouts/PlatformLayout.astro). If this page describes purchasable compute, consider SoftwareApplication with applicationCategory: "BusinessApplication".