Misc refactoring of docs/ folder content

Author: jgwest

docs/building.md

@@ -99,4 +99,4 @@ docker run --rm -it gitops-service:latest # to get /bin/bash
 [psql.sh]: https://github.com/redhat-appstudio/managed-gitops/blob/main/psql.sh
 [Operation CRD]: https://github.com/redhat-appstudio/managed-gitops/blob/main/backend-shared/config/crd/bases/managed-gitops.redhat.com_operations.yaml
 [routes]: https://github.com/redhat-appstudio/managed-gitops/tree/main/backend/routes
-[Design]: https://docs.google.com/document/d/1e1UwCbwK-Ew5ODWedqp_jZmhiZzYWaxEvIL-tqebMzo/edit#heading=h.s0hdo22ap5cp
+[Design]: ./designs/gitops-service-internal-architecture-appstudio

docs/components.md

@@ -47,4 +47,4 @@ Plus, within each of the components there is a `Makefile`, which can be used for
 [psql.sh]: https://github.com/redhat-appstudio/managed-gitops/blob/main/psql.sh
 [Operation CRD]: https://github.com/redhat-appstudio/managed-gitops/blob/main/backend-shared/config/crd/bases/managed-gitops.redhat.com_operations.yaml
 [routes]: https://github.com/redhat-appstudio/managed-gitops/tree/main/backend/routes
-[Design]: https://docs.google.com/document/d/1e1UwCbwK-Ew5ODWedqp_jZmhiZzYWaxEvIL-tqebMzo/edit#heading=h.s0hdo22ap5cp
+[Design]: ./designs/gitops-service-internal-architecture-appstudio

docs/designs/initial-api-design.md

@@ -2,6 +2,7 @@
 
 ### Written by
 - Jonathan West (@jgwest)
+- Originally written from Sept 30, 2021 to Nov 19, 2021, with additional updates throughout 2022 and 2023
 
 # Definitions
 

docs/profiling.md

@@ -65,6 +65,3 @@ docker run --rm -it --network="host" -v $HOME/managed-gitops/parca.yaml:/parca.y
 
 4. Select a profile from the dropdown menu to visualize the icicle graph.
 
-### Reference
-
-1. [Profiling HAS](https://docs.google.com/document/d/1LqLeDEhYXDK07lz_p582c1LRVwxwFCdqFLk1fh33Dn8/edit#heading=h.852ozrf8sxek)

docs/sandboxing-via-appprojects.md

@@ -84,7 +84,7 @@ spec:
 
 # Argo CD’s default Repository Credential behaviour is not a good fit for multitenancy, and AppProject doesn’t fix that
 
-The way that Argo CD handles repository credentials does not fit well with multitenancy. This is covered [in this document](https://docs.google.com/document/d/1aYUFlOvGB0R5142PTg5Y4BQwp_1kugj-zveziErRwJY/edit#heading=h.5mbvxcu19jxr).
+The way that Argo CD handles repository credentials does not fit well with multitenancy. This is covered [in this document](./designs/gitops-service-internal-architecture-appstudio).
 
 In short, if one Argo CD Application has the credentials to read from a private Git repository, then ANY Argo CD Application can read from that Git repository (and will use those credentials).