Add Features List to README

README.md

@@ -26,7 +26,14 @@ This repository is a [monorepo](https://en.wikipedia.org/wiki/Monorepo) that hol
 
 See [rush.json](./rush.json) for the complete list of packages and [Versioning.md](./Versioning.md) for package and API versioning policies.
 
-Each package has its own **node_modules** directory that contains symbolic links to *common* dependencies managed by Rush.
+Each package has its own **node_modules** directory that contains symbolic links to _common_ dependencies managed by Rush.
+
+## Features
+
+- ✅ Create infrastructure digitals twins of assets or projects
+- ✅ Aggregate BIM, Reality, GIS, and IoT and other standard formats together
+- ✅ Visualize data and engineering changes in 3D and 4D
+- ✅ Analyze data to gain insights and drive new business outcomes across multiple platforms
 
 ## Prerequisites
 
@@ -71,11 +78,11 @@ For incremental builds, the `rush build` command can be used to only build packa
 4. Locally commit changes: `git commit` (or use the Visual Studio Code user interface)
 5. Repeat steps 1-4 until ready to push changes
 6. Check for API signature changes: `rush extract-api`. This will update the signature files, located in `common/api`. **Note:** before doing this, first do the following:
-    - Be sure that your branch is up to date with the target branch (i.e. `git merge origin/master`)
-    - Cleanup your build output: `rush clean`
-    - Rebuild the project: `rush build`
+   - Be sure that your branch is up to date with the target branch (i.e. `git merge origin/master`)
+   - Cleanup your build output: `rush clean`
+   - Rebuild the project: `rush build`
 7. Review any diffs to the API signature files in the `common/api` directory to ensure they are compatible with the intended release of the package.
-    - If any differences are in packages not modified on this branch, revert the changes before committing.
+   - If any differences are in packages not modified on this branch, revert the changes before committing.
 8. Add changelog entry (which could potentially cover several commits): `rush change`
 9. Follow prompts to enter a change description or press ENTER if the change does not warrant a changelog entry. If multiple packages have changed, multiple sets of prompts will be presented. If the changes are only to non-published packages (like **display-test-app**), then `rush change` will indicate that a changelog entry is not needed.
 10. Completing the `rush change` prompts will cause new changelog entry JSON files to be created.
@@ -86,14 +93,15 @@ For incremental builds, the `rush build` command can be used to only build packa
 
 If using the command line, steps 8 through 11 above can be completed in one step by running `rushchange.bat` from the imodeljs root directory.
 Only use `rushchange.bat` if none of the changes require a changelog entry.
+
 > Note: The CI build will break if changes are pushed without running `rush change` and `rush extract-api` (if the API was changed). The fix will be to complete steps 6 through 11.
 
 Here is a sample [changelog](https://github.com/microsoft/rushstack/blob/master/apps/rush/CHANGELOG.md) to demonstrate the level of detail expected.
 
 ## Updating dependencies/devDependencies on packages within the monorepo
 
 The version numbers of internal dependencies should not be manually edited.
-These will be automatically updated by the overall *version bump* workflow.
+These will be automatically updated by the overall _version bump_ workflow.
 Note that the packages are published by CI builds only.
 
 ## Updating dependencies/devDependencies on packages external to monorepo