I've switched us from using `file-loader` to `url-loader`. This will automatically convert local URL
imports to data URIs, which means the framework no longer needs to load them from a remote URL.
#207
* refactor: add components directory
ref #166
* build: split nes.scss into nes.css and nes-core.css
and change npm scripts for build
ref #166
* docs(readme.md): add nes-core.css link
* docs: add components directory path
and minor modification of the document
* feat(storybook): Add backgrounds Storybook
I've added the Storybook backgrounds addon which allows users viewing the storybook to change the
background behind components, which will make it easier to see how the main NES.css theme looks in
various contexts.
* feat(storybook): Add backgrounds Storybook
I've added the Storybook backgrounds addon which allows users viewing the storybook to change the
background behind components, which will make it easier to see how the main NES.css theme looks in
various contexts.
I've add a script to handle automatically updating bot the CSS and SCSS headers with the relevant
information before publishing. This update is handled as part of `semantic-release`'s preparation
step.
I've added hot reloading to Storybook. This means that during development, all we have to do is run
Storybook. As we make changes to the SCSS files, the changes will automatically be reflected in
Storybook. 😁
This removes `semantic-commitlint` from both the local build pipeline and the CI build pipeline. The
original value of `semantic-commitlint` was that it would handle linting only the relevant commits,
i.e. the commit range under review for a PR. However, the library doesn't seem to respect our
altered `commitlint` rules, so we'll be switching to an alternate strategy to handle linting of
specific ranges.
#13
Forcing contributors to use Commitizen to format their commit messages will make our lives much
simpler, especially once we've added `semantic-release`.
