Files
leptos-shadcn-ui/docs
Peter Hanssens 9feafad89f 🚀 Release v0.9.0 - Massive Code Refactoring Achievement
- 99% file size reduction across 9 critical components
- 45+ test modules created with comprehensive coverage
- Enterprise-grade modular architecture implemented
- All compilation issues resolved
- Production-ready code quality achieved

Components refactored:
- Button: 2,577→20 lines (99.1% reduction)
- Card: 1,651→16 lines (99.0% reduction)
- Checkbox: 1,082→8 lines (99.3% reduction)
- Combobox: 618→8 lines (98.7% reduction)
- Context-menu: 624→8 lines (98.7% reduction)
- Select: 1,517→12 lines (99.2% reduction)
- Dropdown-menu: 500→4 lines (99.2% reduction)
- Popover: 326→4 lines (98.8% reduction)
- Command: 591→8 lines (98.6% reduction)

Total impact: 9,892→95 lines (99% reduction)
2025-09-22 13:00:50 +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