You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 30, 2024. It is now read-only.
You can add jekyll-bootstrap as a remote to your repository, fetch it, then compare it to your HEAD. This is better outlined here: #35
There are 4 main integration points between Jekyll-Bootstrap and Jekyll.
_config.yml
There are still some variables in use that are not namespaced into JB hash. But ideally we'll place every variable in JB and then find a clean way to merge the file without reorganizing the user data.
Rakefile
The Rakefile can be upgraded cleanly, provided we add this feature in: Loading custom rake file from _rake/*.rake #33 which allows users to extend the rakefile freely with their own tasks.
Themes
Themes should be namespaced and versioned independently from the JB core so with the exception of a major version release the theme API should not be affected at all when updating.
Are there any more areas I've missed? Ideally we need to fully automate this task. However it's better to not do anything than to risk overwriting user data. So I want to make sure to avoid any such possibility.
I would like to hear your thoughts on this, thanks!
There is no obvious way to upgrade Jekyll-Bootstrap versions.
The text was updated successfully, but these errors were encountered: