Newsletter
Join the Community
Subscribe to our newsletter for the latest news and updates
A Jekyll theme-template-boilerplate for launching a free personal website or blog on GitHub Pages without local setup.
Forever Jekyll is a Jekyll theme-template-boilerplate that lets you launch a free personal website or blog on GitHub Pages using only a browser, with no local Ruby, HTML, CSS, or JavaScript setup.
Forever Jekyll is a Jekyll-based theme and boilerplate designed to eliminate the upfront setup of a static site. It takes a GitHub account and a few minutes of browser editing to produce a fully featured personal website hosted at yourusername.github.io. The project targets non-programmers, so all configuration happens by editing _config.yml and writing Markdown posts directly in the GitHub web interface. It is maintained with community discussions and offered as a free public repository.
The theme builds on the Jekyll static site generator, meaning no database or server-side processing is needed. It includes a live demo at https://forever-jekyll.github.io, which showcases every post truncated with the more comment technique. Since Jekyll generates static HTML, the resulting site is fast and can be hosted for free on GitHub Pages, which is configured automatically by the repository name.
_config.yml, with no database or server-side dependencies.@import "cactus" step when enabling comments.Forever Jekyll is aimed at people who want a personal website or blog without learning web development. Non-technical users can fork the repository, rename it to their GitHub username, and edit files in the browser to publish content. Bloggers who write in Markdown benefit from the simple post workflow, while privacy-conscious site owners can enable Cactus Comments and GoatCounter instead of third-party trackers. It also suits Jekyll beginners who want a pre-configured theme rather than building a site from scratch.
_config.yml and Markdown files online — no local tools required.YEAR-MONTH-DAY-title.md filenames, and use the more comment to show excerpts on the homepage.Start by forking the repository on GitHub and renaming it to yourusername.github.io. GitHub Pages then builds and serves the site automatically. To customize, edit _config.yml (title, description, URL, footer links, timezone) and replace the avatar and favicons in the assets/image folder. For posts, add Markdown files to _posts following the required date-based filename convention and front matter. Optional features like comments and analytics require uploading layout files such as default.html and post.html into _layouts and registering with the respective services.
Forever Jekyll is free to use and hosted for free on GitHub Pages. The repository is public, and optional costs are limited to third-party services: GoatCounter is free for non-commercial use, while Cactus Comments is completely free and open source. The project accepts voluntary support via PayPal, Buy Me a Coffee, and Liberapay.
No. The whole point of Forever Jekyll is to work without a local environment. You edit files in the GitHub web interface, and GitHub Pages runs Jekyll for you in the cloud. The only requirements are a computer, a browser, and an internet connection.
Fork the repository and rename it to yourusername.github.io. Within a few seconds or minutes, the site appears at that URL. If it doesn't, open Settings > Pages and confirm the Source is set to Branch: main and root folder, then save.
Yes. Comments are handled by Cactus Comments, a privacy-friendly system on the Matrix protocol. Analytics can be added with GoatCounter (privacy-focused, free for non-commercial use) or Google Analytics. Both require editing layout files in _layouts and adding a tracking ID in _config.yml.
Posts in the _posts folder must follow the format YEAR-MONTH-DAY-title.md, for example 2012-09-12-how-to-write-a-blog.md. Each post must begin with front matter that sets layout and title, and you can optionally add categories for organization.
Insert the standard Jekyll excerpt-break comment on its own line at the point where you want the post truncated. The text before that comment appears on the homepage, while the full post remains accessible on its own page.
