jekyllrc / jekyllthemes

A directory of the best-looking themes for Jekyll blogs

Jekyll Themes

A directory of the best-looking themes for Jekyll blogs

Submitting a Theme

Have a theme you want to share?

• Fork the site on GitHub
• Create a new post in the _posts directory and fill out the relevant YAML fields
• Make a 750x600 thumbnail and drop it in the thumbnails directory. List its filename in the post's markdown file.
• Test it out with the command bundle exec jekyll serve --config _config-dev.yml
• When you're happy, push your changes up and open a pull request.

License

The contents of this repository are licensed under the GNU Public License.

jekyllthemes's Issues

config-dev.yml still uses rdiscount which causes an error on build

Following the instructions for this repo I ran:

bundle exec jekyll serve --config _config-dev.yml

But I got the following error on build

Dependency Error: Yikes! It looks like you don't have rdiscount or one of its dependencies installed. In order to use Jekyll as currently configured, you'll need to install this gem. The full error message from Ruby is: 'cannot load such file -- rdiscount' If you run into trouble, you can find helpful resources at https://jekyllrb.com/help/!
  Conversion error: Jekyll::Converters::Markdown encountered an error while converting '_posts/2011-01-27-jamesyu_jekyll_template.markdown':
                    rdiscount
             ERROR: YOUR SITE COULD NOT BE BUILT:
                    ------------------------------------
                    rdiscount

config-dev.yml needs to be updated from using markdown: rdiscount to markdown: kramdown

It looks like config.yml was already updated. So probably just need to update the dev file as well.

Rebase on Upstream?

Before Matt resurfaced it was easy to merge in PRs as this fork was ahead of the upstream repo that the PRs were based on. However now the PRs are based on a divergent history, so as far as I know, they have to be merged in manually. That is why currently the following PRs have not been merged:

#205
#208
#209

Would it be easiest to rebase this fork on the current mattvh repo? Or is there a better way to keep up to date?

@jekyllrc/core

Images are pixelated

In the old jekyllthemes website, images were 200x250. In this version, the size has been increased, but since the image files themselves are 200x250, they all look pixelated. I'm not sure what the solution should be, just raising the issue.

Perhaps the instructions on the new site should be updated to use the new dimensions rather than 200x250, so that any NEW submissions will at least benefit from that

Use kramdown instead of rdiscount

Since rdiscount will be deprecated at 2016-05-01 we should use kramdown instead.

Add Piwik analytics

@jekyllrc/themes since I'm not a fan of Google spyware products like Google Analytics then are You fine when I'll add this page to my Piwik set-up (https://www.kits.ee/analytics/) so I can get some analytics about the page?

The disadvantage is that I can't add You access to the analytics, but maybe I can produce monthly reports somehow (not sure at the moment, if there are built-in functions for that).

Randomize order of themes

This is an issue I've been wanting to open for jekyllthemes.org but it didn't make sense there because of pagination.

I think it's a little unfair for any themes that are not the last ones to be added that the order is chronological, because I assume most come to the site and look at the first few rows and the further down you scroll the more people you lose. Since all the themes are shown on one page, I think it'll be pretty easy to randomize the order of the themes on each page load. It could even be done with javascript.

I'm not sure if you guys agree with this idea or not, just my two cents.

Domain name proposition: themes.jekyllrc.org

Hei!

I have registered jekyllrc.org domain. What do You think about serving this repository from themes.jekyllrc.org?

Günter.

/cc @jekyllrc/themes

Demo pages

@mushishi78 Is the https://github.com/jekyll-demos project created by You? What would you think about an idea to create a repository called jekyllthemes-demos and link all those as submodules?

Pros:

• all in one repo;
• we can use existing teams workflow, therefore can give Themes team access to it;
• easier to update;
• we can serve those via demos.jekyllrc.org domain;
• one less organization to manage.

Cons:

• must manually build all pages (but can be fully automated using a simple unix makefile and Jenkins).

Theme Demos

I absolutely love the demos page! It's a great idea and well implemented.

A problem I'm having with it though it the scrolling gets a bit difficult. I need to scroll down the page to view the whole demo but as soon as my mouse enters the demo window it starts to scroll the demo instead.

My suggestion would be to redesign the page so that the demo is pretty much full screen but with a navbar at the top for Jekyll Themes and a drop down to select the theme. This could look pretty much as it does now except the current navbar could be made smaller, the margins around the demo could be reduced to zero and the theme selector could hide when a theme is selected and have a button on the navbar to show it again.

Thoughts?

Hi, Is this repo still maintained?

I just submitted a theme, Looks like after august 2021 no PR was merged. Is this repo still maintained?
Thank you.

Illegally formed thumbnails

Wrong aspect ratio (stretched in or outwards):

• Vanilla Bean Creme
• Green Tea
• Left
• Minimal Mistakes
• Kasper
• Simply Grey
• brume
• Bitwiser
• Clean Blog
• Freshman21
• Carte Noire
• Polar Bear
• Arctic Fox
• { Personal }
• Jekyll Material Design Lite
• Mickey
• Carte
• Book

Update { Personal } theme

Probably needs manual merge as described in this PR: mattvh#199