Files
Peter Hanssens eb8f7ae9d6 feat: comprehensive component updates and testing infrastructure
- Update multiple components with improved signal management and error handling
- Add integration tests for dialog, popover, dropdown-menu, command, and sheet components
- Enhance form validation with comprehensive type system
- Add visual testing infrastructure with Playwright
- Add analytics package for component tracking
- Improve lazy loading with new component browser
- Enhance error boundary with context and new_york variants
- Update tailwind-rs-core with improved responsive utilities
- Add extensive error handling utilities across packages

Co-Authored-By: Claude <noreply@anthropic.com>
2026-01-10 12:15:52 +00:00
..
2026-01-10 07:04:56 +00:00
2026-01-10 09:37:34 +00: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:

🎓 Tutorials

Step-by-step video and written tutorials:

🧪 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. Watch the Video Tutorials
  3. Try the Basic Examples
  4. Read the Component API Reference

For Developers

  1. Review Architecture Overview
  2. Check Testing Guidelines
  3. Follow Contributing Guidelines
  4. Explore Performance Optimization Guide for best practices

For Maintainers

  1. Understand Release Process
  2. Review Roadmap
  3. Check Performance Benchmarks
  4. Review Measurement & Benchmarking Guide for continuous monitoring

🔗 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