This is not something new for repositories since they had this ability for a long time, and GitHub allows this kind of use of images for interactive badges. *At the time of writing this, Beautiful Jekyll is the second-highest starred Jekyll theme on GitHub and the second-most forked repository.Cache-Control: max-age=0, no-cache, no-store, must-revalidate For an example of a GitHub website that uses the remote_theme feature, you can see the repository that serves the demo site. Using these new methods, you’ll be able to always keep up to date with the latest version of Beautiful Jekyll automatically. While forking the project is still the easiest way to use Beautiful Jekyll and is the recommended way for beginners, advanced users can now use the theme as a Ruby Gem if they want to install Jekyll on a private server, or use GitHub’s remote_theme feature. One of the big focuses of the recent updates was to allow for more ways to use Beautiful Jekyll. This works, and if you only want to sync your site to Beautiful Jekyll very rarely then it’s ok, but this is clearly not ideal. You could save all your blog posts and any custom pages you created, make a fresh fork of the current repository so that you’ll have the latest features, and then add back all your own content. One major limitation of this method is that if you fork the theme and then I add new features, there’s no easy way for you to sync your project with my updated version. Up until the recent updates, Beautiful Jekyll only had instructions for how to set up the site using the simple, yet least flexible, method of forking the GitHub repository. Over the years, as new features consistently got added to the theme, I often received questions from users asking me how can they incorporate the latest changes from the theme into their existing site. Alternatively, one-time donations are also greatly appreciated if you find this project useful. One of my biggest goals is to have a few people sponsor me to help this project flourish, so that I can focus more on projects that help the community instead of client work. On a related note, the countless of hours I spend on this project are done with no pay, often while sacrificing time that I would otherwise use to work for clients and therefore literally causing me to lose money. One of my goals with the next release is to transition from CSS to Sass which would require a major rewrite of a large portion of the code, but otherwise I don’t plan any more major changes for a while. There are always more features to add, and maintaining the current codebase is in itself a part time job.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |