Open-source project
saicaca/fuwari avatar
saicaca/fuwari

Fuwari: an Astro blog template held together by one config file

✨A static blog template built with Astro.

5,164 stars1,271 forksAstroMIT

At a glance

What is it?
Fuwari is a static blog template built with Astro, Tailwind CSS and Svelte, scaffolded by one of five package managers but installable only with pnpm, with search generated at build time by Pagefind and every post written into src/content/posts.
Who is it for?
Fuwari suits someone who wants a finished looking blog with dark mode, table of contents, RSS and search on day one and is willing to live inside a pnpm-only workflow with a handful of root level config files. It does not suit someone who needs npm or yarn, a dev server with working search, or a documented upgrade path, because the project ships version 0.0.1, no releases, and a last push on 2026-03-10.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Activity is slowing. The repository last received commits 8 months ago.
What is it written in?
Mainly Astro, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • saicaca/fuwari5,164 ★ · +135
Star history
Repository2026-09-232026-11-15
saicaca/fuwari5k5.2k

135 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Five commands can scaffold the template, only one package manager can install it

Step one of the setup offers five interchangeable ways to create the repository, either by generating from the template or by forking it:

sh
npm create fuwari@latest
yarn create fuwari
pnpm create fuwari@latest
bun create fuwari@latest
deno run -A npm:create-fuwari@latest

Step two then narrows that choice to exactly one. You clone the repository and run pnpm install, and the page tells you to install pnpm with npm install -g pnpm if you have not. The reason sits in package.json, where every script lives together with a preinstall hook:

json
"scripts": {
    "dev": "astro dev",
    "start": "astro dev",
    "check": "astro check",
    "build": "astro build && pagefind --site dist",
    "preview": "astro preview",
    "astro": "astro",
    "type-check": "tsc --noEmit --isolatedDeclarations",
    "new-post": "node scripts/new-post.js",
    "format": "biome format --write ./src",
    "lint": "biome check --write ./src",
    "preinstall": "npx only-allow pnpm"
  },

That hook runs only-allow pnpm before dependencies resolve, so an npm or yarn install of a freshly scaffolded blog stops at the first step, and the only lockfile at the root is pnpm-lock.yaml. Scaffolding with bun or deno therefore produces a project those same tools cannot install into.

Search exists only after a build, because Pagefind runs against dist

The feature list credits search functionality with Pagefind, and the way that is wired has a consequence worth knowing before you write your first post. The build script is astro build && pagefind --site dist, a two stage pipeline where Astro writes the static site into ./dist and Pagefind then indexes that output. Its settings live in pagefind.yml at the repository root. The dev script is plain astro dev, with no indexing step attached, and the dev server is documented at localhost:4321. So while you are editing, the search box in the layout has nothing to query. The index only exists after pnpm build, and the way to look at it is pnpm preview, which serves the build before deploying. Two rules follow. Treat search as a build artifact: anything not built is not searchable. And keep an eye on the Pagefind version, since pagefind is pinned with a caret range like the rest of the tooling while astro itself is pinned exactly at 5.13.10.

new-post runs a Node script that drops a file into src/content/posts

Writing is wired to a script rather than to an editor plugin. The new-post script is node scripts/new-post.js, it takes a filename, and the file lands in src/content/posts/ where you edit it by hand. Each post carries frontmatter, and the shape is fixed enough to copy:

yaml
---
title: My First Blog Post
published: 2023-09-09
description: This is the first post of my new Astro blog.
image: ./cover.jpg
tags: [Foo, Bar]
category: Front-end
draft: false
lang: jp      # Set only if the post's language differs from the site's language in `config.ts`
---

Two of those fields carry rules the example states in a comment. lang is set only when the post's language differs from the site language in config.ts, so a single-language blog leaves it out. draft: false is what publishes, and image: ./cover.jpg is a path relative to the post file. The root also holds a frontmatter.json file.

Site settings split across src/config.ts, astro.config.mjs and five more root files

Customization starts in one place: step three of the setup says to edit the config file src/config.ts to customize your blog, and the theme colors and banner named in the feature list are configured there. Deployment is the exception, and it is the step most likely to surprise you. Step five sends you to the Astro deployment guides for Vercel, Netlify, GitHub Pages and similar hosts, with one requirement of its own: edit the site configuration in astro.config.mjs before deployment. Everything else in that sentence is somebody else's documentation. The root directory shows how many tools are in play: svelte.config.js, tailwind.config.cjs, postcss.config.mjs, biome.json, tsconfig.json, vercel.json and .npmrc sit beside astro.config.mjs, with public/ for static assets and docs/ for the translated pages. The Svelte integration is a dependency at a pinned 7.2.3, which is why a Svelte config exists at all. For a reader, the practical consequence is that hosting under a subpath, such as GitHub Pages project sites, needs base path edits that this page never spells out.

Dark mode, banner colors and the icon set are config values with no documented storage

The visual layer is a fixed set of dependencies rather than something you assemble. Fonts arrive as packages, @fontsource/roboto and @fontsource-variable/jetbrains-mono. Icons come through astro-icon with Iconify sets for fa6-brands, fa6-regular, fa6-solid and material-symbols. Page transitions are handled by @swup/astro, overlays scrollbars come from overlayscrollbars, image galleries from photoswipe, and reading time is computed by the reading-time package. The table of contents has its own cause: rehype-slug and rehype-autolink-headings add heading identifiers and anchor links, which is what an in-page table can link to. Feeds and sitemaps come from @astrojs/rss and @astrojs/sitemap. Now the gap. The README never says where the light or dark choice is stored, whether a cookie, localStorage or something server side. There is also no documented hook for analytics, comments or image hosting. Those are additions to the code, not settings you can flip.

