From 9ecbab433f16be7a1516d944fe5c0507255710e3 Mon Sep 17 00:00:00 2001 From: ContentOneBot Date: Thu, 2 Jul 2026 13:00:34 -0400 Subject: [PATCH 1/6] Add /on-demand-developers landing page for kaya MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 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) --- webengine/views/on-demand-developers.html | 236 ++++++++++++++++++++++ 1 file changed, 236 insertions(+) create mode 100644 webengine/views/on-demand-developers.html diff --git a/webengine/views/on-demand-developers.html b/webengine/views/on-demand-developers.html new file mode 100644 index 0000000..812c59e --- /dev/null +++ b/webengine/views/on-demand-developers.html @@ -0,0 +1,236 @@ + + + + + + On-Demand Developers — real engineers for migrations, bugs, and integrations | Content.One + + + + + + + + + + + + + + + + + +
+
+ + Content.One + + +
+
+ + +
+
+
+
+ +
+

On-Demand Developers to Debug and Scale Your Multi-Site Ecosystem

+

+ Something’s broken? Not on our watch. +

+

+ Most CMS platforms just give you documentation and a support inbox. Content.One gives you real engineers who join your team, fix problems, and build what you need, with contracts that adjust to your workload. +

+
+ Talk to an engineer + See Content.One capabilities +
+
+ +
+
+ Content.One engineer pairing with a marketing team inside the CMS dashboard +
+
+ +
+
+
+ + +
+
+

Trusted by enterprise teams shipping on Content.One

+
+ The Salvation Army + Singlife (Rebar Solutions) + Sony + Kin Insurance + Phoenix Suns + Wattpad +
+

Also trusted by Cornershop by Uber and other enterprise CMS teams.

+
+
+ + +
+
+

What on-demand developers actually does

+

+ Development support that doesn’t route through three layers of account management. +

+

+ Most CMS vendors just sell you the software, leaving you to hire a third-party agency to get your project over the line. With Content.One, you get a team that’s always on and ready to help you build. Our On-Demand Developers work directly in your stack, on your schedule, with no extra procurement steps. +

+
+
+ + +
+
+

Capabilities

+

+ What our engineers do the moment they join your team. +

+ +
+ +
+

01 · Bug fixes and patches

+

Fixes ship the moment they’re triaged

+

If something breaks and you’re losing traffic or leads, an engineer will handle it right away instead of putting it in a queue.

+
+ +
+

02 · Migration support

+

Moving off a legacy CMS, handled end-to-end

+

Moving off a legacy CMS is where many projects get stuck. Content.One engineers manage the migration themselves, so you don’t need a separate partner.

+
+ +
+

03 · Custom integrations

+

Real API connections instead of Zapier workarounds

+

CRM, marketing automation, internal tools — if you need an API connection, an engineer will build it for you, so you don’t have to rely on a Zapier workaround.

+
+ +
+

04 · Scaling and performance work

+

Tuning before the traffic spike, not after

+

Whether you face traffic spikes, enter new markets, or deal with seasonal loads, engineers will tune your infrastructure before problems happen.

+
+ +
+

05 · Flexible engagement

+

Six- to twelve-month contracts, part-time or full-time

+

Choose part-time or full-time, with contracts from six to twelve months. You get the support you need without hiring full-time or taking on extra overhead.

+
+ +
+

06 · Direct access, no agency layer

+

Slack or Teams channel to the engineer on your account

+

Get a Slack or Teams channel directly to the engineer working on your account. You won’t have to go through an account manager to get updates or share feedback.

+
+ +
+
+
+ + +
+
+

Ready when you are

+

+ Put a real engineer on your team — without the overheads. +

+

+ Tell us what you’re working on. We’ll match you with an engineer who already knows the platform, your stack, and how to ship. +

+
+ Talk to an engineer + See Content.One capabilities +
+
+
+ + + + + + From 8b15130c32f265ceea2d6b386a6fa9f258c3900c Mon Sep 17 00:00:00 2001 From: ContentOneBot Date: Thu, 2 Jul 2026 14:03:39 -0400 Subject: [PATCH 2/6] on-demand-developers: update hero copy per kaya MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - 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) --- webengine/views/on-demand-developers.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/webengine/views/on-demand-developers.html b/webengine/views/on-demand-developers.html index 812c59e..5926a0d 100644 --- a/webengine/views/on-demand-developers.html +++ b/webengine/views/on-demand-developers.html @@ -95,12 +95,12 @@
-

