feat: add guide for splitting STEP assemblies into separate part files - #89
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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 changed
src/pages/guides/SplitStepAssembly.tsx— a real, server-rendered page (same pattern as Landing) targeting "how to split a STEP assembly into separate part files," a validated real pain point with no existing free-online answer/guides/split-step-assemblyto the routes array insrc/main.tsxpublic/sitemap.xmland a new "Guides" section inpublic/llms.txtoverflow: hiddenstyles meant for the full-screen viewer/landing hero. Fixed by scoping abody.guide-pageclass (set via this page's<Head>) and overridingoverflow/heightonly for that class —/and/viewerare unaffectedFAQPage) matching the visible FAQ content word-for-word, so Google can render it as an expandable rich result/and/vieweruntouched) with a modern, skimmable layout — card-style "why you'd need this" items, numbered step cards, accordion-style FAQ, generous spacing/line-height, max-width readable columnpublic/guides/split-step-assembly-demo.pngsrc/pages/Landing.tsxog:title,og:description,og:url,og:type, and Twitter title/description specific to this page (previously it would've inherited the homepage's generic social preview)Why
Validation
npm run preview: page scrolls correctly end-to-enddist/guides/split-step-assembly.htmlcontains full server-rendered content, both JSON-LD blocks, and the image reference)/guides/split-step-assemblyloads correctly; screenshot image actually renders (not broken)Notes
/and/viewerare functionally and visually untouched — all theme/layout changes are scoped to this route only