docs(examples): describe generated command path
Keep example READMEs aligned with the generated-resource, tuple-composed IntoEffect authoring path instead of lower-level handle/EffectBatch wording. req: dx/006 req: examples/003
This commit is contained in:
@@ -11,8 +11,8 @@ This is a polished Linear-style product demo for planning typed work across lane
|
||||
- modern SSR-first UI
|
||||
- generated resource modules from `.heml`
|
||||
- hemplate partials for issue lanes, cards, and inspector panels
|
||||
- native form posts carrying generated slhx handle fields
|
||||
- multi-target `application/slhx` EffectBatch responses
|
||||
- native form posts wired through generated slhx handles
|
||||
- multi-target tuple-composed `IntoEffect` / `application/slhx` responses
|
||||
- generated slot updates instead of selectors
|
||||
- root-scoped runtime lowering (`data-hid`, `data-sid`)
|
||||
- page-enhancer navigation with native link fallback
|
||||
|
||||
Reference in New Issue
Block a user