VitruvianOS
    • Home
      • Building
      • How To Install
        • Linux
        • Windows
        • macOS
      • FAQ
      • Coding Guidelines
      • API Changes
      • Filesystem Layout
      • Legacy Documentation
      • Nexus
      • Donate
    • GitHub

    Development

    For people working on VitruvianOS itself.

    • Coding Guidelines: code style, naming conventions, error handling
    • API Changes: where Vitruvian diverges from BeOS/Haiku APIs
    • Filesystem Layout: path mapping and attribute storage
    • Nexus: the kernel bridge
    Backward FAQ Coding Guidelines Forward