-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Demo minima on GitHub Pages #76
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! @benbalter, seem OK to you?
This would not allow the example site to showcase the current version of Minima, but would rely on the version included in GitHub Pages, is that correct? |
Correct. I'm fine with it essentially showing the released version, unless there's any objection. |
I'm 👎 on this primarily because:
|
@DirtyF Thanks for implementing this and sorry it took so long to review. In order to facilitate demos, local development, and legacy theme workflows (fork and edit), Jekyll themes were intended to be just Jekyll sites that had a Gemspec added. I really like the simplicity this PR allows for and how much it simplifies the local development experience. Anyone who knows how to edit a Jekyll site can now contribute to minima. Thank you! @jekyllbot: merge +dev. |
@benbalter Please add the preview link on the repo's index page |
@ashmaroli I guess like the rest of the themes:
|
@alxn I agree with your point. But I also liked how earlier I could make the distinction between a Jekyll Site and the Minima gem contents while developing... |
To add to my point above, say, I add a |
Merge pull request 76
fix #67
/cc @jekyll/minima