We have no travis build steps for this project

Is this required or replaced by a vanilla component?

If still required follow through the checklist below:

• Resolve all linting issues
• Rename and fix variable issues
• Remove and follow the same comment structure
• Update any markup requirements
• Move documentation from one page to vanilla docs theme .md file

Is this required or replaced by a vanilla component?

If still required follow through the checklist below:

• Resolve all linting issues
• Rename and fix variable issues
• Remove and follow the same comment structure
• Update any markup requirements
• Move documentation from one page to vanilla docs theme .md file

Is this required or replaced by a vanilla component?

If still required follow through the checklist below:

• Resolve all linting issues
• Rename and fix variable issues
• Remove and follow the same comment structure
• Update any markup requirements
• Move documentation from one page to vanilla docs theme .md file

Is this required or replaced by a vanilla component?

If still required follow through the checklist below:

• Resolve all linting issues
• Rename and fix variable issues
• Remove and follow the same comment structure
• Update any markup requirements
• Move documentation from one page to vanilla docs theme .md file

Create the new secondary navigation - designs can be found here https://github.com/CanonicalLtd/MAAS-design/tree/master/Secondary%20navigation

Hey @richmccartney Tom has redesigned the MAAS logo so we need to update in the GUI.
I have linked to the relevant logo to certain sections of the GUI where it needs updating.

Navigation
https://www.dropbox.com/home/99%20-%20Design%20team%20shared/2.%20BRAND_DESIGN_BACK-UP/BRANDMARK_%26_LOGO_ARTWORK/20.%20MAAS_LOGO_AW/Files%20for%20web/SVG?preview=maas_white-orange_hex.svg

Favicon
https://www.dropbox.com/home/99%20-%20Design%20team%20shared/2.%20BRAND_DESIGN_BACK-UP/BRANDMARK_%26_LOGO_ARTWORK/20.%20MAAS_LOGO_AW/Files%20for%20web/SVG?preview=maas_black-orange_hex.svg

As mentioned in canonical/vanilla-framework#470.

We will no longer be going off finding vanilla-framework from parent directories. Instead we will expect vanilla-framework to be available in SASS's include-path setting.

This should then be published as a minor (or major) version change to this theme, as it will require project to update how they locally run SASS to use the correct include-path before it will work.

Required changes

@import '../node_modules/vanilla-framework/scss/vanilla';

Needs to be changed to:

@import 'vanilla-framework/scss/vanilla';

Visual reference below of updated icon in accordion, changing from arrow up/down to plus/minus pattern (17/02):

Vanilla framework is lacking example for notifications.

https://github.com/CanonicalLtd/MAAS-design/tree/master/Notifications/Flat_Visuals/

With the new way we have created setting files in vanilla framework, the theme will need to follow the same format. Split out any settings into their own respective files.

Convert the project to dashboard and set as v0.1 for any project that might require it (MAAS 2.1 for example)

It would be nice if the footer of the demo included a "file a bug" link

Is this required or replaced by a vanilla component?

If still required follow through the checklist below:

• Resolve all linting issues
• Rename and fix variable issues
• Remove and follow the same comment structure
• Update any markup requirements
• Move documentation from one page to vanilla docs theme .md file

The example page lists the following icons however these icons are not shown on the example page nor are they usable in MAAS.

<i class="icon icon--status-failed">..</i>
<i class="icon icon--status-in-progress">..</i>
<i class="icon icon--status-queued">..</i>
<i class="icon icon--status-succeeded">..</i>
<i class="icon icon--status-waiting">..</i>

Currently the MAAS GUI theme isn't an npm package or using the same tools as per vanilla framework.

Tasks

• Setup Travis build process
• Create the theme to be a npm module
• Create release notes
• Update gulp build tools

Is this required or replaced by a vanilla component?

If still required follow through the checklist below:

• Resolve all linting issues
• Rename and fix variable issues
• Remove and follow the same comment structure
• Update any markup requirements
• Move documentation from one page to vanilla docs theme .md file

Require updating all file names to follow the same format as vanilla framework v1

Currently we have a few mixins which live in a bulk file. These mixins should either live in their own respective files or with in the files they primary effect.

Visual reference below of updated icon in Interfaces table, changing from 'plus' icon to 'add' icon used in Juju. Consistency of icon library use across Cloud products (17/02):

Is this required or replaced by a vanilla component?

If still required follow through the checklist below:

• Resolve all linting issues
• Rename and fix variable issues
• Remove and follow the same comment structure
• Update any markup requirements
• Move documentation from one page to vanilla docs theme .md file

Is this required or replaced by a vanilla component?

If still required follow through the checklist below:

• Resolve all linting issues
• Rename and fix variable issues
• Remove and follow the same comment structure
• Update any markup requirements
• Move documentation from one page to vanilla docs theme .md file

Is this required or replaced by a vanilla component?

If still required follow through the checklist below:

• Resolve all linting issues
• Rename and fix variable issues
• Remove and follow the same comment structure
• Update any markup requirements
• Move documentation from one page to vanilla docs theme .md file

Is this required or replaced by a vanilla component?

If still required follow through the checklist below:

• Resolve all linting issues
• Rename and fix variable issues
• Remove and follow the same comment structure
• Update any markup requirements
• Move documentation from one page to vanilla docs theme .md file

Is this required or replaced by a vanilla component?

If still required follow through the checklist below:

