+1 (non-binding) As a community member who has spent significant time helping other users work through issues, I want to express strong support for having proper documentation, working examples, and an organized website - regardless of the technical implementation details.
The current situation with: - Lack of documentation for 10.0 - Outdated/broken examples - Fragmented/outdated websites is creating a very high barrier to entry for new community users. While I cannot speak to the technical merits of moving things to KIE-Tools vs other approaches, I can definitively say that the status quo is hurting community adoption and engagement. I've personally spent considerable time helping users work through issues that could have been prevented with proper documentation and examples. I appreciate the concerns raised about added complexity, but from a community user perspective, the current fragmentation and lack of maintained documentation is a bigger problem. As someone willing to contribute to documentation efforts, I support any systematic approach that will: 1. Provide centralized, maintained documentation 2. Ensure examples stay in sync with releases 3. Lower the barrier to entry for new users The specific technical implementation matters less to me than having a committed plan to address these fundamental community needs.
