feat(site): comparison pages, partners program, remote-mode diagram, intake polish (Sections 18+21)#304
Merged
Conversation
…intake polish (Sections 18+21) - /compare/<slug> pages for UiPath, Power Automate, computer-use agents, record-and-replay tools, browser-agent platforms, and hand-rolled scripts, driven by data/comparisons.js under enforced honesty rules: credit real competitor strengths, differentiate only on independent effect verification, explicit outcomes, the external zero-install remote lane, customer-controlled data, deterministic model-free healthy runs, the MIT runtime, and qualification evidence; never on commoditized recording/visual-targeting/Citrix/self-healing. - /partners page with four tracks (vertical software/OEM, RCM+BPO, integration/services, MSP/deployment), each stating model and qualification/support/packs boundaries, plus a dedicated Netlify partner-inquiry intake with a track selector registered in public/form.html. Status-honest: application-based, no self-serve portal. - Remote execution modes figure on /how-it-works: in-session vs external black-box, labeled per current qualification status (deterministic stand-in qualified; real ICA/HDX per customer). - Nav/footer: Partners & OEM in Solutions dropdown and footer Company column; Contribute workflows in footer Connect column. - Qualification intake: required privacy-consent checkbox linking the Privacy Notice, captured leadSegment field, method=POST fallback, and node + Cypress tests asserting no lead field ever appears in a URL. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NyCHrzA1psrKMFfroYbzaM
✅ Deploy Preview for cosmic-klepon-3c693c ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
What
Targeted public-site work from roadmap Sections 21 and 18 plus small intake enhancements. Builds on the recently merged contribute set (#262), case study (#301), and hero reconciliation (#302). Does not touch the homepage hero/narrative, the case-study page, or /contribute content.
1. Comparison pages (Section 21)
Six pages under
/compare/<slug>, driven bydata/comparisons.jsand rendered bypages/compare/[slug].js; the existing/compareoverview gains a linking section (its existing copy/tests unchanged):/compare/uipath/compare/power-automate/compare/computer-use-agents/compare/record-and-replay/compare/browser-agents/compare/hand-rolled-scriptsHonesty rules are enforced by
tests/comparisonPages.test.js: each page credits at least four real competitor strengths; OpenAdapt differentiates only on independent out-of-band effect verification, explicit verified-or-halted outcomes, deterministic zero-model-call healthy runs, the external zero-install remote lane (status-hedged), customer-controlled data, the MIT runtime, and published qualification evidence. Recording, visual targeting, Citrix awareness, and self-healing are explicitly disclaimed as commodities. The only competitor dollar figures allowed anywhere are Power Automate's published ~$15/user/mo and ~$215/bot/mo hosted-RPA class, both hedged ("published pricing starts around ...").2. Partners page (Section 18 v1)
/partnerswith four tracks (vertical software/OEM, RCM+BPO operators, integration/services, MSP/deployment). Each track states its model (embed/white-label, managed operations, services delivery, managed deployment) and responsibility boundaries for qualification, support, and packs. Status-honest: application-based program, explicitly "not a self-serve portal". Dedicated Netlify formpartner-inquiry(track selector, durable POST to/form.html, registered inpublic/form.html), same pattern ascontributor-program. Guarded bytests/partnersProgram.test.js(form-name sync, track parity, boundary completeness, status honesty).3. Nav / footer IA
/partners/partners/contribute(community path)Enterprise (
/qualify, solutions, security) and developers (Developers menu) paths already existed and are unchanged.4. External-vs-in-session diagram (Section 21)
components/RemoteModesFigure.json/how-it-works: styled HTML/CSS figure showing in-session (runner inside the managed session, when policy permits) vs external black-box (runner drives the local Citrix/RDP client window; zero install in the remote session). Status caption mirrorspublic/status.json: external lane qualified against a deterministic no-DOM stand-in plus a real FreeRDP round trip; real ICA/HDX qualified per customer before consequential use. Honesty wording is test-enforced.5. Intake polish
On the workflow-qualification form (structure otherwise unchanged):
/privacy-policy, serialized asprivacyConsent=yesleadSegmentselect (enterprise_operator / oem_vertical / bpo_services / developer / community)public/form.htmldefinitionmethod="POST"on the form element so even a JS-less native submit cannot GET lead fields into a URLtests/leadPrivacy.test.js(node) +cypress/e2e/lead-privacy.cy.js(browser): lead fields travel only in the POST body; the page URL never contains a lead valueAlso: sitemap.xml and llms.txt updated with the seven new routes.
Competitor facts asserted (for founder double-check)
Tests
npm test: 153/153 pass (includes 3 new test files)npm run build(prebuild tests + verify + next build): green; all 7 new routes prerender🤖 Generated with Claude Code
https://claude.ai/code/session_01NyCHrzA1psrKMFfroYbzaM