• Resolve all linting issues
• Rename and fix variable issues
• Remove and follow the same comment structure
• Update any markup requirements
• Move documentation from one page to vanilla docs theme .md file

In component tables it currently holds the base and component level styles for interactive tables. This should be split out completely so normal table styles live under a base level file.

Is this required or replaced by a vanilla component?

If still required follow through the checklist below:

• Resolve all linting issues
• Rename and fix variable issues
• Remove and follow the same comment structure
• Update any markup requirements
• Move documentation from one page to vanilla docs theme .md file

Is this required or replaced by a vanilla component?

If still required follow through the checklist below:

• Resolve all linting issues
• Rename and fix variable issues
• Remove and follow the same comment structure
• Update any markup requirements
• Move documentation from one page to vanilla docs theme .md file

Is this required or replaced by a vanilla component?

If still required follow through the checklist below:

• Resolve all linting issues
• Rename and fix variable issues
• Remove and follow the same comment structure
• Update any markup requirements
• Move documentation from one page to vanilla docs theme .md file

Create the new meter and progress pattern - designs can be found here. https://github.com/CanonicalLtd/MAAS-design/issues/84

Speak to @kwm14 to get the up to date version

Is this required or replaced by a vanilla component?

If still required follow through the checklist below:

• Resolve all linting issues
• Rename and fix variable issues
• Remove and follow the same comment structure
• Update any markup requirements
• Move documentation from one page to vanilla docs theme .md file

On the new docs page our inline code example is in red, change this to be the new Ubuntu orange colour so its consistent and on brand

Is this required or replaced by a vanilla component?

If still required follow through the checklist below:

• Resolve all linting issues
• Rename and fix variable issues
• Remove and follow the same comment structure
• Update any markup requirements
• Move documentation from one page to vanilla docs theme .md file

Currently npm doesn't pull in assets (fonts, images) as a part of the package. Look into adding an npm module which will manage this and publish any files required

Move the repo from the Ubuntu designers org to MAAS.

• Rename repo
• Update all documentation on all three demo pages and README.md
• Move the repo to the MAAS organisation
• Setup travis CI with the organisation #39
• Republish NPM

Is this required or replaced by a vanilla component?

If still required follow through the checklist below:

• Resolve all linting issues
• Rename and fix variable issues
• Remove and follow the same comment structure
• Update any markup requirements
• Move documentation from one page to vanilla docs theme .md file

Create the option in the framework to add offline or online assets as the use case for the framework will require this

Is this required or replaced by a vanilla component?

If still required follow through the checklist below:

• Resolve all linting issues
• Rename and fix variable issues
• Remove and follow the same comment structure
• Update any markup requirements
• Move documentation from one page to vanilla docs theme .md file

Is this required or replaced by a vanilla component?

If still required follow through the checklist below:

• Resolve all linting issues
• Rename and fix variable issues
• Remove and follow the same comment structure
• Update any markup requirements
• Move documentation from one page to vanilla docs theme .md file

Requires white labelling the project and removing its link to MAAS. Update the project to use Vanilla framework as its only dependancy.

Is this required or replaced by a vanilla component?

If still required follow through the checklist below:

• Resolve all linting issues
• Rename and fix variable issues
• Remove and follow the same comment structure
• Update any markup requirements
• Move documentation from one page to vanilla docs theme .md file

Is this required or replaced by a vanilla component?

If still required follow through the checklist below:

• Resolve all linting issues
• Rename and fix variable issues
• Remove and follow the same comment structure
• Update any markup requirements
• Move documentation from one page to vanilla docs theme .md file

Is this required or replaced by a vanilla component?

If still required follow through the checklist below:

• Resolve all linting issues
• Rename and fix variable issues
• Remove and follow the same comment structure
• Update any markup requirements
• Move documentation from one page to vanilla docs theme .md file

Is this required or replaced by a vanilla component?

If still required follow through the checklist below:

• Resolve all linting issues
• Rename and fix variable issues
• Remove and follow the same comment structure
• Update any markup requirements
• Move documentation from one page to vanilla docs theme .md file

Is this required or replaced by a vanilla component?

If still required follow through the checklist below:

• Resolve all linting issues
• Rename and fix variable issues
• Remove and follow the same comment structure
• Update any markup requirements
• Move documentation from one page to vanilla docs theme .md file

Create the new notifications pattern - designs can be found here https://github.com/CanonicalLtd/MAAS-design/tree/master/Notifications
https://github.com/CanonicalLtd/MAAS-design/tree/master/Notification%20signal

Is this required or replaced by a vanilla component?

If still required follow through the checklist below:

• Resolve all linting issues
• Rename and fix variable issues
• Remove and follow the same comment structure
• Update any markup requirements
• Move documentation from one page to vanilla docs theme .md file

Is this required or replaced by a vanilla component?

If still required follow through the checklist below:

• Resolve all linting issues
• Rename and fix variable issues
• Remove and follow the same comment structure
• Update any markup requirements
• Move documentation from one page to vanilla docs theme .md file

Is this required or replaced by a vanilla component?

If still required follow through the checklist below:

• Resolve all linting issues
• Rename and fix variable issues
• Remove and follow the same comment structure
• Update any markup requirements
• Move documentation from one page to vanilla docs theme .md file

@richmccartney Could we update please, reason for change of colour is accessibility.

The contrast ratio against our default background of #f7f7f7 supports and passes AA web standards.