Annotate coming soon pages in the docs

ox-harris · ox-harris · commit 751cef20ad64 · 2025-11-25T07:41:56.000+01:00
diff --git a/site/api/webflo-fetch/FormData.md b/site/api/webflo-fetch/FormData.md
diff --git a/site/api/webflo-fetch/Headers.md b/site/api/webflo-fetch/Headers.md
diff --git a/site/api/webflo-fetch/LiveResponse.md b/site/api/webflo-fetch/LiveResponse.md
diff --git a/site/api/webflo-fetch/Request.md b/site/api/webflo-fetch/Request.md
diff --git a/site/api/webflo-fetch/Response.md b/site/api/webflo-fetch/Response.md
diff --git a/site/api/webflo-fetch/fetch.md b/site/api/webflo-fetch/fetch.md
diff --git a/site/api/webflo-routing/HttpCookies.md b/site/api/webflo-routing/HttpCookies.md
@@ -0,0 +1 @@
+# HttpCookies (Page Coming Soon)
diff --git a/site/api/webflo-routing/HttpEvent.md b/site/api/webflo-routing/HttpEvent.md
@@ -1,4 +1,4 @@
-# HTTP Event
+# HTTP Event (Page Coming Soon)
 
 The `event` object represents the request and provides access to all request data, state, and lifecycle helpers.
 
diff --git a/site/api/webflo-routing/HttpEvent/respondWith.md b/site/api/webflo-routing/HttpEvent/respondWith.md
@@ -1 +1 @@
-# `event.respondWith()`
+# `event.respondWith()` (Page Coming Soon)
diff --git a/site/api/webflo-routing/HttpEvent/waitUntil.md b/site/api/webflo-routing/HttpEvent/waitUntil.md
@@ -1 +1 @@
-# `event.waitUntil()`
+# `event.waitUntil()` (Page Coming Soon)
diff --git a/site/api/webflo-routing/HttpEvent/waitUntilNavigate.md b/site/api/webflo-routing/HttpEvent/waitUntilNavigate.md
@@ -1 +1 @@
-# `event.waitUntilNavigate()`
+# `event.waitUntilNavigate()` (Page Coming Soon)
diff --git a/site/api/webflo-routing/HttpSession.md b/site/api/webflo-routing/HttpSession.md
@@ -0,0 +1 @@
+# HttpSession (Page Coming Soon)
diff --git a/site/api/webflo-routing/HttpState.md b/site/api/webflo-routing/HttpState.md
@@ -0,0 +1 @@
+# HttpState (Page Coming Soon)
diff --git a/site/api/webflo-routing/HttpUser.md b/site/api/webflo-routing/HttpUser.md
@@ -0,0 +1 @@
+# HttpUser (Page Coming Soon)
diff --git a/site/api/webflo-routing/handler.md b/site/api/webflo-routing/handler.md
@@ -1,4 +1,4 @@
-# Handler API
+# Handler API (Page Coming Soon)
 
 Handlers are the entry point for all requests in Webflo. This page documents the formal contract for handler functions.
 
diff --git a/site/api/webflo-routing/handler/fetch.md b/site/api/webflo-routing/handler/fetch.md
@@ -1,4 +1,4 @@
-# Handler::`fetch()`
+# Handler::`fetch()`  (Page Coming Soon)
 
 Make inbound or outbound calls.
 
diff --git a/site/api/webflo-routing/handler/next.md b/site/api/webflo-routing/handler/next.md
@@ -1,4 +1,4 @@
-# Handler::`next()`
+# Handler::`next()` (Page Coming Soon)
 
 Delegate to next step or make inbound calls.
 
diff --git a/site/docs/advanced.md b/site/docs/advanced.md
@@ -1,9 +1,12 @@
-# Advanced Concepts
+# Advanced Concepts (Page Coming Soon)
 
+<!--
 Talk about:
 + HTTP State
     + Cookies
     + Session
     + User
 + Redirects
-+ Lifecycles
++ Lifecycles
+
+-->
diff --git a/site/docs/advanced/lifecycles.md b/site/docs/advanced/lifecycles.md
@@ -1,4 +1,6 @@
-# Webflo Lifecycles
+# Webflo Lifecycles (Page Coming Soon)
+
+
 
 A place to see all the various lifecycles
 
