docs: add _app crate convention for Dioxus WASM frontends #49

Merged

mik-tf merged 1 commit from development_app_convention into development

2026-03-05 15:14:56 +00:00

mik-tf commented

2026-03-05 14:16:43 +00:00

Owner

Summary

Adds _app suffix to the hero_service skill's crate table and workspace layout
Documents the build-time Dioxus WASM frontend pattern: _app compiles to WASM assets, _ui serves them
Clarifies that _app is NOT a deployed service (no socket, no binary, no TOML)

Closes #48

Test plan

Review the added documentation for accuracy
Verify consistency with the hero_os rename (hero_os_ui → hero_os_app)

## Summary - Adds `_app` suffix to the hero_service skill's crate table and workspace layout - Documents the build-time Dioxus WASM frontend pattern: `_app` compiles to WASM assets, `_ui` serves them - Clarifies that `_app` is NOT a deployed service (no socket, no binary, no TOML) Closes #48 ## Test plan - [ ] Review the added documentation for accuracy - [ ] Verify consistency with the hero_os rename (hero_os_ui → hero_os_app)

mik-tf added 1 commit

2026-03-05 14:16:43 +00:00

docs: add _app crate convention for Dioxus WASM frontends 15057b26d3

The _app suffix designates a build-time Dioxus WASM frontend crate that
compiles to static assets served by the _ui crate. Unlike _server and _ui,
_app is not a deployed service — it has no socket, no binary, and no TOML
service definition.

Example: hero_os_app compiles to WASM, hero_os_ui serves those assets.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

mik-tf commented

2026-03-05 14:18:25 +00:00

Author

Owner

@despiegk @timur makes sense?