docs: complete DX1 resources, glossary, and shared FAQ - #615
Merged
IbrahimIjai merged 4 commits intoAug 25, 2026
Conversation
The GLV client read an optional import.meta environment value even though the network configuration already validates and exposes the required RPC URL. Using the shared configuration restores strict typechecking on main.
Publish the assigned resource pages from one validated content tree, generate the landing FAQ from that source, and make link, navigation, glossary order, and drift failures visible in CI. The DX1 specs record the currently deferred prerequisite content instead of presenting unbuilt reader paths as complete.
|
@0xsamuel1 is attempting to deploy a commit to the Ijai's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
@0xsamuel1 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Resolves conflicts from the GMX landing-page redesign (main) against this PR's docs/FAQ wiring: - routes/index.tsx: keep main's new landing component set (HeaderMenu, HeroSection, LaunchSection, etc.), dropping the old Navbar/Hero/ Footer imports this PR previously used. - ui/landing/faq-section.tsx: main introduced this file with hardcoded FAQ copy; rewired it to source LANDING_FAQS from faq.generated.ts (generated from apps/docs/content/resources/faq.mdx) instead, and removed the now-superseded faq.tsx. faq.test.tsx renamed to faq-section.test.tsx to match. - ui/landing/footer.tsx: main deleted the footer component entirely as part of the redesign (no footer anywhere in the new landing page). Accepted the deletion rather than reintroducing an old-design footer. - e2e/landing-a11y-check.spec.ts: updated the FAQ trigger selector from main's hardcoded question text to the generated FAQ's first entry.
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
2 participants
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
apps/docsworkspace that publishes printable static routes from validated MDX contentfaq.mdx, wire the landing accordion and footer links, and fail CI when generated data driftsmainLegal review
/resources/termsis intentionally markedstatus: draft. Its eligibility and jurisdiction section is prominently marked pending legal sign-off. It must not be treated as final legal language without maintainer and counsel approval.Content audit
The glossary audit scans every
<Term id="…">reference used by concept pages and resolves it against a stable glossary heading. The content check also requires<Term>usage on at least three concept pages, checks alphabetical order with a case-insensitive English comparison, and verifies that every glossary definition has an onward link to an existing page.The site audit walks both directions between
content/meta.jsonand the MDX tree, then validates every internal route and anchor. Result: 8 reachable pages, 0 orphan pages, and 0 broken internal links.The content-map reader paths were audited against the built site:
These divergences are recorded in
docs/dx_1/003_content_map.md; the PR does not claim that unbuilt pages exist.Verification
bun lintbun typecheckbun run check:tokensbun run testbun run test:coveragebun run buildbun run check:contentbun run check:linksbun run --cwd apps/docs check:faqAGENTS.mdweb/indexer integration commandsbun install --frozen-lockfile, lint, typecheck, test, and buildAll commands passed locally. Existing lint/build warnings remain unchanged.
Closes #609
Closes #610
Closes #611
Closes #612