cleanup, docs

site/doc/pages/component.txt

@@ -36,64 +36,18 @@ When a component unit defines `ONCE(Request& context)`, the runtime calls that h
 
 Default component handler:
 
-```cpp
-DValue props;
-props["title"] = "Status";
-
-<><?: component("workspace/panel", props, context) ?></>
-```
 
 Named component handler:
 
-```cpp
-DValue props;
-props["title"] = "System";
-props["body"] = "Healthy";
-
-print(component("components/card:BODY", props, context));
-```
 
 Self-targeted named handler from inside the same file:
 
-```cpp
-COMPONENT(Request& context)
-{
-	<>
-		<section class="card">
-			<?: component(":BODY", context.props, context) ?>
-		</section>
-	</>
-}
-
-COMPONENT:BODY(Request& context)
-{
-	<>
-		<p><?= context.props["body"] ?></p>
-	</>
-}
-```
 
 Preparing props in C++ before rendering:
 
-```cpp
-DValue props;
-props["items"][0] = "alpha";
-props["items"][1] = "beta";
-props["items"][2] = "gamma";
-
-String html = component("components/list", props, context);
-print(html);
-```
 
 Embedding returned component markup inside a literal block:
 
-```cpp
-<>
-	<div class="panel">
-		<?: component("components/card", props, context) ?>
-	</div>
-</>
-```
 
 Because `<?= ... ?>` escapes HTML, use `<?: ... ?>` when inserting the returned markup from `component()`.
 
@@ -103,7 +57,5 @@ Because `<?= ... ?>` escapes HTML, use `<?: ... ?>` when inserting the returned
 - `ONCE(Request& context)` runs once per request before the first component or render entrypoint from that file.
 - `component()` then calls either `COMPONENT(Request& context)` or the selected `COMPONENT:NAME(Request& context)` handler.
 
-## Related Concepts
-
-- PHP: reusable template partials or helper-rendered view fragments returned as strings
-- JavaScript / Node.js: component render helpers, especially patterns that return markup as a string
+:example
+print("component example\n");