Closed mscharley closed 10 years ago
good idea. I've been working on one with bourbon.
Here's an initial attempt: https://github.com/jekyll/jekyll/wiki/Template-Websites
Check out @imathis's octopress-ink: it's a way of shipping your themes as gems and allowing seamless inheritance of various layout elements. https://github.com/octopress/ink
I was thinking of something a lot less complete than entire themes. More like starting points with various frameworks pre-installed as a jumping point for an actual theme. Does octopress-ink require octopress? From the gemspec it doesn't seem to. And for future readers, the correct link is https://github.com/octopress/ink
On 18 April 2014 00:26, Parker Moore notifications@github.com wrote:
Check out @imathis https://github.com/imathis's octopress-ink: it's a way of shipping your themes as gems and allowing seamless inheritance of various layout elements. https://github.com/octopress/octopress-ink
— Reply to this email directly or view it on GitHubhttps://github.com/jekyll/help/issues/20#issuecomment-40719596 .
It does not require Octopress at all! Octopress has turned into tooling around making Jekyll even easier to use, and less about providing default themes and such like it is now.
@mscharley I am working on one with Foundation.
I was thinking of something a lot less complete than entire themes.
I’m not sure where to stop. What do you expect from such minimal setup?
@penibelst I suppose that depends entirely on what you can get away with generically... have a look at my Foundation one: https://github.com/mscharley/template-jekyll-foundation5
@mscharley Haha, Foundation gets much love. Maybe we can work together? I switch the discussion to your repository.
What I love about Jekyll is that it doesn't include any junk. I'd hate to see a change like this.
It's also a question of maintenance, why incorporate what is essentially third-party code and create a maintenance burden in the process? Someone would have to ensure that there was parity between the upstream third-party code and the Jekyll version. It's creates dependencies that needn't exist.
I recently built a Jekyll site using Foundation 5 as a start-point and incorporating it was as easy as opening terminal, cd'ing to my project folder and typing bower install foundation --save
. Third-party dependencies should, in my opinion, always be ring-fenced and treated as external assets, not internalised.
@nternetinspired Noone's suggesting this would ever touch jekyll core in any form. My original concept was more along the line of 'themes' in other CMS's. And yes, you can install foundation that quickly and easily. But in my case, there's other things going on as well. Setting up jekyll-compass to work, adding RequireJS to support jQuery and Foundation, and a few other bits and pieces. Now I can just clone that repository, fork it and do whatever I need without having to worry about setting up all those dependencies for my new project. Maintenance of each theme would be provided (or not!) by the original creator of it. Since it's just a git repository of an actual site, there's no added burden to jekyll at all, and if you don't want to use any of them then that's your prerogative.
As an aside, I think that Octopress Ink is probably going to be the way to approach this in the future.
Gotcha. Sorry, too early in my day I totally misunderstood.
There's plenty such themes out there, I agree a centralised list of them would be cool. Maybe just start one and then send a pull request?
I did start one on the wiki, I'm not sure if people have added to it or not since then though.
On 9 May 2014 20:53, Seth Warburton notifications@github.com wrote:
Gotcha. Sorry, too early in my day I totally misunderstood.
There's plenty such themes out there, I agree a centralised list of them would be cool. Maybe just start one and then send a pull request?
— Reply to this email directly or view it on GitHubhttps://github.com/jekyll/jekyll-help/issues/20#issuecomment-42654213 .
I was thinking of adding to it, though I was thinking of doing one that includes a few items that I find helpful (config file stuff to, for instance, put in your google analytics id, or toggle production state), and to add some test content ala Wordpress unit tests. So, something that stands between a full-blown theme and the more skeleton-like starters you were suggesting, @mscharley.
@budparr Hey, I’m interested in doing the same, providing Bourbon and Neat. I’m actually having some problems trying to get Jekyll to load the SCSS files. I saw your repo at https://github.com/budparr/jekyll-starter — figured this is the one you’re working on? (:
Hi @klepas I don't think I've worked on that since 2.x came out. I think I'm going to abandon jekyll-starter in favor of jekyll-on-the-rocks, but that one too use the pages gem (i.e. 1.5.1). You can look at any of my client repos under my company name. The top two are things I'm working on currently so are 2.x (that said, they too are drafts and quite messy): https://github.com/sonnetmedia
I added JekyllKB to the Jekyll Template wiki page. Right now JekyllKB is just a starter site for Jekyll using Bootstrap and Font Awesome. The goal is to make it a starting point for your Jekyll powered Knowledge Base or documentation site. Contributions are welcome.
@parkr Is support for themes something that might appear in Jekyll 3.0? I seem to recall a conversation about including a "theme gem" in one's config file, but I'm not sure where that went.
Eventually, I think we'll go with @imathis's Octopress Ink project which is absolutely baller. We won't ever include it in Jekyll core (it would stay a plugin but be a runtime dependency), but I have concerns over it ever making it onto GitHub Pages (security, security, security).
So keep moving on this front – it's a sure-fire way to see "themes" like this on GHP. Octopress Ink will come later.
:boom:
Similar to https://github.com/jekyll/jekyll/wiki/Sites would it be useful to have a list of some skeleton setups with different frameworks? For instance, I've been working on a new site, and there's still nothing site-specific in the repo, uploading it to a repo as an example and skeleton setup for Jekyll + Compass + ZURB Foundation 5 could be useful to others.