feat: Clean up root directory and create docs folder

docs/PLAN.md

@@ -0,0 +1,206 @@
+# KNEL Cloudron Packaging Plan
+
+## 🎯 Mission Statement
+
+Package ~100 applications for KNEL's Cloudron platform to create a comprehensive self-hosted application ecosystem for internal use and potential contribution to the broader Cloudron community.
+
+## 📋 Strategic Objectives
+
+### Phase 1: Foundation (Q1 2025) - ✅ COMPLETED
+- [x] Establish repository structure and workflows
+- [x] Create development tooling and containerized environment
+- [x] Document packaging standards and processes
+- [x] Create template and examples (EasyGate, InvenTree baseline)
+- [x] Implement git workflow with feature branches
+
+### Phase 2: Core Applications (Q1-Q2 2025) - 🚧 IN PROGRESS
+**Target: 25 essential applications**
+
+#### Priority Tier 1 (Business Critical)
+- [ ] Apache APISIX (API Gateway) - 🚧 **IN PROGRESS**
+- [ ] Jenkins (CI/CD)
+- [ ] Grist (Database/Spreadsheet)
+- [ ] Rundeck (Job Scheduler)
+- [ ] ReviewBoard (Code Review)
+- [ ] Consul Democracy (Governance)
+
+#### Priority Tier 2 (Development Tools)
+- [ ] ElabFTW (Laboratory Management)
+- [ ] Resgrid (Emergency Management)
+- [ ] Database Gateway
+- [ ] Core infrastructure tools
+
+#### Priority Tier 3 (Productivity & Collaboration)
+- [ ] Document management systems
+- [ ] Communication tools
+- [ ] Project management applications
+
+### Phase 3: Extended Ecosystem (Q2-Q3 2025)
+**Target: 50 additional applications**
+- [ ] Monitoring and observability tools
+- [ ] Security and compliance applications
+- [ ] Backup and storage solutions
+- [ ] Development and testing tools
+
+### Phase 4: Specialized Applications (Q3-Q4 2025)
+**Target: 25 remaining applications**
+- [ ] Industry-specific tools
+- [ ] Advanced analytics platforms
+- [ ] Integration and automation tools
+- [ ] Experimental and emerging technologies
+
+## 🏗️ Technical Strategy
+
+### Packaging Approach
+1. **Container-First**: All development in `tsys-cloudron-packaging` container
+2. **Source-Based**: Use actual upstream sources from `CloudronPackagingWorkspace/`
+3. **Standardized**: Follow consistent patterns across all packages
+4. **Tested**: Build, deploy, and validate each package before finalization
+
+### Architecture Patterns
+- **Web Applications**: Nginx + App Server + Database
+- **API Services**: Direct exposure with proper health checks
+- **Background Services**: Supervisor-managed processes
+- **Databases**: Utilize Cloudron database addons
+- **Storage**: Proper persistent volume management
+
+### Quality Standards
+- **Security**: No hardcoded secrets, proper permissions, security headers
+- **Monitoring**: Comprehensive logging and health checks
+- **Performance**: Resource limits and optimization
+- **Reliability**: Error handling and graceful degradation
+- **Maintainability**: Clear documentation and build notes
+
+## 🔄 Development Workflow
+
+### Git Strategy
+```
+main (stable packages)
+  ↑
+integration (testing multiple packages)
+  ↑
+feature/package-[appname] (individual development)
+```
+
+### Development Cycle
+1. **Research** → Understand application requirements
+2. **Package** → Create Cloudron-compatible container
+3. **Build** → Test container construction
+4. **Deploy** → Test on development Cloudron instance
+5. **Validate** → Verify functionality and integration
+6. **Document** → Create comprehensive build notes
+7. **Review** → Code review and quality assurance
+8. **Integrate** → Merge to integration branch
+9. **Release** → Promote to main after validation
+
+### Automation Goals
+- [ ] Automated testing of package builds
+- [ ] Integration testing with Cloudron
+- [ ] Automated documentation generation
+- [ ] Upstream source monitoring and updates
+
+## 📊 Success Metrics
+
+### Quantitative Goals
+- **Package Count**: 100 applications packaged
+- **Success Rate**: >90% of packages deploy successfully
+- **Update Frequency**: Monthly upstream sync
+- **Documentation Coverage**: 100% packages have build notes
+
+### Qualitative Goals
+- **Reliability**: Packages start consistently and remain stable
+- **Security**: All packages follow security best practices
+- **Usability**: Clear setup and configuration processes
+- **Maintainability**: Packages can be updated with minimal effort
+
+## 🛣️ Roadmap Milestones
+
+### 2025 Q1 - Foundation Complete ✅
+- Repository and tooling established
+- Initial examples working (EasyGate, InvenTree)
+- Documentation and processes defined
+
+### 2025 Q2 - Core Applications
+- 25 essential business applications packaged
+- Testing and validation processes refined
+- Integration branch workflow proven
+
+### 2025 Q3 - Extended Ecosystem  
+- 75 total applications packaged
+- Automation and monitoring implemented
+- Performance optimization and scaling
+
+### 2025 Q4 - Complete Ecosystem
+- 100 applications packaged and maintained
+- Community contribution pipeline established
+- Next-generation planning and roadmap
+
+## 🚀 Resource Allocation
+
+### Development Team
+- **Primary Developer**: Focus on complex applications
+- **Secondary Developer**: Handle standard web applications  
+- **QA/Testing**: Validation and integration testing
+- **Documentation**: Build notes and user guides
+
+### Infrastructure
+- **Development Cloudron**: Package testing and validation
+- **Staging Environment**: Integration testing
+- **Container Registry**: Package storage and distribution
+- **CI/CD Pipeline**: Automated build and test
+
+### Time Estimates
+- **Simple Web App**: 4-8 hours
+- **Complex Service**: 1-2 days
+- **Database-Heavy App**: 2-3 days
+- **Custom Integration**: 3-5 days
+
+## 🔍 Risk Management
+
+### Technical Risks
+- **Upstream Changes**: Applications may change build requirements
+- **Cloudron Updates**: Platform updates may break packages
+- **Resource Constraints**: Complex applications may exceed limits
+- **Integration Issues**: Inter-application dependencies
+
+### Mitigation Strategies
+- Regular upstream monitoring and updates
+- Version pinning for critical dependencies
+- Comprehensive testing before releases
+- Fallback and rollback procedures
+
+## 🌟 Future Opportunities
+
+### Community Contribution
+- Submit high-quality packages to Cloudron app store
+- Contribute improvements back to upstream projects
+- Share packaging expertise with broader community
+
+### Advanced Features
+- Multi-instance deployments
+- Cross-application integrations
+- Advanced monitoring and alerting
+- Custom authentication and SSO integration
+
+## 📝 Decision Log
+
+### 2025-01-04: Repository Structure
+- **Decision**: Use workspace pattern with gitignored upstream sources
+- **Rationale**: Keeps git history clean while preserving source access
+- **Impact**: Scalable to 100+ applications without repo bloat
+
+### 2025-01-04: Container-Based Development
+- **Decision**: All packaging work in persistent container
+- **Rationale**: Consistent environment, host isolation, team standardization
+- **Impact**: Reproducible builds and simplified onboarding
+
+### 2025-01-04: Branch Strategy
+- **Decision**: Feature branches per application with integration branch
+- **Rationale**: Isolates work, enables parallel development, staged integration
+- **Impact**: Better quality control and easier rollback capabilities
+
+---
+
+**Last Updated**: 2025-01-04  
+**Next Review**: 2025-02-01  
+**Owner**: KNEL/TSYS Development Team