A minimal Astro 5 starter deployed on Webflow Cloud.
This is the vanilla variant — the exact output of npm create astro@latest, styled with a branded landing page and a few doc links to get you going.
Looking for the variant with Cloudflare bindings (D1, R2, KV)? See
hello-world-astro-app-bindings.
npm install
npm run dev
# → http://localhost:4321- Fork this repo.
- In your Webflow site, open Apps → Webflow Cloud → Create new app and select this repo.
- Pick a mount path and click Deploy.
Full walkthrough: https://developers.webflow.com/webflow-cloud/quickstart.
- Astro 5 (static, no framework islands)
- Tailwind CSS v3 via
@astrojs/tailwind - Branded landing page with Webflow Cloud doc links
The landing page lives in src/pages/index.astro. Styles are in
src/styles/global.css under the wf-* prefix.
Built with Astro · Deployed on Webflow Cloud.
This repo is the canonical hello-world-<framework>-app example. Every framework
version and variant lives on a branch here, not in a separate repo:
| Branch | Contents |
|---|---|
main |
Current default example. Advances to the latest framework version once dependent pipelines are updated. |
vN |
Framework major version N, no storage bindings (for example v6). |
vN-with-bindings |
Version N plus D1, R2, and KV bindings and a /api/binding-status health check. |
sentry |
Latest version with bindings, plus a working Sentry setup. |
When a new major version M ships:
- Create
vMfrom the new plain app andvM-with-bindingsfrom its bindings variant. - Point
sentryat the latest version with bindings. - Leave
mainuntil the pipelines that consume this repo (webflow-cli, infrastructure/cosmic-builder, cosmic-test) are updated, then advancemaintovM. - Keep older
vN/vN-with-bindingsbranches so pinned references keep working.
Version branches (vN, vN-with-bindings, sentry) are protected: they can't be
deleted or force-pushed.