diff --git a/site/docs/advanced/redirects.md b/site/docs/advanced/redirects.md
@@ -0,0 +1 @@
+# Redirects (Page Coming Soon)
diff --git a/site/docs/advanced/routing.md b/site/docs/advanced/routing.md
@@ -1 +1 @@
-# Advanced Routing
+# Advanced Routing (Page Coming Soon)
diff --git a/site/docs/concepts/rendering.md b/site/docs/concepts/rendering.md
@@ -1,60 +1 @@
-# Rendering
-
-Rendering in Webflo is about turning handler data into UI, both on the server (SSR) and in the browser (CSR).
-
-## The Mental Model
-
-- Your handler returns data (a plain object or Response).
-- Webflo makes this data available as `document.bindings.data` in your HTML.
-- Rendering can happen on the server, the client, or both—using the same mental model.
-
-## Example: Returning Data
-
-```js
-// app/handler.server.js
-export default async function(event, next) {
-  if (next.stepname) return await next();
-  return { title: 'Home', greeting: 'Hello World!' };
-}
-```
-
-## Accessing Data in HTML
-
-```html
-<!-- public/index.html -->
-<!DOCTYPE html>
-<html>
-  <head>
-    <title>My App</title>
-    <script>
-      setTimeout(() => {
-        document.title = document.bindings.data.title;
-      }, 0);
-    </script>
-  </head>
-  <body>
-    <h1 id="greeting"></h1>
-    <script>
-      setTimeout(() => {
-        document.getElementById('greeting').textContent = document.bindings.data.greeting;
-      }, 0);
-    </script>
-  </body>
-</html>
-```
-
-## SSR & CSR
-
-- **SSR:** Data is rendered into HTML on the server for fast first paint and SEO.
-- **CSR:** Data is updated in the browser for dynamic, interactive UIs.
-- **Hybrid:** You can use both together for best results.
-
-## Reactivity & OOHTML
-
-- Use [OOHTML](https://github.com/webqit/oohtml) for reactive UI logic and templates.
-- OOHTML enables `<script quantum>` and `<template>` for declarative, reactive UIs.
-
----
-
-- [See Templates →](./templates.md)
-- [See Lifecycle →](./lifecycle.md)
+# Rendering (Page Coming Soon)
diff --git a/site/docs/concepts/requests-responses.md b/site/docs/concepts/requests-responses.md
@@ -1,47 +1 @@
-# Requests & Responses
-
-This page explains how Webflo orchestrates each interaction from request to response, and how you can hook into various stages, including realtime.
-
-## Overview
-1. A request is received and a route is resolved.
-2. Matching handler(s) execute, optionally delegating via `next()` for nested routes.
-3. A value is produced: data, `Response`, or `LiveResponse`.
-4. The client renders data into the UI or consumes the response stream.
-5. Optional realtime keeps the channel open for additional updates until closed.
-
-## The HttpEvent
-- `event.request`, `event.url` — normalized request data.
-- `event.cookies`, `event.session`, `event.user` — common state interfaces.
-- `event.signal` — aborts when lifecycle completes or client aborts.
-- `event.waitUntil(promise)` — extend lifecycle to await background work.
-- `event.respondWith(value, optionsOrCallback)` — emit one or more responses.
-
-See also: [/api/webflo-routing/HttpEvent](/api/webflo-routing/HttpEvent)
-
-## Delegation via next()
-```js
-export default async function (event, next) {
-  if (next.stepname) return next();
-  return { title: 'Home' };
-}
-```
-
-## Returning Values
-- Single value: `return {...}` or `return Response.json({...})`
-- Multiple/progressive values: call `event.respondWith(...)` one or more times
-- Generators or live functions can yield multiple values naturally
-
-See: [/api/webflo-routing/handler](/api/webflo-routing/handler)
-
-## Realtime
-Realtime extends the lifecycle beyond a single response so server and client can exchange multiple messages.
-
-Close conditions:
-- Handler finishes and no more messages are expected
-- `HttpEvent.signal` aborts (client navigated away or server closed)
-
-See: [/docs/concepts/realtime](/docs/concepts/realtime)
-
-## Completion and Abort
-- The root event aborts when all subtree handlers complete or the request aborts.
-- Child events inherit from the parent and abort when the parent aborts.
+# Requests & Responses (Page Coming Soon)
diff --git a/site/docs/concepts/state.md b/site/docs/concepts/state.md
@@ -1,5 +1,6 @@
-# State, Mutation, & Reactivity
+# State, Mutation, & Reactivity (Page Coming Soon)
 
+<!--
 Webflo’s approach to state is refreshingly simple: your UI state is just a plain JavaScript object. When your server handler returns data, it becomes available as `document.bindings.data` for your templates and UI. No special syntax, no framework-specific magic—just JavaScript you already know.
 
 ## How State Flows
@@ -42,3 +43,4 @@ document.bindings.data.todos.push("Write code"); // UI updates!
 - [Rendering](./rendering.md)
 - [Realtime](./realtime.md)
 - [API: Observer](../api/observer.md)
+-->
diff --git a/site/docs/concepts/templates.md b/site/docs/concepts/templates.md
@@ -1,5 +1,6 @@
-# Templates
+# Templates (Page Coming Soon)
 
+<!--
 Templates let you compose, reuse, and organize HTML in your Webflo app using modern standards.
 
 ## The Mental Model
@@ -11,10 +12,10 @@ Templates let you compose, reuse, and organize HTML in your Webflo app using mod
 ## Example: HTML Modules & Imports
 
 ```html
-<!-- public/header.html -->
+<!-- public/header.html - ->
 <header>Header Area</header>
 
-<!-- public/index.html -->
+<!-- public/index.html - ->
 <!DOCTYPE html>
 <html>
   <head>
@@ -46,3 +47,4 @@ oohtml bundle --recursive --auto-embed=app
 
 - [See Rendering →](./rendering.md)
 - [See Lifecycle →](./lifecycle.md)
+-->
diff --git a/site/docs/tech-stack.md b/site/docs/tech-stack.md
@@ -1,4 +1,4 @@
-# The Technology Stack
+# The Technology Stack (Page Pending Update)
 
 This part covers the technologies that make up the Webflo stack.
 
diff --git a/site/examples/pwa.md b/site/examples/pwa.md
@@ -1,4 +1,4 @@
-# Example: PWA
+# Example: PWA (Page Coming Soon)
 
 Add manifest, service worker, and offline caching.
 
diff --git a/site/examples/web.md b/site/examples/web.md
@@ -1,4 +1,4 @@
-# Example: Web App
+# Example: Web App (Page Coming Soon)
 
 Conventional web app with server-rendered data and client interactivity.
 
diff --git a/site/guides/guide-auth.md b/site/guides/guide-auth.md
@@ -1,4 +1,4 @@
-# Guide: Auth
+# Guide: Auth (Page Coming Soon)
 
 Patterns for session, cookies, and user state.
 
diff --git a/site/guides/guide-file-upload.md b/site/guides/guide-file-upload.md
@@ -1,4 +1,4 @@
-# Guide: File Upload
+# Guide: File Upload (Page Coming Soon)
 
 Handle form uploads and streaming.
 
diff --git a/site/guides/guide-service-worker.md b/site/guides/guide-service-worker.md
@@ -1,4 +1,4 @@
-# Guide: Service Worker
+# Guide: Service Worker (Page Coming Soon)
 
 Integrate a Service Worker for offline and caching.
 
diff --git a/site/guides/tutorial-1-todo.md b/site/guides/tutorial-1-todo.md
@@ -1,4 +1,4 @@
-# Tutorial: Todo App
+# Tutorial: Todo App (Page Coming Soon)
 
 Build a minimal Todo app to learn core Webflo flows.
 

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-# HTTP Event`
	`1`	`+# HTTP Event (Page Coming Soon)`
`2`	`2`
`3`	`3`	The `event` object represents the request and provides access to all request data, state, and lifecycle helpers.
`4`	`4`
Original file line number	Diff line number	Diff line change
`@@ -1 +1 @@`
`1`		-# `event.respondWith()`
	`1`	+# `event.respondWith()` (Page Coming Soon)
Original file line number	Diff line number	Diff line change
`@@ -1 +1 @@`
`1`		-# `event.waitUntil()`
	`1`	+# `event.waitUntil()` (Page Coming Soon)