On-Demand Developers to Debug and Scale Your Multi-Site Ecosystem

+

Migrate, build, and scale with on-demand developers

- Something’s broken? Not on our watch. + On-Demand Developers to Debug and Scale Your Digital Operations

- Most CMS platforms just give you documentation and a support inbox. Content.One gives you real engineers who join your team, fix problems, and build what you need, with contracts that adjust to your workload. + Most CMS platforms just give you documentation and a support inbox. Content.One gives you real engineers who join your team, fix problems, and build what you need to grow.

Talk to an engineer From 9cf067aeb4b7147b1752d5b6a9c3e7cb080565cd Mon Sep 17 00:00:00 2001 From: ContentOneBot Date: Thu, 2 Jul 2026 14:09:12 -0400 Subject: [PATCH 3/6] on-demand-developers: shorten H1 per kaya MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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) --- webengine/views/on-demand-developers.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/webengine/views/on-demand-developers.html b/webengine/views/on-demand-developers.html index 5926a0d..6afcfbc 100644 --- a/webengine/views/on-demand-developers.html +++ b/webengine/views/on-demand-developers.html @@ -97,7 +97,7 @@

Migrate, build, and scale with on-demand developers

- On-Demand Developers to Debug and Scale Your Digital Operations + On-Demand Developers to Help you Debug and Scale

Most CMS platforms just give you documentation and a support inbox. Content.One gives you real engineers who join your team, fix problems, and build what you need to grow. From dc495398b93a4bb55c519f40e2c616966138fb1b Mon Sep 17 00:00:00 2001 From: ContentOneBot Date: Thu, 2 Jul 2026 14:23:20 -0400 Subject: [PATCH 4/6] on-demand-developers: closing CTA copy per kaya MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit "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) --- webengine/views/on-demand-developers.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/webengine/views/on-demand-developers.html b/webengine/views/on-demand-developers.html index 6afcfbc..115e74f 100644 --- a/webengine/views/on-demand-developers.html +++ b/webengine/views/on-demand-developers.html @@ -204,7 +204,7 @@

Slack or Teams channel to th

Ready when you are

- Put a real engineer on your team — without the overheads. + Put a real engineer in your team, today.

Tell us what you’re working on. We’ll match you with an engineer who already knows the platform, your stack, and how to ship. From 6d1aecc0daa7f182b351c4b527890a33441ac905 Mon Sep 17 00:00:00 2001 From: ContentOneBot Date: Mon, 10 Aug 2026 12:08:40 -0400 Subject: [PATCH 5/6] footer: add 'Company' sub-stack below Resources with Brand + About Us 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). --- webengine/views/components/footer.html | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/webengine/views/components/footer.html b/webengine/views/components/footer.html index 25d9710..42d3d6e 100644 --- a/webengine/views/components/footer.html +++ b/webengine/views/components/footer.html @@ -104,7 +104,13 @@

  • Blog
  • Documentation
  • Github & Commit Log
    • + +
    +
    +

    Company

    +

    From 4d1b1330c8115d079d43dc2d8cfd4d71557e7381 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Fri, 14 Aug 2026 01:40:23 +0000 Subject: [PATCH 6/6] chore: map new Zesty resource ZUIDs [skip ci] --- zesty.config.json | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/zesty.config.json b/zesty.config.json index 26567ce..75040c2 100644 --- a/zesty.config.json +++ b/zesty.config.json @@ -1045,6 +1045,12 @@ "type": "ajax-json", "updatedAt": "2026-08-10T15:46:28Z", "createdAt": "2026-08-10T15:46:28Z" + }, + "/on-demand-developers.html": { + "zuid": "11-f6bfccaff5-slftqj", + "type": "ajax-json", + "updatedAt": "2026-08-14T01:40:22Z", + "createdAt": "2026-08-14T01:40:22Z" } }, "styles": {