Extended Markdown is a plugin set you inherit whole

Beyond GitHub Flavored Markdown, three extras are called out, and the dependency list explains how each one is built. Admonitions arrive through remark-github-admonitions-to-directives together with remark-directive and remark-directive-rehype, so GitHub style alerts in a post file are converted into rendered callouts. Enhanced code blocks come from Expressive Code: @expressive-code/core plus the collapsible sections and line numbers plugins, wired in through astro-expressive-code. katex and rehype-katex are listed for mathematics. markdown-it and mdast-util-to-string round out the parsing side. The consequence for an author is that the vocabulary of a post is fixed at the template level. If you want diagrams, footnotes with special behaviour, or a different code block theme, you are editing dependencies and configuration rather than adding an option, and the project exposes no list of which syntax is guaranteed to survive a future upgrade.

Version 0.0.1, no releases, and a last push dated 2026-03-10

The version field in package.json reads 0.0.1 and the repository has no GitHub releases at all, so there is no tag to install from and no changelog to diff. The last push to the default branch main is dated 2026-03-10, which sets the pace you can expect from the template: check the commit history before assuming a fix landed. Version pinning is inconsistent in a way that matters. astro is pinned exactly at 5.13.10 and @astrojs/svelte exactly at 7.2.3, while most other entries use caret ranges, including @astrojs/rss, pagefind, katex and the Expressive Code family. An Astro major upgrade is therefore a manual edit in package.json followed by whatever pnpm check and tsc report, not something the template handles for you. Around it sit the ordinary community files: LICENSE under MIT, CONTRIBUTING.md, a FOSSA license badge, and a DeepWiki link for navigation. Seven translated READMEs sit in docs/ for Chinese, Japanese, Korean, Spanish, Thai, Vietnamese and Indonesian, each flagged as provided by the community and not always up to date, so a stale instruction is as likely to come from a translation as from the English page.

The command table is nine rows long, and none of them tests anything

Every workflow in the project fits in one table, and the shape of it says a lot about what the maintainers expect you to run:

| Command | Action | |:---------------------------|:----------------------------------------------------| | `pnpm install` | Installs dependencies | | `pnpm dev` | Starts local dev server at `localhost:4321` | | `pnpm build` | Build your production site to `./dist/` | | `pnpm preview` | Preview your build locally, before deploying | | `pnpm check` | Run checks for errors in your code | | `pnpm format` | Format your code using Biome | | `pnpm new-post <filename>` | Create a new post | | `pnpm astro ...` | Run CLI commands like `astro add`, `astro check` | | `pnpm astro --help` | Get help using the Astro CLI |

Two rows hide real work. Formatting and linting both write into ./src through Biome, one with biome format --write and one with biome check --write, so they rewrite files rather than just report. And the command set contains no test script anywhere: package.json defines check as astro check and a separate type-check that runs tsc with --noEmit and --isolatedDeclarations, which is a type gate and not a test run. For a template that publishes pages, that means nothing verifies a broken link, a missing image, or an empty feed before deploy. Astro's own add command is the escape hatch for pulling in integrations, and you are expected to read its help output rather than a project page.

Editorial conclusion

Fuwari suits someone who wants a finished looking blog with dark mode, table of contents, RSS and search on day one and is willing to live inside a pnpm-only workflow with a handful of root level config files. It does not suit someone who needs npm or yarn, a dev server with working search, or a documented upgrade path, because the project ships version 0.0.1, no releases, and a last push on 2026-03-10. Before building on it, read src/config.ts, run pnpm check, and confirm the Astro version pin still matches your deployment target.

Frequently asked questions

How do I create a new Fuwari blog?

Run npm create fuwari@latest, yarn create fuwari, pnpm create fuwari@latest, bun create fuwari@latest or deno run -A npm:create-fuwari@latest, or generate a repository from the template. Then clone it, run pnpm install, and edit src/config.ts to customize the blog.

Why does npm install stop working on a Fuwari project?

package.json carries a preinstall hook that runs npx only-allow pnpm, and pnpm-lock.yaml is the only lockfile in the repository. The setup instructions therefore tell you to run pnpm install, and to get pnpm first with npm install -g pnpm.

Does Fuwari's search work while I am developing?

Not until you build. The build script runs astro build and then pagefind --site dist, with settings in pagefind.yml, while the dev script is plain astro dev on localhost:4321. Use pnpm build and pnpm preview to see a working search index.

Where do I change Fuwari's theme colors and banner?

In src/config.ts, which step three of the setup names as the file to edit for blog customization, alongside the light and dark mode support in the feature list. Hosting changes go elsewhere: astro.config.mjs has to be edited before you deploy.

Official sources

  1. Issues
  2. License: MIT
  3. Project website
  4. README
  5. saicaca/fuwari on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/saicaca-fuwari.svg)](https://hysenlabs.com/projects/saicaca-fuwari)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/saicaca-fuwari.svg)](https://hysenlabs.com/projects/saicaca-fuwari)

Was this useful?