Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Lowering the barrier to entry for Jekyll #1975
Hope this isn't off topic from how the conversation got started, but seems to me the biggest barrier to using Jekyll isn't for devs, it's for content creators.
I absolutely love working on text on my desktop and pushing it up to Github Pages—the real beauty of a SSG in terms of content—but that's pretty much out of the question for most site owners/production/creators. Prose.io is great, but not foolproof; there's no real error handling or working support for images. I even think the Github interface isn't that bad (with a bit of training), but there's no image handling there.
p.s. Love the collections idea!
referenced this issue
Jan 22, 2014
cc @mhulse for his previously articulated thoughts/further input.
@budparr VERY much agree re: learning curve for content creators. Would love to discuss that more, but perhaps in a new issue so we can keep this one focused on the barrier to entry on the dev side?
I've opened #1977 so we can discuss it more there.
@jglovier, thanks for the reminder!
I plan on collecting my thoughts and reading through the related issues this weekend. At the very minimum, I think I could contribute a few small changes to the docs as mentioned above.
With that said, let me bombard ya'll with some random ideas:
Not sure if any of the above is useful to anyone.
Either way, if I see something I could improve via the docs, I'll be back this weekend with a PR for review by the pros.
Just to jump in and clarify a few things: the Ruby CLI projects listed above were pertaining to another discussion and have no relevance in this one.
I support teaching users about advanced topics of bootstrapping Jekyll, but I don't think videos are necessary for that. Better installation guide (in writing) covering potential Gemfile usage and different approaches whether you're using GitHub Pages or latest Jekyll + plugins would be enough.
I wouldn't ever recommend hosting Jekyll sites on Heroku. It's an overkill for static sites. As a static host, I recommend https://getforge.com
My bad. My lack of experience with Ruby/the tools you mentioned is shining through.
Sorry to drag you into this convo.
Anyway, thanks for the clarification and the other thoughts/contributions!
That sounds like an excellent starting point to me. If you don't mind, I may cc you if I do a PR so I can get your feedback.
Ah, good to know! I've only used Heroku a couple times, and I do remember it being a bit of leg work to get the ball rolling (I was trying to host webfonts at the time).
Thanks for the host recommendation! is there a WIKI page around here that has a list of hosts? Like, S3, GetForge, and GitHub? I wonder if somehow the installation instructions could also tie-in notes on alternative hosting locations (other than GitHub, for example).
Looking forward to reading through that issue, and perhaps contributing, this coming weekend ... .
From that PR:
Though I did not mention in my last comment, that thought had crossed my mind as well. I really like that idea!
Just a FYI that I have a 40 minute intro on Jekyll on Youtube.
It's not high qual but a few folks have thanked me for it so I guess it has some value ;)
referenced this issue
Feb 4, 2014
One interesting observation of this discussion: no one has addressed why the barrier exists (or what it is!)
Some thoughts on the why:
Every project has to deal with this stuff. There's a barrier to entry for every software, ever. Identifying the hurdles is the first step to jumping over them.
Some thoughts on what could be done here:
Maybe I'm just spitballing here...but I'm seeing a lot of solutions offered without talking about the problems at hand first. Hopefully this draws more discussion out.
I just reread this thread and it seems like I missed the "mini-summit" mentioned in #1929. It would have been a bad time anyway with a one-month old newborn. The "vision" mentioned in that thread seems to clash with what I view Jekyll as. Perhaps my "vision" is outdated. That's ok though. Things change!
Maybe it's best if I just bow out and let the current captains continue to sail the ship, as they have been fantastic stewards so far. I need to concentrate my OSS time & energy anyway, and I'd rather do that on RubyGems.
Maybe we can organize a “Jekyll failathon” somewhere, not with the goal of finishing a product, but of learning how to fail the right way as a neophyte, and how to identify and solve those problem as a Jekyll pro?
It lowers expectations and hesitations on behalf of people curious to try out Jekyll, and it creates a good environment for asking for and providing help, which we in turn can use to identify the bottlenecks.