Skip to content

Conversation

@uhyo
Copy link
Owner

@uhyo uhyo commented Jan 24, 2026

Summary

  • Add a new "Learn" section to the documentation site for use-case-driven learning materials
  • Create comprehensive Nested Routes tutorial covering route matching, Outlet component, parameter inheritance, and more
  • Refactor styles.css into modular files (base.css, layout.css, components.css, pages.css, responsive.css)

Test plan

  • Run pnpm --filter funstack-router-docs dev and verify the Learn section appears in navigation
  • Navigate to /funstack-router/learn and verify the Learn index page renders
  • Navigate to /funstack-router/learn/nested-routes and verify the tutorial content renders
  • Verify all code examples display correctly with syntax highlighting
  • Test responsive behavior on mobile viewport
  • Run pnpm typecheck to verify no type errors
  • Run pnpm format:check to verify formatting

🤖 Generated with Claude Code

uhyo and others added 2 commits January 24, 2026 13:14
Add a new "Learn" section to the documentation site for use-case-driven
learning materials. The first page covers Nested Routes with:

- Why nested routes are useful
- The Outlet component
- Defining nested routes with children
- Route matching behavior (prefix vs exact matching)
- Multiple levels of nesting
- Parameter inheritance
- Sharing data with loaders
- Pathless layout routes
- Complete practical example

Also refactors styles.css into modular files for better maintainability:
- base.css: Reset, CSS variables, base elements
- layout.css: Layout, header, footer, nav
- components.css: Buttons, code blocks, cards, tables
- pages.css: Page-specific styles
- responsive.css: Media queries

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@uhyo uhyo merged commit 1aec38a into master Jan 24, 2026
1 check passed
@uhyo uhyo deleted the docs/learn-nested-routes branch January 24, 2026 04:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants