stage → production: on-demand developers + bobby footer + sync-to-zesty re-run for sitemap - #91
Merged
Merged
Conversation
Standalone HTML endpoint (bypasses loader — ships own DOCTYPE, head,
Tailwind CDN, nav, footer). Copy is kaya's brief verbatim (attached to
her Discord request) with two light adjustments:
- Capability 03 heading typo fixed: "C03. Custom integrations" →
"03. Custom integrations".
- Section 1 body: "Content.one" → "Content.One" (brand casing).
Page structure:
Hero (dark, royal-gradient) — overline + H1 + subhead + dual CTAs
(Talk to an engineer → /contact-us/, See Content.One capabilities
→ /product/), dashboard preview on the right at lg+.
Logo strip — 6 real customer logos (Salvation Army, Singlife/Rebar,
Sony, Kin, Phoenix Suns, Wattpad); Cornershop by Uber called out
in the strip caption since we don't have a shipped logo asset yet.
Section 1 (light) — "Development support that doesn't route through
three layers of account management."
Section 2 (light, white bg) — 6 capability cards (01–06) with the
kicker-num pattern from other standalones.
Closing CTA (dark) — repeat Talk to an engineer + capabilities row.
Footer (dark) — minimal, four link row.
Serves at /on-demand-developers.html (top-level HTML views take the
.html extension by design — see BridgeTECH landing).
## Manual follow-ups (not in this PR)
- Add /on-demand-developers.html to the Solutions dropdown nav. The
nav pulls Solutions items from the `product_solutions` CMS pageset,
so kaya (or admin) needs to create a matching content item in the
Zesty admin. Once added, it'll appear in the dropdown automatically
on every page.
- Sitemap coverage: PR #46 (kaya-sitemap-coverage) adds a custom
sitemap; on merge, add a <url> row for this page. Not in this PR
because stage doesn't have sitemap.xml yet.
- Hero image: currently reuses the Content.One Dashboard shot. If
there's a preferred "engineer + marketing team pairing" photo,
drop the URL and I'll swap.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- Eyebrow → "Migrate, build, and scale with on-demand developers"
- H1 → "On-Demand Developers to Debug and Scale Your Digital Operations"
("Your Digital Operations" gets the royalLite accent)
- Subhead → trimmed the "with contracts that adjust to your workload"
clause; ends on "build what you need to grow."
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
H1 → "On-Demand Developers to Help you Debug and Scale". Kept the royalLite accent — moved it to "Debug and Scale" since that's the value-verb pair. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
"Put a real engineer on your team — without the overheads." → "Put a real engineer in your team, today." Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Bobby (2026-08-10): add a new Company subheading in the footer, below Resources. Under Company: - Brand (moved from Resources sub-stack) - About Us -> /about/ Structure now inside the Platform/Governance/Resources column: Platform -> Governance -> Resources -> Company (4 sub-stacks).
footer: add Company sub-stack (Brand + About Us) — bobby
Add /on-demand-developers landing page
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Promoting stage → production per ardeay's urgent SEO/GEO Discord message (2026-08-13).
Scope — what actually needs promoting
Also re-runs sync-to-zesty for the sitemap fix
Ardeay noted he "fixed a sitemap issue" on the Zesty side. This deploy will trigger a fresh sync-to-zesty pass against the (presumably now-correct)
/sitemap.xmlview record, which should finally make our custom sitemap.xml the live version — the ZUID wiring landed in production via PR #89 on 2026-08-10 but the live/sitemap.xmlis still empty of standalone HTML entries as of this check.Already in production (from earlier ardeay-authorized push — noting for the record so no double-work)
Ardeay's original list included these three but they're already live. Confirmed via
gh pr view.After this deploy
/on-demand-developers/becomes live/sitemap.xmlshould populate with all standalone HTML pages (assuming ardeay's Zesty-side fix reconciled the ZUID/view type)Sanity checks after CI
https://www.content.one/on-demand-developers/loadshttps://www.content.one/sitemap.xmllists our 15+ standalone HTML pages (pricing, free-tools, all 8 Vs pages, MCP press releases, RFP template, bridgetech, why-building-websites, dei-community). If it's still empty of standalones, the ZUID/view-type mismatch persists — flag to ardeay.