Merge branch 'v2-dev' into color-variables

# Conflicts:
#	sass/components/_sidenav.scss

Author: bugy

.github/PULL_REQUEST_TEMPLATE.md

@@ -14,7 +14,7 @@
 ## Checklist:
 <!-- Go over all the following points, and put an `x` in all the boxes that apply. If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
 
-- [ ] I have read the **[CONTRIBUTING document](https://github.com/materializecss/materialize/blob/master/CONTRIBUTING.md)**.
+- [ ] I have read the **[CONTRIBUTING document](https://github.com/materializecss/materialize/blob/main/CONTRIBUTING.md)**.
 - [ ] My change requires a change to the documentation.
 - [ ] I have updated the documentation accordingly.
 - [ ] I have added tests to cover my changes.

.github/workflows/docs.yml

@@ -2,7 +2,7 @@ name: Docs
 on:
   push:
     branches:
-      - v1-dev
+      - main
 
 jobs:
     docs:

CHANGELOG.md

@@ -1,5 +1,5 @@
 # Changelog
-All notable changes to this project will be documented in this file. For changes made before this fork, please refer to [HISTORY.md](https://github.com/materializecss/materialize/blob/v1-dev/HISTORY.md).
+All notable changes to this project will be documented in this file. For changes made before this fork, please refer to [HISTORY.md](https://github.com/materializecss/materialize/blob/main/HISTORY.md).
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
@@ -8,7 +8,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Added
 
-- Nightly builds of the latest code available through github actions ([Easy link for the latest build](https://nightly.link/materializecss/materialize/workflows/nightly/v1-dev/build)) ([58d18003](https://github.com/materializecss/materialize/commit/58d180036374f2b38a244e5e96c33838ce185220))
+- Nightly builds of the latest code available through github actions ([Easy link for the latest build](https://nightly.link/materializecss/materialize/workflows/nightly/main/build)) ([58d18003](https://github.com/materializecss/materialize/commit/58d180036374f2b38a244e5e96c33838ce185220))
 - Added support for text input suffix icons ([3e516e5b](https://github.com/materializecss/materialize/commit/3e516e5b322e4f8c7299cc37504389d0ddbb1ed6))
 - Added dragTargetWidth option ([6f4b2a15](https://github.com/materializecss/materialize/commit/6f4b2a15fc9f21a91ce95a1baffe60cfb15619df))
 - Added ability to change tooltip animate opacity ([8fce193f](https://github.com/materializecss/materialize/commit/8fce193fa94fe6d5a04630e732623c84fc803c3d))
@@ -43,7 +43,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Fixed XSS vulnerabilities ([3aae4cc9](https://github.com/materializecss/materialize/commit/3aae4cc9bb2b58c337bf25d2f04f129a2a0fa78f))
 
 #### Many other small changes have been made:
-https://github.com/Dogfalo/materialize/compare/v1-dev...materializecss:v1-dev
+https://github.com/Dogfalo/materialize/compare/v1-dev...materializecss:1.1.0-alpha
 
 #### Contributors
 Many thanks to all the contributors that made this release possible.

CONTRIBUTING.md

@@ -1,21 +1,26 @@
-Contributing
-------------
+# Contributing
 
 Looking to contribute something to Materialize? **Here's how you can help.**
 
-### Table of contents:
+## Table of contents:
+- [Table of contents:](#table-of-contents)
 - [Introduction](#introduction)
-- [Communication channels](#communication-channels)
+  - [Communication channels](#communication-channels)
 - [Using the issue tracker](#using-the-issue-tracker)
   - [Issues and labels](#issues-and-labels)
   - [Bug reports](#bug-reports)
+    - [Guidelines for bug reports:](#guidelines-for-bug-reports)
   - [Feature Requests](#feature-requests)
   - [Code Examples](#code-examples)
 - [Pull Requests](#pull-requests)
   - [Documentation](#documentation)
   - [Submitting Your Pull Request](#submitting-your-pull-request)
 - [Translations](#translations)
-- [Jasmine Testing Guide](#jasmine-testing-guide)
+- [Jasmine Testing Guide:](#jasmine-testing-guide)
+  - [Starting Out](#starting-out)
+  - [Writing Tests](#writing-tests)
+  - [Useful Jasmine Tips](#useful-jasmine-tips)
+- [License](#license)
 
 ## Introduction
 Please take a moment to review this document in order to make the contribution
@@ -31,8 +36,8 @@ patches and features.
 Before you now get lost in the repository, here are a few starting points for you to check out. You might find that others have had similar questions or that your question rather belongs in one place than another.
 
 * Chat: https://gitter.im/materializecss/materialize
-* Website: http://materializecss.com
-* Twitter: https://twitter.com/materializecss
+* Website: https://materializecss.github.io/materialize
+* Github discussions: https://github.com/materializecss/materialize/discussions
 
 ## Using the issue tracker
 
@@ -56,12 +61,11 @@ Our bug tracker utilizes several labels to help organize and identify issues. He
 
 - `component:*` - Each component has been provided a label. Add the labels for any component the issue is triggered by.
 - `confirmed` - Issues that have been confirmed with a reduced test case and identify a bug in Materialize.
-- `css` - Issues stemming from our compiled CSS or source Sass files.
+- `css/sass` - Issues stemming from our compiled CSS or source Sass files.
 - `js` - Issues stemming from our compiled or source JavaScript files.
-- `docs` - Issues for improving or updating our documentation.
-- `help-wanted` - Issues we need or would love help from the community to resolve.
+- `documentation` - Issues for improving or updating our documentation.
+- `help wanted` - Issues we need or would love help from the community to resolve.
 - `meta` - Issues with the project itself or our GitHub repository.
-- `on-hold` Issues or pull that should be worked on, but for any reason it won't be worked on/accepted as a PR anytime soon.
 
 For a complete look at our labels, see the [project labels page](https://github.com/materializecss/materialize/labels).
 
@@ -75,7 +79,7 @@ Good bug reports are extremely helpful! Unclear issues with little explanations
 
 1. **Use the GitHub issue search** - check if the issue has already been reported.
 
-2. **Check if the issue has been fixed** - try to reproduce it using the latest `master` or development branch in the repository.
+2. **Check if the issue has been fixed** - try to reproduce it using the latest commited branch in the repository. The [`main`](https://github.com/materializecss/materialize/tree/main) branch is stable, other branches are used for development.
 
 3. **Isolate the problem** — create a [reduced test case](https://css-tricks.com/reduced-test-cases/) using **our** [Codepen template](#code-examples).
 
@@ -88,9 +92,9 @@ We like feature requests but make sure that it can be seen within the goals of t
 ### Code Examples
 
 - Issues without a [Codepen](#code-examples) (where applicable) will be closed or ignored.
-- Use this [Codepen](http://codepen.io/Dogfalo/pen/xbzPQV) to illustrate your problem.
+- Use this [Codepen](https://codepen.io/pen/?template=MRNObV) to illustrate your problem.
 
-## Pull requests
+## Pull Requests
 
 Good pull requests - patches, improvements, new features - are a fantastic help. Thanks for taking the time to contribute.
 
@@ -104,7 +108,7 @@ and/or [`/materialize/js/`](https://github.com/materializecss/materialize/tree/m
 ### Documentation
 
 When contributing to Materialize's documentation, you should edit the documentation source files in
-[the `/materialize/jade/page-contents/` directory of the `master` branch](https://github.com/materializecss/materialize/tree/master/jade).
+[the `/materialize/pug/page-contents/` directory of the `master` branch](https://github.com/materializecss/materialize/tree/master/pug).
 **Do not edit the `gh-pages` branch.** That branch is generated from the documentation source files and is managed separately by the Materialize maintainers.
 
 ### Submitting Your Pull Request
@@ -136,7 +140,7 @@ Adhering to the following process is the best way to get your work included in t
    git checkout -b <topic-branch-name>
    ```
 
-4. Commit your changes in logical chunks with messages written in english. Please adhere to these [git commit message guidelines](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html) or your code is unlikely be merged into the main project.
+4. Commit your changes in logical chunks with messages written in English. Please adhere to these [git commit message guidelines](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html) and use [conventional commit format](https://github.com/conventional-changelog/commitlint/#what-is-commitlint) in your commit messages (or use `npm run commit` to make your life easier). Failing to do this makes your commits unlikely to be merged into the main project.
 
 5. Locally merge (or rebase) the upstream development branch into your topic branch:
 
@@ -150,19 +154,18 @@ Adhering to the following process is the best way to get your work included in t
    git push origin <topic-branch-name>
    ```
 
-7. [Open a Pull Request](https://help.github.com/articles/using-pull-requests/) with a clear title and description against the `master` branch. Reference any open issue in the description so it is automatically linked. Try and keep your commit history clean and concise. Once you submit your pull request, [Travis CI](https://travis-ci.org/materializecss/materialize) will automatically run your tests and will show a checkmark to show that all the tests have passed. Once this is done, we’ll review your tests and code and make comments if there are issues or things we think could be improved. Then once everything looks good we’ll merge the code in!
+7. [Open a Pull Request](https://help.github.com/articles/using-pull-requests/) with a clear title and description against the current development branch, usually `vX.X.X-dev`. Reference any open issue in the description so it is automatically linked. Try and keep your commit history clean and concise. Once you submit your pull request, Github Actions will automatically run your tests and will show a checkmark to show that all the tests have passed. Once this is done, we’ll review your tests and code and make comments if there are issues or things we think could be improved. Then once everything looks good we’ll merge the code in!
 
 ## Translations
 
-If you want to help us translate the documentation into other languages, please send us an email at [email protected] telling us which language team you want to join. We use [Transifex](https://www.transifex.com) as our localization platform and we will send you an invite there.
+If you want to help us translate the documentation into other languages, you can visit the [translation discussion here](https://github.com/materializecss/materialize/discussions/182).
 
 ## Jasmine Testing Guide:
 
 **References:**
 - [Jasmine Documentation](http://jasmine.github.io/2.0/introduction.html)
 - [Grunt Jasmine Plugin](https://github.com/gruntjs/grunt-contrib-jasmine)
 - [Example Jasmine Tests](https://github.com/materializecss/materialize/tree/master/tests/spec)
-- [Travis CI](https://travis-ci.org/materializecss/materialize)
 
 After `npm install`, you can run `npm test` and it will run the tests. If you get any errors and have not made any changes, it means you have not installed the proper dependencies.