Boilerplate Next Goals

Here's our goals for the next version of Boilerplate (Milestone 2020).

Mindset

First up is a mindset change - previous versions of Boilerplate we generally aimed for the simplest possible implementation of a component. It minimized code, but also left out a lot of functionality and left nearly every component in Boilerplate incomplete.

For 2020, we're going to aim to provide minimal, complete implementations of components. This means more opinionated code, but means some components may not require additional work, and those that do act as a 'checklist' of what should be re-implemented.

For example, in Boilerplate 4, we had effectively a single button style. In Boilerplate Next, we're adding a set of visual styles and transitions. Nearly every site should have multiple button styles for visual hierarchy with transitions; if the ones included aren't to your liking, that's fine - but at least you have a set to start with and rework, rather than starting from scratch.

Specific Goals

• Update documentation (and where possible UI) to be more friendly to non-technical users like clients. Ideally, it'd feel like a deliverable when a site is completed.
• Update dependencies to current versions, including Laravel Mix, Sass, FontAwesome, Fractal, etc.
• Remove or update legacy, non-ABEM components.
• Swap out jQuery for Vue.
• Remake jQuery-based components we want to keep with Vue.
• Improve Fractal Theme so components feel more on par with Tailwind/Codyhouse. Consider a copy-to-clipboard button.
• Consider removing components that we might be better off always using a third party lib for (Mobile Menu, Carousel.)
• Identify gaps and create new components where needed