update tree Token Parser Documentation

tools/apiview/parsers/CONTRIBUTING.md

@@ -8,7 +8,7 @@ The main idea is to capture the hierachy of the API using a tree data structure,
 
 ![APITree](APITree.svg)
 
-Each tree node has top tokens which should be used to capture the main data on the node. If your language requires it use the bottom tokens to capture data that closes out the node.
+Each tree node has top tokens which should be used to capture the main tokens on the node. If your language requires it use the bottom tokens to capture tokens that closes out the node.
 
 - Here are the models needed
   ```
@@ -26,6 +26,7 @@ Each tree node has top tokens which should be used to capture the main data on t
     string Value
     string Id
     StructuredTokenKind Kind
+    Set<string> Tags
     Dictionary<string, string> Properties 
     Set<string> RenderClasses 
 
@@ -38,39 +39,44 @@ Each tree node has top tokens which should be used to capture the main data on t
     Url
   ```
 ### APITreeNode
-- `Name` : The name of the tree node which will be used for page navigation.
-- `Id` : Id of the node, which should be unique at the node level. i.e. unique among its siblings. Also the id should be [valid HTML id](https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/id).
+- `Name` : The name of the tree node which will be used for API navigation.
+- `Id` : Id of the node, which should be unique at the node level. i.e. unique among its siblings
 - `Kind` : What kind of node is it. (namespace, class, module, method e.t.c)
-- `Tags` : Use this for thigs like `Deprecated`, `Hidden`
-- `Properties` : If the node needs more specification e.g. Use `SubKind` entry to make the node kind more specific. Feel free to push any other data that you think will be useful here, then file an issue for further implementation in APIView.
+- `Tags` : Use this for opt in or opt out boolean properties e.g. `Deprecated`, `Hidden`, `HideFromNavigation`
+- `Properties` : Use this for other properties of the node. If the node needs more specification e.g. Use `SubKind` entry to make the node kind more specific. 
 - `TopTokens` : The main data of the node.
 - `BottomToken` : Data that closes out the node.
-- `Childrens` : Node immediate descendant
+- `Children` : Node immediate descendant
 
 ### StructuredToken
 - `Value` : The token value which will be dispalyed.
-- `Id` : which will be used to navigate and find token on page.
-- `Kind` : Could be `LineBreak` `NoneBreakingSpace` `TabSpace` `ParameterSeparator` `Url` `Content`
-  All tokens should be content except for spacing tokens. ParameterSeparator should be used between method or function parameters. Spacing token dont need to have value.
-- `Properties` : Capture any other interesting data here. e.g Use `GroupId` : `documentation` to group consecutive tokens.
-- `RenderClasses` : Add css classes for how the tokens will be rendred.
+- `Id` : Which will be used to navigate and find token on page.
+- `Kind` : Could be `Content` `LineBreak` `NoneBreakingSpace` `TabSpace` `ParameterSeparator` `Url`
+  All tokens should be content except for spacing tokens and url. ParameterSeparator should be used between method or function parameters. Spacing token dont need to have value.
+- `Tags` : Use this for opt in or opt out boolean properties e.g. `SkippDiff`
+- `Properties` : Capture any other interesting data here. e.g Use `GroupId` : `documentation` to group consecutive comment tokens.
+- `RenderClasses` : Add css classes for how the tokens will be rendred. Classes currently being used are `text` `keyword` `punctuation` `type-name` `member-name` `literal` `string-literal` `comment` Feel free to add your own custom class. Whatever custom classes you use please provide us the appriopriate css for the class so we can update APIView.
+
+Each module of the API (namespace, class, method) should be its own node.
 
 If you want to have space between the API nodes add an empty token and lineBreak at the end of bottom tokens to simulate one empty line.
 
 Dont worry about indentation that will be handeled by the tree structure, unless you want to have indentation between the tokens then use `TabSpace` token kind.
 
-If your packages contains multiple languages then you will have multiple trees with multiple roots.
+If your packages contains multiple assemblies then you will have multiple trees with multiple roots.
 Assign the final parsed value to `APIForest` property of the `CodeFile`.
 
-## Commons Scenarios
+Serialize the generated code file to JSON `.json` and MessagePack `.msgpack`. MessagePack will be used by APIView as it has way better download / deserilization performance. We will revert to JSON if you don`t provide MessagePack.
+
+## How to handle commons Scenarios
 - TEXT, KEYWORD, COMMENT : Add `text`, `keyword`, `comment` to RenderClasses of the token
 - NEW_LINE : Create a token with `Kind = LineBreak`
 - WHITE_SPACE :  Create token with `Kind = NoneBreakingSpace`
 - PUNCTUATION : Create a token with `Kind = Content` and the `Value = the punctuation`
 - DOCUMENTATION : Add `GroupId = documentation` in the properties of the token. This identifies a range of consecutive tokens as belonging to a group.
-- SKIP_DIFF :  Add `SkipDiff` to the node Tag to indicate that diff should be skipped.
-- LINE_ID_MARKER : You can add a empty token. `Kind = Content` and `Value = Empty String` then give it an Id to make it commentable.
+- SKIP_DIFF :  Add `SkipDiff` to the Tag to indicate that node or token should not be included in diff computation
+- LINE_ID_MARKER : You can add a empty token. `Kind = Content` and `Value = ""` then give it an `Id` to make it commentable.
 - EXTERNAL_LINK : Create a single token set `Kind = Url`, `Value = link` then add the link text as a properties `LinkText`;
-- Common Tags: `Deprecated`, `Hidden`, `HideFromNavigation`
-
+- Common Tags: `Deprecated`, `Hidden`, `HideFromNavigation`, `SkipDiff`
 
+Please reach out at [APIView Teams Channel](https://teams.microsoft.com/l/channel/19%3A3adeba4aa1164f1c889e148b1b3e3ddd%40thread.skype/APIView?groupId=3e17dcb0-4257-4a30-b843-77f47f1d4121&tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47) if you need more infomation.