WE Documentation

Getting Started

New to WE? Start here.

• Developer Setup — Prerequisites, clone, build, run
• Seed System — How we-seed.json configures everything

Architecture

How WE is designed and why.

• What is WE? — Grounded vision for WE as a community-first meta-app
• Why WE — The problem WE is responding to and why it matters
• Why a Meta-App Instead of Many Separate Apps? — Why shared continuity and cumulative evolution matter
• Practical Examples — Simple examples of how WE ideas work in practice
• Overview — Block system, schema system, entity models, design principles
• Package Conventions — How packages are structured and named in the monorepo

Guides

How to build with WE.

• Module Development — Building and publishing custom modules
• Launcher UI Customization — Customizing boot screen and settings via seed
• Cesium Layers — Using the 3D globe layer system
• Cesium Implementation — Implementation details and status

Design Decisions

Why we chose this architecture.

• Block System Advantages — Why standardised blocks solve content fragmentation
• Schema System Advantages — Why declarative schemas solve UI fragmentation
• Critical Analysis — Counter-arguments and responses

Internal

Working notes for maintainers.

• Todos
• plans/ — Strategy docs for upcoming work (delete after merging)