Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Let's talk about the Resources page #3188

Closed
jordanthornquest opened this issue Dec 5, 2014 · 5 comments
Closed

Let's talk about the Resources page #3188

jordanthornquest opened this issue Dec 5, 2014 · 5 comments

Comments

@jordanthornquest
Copy link
Contributor

Hey, folks!

Foreword: this is a minor issue in the grand scheme of Jekyll's development and improvement, but being fairly inexperienced when it comes to refining Jekyll's backend and logic, I figured this was a good way that I and like-minded developers could help better Jekyll for users. I think Jekyll rocks, and I'd love to do my part in making it easier for people to wield the tool and approach it.

Jekyll has proven to be a powerful tool with a bit of a learning curve and, as a result, much of the discussion about Jekyll is centered around questions like, "How do I do (x) in Jekyll?" The whole process of working with static pages and Jekyll's template-to-site workflow enables a lot of functionality in a static site, but also opens up a lot of mystery, due to Jekyll's fairly un-opinionated design.

As a result, there are an abundance of articles, tips, and tricks about how to make Jekyll do what you want, written both independently by a developer who pioneered a solution themselves and by clever problem-solvers who respond to questions asked by Jekyll users via IRC, StackOverflow, or Jekyll's own help repo.

Here's what I want to bring to the table:

  • Is there a place or a need for the Resources page within Jekyll's documentation? Or does the ability to Google a solution prove its use limited?
  • Is there a better, more prominent place we could put it?
  • Should there be a more active curation and spread of useful articles, tips, and tricks that can be shared to those using Jekyll?

I consider this a worthy discussion because, after asking about Jekyll's resources page on Twitter, the response seemed to infer that the resources page had been left untouched for a while. And, after making a pull request of my own about adding an article, another user did the same thing a little while later with their own excellent article! In other words, there seems to be some interest about this topic.

Any other discussion points, questions, or ideas about the Resources page are also appreciated here.

@troyswanson
Copy link
Member

Hey @jordanthornquest! We're gonna talk about this tonight in our Jekyll Meetup tonight!

Feel free to join us if you'd like.

Ref #2358

@jordanthornquest
Copy link
Contributor Author

Here's the conversation from the aforementioned Jekyll Meetup.

@eduardoboucas
Copy link
Contributor

@jordanthornquest Thanks for mentioning my article.

Not sure if this is relevant here, but I've actually just published another article about Jekyll.

@budparr
Copy link

budparr commented Dec 7, 2014

I recently started a blog and list of resources on static site building. While it's not specific to Jekyll, there's a lot of stuff there on it since I'm an avid user, including a link to your recent post on Ajax, @eduardoboucas. I'll soon be adding some filtering to make it more organized. I welcome pull requests.

http://www.thenewdynamic.com/

@parkr
Copy link
Member

parkr commented Dec 13, 2015

Feel free to submit PR's to this page if you'd like. They should be:

  1. Generally relevant – all Jekyll users could benefit from this information
  2. Tested on the latest version

Ideally, they would also be vetted by other Jekyll users or core team members. Thanks!

@parkr parkr closed this as completed Dec 13, 2015
@jekyll jekyll locked and limited conversation to collaborators Feb 27, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants