onboarding doc update

docs/site/config/team.json

@@ -48,5 +48,20 @@
     "name": "Nancy Wu",
     "domain": ["iOS"],
     "avatar": "https://avatars.githubusercontent.com/u/66387473?v=4"
-  }
+  },
+  {
+    "name": "Chloe Han",
+    "domain": ["React", "Core"],
+    "avatar": "https://avatars.githubusercontent.com/u/15382804?v=4"
+  },
+  {
+    "name": "Sakuntala Niharika Motukuri",
+    "domain": ["Android"],
+    "avatar": "https://avatars.githubusercontent.com/u/171299777?v=4"
+  },
+  {
+    "name": "Mrigank Mehta",
+    "domain": ["React", "Core"],
+    "avatar": "https://avatars.githubusercontent.com/u/16272231?v=4"
+  } 
 ]

docs/site/pages/content/assets-views.mdx

@@ -41,7 +41,7 @@ The `id` of the views are used in the navigation section to reference a specific
 
 ## Cross-field validation
 
-The other special property of a `view` vs. an `asset` is the addition of a `validation` property on the view. These contain [`validation` objects](/schema) that are used for validations crossing multiple fields, and are ran on user navigation rather than data change.
+The other special property of a `view` vs. an `asset` is the addition of a `validation` property on the view. These contain [`validation` objects](/content/schema) that are used for validations crossing multiple fields, and are ran on user navigation rather than data change.
 
 Example:
 
@@ -72,14 +72,14 @@ Any object in the tree (including _assets_) may contain an `applicability` prope
 
 # Switches
 
-Switches are ways of dynamically changing the structure of the view based on data. There are 2 types of switches: `static` and `dynamic`, but their structures are identical. `switches` can appear anywhere you'd find a normal asset, and (similar to [templates](./templates)) are removed from the view before it reaches the UI layer.
+Switches are ways of dynamically changing the structure of the view based on data. There are 2 types of switches: `static` and `dynamic`, but their structures are identical. `switches` can appear anywhere you'd find a normal asset, and (similar to [templates](#templates)) are removed from the view before it reaches the UI layer.
 
 ## Usage
 
 The switch is simply a list of objects with `case` and `asset` properties:
 
 - `asset` - The asset that will replace the switch if the case is true
-- `case` - An [expression](./expression) to evaluate.
+- `case` - An [expression](/content/data-expressions) to evaluate.
 
 The switch will run through each _case_ statement until the first case expression evaluates to true. For the _default_ case, simple use a value of `true` at the end of the array.
 

newCONTRIBUTORS.md

@@ -42,6 +42,11 @@ From here, you can create a new branch
 git checkout -b my-new-feature
 ```
 
+And when we're ready to commit and push to GitHub, we just run the same command as usual:
+```
+git push -u origin my-new-feature
+```
+
 The -u here is important because it allows any future push-es to this repo to always use origin as the remote that it wants to push to.
 
 When you're ready to submit a Pull Request, there's a great CLI command for that one too: