docs(www): expand competitor comparison page to 8 frameworks (#329)#374
Merged
Conversation
The comparison page at /architecture/comparison was a stub (three high-level groupings). #329 (real) / batch #328 asks for a real comparison of openElement against Next.js, Nuxt, SvelteKit, Astro, Fresh, Lit, Enhance, and Stencil, covering architecture, rendering model, DX, and lock-in. - Rewrote comparison.tsx with one card per framework (openElement + the 8), each covering Architecture / Rendering / DX / Lock-in. Honest, no invented benchmarks. Kept the existing "does not invent benchmark claims" stance and the decision-criteria section. - Added a Comparison row to the README Documentation table linking to openelement.org/architecture/comparison (the page is already in the site nav via its route meta). README.zh.md was intentionally left unchanged: its 文档 table links to local docs, not openelement.org pages, so a parallel website link would introduce drift rather than parity. Closes #329
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Deploying openelement with
|
| Latest commit: |
fd8a530
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://681c4a4b.lessjs.pages.dev |
| Branch Preview URL: | https://fix-329-competitor-page.lessjs.pages.dev |
Contributor
|
APIError: Insufficient Balance |
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
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
#329 (real) / batch #328 — "Implement competitor comparison page".
The page at
/architecture/comparisonalready existed but was a stub (threehigh-level groupings). This expands it into a real comparison of openElement
against the eight frameworks the issue names:
Each framework gets a card covering the four dimensions the issue calls out:
The page keeps its explicit "does not invent benchmark claims" stance; the
comparison is directional and honest, not a speed ranking. The existing
decision-criteria section was expanded to map each framework family to when
you'd pick it.
The page was already in the site nav (via its route
meta), so the onlylinkage gap was README. Added a Comparison row to the README
Documentation table pointing at
openelement.org/architecture/comparison.README.zh.mdwas intentionally left unchanged: its 文档 table links to localdocs, not
openelement.orgpages, so adding a website link there would createdrift rather than parity.
Test plan
deno check www/app/routes/architecture/comparison.tsx: clean.deno fmt --checkclean on both files.Closes #329