chore(docs): final polish to comparison table. (#709)

some changes to comparison table(docs)

#### Migration notes

_No Migrations Needed_

<!-- 5. Readiness checklist
- [ ] The change come with new or modified tests
- [ ] Hard-to-understand functions have explanatory comments
- [ ] End-user documentation is updated to reflect the change
-->


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit


- **Documentation**
- Introduced a new section on Artifact Tracking Protocol in the
architecture documentation, explaining artifact classification and
tracking modes in Metatype.
- Updated comparisons documentation with additional platforms, criteria
for choosing Metatype, and detailed feature comparison tables.
- Renamed project directory for clarity and consistency in project setup
documentation.
- **Bug Fixes**
  - Removed outdated `TODO` comment in installation documentation.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

website/docs/concepts/comparisons/index.mdx

@@ -21,8 +21,8 @@ These are great platforms to quickly start a new project. However, they hardly s
 **When to choose Metatype**
 
 1. You want to build modular APIs by composing pre-defined blocks and import the ones you need from existing systems.
-2. You want to take advantage of developers tooling you are familiar with like version controls or multiple environments.
-3. You favor interoperability and extensibility over vendor lock-in and follow your future needs with ease.
+2. You want to take advantage of developers tooling you are familiar with, like version controls or multiple environments.
+3. You favor interoperability and extensibility over vendor lock-in, and follow your future needs with ease.
 4. You want to decouple your database from your API and change where the data is stored as the project evolves.
 
 ## Headless CMS
@@ -54,6 +54,7 @@ Low Code platforms are a game changer when it comes to faster development cycle,
 3. When you want to have the freedom to make detailed changes to your application to gain that extra peformance.
 
 
+<br/>
 Feature/Capability Key:
 - :white_check_mark: 1st class, with no extra dependencies. 
 - :white_circle: supported, but with extra 3rd party dependencies
@@ -63,32 +64,29 @@ Feature/Capability Key:
 |  | Metatype | Development Platforms | Headless CMS | Low code platform |
 |------------------------|----------------------|-------------|----------------|---------------------------|
 | Licensing | [Open Source](https://github.com/metatypedev/metatype/blob/main/dev/LICENSE-MPL-2.0.md) | Open Source <br/> Proprietary | Open Source | Proprietary |
-| Platform's Requirements | Cloud-based: None <br/> Locally: Deno/NodeJS/Python Runtime <br/> Redis <br/> Docker | Cloud-based: None <br/> Running Locally: Docker  DBMS | NodeJS runtime <br/> DBMS | Cloud-based: None |
-| Architecture Model | Declarative <br/> Less Code <br/> Serverless | Serverless, API over Database |  | Visual drag and drop |
+| Platform's Requirements | - Cloud-based: None <br/> - Locally: Deno/Node.js/Python Runtime, Redis, Docker | - Cloud-based: None <br/> - Running Locally: Docker, DBMS | - NodeJS runtime <br/> - DBMS | Cloud-based: None |
+| Architecture Model | - Declarative <br/> - Less Code <br/> - Serverless | - API over Database <br/> - Serverless | - Headless Architecture <br/> - Serverless | - Visual drag and drop <br/> - Serverless |
 | REST/HTTP | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: |
 | GraphQL | :white_check_mark: | :white_circle: | :white_check_mark: | :large_orange_diamond: |
-| gRPC |  | :large_orange_diamond: | :large_orange_diamond: | :large_orange_diamond: |
+| gRPC | :large_orange_diamond:* | :large_orange_diamond: | :large_orange_diamond: | :large_orange_diamond: |
 | GUI for non programmers | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: |
-| Development SDKs | :white_check_mark: | :white_check_mark: | :red_circle: | :red_circle: (Most)  :white_check_mark: (few) |
-| CLI | :white_check_mark: | :white_check_mark: (some)  :red_circle: (some) | :white_check_mark: | :red_circle: |
+| Development SDKs | :white_check_mark: | :white_check_mark: | :red_circle: | :red_circle: (Most) <br/> :white_check_mark: (few) |
+| CLI | :white_check_mark: | :white_check_mark: (some) <br/> :red_circle: (some) | :white_check_mark: | :red_circle: |
 | Dev Tools | :white_check_mark: | :white_check_mark: | :white_check_mark: | :red_circle: |
 | LSP and Extensions | :white_check_mark:* | :white_circle: | :white_circle: | :red_circle: |
-| Authentication | Basic Auth  JWT  OAuth | Basic Auth  JWT  OAuth  JWT | email/phone/password  JWT  OAuth  JWT | email/phone/password  JWT  OAuth  JWT |
-| Authorization | policy-based access control (PBAC) | policy-based access control (PBAC)  role-based access control (RBAC) | role-based access control (RBAC) | Custom Authorization logic from the User |
-| Type System | [Custom Types](/docs/reference/types) | JS objects  GraphQL Schemas  Database Types | JS objects | Custom Types |
-| Database Toolkit/ORM | Prisma | PostgreSQL  Custom ORMs | Waterline  Custom ORMs | N/A |
-| Query Planning Model |  | proprietary query planner <br/> PostgreSQL's query planner | DBMS's query planner | proprietary query planner |
-| Query Computing Model |  | distributed computing model <br/> PostgreSQL's query execution model | DBMS's query execution engines | proprietary query computing model |
+| Authentication | - Basic Auth <br/> - JWT <br/> - OAuth | - Basic Auth <br/> - JWT <br/> - OAuth <br/> - JWT | - email/phone/password <br/> - JWT  - OAuth | - email/phone/password <br/> - JWT <br/> - OAuth <br/> - JWT |
+| Authorization | - policy-based access control (PBAC) | - policy-based access control (PBAC) <br/> - role-based access control (RBAC) | - role-based access control (RBAC) | - Custom Authorization logic from the User |
+| Type System | [Custom Types](/docs/reference/types) | - JS objects <br/> - GraphQL Schemas <br/> - Database Types | JS objects | Custom Types |
 | Custom Code Support | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: |
-| Version Control | Git <br/> BitBucket | Git <br/> BitBucket | Git <br/> BitBucket | Git <br/> BitBucket |
+| Version Control Friendly | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: |
 | GitOPs Friendly | :white_check_mark: | :white_check_mark: | :white_circle: | :white_circle: |
 | Vertical Scalability | Flexibile | Limited | Flexibile | Limited |
 | Service Decomposition | :white_check_mark: | :white_check_mark: | :white_check_mark: | :red_circle: |
-| Deployment Options | On premise <br/> cloud-based platforms | On premise <br/> cloud-based platforms | On premise <br/> cloud-based platforms | On premise <br/> cloud-based platforms |
+| Deployment Options | - On premise <br/> - Cloud-based platforms | - On premise <br/> - Cloud-based platforms | - On premise <br/> - Cloud-based platforms | - On premise <br/> - Cloud-based platforms |
 | Monitoring and Tracking | :white_check_mark:* | :white_check_mark: | :white_check_mark: | :large_orange_diamond: |
 | Logging | :white_check_mark:* | :white_check_mark: | :white_check_mark: | :large_orange_diamond: |
-| Query Plan Time |  |  |  |  |
-| Query Compute Time |  |  |  |  |
+{/* | Query Plan Time |  |  |  |  |
+| Query Compute Time |  |  |  |  | */}
 
 
 ### Table Parameters Legend
@@ -98,7 +96,7 @@ Feature/Capability Key:
 
 **Platform's Requirements**: The prerequisites and dependencies required for the software to run efficiently, including hardware, operating system, runtime environment, etc.
 
-**Architecture Model**: The underlying design principles and patterns governing the structure of the software solution.
+**Architecture Model**: The underlying design principles and patterns governing the behavior/structure of the software solution.
 
 #### Network comms
 
@@ -127,17 +125,17 @@ Feature/Capability Key:
 #### Database Interaction
 **Type System**: The system governing the data types and structures used by which the application entities and models are constructed.
 
-**Database Toolkit/ORM**: Tools or Object-Relational Mapping (ORM) frameworks used internally.
+{/* **Database Toolkit/ORM**: Tools or Object-Relational Mapping (ORM) frameworks used internally. */}
 
-#### Query Processing
+{/* #### Query Processing
 **Query Planning Model**: The approach used for optimizing and planning the execution of incoming requests to improve performance and efficiency.
 
-**Query Computing Model**: The model used for executing network queries and processing data.
+**Query Computing Model**: The model used for executing network queries and processing data. */}
 
 #### System Flexibility
 **Custom Code support**: The ability of the software solution to accommodate custom code or extensions developed by users or third-party developers.
 
-**Customizability**: 
+{/* **Customizability**:  */}
 
 #### Versioning and CI/CD
 **Version Control**: The support for versioning and revision control of software artifacts, typically using systems like Git, SVN, etc.
@@ -158,9 +156,10 @@ Feature/Capability Key:
 
 **Logging**: Facilities for recording and storing system events, errors, and other relevant information for troubleshooting, analysis, and auditing purposes.
 
-#### Safety and Fault tolerance
 
-#### Basic Benchmarks
+{/* #### Safety and Fault tolerance (TODO) */}
+
+{/* #### Basic Benchmarks (TODO)
 **Query Plan Time**: The time taken by the system to plan and optimize the execution of a request.
 
-**Query Compute Time**: The time taken by the system to process and compute the results of a request.
+**Query Compute Time**: The time taken by the system to process and compute the results of a request. */}