The build system within the upstream v4.6.0 release of Twitter Bootstrap dropped the Jekyll static site builder and adopted Hugo instead (using Go rather than Ruby, so also dropping all the support for Ruby). Arizona Bootstrap needs to follow this change to remain synchronized with the upstream versions, but users of Arizona Bootstrap (including Quickstart) should be unaffected by the change.
Is your feature request related to a problem? Please describe.
Dependabot keeps complaining about obsolete dependencies in Arizona Bootstrap, but it is now difficult to see which updates are compatible with Bootstrap, and which need ignored to pin to a known working version.
Proposed Resolution
Describe the solution you'd like
Reconstruct the Arizona Bootstrap build system to use Hugo.
Describe alternatives you've considered
Continuing with Jekyll is possible, but involves more maintenance work going forward, and without the guidance of the maintained Twitter Bootstrap releases.
Motivation
The build system within the upstream v4.6.0 release of Twitter Bootstrap dropped the Jekyll static site builder and adopted Hugo instead (using Go rather than Ruby, so also dropping all the support for Ruby). Arizona Bootstrap needs to follow this change to remain synchronized with the upstream versions, but users of Arizona Bootstrap (including Quickstart) should be unaffected by the change.
Is your feature request related to a problem? Please describe.
Dependabot keeps complaining about obsolete dependencies in Arizona Bootstrap, but it is now difficult to see which updates are compatible with Bootstrap, and which need ignored to pin to a known working version.
Proposed Resolution
Describe the solution you'd like
Reconstruct the Arizona Bootstrap build system to use Hugo.
Describe alternatives you've considered
Continuing with Jekyll is possible, but involves more maintenance work going forward, and without the guidance of the maintained Twitter Bootstrap releases.