Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Fork and add a copy of Tom Johnson's Jekyll Documentation Theme

Open
#8 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
css, jekyll
Domain
documentation

Research direction

Start by reviewing the linked Tom Johnson Documentation theme and the liquidoc-cmf repository. Resolve whether this should be a maintained fork or a converter, then define how it will support AsciiDoc and LiquiDoc and whether it will remain an optional branch. Done means a working theme approach is selected and integrated for users.

Written by the indexing model from the issue text.

Description

enhancement Summer2019

It's time to make a version of the Documentation theme that works well with AsciiDoc and LiquiDoc.

One idea is to make a converter, which would rename directories, insert some files, but otherwise fall back on the prime version. But it's more likely the best idea to maintain a proper fork, as some modifications we would make sense to contribute back, even if the overhaul is pretty thorough. We may keep it as an optional branch of this repo, so users can choose a bare-bones LDCMF and code their own theme, or they can stay in sync with the latest boilerplate edition of this theme, and maybe later others as well.

Dominant language
CSS
Stars
9
Forks
2
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DocOps/liquidoc-cmf

All issues in DocOps/liquidoc-cmf

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.