test(examples): guard low-level docs wording
Keep beginner example docs on target objects and tuple IntoEffect responses instead of runtime lowering/application wire vocabulary. req: dx/006 req: examples/003
This commit is contained in:
@@ -9,12 +9,12 @@ Open <http://127.0.0.1:3002>.
|
||||
This is a polished Linear-style product demo for planning typed work across lanes. It is tailored to showcase slhx strengths:
|
||||
|
||||
- modern SSR-first UI
|
||||
- generated resource modules from `.heml`
|
||||
- generated target objects from `.heml`
|
||||
- hemplate partials for issue lanes, cards, and inspector panels
|
||||
- native form posts wired through generated slhx handles
|
||||
- multi-target tuple-composed `IntoEffect` / `application/slhx` responses
|
||||
- native form posts wired through generated form/handle resources
|
||||
- multi-target tuple-composed `IntoEffect` responses
|
||||
- generated slot updates instead of selectors
|
||||
- root-scoped runtime lowering (`data-hid`, `data-sid`)
|
||||
- root-scoped runtime application without selector lookups
|
||||
- page-enhancer navigation with native link fallback
|
||||
- SSE server push into a generated slot
|
||||
- drag-and-drop lane moves persisted by typed server handlers through the slhx runtime
|
||||
|
||||
Reference in New Issue
Block a user