This roadmap prioritizes low maintenance and high teaching value.
- Clean project structure
- Leveled example scripts (beginner → advanced)
- Official-definition generator
- Basic Sublime syntax + settings
- Documentation for external editors and beginners
- Maintenance guide designed for limited staff
- Basic CI validation
- Run generator against current official
lsl_definitions.yaml - Publish new repository under buildersbrewery
- Archive old 2020-era repositories
- Update website / Discord / in-world links
- Short announcement for the media blitz
- Generate real Sublime completions + tooltips from the YAML
- Add 4–6 more advanced examples (pathfinding, PBR/GLTF, robust experiences, multi-script patterns)
- Optional: simple “What’s new in LSL” page generated from definition dates
- Community call for example-script contributions
- Scheduled check for newer official definitions (GitHub Action)
- Clear “Adopt-a-section” model so volunteers can own examples or docs
- Consider light VS Code support using the same generated data
- Annual review of whether the project still meets the not-for-profit teaching mission
- Does this reduce or increase the work required from limited staff?
- Does this help a complete beginner or only advanced users?
- Can a new volunteer understand this in one sitting?
- Does this stay honest about what is official Linden Lab data vs what we added for teaching?