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.
GITHUB PAGES THEME HOW TO
Rewrote and greatly simplified the entire documentation to make it as simple and easy to understand.Added accessibility features, improved performance of the theme, updated jQuery to improve security.Made the theme available using remote_theme through GitHub Pages (or through a Ruby Jekyll site) for intermediate users.Made the theme available as a Ruby gem for advanced users.Migrated from Bootstrap 3 to Bootstrap 4.
GITHUB PAGES THEME FULL
I had myself a list of tasks I wanted to accomplish, and on top of that I took a good look at all the open bug reports and feature requests that people submitted and tackled almost all of them.įor a full list of new features and changes, see the CHANGELOG. What changed?įrom adding many small features, to completely re-working the documentation and the codebase, to migrating to Bootstrap 4, there was a lot to do. Yes, that’s right, it jumped 3 major versions! I was planning on just doing a v2, but I kept getting excited by more big changes and I couldn’t stop until I was fully satisfied. The past several months have been a very long journey with hundreds of hours (not an exaggeration) and some very (VERY) late nights, but I’m happy to announce that Beautiful Jekyll has graduated from v1 to v4. I found myself stuck at home and had some time to dedicate to many of my projects. From 2015-2019 I incrementally added new features to make the theme easier to use and more customizable, but I was always wary about making large-scale changes. Starting from day 1, the goal with Beautiful Jekyll has been to allow anyone–and I mean literally anyone regardless of coding skill–to create a simple, clean, customziable website within minutes.
0 kommentar(er)
