Vybe Documentation
Vybe Main page
Documentation Improvement Roadmap
Documentation is a living part of the project. Here are several ways we can continue to improve the Vybe documentation:
1. Contextual Code Snippets
While we've added high-level examples, every single function and property should ideally have a "Try it out" snippet.
- Goal: 100% example coverage for
builtins.
2. Tutorials & "Quickstart" Guides
The current documentation is reference-heavy. Adding step-by-step tutorials would lower the barrier for new users.
- Potential Guides: "Building your first 'Hello World' app", "Implementing a simple calculator", "Working with files and JSON".
3. Visual Aids & Diagrams
We've added a basic architecture diagram, but more granular flowcharts would help.
- Ideas: "Event Loop Flow", "Parser State Machine", "Form Serialization Lifecycle".
4. API Reference Generation
As the project grows, manually maintaining markdown files becomes difficult.
- Future Step: Use a tool like
rustdocor a custom generator to pull function signatures and docstrings directly from the Rust source code.
5. Interactive Playground
If Vybe is compiled to WASM (on the roadmap), we could host an interactive documentation site where users can write and run Vybe code directly in their browser.
6. Contribution Guide
A dedicated CONTRIBUTING.md (or similar) detailing the process for adding new builtins or controls would empower the community.