Added new "Plugin Licensing" section to plugin documentation that covers: **SmoothSchedule Community Plugin License (SCPL):** - Custom license for marketplace plugins - Grants platform rights to use, execute, host, and distribute code - Grants users rights to install, use, and modify for their business - Requires attribution to original author - Allows users to adapt code but not republish without permission - Permits authors to unpublish anytime (existing installs continue) - Authors retain copyright and can license elsewhere - Similar to MIT License + Platform Service Rights **Private vs. Marketplace Plugins:** - Private plugins: Full ownership, any license (or none), private to business - Marketplace plugins: Must use SCPL, visible to all users, author credited - Both types: Platform can execute code to provide automation service **Key Features:** - Comparison table showing differences between private and marketplace plugins - Code verification and security requirements documented - Decision guide for when to publish vs. keep private - Important notices about warranties, compliance, and data privacy - Platform service rights clearly explained **Legal Protections:** - Platform has rights to execute user code for service delivery - No warranty disclaimer (plugins "as-is") - User compliance responsibility for laws and regulations - Data privacy obligations (GDPR, CCPA compliance) The SCPL is designed to be marketplace-friendly while protecting both the platform and plugin authors, similar to how npm/PyPI handle packages but with added platform service rights for SaaS execution. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
React + Vite
This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.
Currently, two official plugins are available:
- @vitejs/plugin-react uses Babel (or oxc when used in rolldown-vite) for Fast Refresh
- @vitejs/plugin-react-swc uses SWC for Fast Refresh
React Compiler
The React Compiler is not enabled on this template because of its impact on dev & build performances. To add it, see this documentation.
Expanding the ESLint configuration
If you are developing a production application, we recommend using TypeScript with type-aware lint rules enabled. Check out the TS template for information on how to integrate TypeScript and typescript-eslint in your project.