Nexamas UI Documentation
Nexamas UI documentation is organized for evaluation, application development, maintenance, and API review. The source of truth is the Nexamas UI source tree, package contract, public/Friend boundaries, quality assets, and evidence inventories. The Showcase is a demonstration surface, not the authority for product claims.
Start by Audience
| Audience | Start here | Purpose |
|---|---|---|
| Customer or buyer | Customer guide | Understand what Nexamas UI is, what is included, and what is not included. |
| Company evaluator | Company adoption guide | Review adoption boundaries, evaluation flow, package scope, and commercial limits. |
| Application developer | User documentation | Build a real application with the beginner public consumer surface. |
| SDK developer | Developer guide | Review implementation-oriented public consumer patterns. |
| Maintainer | Maintaining documentation | Keep docs aligned with code, package, and quality evidence. |
| API reviewer | Reference guide | Inspect public surfaces, inventories, and evidence. |
| Release reviewer | Quality proof guide | Check what proof assets exist and what must be run on Windows. |
Build with Nexamas UI
Use User documentation as the beginner path, then use these core pages when writing a real application:
- Application and window lifetime
- Layout and composition
- Controls and component factories
- Theme and surface materials
- DataGrid and DataView
- Localization and RTL
- Motion behavior
- Diagnostics and quality proof
- Packaging and external consumer use
Copy, Adapt, Then Build
| Need | Page |
|---|---|
| Fastest first window | Quickstart copy-paste |
| Common SDK usage patterns | Common consumer patterns |
| Public examples | Copy-paste examples |
| Beginner user path | User documentation |
| Task-oriented recipes | Recipes |
| Minimal external consumer sample | MinimalConsumerApp |
Public API and References
| Area | Reference |
|---|---|
| Full API coverage | API Reference coverage |
| Controls and components API batch | Batch 2 Controls and Components |
| Systems/evidence/compatibility API batch | Batch 3 Systems/Evidence/Compatibility |
| Application API batch | Batch 1 Application API |
| V1 Public API catalog | V1 Public API catalog |
| Public API overview | Public API surface |
| Application facade | Application facade surface |
| Component factories | Component factory surface |
| Layout and size | Layout and size surface |
| Theme and surface | Theme and surface surface |
| Localization and RTL | Localization and RTL surface |
| Data and virtualization | Data component surface |
| Output | Output surface |
| Quality and verification | Quality verification surface |
Product and Commercial Docs
- Product brief
- What is included
- Pricing and evaluation policy
- Licensing and delivery boundary
- Stability and roadmap boundary
- Brand and API identity
- Platform overview
Maintainer, Evidence, and Proof
Maintainer and evidence pages are maintained for reviewers and maintainers. They should not be treated as the beginner path for application developers.
- Maintainer documentation
- Documentation policy
- Source of truth
- Claim ledger
- Documentation status
- Documentation cleanup ledger
- Quality proof guide
- Quality proof archive
- Windows validation runbook
- Release documentation pack inventory
- User documentation audit scope
- Recipe build-verification ledger
- Showcase snippet map
- RecipeVerification Batch 1 sample
- RecipeVerification Batch 2 sample
- RecipeVerification Batch 3 sample
- Latest recorded Windows quality run
- Final user-documentation closure
- Documentation recipes Windows PASS
Rule
No consumer-facing claim should be added unless it is backed by source code, package evidence, a public API boundary, a quality asset, or an inventory entry. Public examples and Showcase snippets must use official public entry points only.