JekyllBlog

onepage — Jekyll Blog Template

By lukas-h

onepage is a Jekyll-based single-page blog theme by lukas-h, released under the MIT license, with site information and post directory configured through _config.yml.

Explore the design

Compare the page layouts and mobile experience. Open any screenshot for a closer look.

2 previews
Desktop homepage1 / 2
Desktop captureTop of page

Actual screenshot captured by the server browser.

All pages & views 2

Screenshots show visual appearance; interactive behavior may differ.

Recorded 2026-10-02View source

What stands out

A quick read of the recorded project description.

01

Single-page layout Jekyll blog theme, with posts presented together on one page

02

Centralized configuration of title, description, URL, baseurl, social accounts, and accent color via _config.yml

03

README provides a four-step process: fork the repository, create a gh-pages branch, edit configuration, and write _posts

04

Supports entering a Google Analytics ID and HTML content language (default English)

05

MIT license, permitting use, modification, commercial use, and distribution of this version of the code

Template Details

onepage is a Jekyll theme positioned as an "uncomplicated single-page blog." It organizes blog content on a single page rather than the traditional multi-page list-and-detail structure. The repository provides an online demo (https://lukas-h.github.io/onepage/) and includes desktop and mobile screenshots.

The usage instructions in the README are specific: fork the repository and rename it, create a gh-pages branch, then edit _config.yml to fill in title, description, url with protocol, baseurl, GitHub and Twitter usernames (without the @ prefix), accent color, address and name email, Google Analytics ID, and the HTML content language isolang (default English). Posts go in the _posts directory, following Jekyll's post conventions.

The theme itself contains no backend or database; building and hosting rely on static hosting environments such as Jekyll and GitHub Pages. The repository was last updated in 2020 and provides no further feature documentation, so the actual usable scope is defined by the repository code and README.

JekyllBlog

Is it right for your project?

Use Cases

  • Building a personal single-page blog with GitHub Pages
  • Migrating existing Jekyll posts to a single-page presentation
  • Using as a sample project to learn Jekyll theme configuration and _posts writing

Suitable For

  • Individual bloggers familiar with or willing to learn basic Jekyll usage
  • Users hosting static sites with GitHub Pages
  • Those who need a simple single-page blog and do not require a complex multi-page structure

Getting started & customization

Use these recorded setup notes alongside the repository instructions for your chosen version.

  1. 1

    First fork the repository and rename it, then create a gh-pages branch

  2. 2

    Fill in title, description, url with protocol, and baseurl in _config.yml

  3. 3

    GitHub and Twitter usernames should not include the @ prefix; accent is the blog column color code

  4. 4

    Posts go in the _posts directory; refer to Jekyll post documentation for writing conventions

  5. 5

    Third-party assets such as demo images, fonts, and icons require separate license verification

Read repository instructions

License & source material

Usage conditions & limitations

Free to use · keep license notice

This entry covers the free version under the MIT license in the public repository; the free scope is this version of the code and does not imply that external services or third-party assets are free.

Must comply with when using

  • Permits free use, modification, commercial use, and distribution of this version of the code.
  • When distributing copies or substantial portions of the code, retain the original author's copyright notice and the full MIT license notice.
  • The code is provided as is; warranties and limitations of liability are governed by the original license and applicable law.

Additional costs & items to verify

  • Google Analytics is an optional external service: if enabled, you must provide your own GA tracking ID and are subject to Google's terms of service and privacy policy; not filling it in does not affect basic theme usage.
  • When configuring GitHub and Twitter usernames, the @ prefix must be removed, otherwise social links will point to incorrect addresses.
  • The url variable must include the http or https protocol prefix, otherwise site links and resource paths may fail.
  • When deployed in a subpath, baseurl must be set correctly (e.g., "/onepage"), otherwise page styles and links will 404.
  • Following the README process, a gh-pages branch must be created for GitHub Pages publishing; this is a deployment prerequisite for using the theme.
  • Demo images, fonts, icons, and other third-party assets must be checked against their respective licenses and cannot be judged solely by the code's MIT license.
  • External services such as domains, hosting, databases, payments, or AI may incur additional charges.
View Original Text Basis

Permission is hereby granted, free of charge

Original License Text

3.7. you are using google analytics? paste your ID to `g_analytics: ""`

Original README

3.4. paste **github** and **twitter** username to the following variables. Important: **without** @ prefix

Original README

3.2. give your site's url with protocol (http or https) to the variable `url`

Original README

3.3. the part after your page domain, for example you have `http://lukas-h.github.io/onepage`, `baseurl: "/onepage"` is the right value

Original README

#### 2. create a branch called `gh-pages`

Original README
https://github.com/lukas-h/onepage/blob/master/LICENSEhttps://github.com/lukas-h/onepage/blob/master/README.md

Compiled by DeepSeek based on repository license and README ·2026-10-02. Results only cover the materials read; dependencies, images, fonts, and subsequent term changes are subject to their respective original texts.

Project checks & description sources

Template Information

Source platforms
GitHub
Documentation and maintenance reference score
Partly documented · 72 / 100
Technologies
Jekyll
Website type
Blog
How this score is calculated

Our heuristic uses license records (up to 30), a demo link (12), a preview (10), stars (15), recorded maintenance (15), description completeness (8), feature records (5) and classification data (5). It is not a code, security or performance test, or a Google score. A link does not establish tested functionality.

What to verify for this project

Repository update recorded
2020-05-09
Screenshot last checked
2026-10-02

A demo link is listed. Check it with your own content and viewport sizes; its presence does not confirm that forms, authentication or payments work.

The catalog identifies Jekyll as the primary stack. Check the actual dependency manifest and lockfile for versions and hosting requirements. These notes use recorded metadata, not a code audit or a deployment test.

Use a selection guide →

How this description was prepared

AI-assisted description based on catalog records and repository material. Repository authors are not automatically the reviewers of this description.

Automatically checked against source and license rules; no manual editorial review.

Inspect the recorded source material

SHA-256: 44139e8a2090a6f3e482d7b6e23d9df198c8afd67cc3e792fa42040747ccb64d

2026-10-02T10:47:46.826Z

Source file / repository
# onepage
uncomplicated single-page jekyll blog theme

## find a demo here [HERE](https://lukas-h.github.io/onepage/)

## use it in 4 easy steps

#### 1. fork this repository and rename it

#### 2. create a branch called `gh-pages`

#### 3. edit the `_config.yml` file  

3.1. paste your `title` and `description`  

3.2. give your site's url with protocol (http or https) to the variable `url`  

3.3. the part after your page domain, for example you have `http://lukas-h.github.io/onepage`, `baseurl: "/onepage"` is the right value

3.4. paste **github** and **twitter** username to the following variables. Important: **without** @ prefix  

3.5. `accent` is the color code for the blog column

3.6. edit address and name, email too.

3.7. you are using google analytics? paste your ID to `g_analytics: ""`

3.8. edit html content language here: `isolang: en`, default is english

#### 4. start writing posts

4.1 posts are in the directory `_posts`  

4.2 see here an introduction: http://jekyllrb.com/docs/posts/  

# thank you
share this project, give a star, contributions welcome  
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
Report a correction

Explore similar templates

Compare previews and descriptions within the same stack and category.