add Add documentation for macros and marts

Author: Student

macros/_macros__definitions.yml

@@ -0,0 +1,5 @@
+version: 2
+
+macros:
+  - name: generate_schema_name
+    description: '{{ doc("generate_schema_name_description") }}'

macros/_macros__docs.md

@@ -0,0 +1,13 @@
+{% docs generate_schema_name_description %}
+This is a built-in dbt macro that changes the dataset name based on `target` and `+schema` config.
+
+* If `target` == `prod`, then models will deploy to separate datasets based on `+schema` config set in `dbt_project.yml`. For example:
+   * `staging`
+   * `warehouse`
+* For any non-`prod` deployment, all models will deploy to the default dataset as indicated in `profiles.yml`. For example:
+   * `dev_mkahan`
+   * `dev_jdoe`
+
+More information can be found at the dbt docs site [here](https://docs.getdbt.com/docs/building-a-dbt-project/building-models/using-custom-schemas#how-does-dbt-generate-a-models-schema-name)
+
+{% enddocs %}

models/marts/_marts__docs.md

@@ -0,0 +1,18 @@
+{% docs nba_games_detail_description %}
+A breakdown of metrics & other context related to individual `games`.
+
+This model is presented on a `game`-level granularity and built with reusability in mind. The expectations is that the data will be aggregated in various ways but access to the underlying data points will still be desired. Example aggregations include by date, team, conference, coach, etc.
+
+The metrics in this model include (but not limited to):
+* Total games played
+* Home/away scores
+* Point differentials
+* Home vs Away wins
+
+Other game & team related detail inslude (but not limited to):
+* Team Names
+* Head Coaches
+* General Managers
+* Day Info (Date, Weekday, Month)
+* Game Status (Regulation, Overtime)
+{% enddocs %}