Basic 8.x-2.x Roadmap [#2847769]

We have had 8.x-1.x out for about a year now -- thanks to all who have contributed! With the upcoming release of Bourbon 5 and Neat 2, I wanted to start a plan for a new 8.x-2.x branch. Neat will no longer have a dependancy on Bourbon. As this is a major version change, we will need to refactor much of Basic's code as well.

Action items

Update package.json to bring in Bourbon 5 and Neat 2 (Last time I checked, the new versions were not available as an option yet).
Bourbon 5 removes mixins that handle vendor prefixing. With this, we should add PostCSS to our Grunt package to handle vendor prefixing moving forward.
Will these updates be ported to the D7 branch?
...add more notes here as we discover what is required.

Items for review

Sass or Scss

While Basic supports the addition of both .sass and .scss files, we frequently get requests to switch Basic's core style sheets to .scss. Let open this up for discussion. With .scss being more common, will this be more welcoming to new Drupal themers?
See: https://www.drupal.org/node/1954488 & https://www.drupal.org/node/2846429

Starter kit for mobile and dropdown menus

There have been a couple request for having responsive and drop down menus in Basic. I believe other themes link Bootstrap and Omega come with this functionality already. Would this be a help addition to basic? I think we should continue to take the "starter-kit" approach keeping the styles simple.
See: https://www.drupal.org/node/2704147 & https://www.drupal.org/node/2798385

Grunt or Gulp

Basic currently uses Grunt. Again, requests have come up in the issue queue about Gulp. Thoughts here?

Doc Improvements

We have some opportunities for better docs in a variety of areas.

D7 & D8: Review install instructions for node/npm.
D7: How to install Sass Globbing
D8: Document why messages & tabs css is in a theme library
...add more notes here as we discover areas for improvement.

Let us know if you have other ideas...

Comments

Comment #1

29 January 2017 at 01:50

leahtard created an issue. See original summary.

Comment #2

leahtard CreditAttribution: leahtard at The Jibe commented 29 January 2017 at 03:10

Issue summary:

View changes

Comment #3

leahtard CreditAttribution: leahtard at The Jibe commented 30 January 2017 at 20:22

Issue summary:

View changes

Comment #4

joelpittet

English

Vancouver

CreditAttribution: joelpittet at The University of British Columbia commented 30 January 2017 at 20:25

+1 for SCSS, I prefer Gulp but would rather not support 2, so stay unless a groundswell or decent argument. Responsive menus are tough but probably worth it if you can find a common & simple pattern.

Comment #5

CatherineOmega CreditAttribution: CatherineOmega as a volunteer commented 31 January 2017 at 03:18

SCSS will definitely be more welcoming to newbies. And if certain Drupal shops REALLY want to use one or the other from the release version, they can just convert the whole directory. :)

Comment #6

calbasi

Catalan

Catalonia

CreditAttribution: calbasi at calbasi.net commented 1 February 2017 at 20:58

And what about subtheming, like Zen does... I mean, keep a parent theme, and create a custom subtheme, and, then, let bug fixes get production themes, adding them at parent/base theme... Maybe this is an old threat at Basic (I'm a newbie here)...

Comment #7

awasson CreditAttribution: awasson commented 1 February 2017 at 21:02

I prefer the way Basic does it. Run the Drush installer, fill in the blanks and it creates a new theme with all of your settings. No need for a parent. It makes for a very clean themeing environment.

Comment #8

joelpittet

English

Vancouver

CreditAttribution: joelpittet at The University of British Columbia commented 2 February 2017 at 19:32

Yeah those other themes are meant for sub theming, means we have a bit more freedom to make changes since people use this to copy and make it their own.

Comment #9

jerry CreditAttribution: jerry commented 19 February 2017 at 18:03

Another vote for SCSS here.

Comment #10

Ramonius CreditAttribution: Ramonius commented 5 May 2017 at 10:08

+1 for SCSS

Comment #11

hs@henrikstrindberg.se CreditAttribution: hs@henrikstrindberg.se commented 7 January 2018 at 10:07

After using Basic on three projects I would like to give you some feedback and thoughts.

First of all: I like Basic! (I have experience from Foundation and Bootstrap). Basic is fun and fast and very well structured!

Most important for version 2: the Neat 2 grid

Maybe no big need for a responsive menu since it is super easy to add the Responsive and off-canvas menu module to a project. It's also easy to style, it seems to use the css from the theme. So maybe an alternative to add a responsive menu to Basic is to add to the documentation a “how-to” add a responsive menu using this module.

Thanks!