blogwright 0.4.0-beta.3 → 0.4.0-beta.5

package/README.md

@@ -1,14 +1,19 @@
 # blogwright
 
-Deploy a static site to AWS from one CLI: S3 + CloudFront hosting, builds in an
-isolated **Lambda MicroVM**, PR previews, keyless GitHub-OIDC CI deploys, and
-optional [standard.site](https://standard.site) (AT Protocol) publishing. No
+Deploy a static site - or a server-rendered Node app - to AWS from one CLI: S3 +
+CloudFront hosting, builds in an isolated **Lambda MicroVM**, PR previews,
+keyless GitHub-OIDC CI deploys, and optional
+[standard.site](https://standard.site) (AT Protocol) publishing. No
 CloudFormation, no Terraform, no CDK - the infrastructure is a reconcilable
 dependency graph the CLI applies directly through signed AWS API calls.
 
 Works with any static site that installs and builds with pnpm: an Astro blog at
 the repo root, a SvelteKit/Vite SPA in a monorepo subdirectory, anything that
-ends in a directory of files to serve.
+ends in a directory of files to serve. With an `ssr` config block it also runs a
+Node server (Astro, SvelteKit `adapter-node`, Nuxt, TanStack Start, Next
+standalone) as a
+**Lambda Web Function** behind the same CloudFront distribution - see
+[Server-rendered sites](https://blogwright.iamstan.dev/guides/server-rendered-sites/).
 
 ## Requirements
 
@@ -27,8 +32,10 @@ pnpm exec blogwright bootstrap # creates the bucket, CDN, roles, builder image
 pnpm exec blogwright deploy    # zip → build in a MicroVM → live site
 ```
 
-`init` asks four questions (site name, region, optional domain, optional GitHub
-repo). `bootstrap` prints the CloudFront domain - and, if you set a domain, the
+`init` asks for the site name, region, optional domain and optional GitHub repo,
+then whether the app is server-rendered and with which framework (`astro`,
+`sveltekit`, `nuxt`, `tanstack-start`, `nextjs` or `other`), writing its `ssr`
+block and entry shim settings. `bootstrap` prints the CloudFront domain - and, if you set a domain, the
 ACM validation CNAMEs to add to DNS. `deploy` streams the build log with live
 progress and ends with a summary card and your URL. The `bw` alias works
 everywhere `blogwright` does.

package/agent/agent-manifest.json

@@ -1,3 +1,3 @@
 {
-  "hash": "c47204363a57"
+  "hash": "af74046ef42e"
 }