Files
leptos-shadcn-ui/docs
Peter Hanssens f6a72352c0 feat: Complete file size optimization - refactor 10 large files into 55 focused modules
- Refactored 6,741 lines across 10 large files into 55 focused modules
- All modules now under 300 lines for better LLM comprehension and maintainability
- Maintained full test coverage and functionality

Files refactored:
- packages/leptos/input/src/implementation_tests.rs (867 lines) → 6 modules
- packages/leptos/form/src/implementation_tests.rs (783 lines) → 5 modules
- packages/signal-management/src/signal_management_tests.rs (766 lines) → 7 modules
- packages/signal-management/src/simple_tests.rs (753 lines) → 7 modules
- packages/signal-management/src/lifecycle_tests.rs (648 lines) → 5 modules
- packages/leptos/input/src/tdd_tests.rs (663 lines) → 6 modules
- packages/leptos/command/src/tdd_tests.rs (607 lines) → 5 modules
- packages/signal-management/src/memory_management_tests.rs (554 lines) → 5 modules
- packages/signal-management/src/component_migration.rs (541 lines) → 4 modules
- packages/leptos/button/src/tdd_tests.rs (560 lines) → 5 modules

Added comprehensive remediation documentation in docs/remediation/
All tests passing - 132 tests for button component alone
2025-09-19 20:57:55 +10:00
..

Leptos ShadCN UI Documentation

Welcome to the comprehensive documentation for the Leptos ShadCN UI component library. This documentation is organized to help you find the information you need quickly, whether you're just getting started or working on advanced features.

📚 Documentation Structure

🚀 Getting Started

Perfect for newcomers to the project:

🏗️ Architecture

Deep dive into the technical design:

🧩 Components

Component library reference:

🧪 Testing

Comprehensive testing documentation:

📦 Releases

Release management and version history:

🗺️ Roadmap

Project planning and future direction:

🤝 Contributing

How to contribute to the project:

🎯 Quick Navigation

For New Users

  1. Start with Getting Started
  2. Try the Basic Examples
  3. Read the Component API Reference

For Developers

  1. Review Architecture Overview
  2. Check Testing Guidelines
  3. Follow Contributing Guidelines

For Maintainers

  1. Understand Release Process
  2. Review Roadmap
  3. Check Performance Benchmarks

🔗 External Resources

📝 Documentation Standards

This documentation follows these principles:

  • User-focused: Organized by user journey and needs
  • Comprehensive: Covers all aspects of the project
  • Up-to-date: Regularly maintained and reviewed
  • Accessible: Clear language and good structure
  • Searchable: Well-organized with clear navigation

🤝 Contributing to Documentation

We welcome contributions to improve this documentation! Please see our Contributing Guidelines for details on how to:

  • Report documentation issues
  • Suggest improvements
  • Submit documentation updates
  • Follow our writing standards

Last updated: September 2025