[ayushozha]

Type of change

• Bug fix (a non-breaking change that fixes an issue)
• New feature (a non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Other (please describe): README documentation only

Checklist

• I have read the CONTRIBUTING document.
• I have checked to ensure that this Pull Request is not for personal changes.
• I have performed a self-review of my own code.
• My changes generate no new warnings.

Related Issue

None.

Changes

Summary: Getting Started step 5 now has a sub-bullet for Wasmer Edge. It shows the import URL pattern for your own repository (https://wasmer.io/apps/create?github=<owner>%2F<repo>) and a Deploy to Wasmer badge for trying this template directly. One line, README only.

Why this repository: Fuwari is a template, and its deploy step points to generic host guides. The build produces a fully static dist/ with Pagefind search, which a static host can serve without changes. Most readers deploy their own generated repository, so the sub-bullet leads with the <owner>/<repo> form.

How To Test

At 6d39b0d, pnpm install --frozen-lockfile && pnpm run build with the pinned pnpm@9.14.4:

• passed on Node 22.22.0;
• passed on Node 24.22.1;
• passed on a second Node 24.22.1 run.

I served dist/ with a local static server. /, /archive/, /about/, /posts/expressive-code/, /pagefind/pagefind.js and /rss.xml all returned 200, and every root-relative href/src in the 8 HTML pages resolved to a file.

One earlier attempt failed once, with Tailwind reporting that the link class does not exist in src/styles/markdown.css. It was running alongside other builds and its install had hit a registry 503 retry. The failure did not reproduce in the three runs above.

Screenshots (if applicable)

N/A

Additional Notes

• The site setting in astro.config.mjs still has to be set before deploying, as the README already says.

• The import page builds the repository given in the URL and does not create a copy. Redeploy-on-push needs your own repository connected to your Wasmer app.

• The live import page was verified with the correct source, main branch, node-static preset and enabled Deploy button. A full hosted Wasmer deployment was not run.

[vercel]

@ayushozha is attempting to deploy a commit to the zephyirdgmailcom's projects Team on Vercel.

A member of the Team first needs to authorize it.