-
Notifications
You must be signed in to change notification settings - Fork 413
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
Rubygems #2
Comments
Hi @aytekinar, thanks for asking, we currently do not have plan for releasing on rubygems. If you are interested, let me know. |
Hey @junlulocky, Thank you for your prompt response. Actually, that would be lovely! I don't think it would cost you a lot of effort, nor time, as is outlined in the documentation. Of course, it might sound a bit rude for you to hear this from a user, but I would definitely want to use this theme and having a gem based theme is really nice. For instance, I will be using GitLab Pages for building my website, and I would not want to clutter my homepage with theme-related files. I would like to see only my posts and the corresponding Just a small (and maybe useful) idea. Thanks, again :) |
Hey @aytekinar, Thanks, I will take a look. but maybe only a couple of days later. Let me know if you also want to participate in this prj. Thanks:) |
Sure, no rush! :) Actually, I can also participate. According to the documentation, we need to clean some folders and maybe restructure some others. Then, we need to register in rubygems.org and publish the gem-based theme directly at rubygems. For that, a simple travis continuous integration with the rubygems password as a secret should be a solution. Then, whenever you make some changes here on GitHub, the continuous integration service could publish automatically on rubygems. Then, we as users simply get the most recent version. Thanks :) EDIT. This is a better link to follow. :) |
@aytekinar Best |
Thank you for the great theme!
I would like to ask one question: "Is there any plan on releasing this theme on rubygems?"
The text was updated successfully, but these errors were encountered: