2nd-Minima

2nd-Minima is a GitHub repository template for building a personal blog with Jekyll, derived from the official Minima theme and tailored for users new to front-end development.

What is 2nd-Minima?

2nd-Minima is an enhanced version of the Jekyll-theme-Minima, packaged as a GitHub template for creating static blogs deployed on GitHub Pages. It takes YAML configuration and Markdown posts as input and outputs a generated Jekyll site with about, archive, all-tags, and tag pages out of the box. The repository is maintained by Deep0Thinking and includes a README that doubles as a full setup manual.

Key Features

• GitHub template workflow — Click "Use this template" on the repository page to create a new repo with the same file structure.
• Pre-configured GitHub Actions — The included .github/workflows/jekyll.yml builds and deploys the site to Pages after every push to main.
• Beginner documentation — The README explains cloning, bundle install, jekyll serve, and deployment in plain steps.
• Customizable navigation — The header_pages field in _config.yml controls the order of archive, about, and all-tags in the top menu.
• Rich post formats — Posts can embed text, images, YouTube videos, external links, LaTeX math via MathJax, downloadable documents, and interactive animations; a How-to-post-posts guide is inside the _posts folder.
• giscus comments — The template ships with placeholder comment sections that you replace with embed code from giscus.app.
• Custom favicon — Drop a replacement favicon.ico into the /favicon/ folder (exact filename required) and the site uses it.
• 2nd-Minima Helper — A custom ChatGPT assistant is available to answer setup and customization questions about this template.

Who is it for?

• Beginner bloggers with no coding background — They can create a blog by following the README's guided setup, without writing front-end code.
• Jekyll users wanting an improved Minima — They get extra layouts, pages, and deployment config on top of the standard Minima theme.
• Researchers and students — They can publish posts containing LaTeX-formatted math equations using the built-in MathJax support.
• GitHub users — Anyone who wants a personal website at their-username.github.io can use the template's pre-set Pages workflow.

What can you do with 2nd-Minima?

• Personal bloggers: publish a blog with posts, tags, an archive, and an about page by editing Markdown files and pushing to GitHub.
• Academics: write posts with LaTeX equations and cite external resources; the MathJax support renders math without extra plugins.
• Researchers/portfolio owners: customize /about.md and /archive.md to create a concise personal profile with a list of projects or publications.

How does 2nd-Minima work?

First, click "Use this template" on GitHub to create a repository, then clone it locally. Run bundle install and bundle exec jekyll serve to preview the site; edit _config.yml, _posts, about.md, and archive.md; then push to main — the GitHub Actions workflow handles deployment to GitHub Pages automatically.

FAQ

Is 2nd-Minima free to use?

Yes, the repository is released under the MIT License, which permits personal and commercial use, modification, and redistribution.

Do I need to know front-end programming?

No, the template is designed for people unfamiliar with front-end programming. The README guides you through configuration and content edits using YAML and Markdown, and the 2nd-Minima Helper chatbot can answer setup questions.

How do I add comments to my blog posts?

2nd-Minima uses giscus.app for comments. Get the embed code from giscus.app, then replace the fake comments sections in /_layouts/post.html, /about.md, and /archive.md with that code.

How do I deploy my site?

After pushing changes to the main branch, the included GitHub Actions workflow builds the Jekyll site and publishes it to GitHub Pages. You may need to enable Pages under Settings → Pages; the README explains the steps and how to check the deployment status.

Can I change the favicon?

Yes, create a favicon.ico (e.g., with favicon.io) and replace the existing file in the /favicon/ folder. The file must be named exactly favicon.ico to work.