EPIC: Gemify the theme #31
Labels
CSS/Sass
Involves hacking some styles
documentation
Improvements or additions to documentation
Jekyll
Involves working heavily with or extending Jekyll SSG
Ruby
Involves some Ruby troubleshooting/coding
Milestone
I was going to put this off to just before 1.0, but that was before I realized all the advantages of packaging this project as a Ruby Gem.
I'm not sure all of these steps are required, but they constitute the best practice.
images/
,js/
, andcss/
toassets/
path #28)Once those are complete, we can add a gemspec and make a few other changes, and document the whole thing in the Readme. In fact:
The big question here is how to handle the AsciiDocsy docs themselves. Do we add them to the gem or do we just keep them in the project for testing and for building the main site? I need to look at how others handle this.
This epic will be disruptive, so I'm going to do it after 0.1.1, maybe as part of 0.2.0, but definitely by 0.3.0.
The text was updated successfully, but these errors were encountered: