DOCS: improve current documentation

[vitorgouveia]

• [x] development environment:

  • [x] what set of tools to use
    • [x] node version
      • [x] yarn or npm
        • [x] explain yarn workspaces
        • [x] explain yarn berry
        • [x] yarn version
      • [x] which code editor to use
        • [x] IDE/Code Editor plugins

• [x] git workflow

  • [x] show step-by-step how our git workflow works
    • [x] explain husky, lint-staged, commit script
  • [x] how we deal with branches
  • [x] releases
  • [x] QA (testing)
  • [x] how is a new contributor supposed to add features/bug fixes
  • [ ] what set of tools to use, version of node, yarn or npm

• [x] architecture

  • [x] what is microfrontends
    • [x] explain all the projects and it's purposes
  • [x] show all the used technologies/dependencies
  • [x] tests
    • [ ] test driven development
  • [ ] code style, eslint, prettier & stylelint
  • [x] accessibility
  • [x] figma file
    • [x] how figma is structured
    • [x] difference between style-guide, design system and ui kit
  • [x] notion file
    • [x] sprints and etc

• [x] contributors

  • [ ] discord
  • [ ] github

[vitorgouveia]

• [x] repository social preview
• [ ] readme "hero" image (from figma)

[vitorgouveia]

• [ ] explain design process from style guide to design system and finally to ui kits

[vitorgouveia]

• [ ] Roadmap
  • [ ] Plugins marketplace
  • [ ] Add own icon and color packages

[vitorgouveia]

• [ ] tools
• [ ] challenges
• [ ] why
• [ ] demo