Add tooling content

content/roadmaps/111-design-system/content/107-tooling/100-development/100-component-catalog.md

@@ -1 +1,3 @@
-# Component catalog
+# Component Catalog
+
+Isolate your UI components’ environment outside of your product codebase to make sure they’re not dependent on any global dependencies and can be easily reused.

content/roadmaps/111-design-system/content/107-tooling/100-development/101-documentation.md

@@ -1 +1,3 @@
-# Documentation
+# Documentation
+
+Having your code documented is key to driving adoption and reducing the load on the contributors.

content/roadmaps/111-design-system/content/107-tooling/100-development/102-code-style.md

@@ -1 +1,3 @@
-# Code style
+# Code Style
+
+Having a defined code style helps align the way code’s written in the system and increases development velocity. It should be automated with the tools provided for each platform.

content/roadmaps/111-design-system/content/107-tooling/100-development/103-unit-testing.md

@@ -1 +1,3 @@
-# Unit testing
+# Unit Testing
+
+Every part of the design system should be covered with unit tests. Once your system’s adopted, any change in the isolated environment may affect how the product works.

content/roadmaps/111-design-system/content/107-tooling/100-development/104-accessibility-testing.md

@@ -1 +1,3 @@
-# Accessibility testing
+# Accessibility Testing
+
+Design systems should cover accessibility as much as possible. Making this automatic reduces the risk of inaccessible components or user flows in the product.

content/roadmaps/111-design-system/content/107-tooling/100-development/105-semantic-versioning.md

@@ -1 +1,3 @@
-# Semantic versioning
+# Semantic Versioning
+
+Version your code with semantic versioning that dictates how version numbers are assigned and incremented.

content/roadmaps/111-design-system/content/107-tooling/100-development/106-release-strategy.md

@@ -1 +1,3 @@
-# Release strategy
+# Release Strategy
+
+Design system releases should be automated and ideally use scripts ran locally or in remote CI pipelines to prevent broken releases.

content/roadmaps/111-design-system/content/107-tooling/100-development/107-commit-guidelines.md

@@ -1 +1,3 @@
-# Commit guidelines
+# Commit Guidelines
+
+Automate the generation of your changelog by adopting a commit message guidelines that categorise and define the changes being made.

content/roadmaps/111-design-system/content/107-tooling/100-development/108-pr-templates.md

@@ -1 +1,3 @@
-# Pr templates
+# Pull Request Templates
+
+Create pull request templates that outline the change being proposed to facilitate productive discussions.

content/roadmaps/111-design-system/content/107-tooling/100-development/109-contribution-guidelines.md

@@ -1 +1,3 @@
-# Contribution guidelines
+# Contribution Guidelines
+
+Define the process of contributing to the code of the design system. Document everything in a discoverable place to make it easier for everyone to contribute.

content/roadmaps/111-design-system/content/107-tooling/100-development/readme.md

@@ -1 +1,3 @@
-# Development
+# Development
+
+One of the main challenges in developing a design system isn’t building the components. It’s making your code stable, easy to read and contribute to.

content/roadmaps/111-design-system/content/107-tooling/101-design/100-design-editor.md

@@ -1 +1,3 @@
-# Design editor
+# Design Editor
+
+There are many design editors available in the market today with the most popular names being Sketch, Figma and Adobe XD. If you're unsure which route to go down it's often best to speak with your team.

content/roadmaps/111-design-system/content/107-tooling/101-design/101-plugins.md

@@ -1 +1,3 @@
-# Plugins
+# Plugins
+
+Most popular Design Editors (Sketch and Figma, especially) come with third-party plugin support. Whilst it's best to use the editors in-built tools for laying out your components, plugins can bring in a range of useful data to populate them.

content/roadmaps/111-design-system/content/107-tooling/101-design/102-version-control.md

@@ -1 +1,3 @@
-# Version control
+# Version Control
+
+Having your design versioned with semantic versioning will allow you to easily align design with development, roll back faulty changes and release changes in code and design at the same time.

content/roadmaps/111-design-system/content/107-tooling/101-design/103-contribution-guidelines.md

@@ -1 +1,3 @@
-# Contribution guidelines
+# Contribution Guidelines
+
+Define the process of contributing to the UI and UX of the design system and document it in a discoverable place to make it easier for everyone to contribute.

content/roadmaps/111-design-system/content/107-tooling/101-design/readme.md

@@ -1 +1,4 @@
-# Design
+# Design
+
+The UI and UX in a design system need to be tied to development as much as possible. The tools in this checklist should help designers and developers work better together.
+

content/roadmaps/111-design-system/content/107-tooling/readme.md

@@ -1 +1,4 @@
-# Tooling
+# Tooling
+
+To make things efficient for anyone using your design system, make tooling essential. Find the workflows where you can integrate things with the tools people use. This helps organically spread your design system and make it crucial to people’s daily work.
+