Newsletter
Join the Community
Subscribe to our newsletter for the latest news and updates
A modern static portfolio generator based on SvelteKit 2 and Tailwind CSS 4
microfolio is a modern static portfolio generator built with SvelteKit 2 and Tailwind CSS 4 by AKER, designed for creatives to showcase projects via a file-based CMS. It compiles folders of Markdown files and images into a fast static website that deploys to GitHub Pages or any static host.
microfolio is a static portfolio generator that takes a folder of Markdown files and images as input and produces a static website as output. It runs on SvelteKit 2 with the adapter-static, uses Tailwind CSS 4 for styling, and is maintained by AKER under an MIT license. A live demo is available at https://aker-dev.github.io/microfolio/ and it supports English and French out of the box.
pnpm optimize-images command generates WebP thumbnails to speed up page loads.brew install aker-dev/tap/microfolio) and add projects as folders with Markdown descriptions.Install the CLI via Homebrew on macOS or clone the repository from GitHub, then run pnpm install and pnpm dev to start a local server. Content is organized in folders with Markdown files, and the build step (microfolio build or pnpm build) generates a static site that can be deployed to GitHub Pages by pushing to the main branch. Detailed guides cover installation, configuration, adding projects, and publishing.
microfolio is free and open source under the MIT License. The source code lives on GitHub and there is no paid tier or hosted version mentioned.
Yes. microfolio is released under the MIT License, so you can use, modify, and distribute it freely. The repository is public on GitHub.
No. microfolio uses a file-based CMS: all projects are stored as folders and Markdown files. This keeps setup simple and makes your content easy to version with Git.
You need Node.js LTS 20 or newer, the pnpm package manager, and Git. macOS users can also install microfolio via Homebrew with brew install aker-dev/tap/microfolio.
Yes. The build command produces a static site that works with GitHub Pages; the documentation includes a quick deploy guide that says to enable GitHub Pages in repository settings and push to the main branch.
