
Template details
blog-hishaku
A classic three-column Astro blog template for Japanese blogs, configured via a single YAML file with Markdown-based posts.
About this template
blog-hishaku is a static blog template built on Astro that pairs a classic three-column layout with the features Japanese-language blogs typically need. All site settings live in a single config/site.yaml file, and posts are plain Markdown files, so the build output is a static site you can host anywhere. The repository is MIT-licensed and maintained under the pithos-day GitHub organization.
What is blog-hishaku?
blog-hishaku is an Astro blog template that takes Markdown files placed anywhere under src/content/blog/ and publishes them as a static blog with a three-column classic layout. Site name, author, URL, SNS links, analytics, and Markdown extension toggles are all set in config/site.yaml, and pnpm build writes the finished site to dist/ together with a Pagefind search index. The template is MIT-licensed and distributed by the pithos-day project, whose author also runs a companion blog documenting the syntax.
Key Features
- Astro-based static output —
pnpm buildemits a static site intodist/plus a Pagefind search index, so any static host can serve it. - Single YAML config — site name, author, URL, SNS links, analytics, and Markdown extension on/off switches all live in
config/site.yaml; changes require a dev-server restart or rebuild. - Markdown frontmatter controls —
linksets the URL slug (file name otherwise),updatedshows a revision date in the header and feeds JSON-LD,subtitlerenders a secondary title,stickypins a post to the top of the list,drafthides it from production builds, andkeywordsfeed SEO metadata. - Japanese-blog layout — a three-column classic design with light and dark themes.
- Built-in site search — Pagefind indexing is generated as part of the build step.
- Structured data — update dates propagate to JSON-LD alongside the visible article header.
- Sample content included — example posts ship inside
src/content/blog/for syntax reference. - Desktop-focused performance tuning — the author reports aiming for all-green PageSpeed Insights scores on desktop.
Who is it for?
- Japanese-language bloggers: writers who want a traditional three-column reading layout and per-post categories and tags without writing layout code.
- Developers who prefer Markdown: anyone who wants to add a post by dropping a Markdown file with frontmatter into
src/content/blog/and rebuilding. - Static-hosting users: people deploying to GitHub Pages, Netlify, or any host that serves a
dist/folder, with no server runtime needed. - Astro learners: developers who want a small, MIT-licensed Astro codebase they can read and adapt.
What can you do with blog-hishaku?
- Publish a personal blog: write Markdown posts with title, date, description, tags, and categories, then pin announcements with
stickyand keep unfinished drafts out of production withdraft. - Configure a whole site in one file: set the site name, author, URL, SNS links, and analytics in
config/site.yamlinstead of editing components. - Ship SEO metadata: use
descriptionfor meta descriptions and list excerpts, andkeywordsplusupdatedfor search metadata and JSON-LD.
How does blog-hishaku work?
Clone the repository, run pnpm install, then pnpm dev to preview at http://localhost:4321. The stated requirements are Node.js 22.12.0 or newer and pnpm 12.10.1 per package.json. Edit config/site.yaml, add Markdown files under src/content/blog/, and run pnpm build to produce dist/ for deployment, or pnpm preview to check the built output.
FAQ
Is blog-hishaku free to use?
Yes. The repository ships under the MIT license, so you can use, modify, and redistribute it, including commercially, as long as you keep the license terms.
What are the system requirements for blog-hishaku?
The project's package.json lists Node.js 22.12.0 or newer and pnpm 12.10.1. You install dependencies with pnpm install and preview the site locally at http://localhost:4321.
Does blog-hishaku include search?
Yes. The build step generates a Pagefind index alongside the static files in dist/, so search works on the deployed static site without a separate search service.
Can I hide a post from the live site?
Yes. Setting draft in a post's frontmatter keeps it out of production builds while leaving it available during development.















