docs: restore contribution guide

Author: tharropoulos

CONTRIBUTING.md

@@ -1,71 +1,68 @@
-# Contributing to DocSearch
+Hi (future) collaborator!
 
-Welcome to the contributing guide for DocSearch!
+<!-- START doctoc generated TOC please keep comment here to allow auto update -->
+<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
 
-If this guide does not contain what you are looking for and thus prevents you from contributing, don't hesitate to leave a message on the [Discord](https://discord.gg/bRTacwYrfX) or to [open an issue](https://github.com/algolia/docsearch/issues).
 
-## Reporting an issue
+- [Where to start?](#where-to-start)
+- [Development workflow](#development-workflow)
+  - [Requirements](#requirements)
+  - [Build](#build)
+  - [Serve](#serve)
+  - [Test](#test)
+  - [Docs](#docs)
+  - [Release](#release)
 
-Opening an issue is very effective way to contribute because many users might also be impacted. We'll make sure to fix it quickly if it's technically feasible and doesn't have important side effects for other users.
+<!-- END doctoc generated TOC please keep comment here to allow auto update -->
 
-Before reporting an issue, first check that there is not an already open issue for the same topic using the [issues page](https://github.com/algolia/docsearch/issues). Don't hesitate to thumb up an issue that corresponds to the problem you have.
+# Where to start?
 
-Another element that will help us go faster at solving the issue is to provide a reproducible test case. We recommend to [use this CodeSandbox template](https://codesandbox.io/s/github/algolia/docsearch/tree/main/examples/demo).
+Have a fix or a new feature? Search for corresponding issues first, then create a new one if needed.
 
-## Code contribution
+# Development workflow
 
-For any code contribution, you need to:
-
-- Fork and clone the project
-- Create a new branch for what you want to solve (fix/_issue-number_, feat/_name-of-the-feature_)
-- Make your changes
-- Open a pull request
-
-Then:
-
-- A team member will review the pull request
-- Automatic checks will be run
-
-When every check is green and a team member approves, your contribution is merged! 🚀
-
-## Commit conventions
-
-This project follows the [conventional changelog](https://conventionalcommits.org/) approach. This means that all commit messages should be formatted using the following scheme:
-
-```
-type(scope): description
-```
+## Requirements
 
-In most cases, we use the following types:
+To run this project, you will need:
 
-- `fix`: for any resolution of an issue (identified or not)
-- `feat`: for any new feature
-- `refactor`: for any code change that neither adds a feature nor fixes an issue
-- `docs`: for any documentation change or addition
-- `chore`: for anything that is not related to the library itself (doc, tooling)
+- Node.js >= v8.7.0, use nvm - [install
+  instructions][15]
+- Yarn 
 
-Even though the scope is optional, we try to fill it in as it helps us better understand the impact of a change.
+## Build
 
-Finally, if your work is based on an issue on GitHub, please add in the body of the commit message "fix #1234" if it solves the issue #1234 (read "[Closing issues using keywords](https://help.github.com/en/articles/closing-issues-using-keywords)").
+`yarn run build` will build all files in `./dist`. This includes regular and
+minified files for `<script>` inclusion, as well as classes for `import`ing.
 
-Some examples of valid commit messages (used as first lines):
+The command itself is split into `yarn run build:js` and `yarn run build:css` if
+you want to build a subset.
 
-> - fix(searchbox): add `type` input property
-> - chore(deps): update dependency rollup-plugin-babel to v3.0.7
-> - fix(modal): increase default height
-> - docs(contributing): reword release section
+## Serve
 
-## Requirements
+You can have all this files served on localhost, along with live-reload, with
+the `yarn run serve` command.
 
-To run this project, you will need:
+## Test
 
-- Node.js ≥ 18 – [nvm](https://github.com/nvm-sh/nvm#install-script) is recommended
-- [Yarn](https://yarnpkg.com)
+You can run all tests with `yarn run test`, and `yarn run test:watch` will run
+them with auto-reload.
 
 ## Release
 
-```sh
-yarn run release
-```
-
-It will create a pull request for the next release. When it's reviewed, approved and merged, then CircleCI will automatically publish it to npm.
+`npm run release` will guide you through the release process. Note that you have
+to use `npm` and not `yarn` for this one otherwise it won't deploy to npm.
+
+[1]: #where-to-start
+[2]: #development-workflow
+[3]: #requirements
+[4]: #launch
+[5]: #local-build
+[6]: #commit-message-guidelines
+[7]: #revert
+[8]: #type
+[9]: #scope
+[10]: #subject
+[11]: #body
+[12]: #footer
+[13]: #releasing
+[15]: https://github.com/creationix/nvm#install-script