fix(docs): rutas relativas en docs - #33
Merged
Merged
Conversation
Contributor
📝 WalkthroughWalkthroughDocumentation links converted from absolute paths with leading slashes to relative paths across sidebar configuration and content pages in backend, react, solid, and universal documentation sections. Navigation targets remain the same but use relative path resolution instead. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
🧪 Generate unit tests (beta)
Comment |
|
View your CI Pipeline Execution ↗ for commit b06d27c
☁️ Nx Cloud last updated this comment at |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (4)
apps/docs/src/content/docs/universal/index.mdx (1)
14-35:⚠️ Potential issue | 🟠 MajorFix relative links to avoid duplicated
/universal/segments.From
/universal/, links likeuniversal/packages/...resolve to/universal/universal/.... Use section-relative paths instead.🔧 Suggested fix
- [Learn more →](universal/packages/chat-domain/) + [Learn more →](packages/chat-domain/) - [Learn more →](universal/packages/shared-types/) + [Learn more →](packages/shared-types/) - [Get Started →](universal/getting-started/) + [Get Started →](getting-started/)apps/docs/src/content/docs/universal/getting-started.md (1)
526-532:⚠️ Potential issue | 🟠 MajorAdjust Next Steps links to be relative to
/universal/getting-started/.Current paths will resolve one level too deep.
🔧 Suggested fix
-- [Chat Domain](universal/packages/chat-domain/) - Learn chat domain logic -- [Shared Types](universal/packages/shared-types/) - Explore common types -- [Universal Concepts](universal/concepts/) - Dive deeper into patterns +- [Chat Domain](../packages/chat-domain/) - Learn chat domain logic +- [Shared Types](../packages/shared-types/) - Explore common types +- [Universal Concepts](../concepts/) - Dive deeper into patternsapps/docs/src/content/docs/backend/getting-started.md (1)
513-519:⚠️ Potential issue | 🟠 MajorFix Next Steps links to avoid duplicated
/backend/segments.Use paths relative to
/backend/getting-started/.🔧 Suggested fix
-- [Node Better Auth](backend/packages/node-better-auth/) - Learn authentication patterns -- [Node Auth App](backend/packages/node-auth-app/) - Explore the complete auth service -- [Backend Reference](backend/reference/) - Dive into the API documentation +- [Node Better Auth](../packages/node-better-auth/) - Learn authentication patterns +- [Node Auth App](../packages/node-auth-app/) - Explore the complete auth service +- [Backend Reference](../reference/) - Dive into the API documentationapps/docs/src/content/docs/backend/index.mdx (1)
14-35:⚠️ Potential issue | 🟠 MajorUse section-relative links in the Backend index.
From
/backend/,backend/...resolves to/backend/backend/....🔧 Suggested fix
- [Learn more →](backend/packages/node-better-auth/) + [Learn more →](packages/node-better-auth/) - [Learn more →](backend/packages/node-auth-app/) + [Learn more →](packages/node-auth-app/) - [Get Started →](backend/getting-started/) + [Get Started →](getting-started/)
🤖 Fix all issues with AI agents
In `@apps/docs/src/content/docs/backend/installation.md`:
- Around line 574-579: In the "Next Steps" list in installation.md the link
targets include a leading "backend/" which causes URLs to resolve to
/backend/backend/...; update the four links inside the Next Steps
block—specifically the link targets for Getting Started, Node Better Auth, Node
Auth App, and Backend Reference—by removing the initial "backend/" prefix so
they become relative (e.g. change "backend/getting-started/" to
"getting-started/", "backend/packages/node-better-auth/" to
"packages/node-better-auth/", etc.) ensuring correct resolution from the current
docs path.
Comment on lines
574
to
+579
| ## Next Steps | ||
|
|
||
| - [Getting Started Guide](/backend/getting-started/) - Learn the basics | ||
| - [Node Better Auth](/backend/packages/node-better-auth/) - Explore authentication | ||
| - [Node Auth App](/backend/packages/node-auth-app/) - Complete auth service | ||
| - [Backend Reference](/backend/reference/) - API documentation | ||
| - [Getting Started Guide](backend/getting-started/) - Learn the basics | ||
| - [Node Better Auth](backend/packages/node-better-auth/) - Explore authentication | ||
| - [Node Auth App](backend/packages/node-auth-app/) - Complete auth service | ||
| - [Backend Reference](backend/reference/) - API documentation |
Contributor
There was a problem hiding this comment.
Fix Next Steps links to avoid /backend/backend/... resolution.
🔧 Suggested fix
-- [Getting Started Guide](backend/getting-started/) - Learn the basics
-- [Node Better Auth](backend/packages/node-better-auth/) - Explore authentication
-- [Node Auth App](backend/packages/node-auth-app/) - Complete auth service
-- [Backend Reference](backend/reference/) - API documentation
+- [Getting Started Guide](../getting-started/) - Learn the basics
+- [Node Better Auth](../packages/node-better-auth/) - Explore authentication
+- [Node Auth App](../packages/node-auth-app/) - Complete auth service
+- [Backend Reference](../reference/) - API documentation🤖 Prompt for AI Agents
In `@apps/docs/src/content/docs/backend/installation.md` around lines 574 - 579,
In the "Next Steps" list in installation.md the link targets include a leading
"backend/" which causes URLs to resolve to /backend/backend/...; update the four
links inside the Next Steps block—specifically the link targets for Getting
Started, Node Better Auth, Node Auth App, and Backend Reference—by removing the
initial "backend/" prefix so they become relative (e.g. change
"backend/getting-started/" to "getting-started/",
"backend/packages/node-better-auth/" to "packages/node-better-auth/", etc.)
ensuring correct resolution from the current docs path.
kattsushi
added a commit
that referenced
this pull request
Mar 15, 2026
* fix(docs): use relative internal links and remove leading slashes; keep site/domain + base subpath * fix(docs): usar rutas relativas para enlaces internos en GitHub Pages
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.
Estandariza enlaces internos a rutas relativas para evitar 404 en GitHub Pages bajo /effectify/.\n\nCambios principales:\n- Ajustes en universal/getting-started.md e índices de secciones.\n- Verificación de ausencia de enlaces absolutos (/](/), href="/, link: /).\n\nPor favor revisa que la navegación funcione en https://devx-op.github.io/effectify/.
Summary by CodeRabbit