SEO: 50 new pages on cross-OS business-logic portability - #80
Merged
Conversation
Targets "what framework lets me write business logic once and run it on any OS" and close permutations. Answers honestly against the current platform matrix (native Linux/macOS/Windows + browser shipped; Android/.NET in progress; iOS blocked) rather than overselling "any OS" the way most cross-platform marketing does. - New question page with FAQPage schema covering the query cluster - New compare/vs-cross-platform-frameworks.astro distinguishing Traverse (business-logic layer) from Flutter/Electron/Tauri/MAUI (UI layer), including a Tauri + traverse-embedder code example - Wired into questions/ and compare/ hub indexes - package-lock.json: npm install resolved a lockfile/package.json version mismatch that had left traverse-embedder-web uninstalled, breaking `npm run build` on a clean checkout Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Extends the "any OS, one binary" question cluster: honest per-OS status pages (does-traverse-support-windows-macos-and-linux, what-operating-systems-does-traverse-support, can-traverse-build-mobile-apps), the device-independent execution model, avoiding logic duplication across platforms, and how Traverse differs from Flutter/Electron/Tauri specifically. All cross-link to platforms.html and the new comparison page rather than restating the platform matrix inconsistently. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
First-person posts in the established blog voice, all answering variants of "does this work on any OS" and building topical authority around the honest platform matrix instead of an oversold one: - "Does this work on any OS?" — the direct, narrative answer - Same binary, three operating systems — the native execution mechanics - Why "cross-platform" rarely means what it sounds like — industry framing for Flutter/Electron/Tauri/React Native/PWA vs the logic layer Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
… honest platform comparisons Rounds out the "any OS / one binary" cluster with generic WASM education (sandbox, is-webassembly-cross-platform), honest comparisons against adjacent approaches (shared Rust library, Docker, .NET MAUI, Electron), migration and packaging mechanics, and direct answers to "what happens if my platform isn't supported yet." Includes one page that names an explicit unmet v1.0 gate (five-platform CI stress matrix) rather than implying cross-OS parity is already fully proven. All wired into questions/index.astro; 125 pages build cleanly. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Covers non-Rust team consumption, performance overhead honesty, explicit anti-persona guidance (when NOT to use Traverse), a buyer's-guide page for evaluating cross-platform approaches generally, cross-OS behavioral consistency, versioning across platforms, and monorepo usage. 132 pages build cleanly. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
compare/vs-wasm-runtimes.astro positions Traverse correctly relative to Wasmtime/WasmEdge/Wasmer: built on top of Wasmtime as a governance layer, not a competing execution engine. The two new posts extend the honesty narrative to versioning claims generally (the v1.0 gates) and to the shared-library alternative specifically. 135 pages build cleanly. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
docs/guides/cross-os-capability.astro walks through building the shipped expedition bundle, inspecting it, running it through the native executor, loading the identical binary in a browser, and confirming the match from the trace artifact rather than by eye. Wired into the guides index and DocsSidebar. 136 pages build cleanly. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Registry bundle portability, PWA vs Traverse positioning, AI-agent consistency across OS, pre-ship testing guidance, minimum viable capability size, and a SaaS-specific use case. 142 pages build cleanly with no broken internal links introduced. This completes the "what framework lets me write business logic once and run it on any OS" content cluster: 1 flagship question page + 44 supporting question pages, 3 new compare pages, 5 blog posts, and 1 hands-on tutorial guide — 50 new pages total across this branch. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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.
Summary
Targets the query cluster "what framework can I use to create apps to deploy in any OS without changing any business logic" and its close permutations, with an SEO/content strategy that leans into this project's existing honesty culture rather than overselling "any OS" the way most cross-platform marketing does.
questions/what-framework-runs-business-logic-on-any-os.html) with FAQPage schema covering the exact phrase and close variantscompare/vs-cross-platform-frameworks.html(Traverse vs Flutter/Electron/Tauri/React Native/.NET MAUI, with a real Tauri +traverse-embeddercode example) andcompare/vs-wasm-runtimes.html(Traverse vs Wasmtime/WasmEdge/Wasmer — positions Traverse as a governance layer built on Wasmtime, not a competing runtime)docs/guides/cross-os-capability.html) walking through building, inspecting, and running the shipped expedition bundle natively and in-browser, verifying identical behavior from the trace artifactAll content is grounded in the current, real platform matrix (native Linux/macOS/Windows + browser shipped; Android/.NET in progress, unreleased; iOS blocked on the WASM engine ecosystem) rather than a rounded-up version of it — matching the standard already set by
/platforms.htmland the/discovertruthfulness tests.Also fixes a pre-existing
package-lock.json/package.jsonversion mismatch (traverse-embedder-web) that was leavingnode_modulesincomplete and breakingnpm run buildon a clean checkout.All new pages are wired into
questions/index.astro,compare/index.astro,blog/index.astro,docs/guides/index.astro, andDocsSidebar.astro— nothing is orphaned. Sitemap regenerates automatically at build time (142 URLs total, up from 92).Test plan
npm run buildsucceeds with no errors (142 pages)/use-cases.htmllinks found in untouched files, left as-is and out of scope)🤖 Generated with Claude Code