Fix getting started section (#185)

* fix up links and other minor nits in getting started section

* fix one more reference to old getting-started guide

Author: Ethan-Arrowood

docs/getting-started.md

@@ -19,23 +19,23 @@ For more advanced concepts in Harper, see our [blog](https://www.harpersystems.d
     <tbody>
         <tr>
             <td>
-                <a href="getting-started/install-harper.md"><strong>Install Harper</strong></a>
+                <a href="./getting-started/install-harper.md"><strong>Install Harper</strong></a>
             </td>
             <td>Pick the installation method that best suits your environment</td>
             <td></td>
-            <td><a href="getting-started/install-harper.md">install-harper</a></td>
+            <td><a href="./getting-started/install-harper.md">install-harper</a></td>
         </tr>
         <tr>
-            <td><a href="getting-started/what-is-harper.md"><strong>What is Harper</strong></a></td>
+            <td><a href="./getting-started/what-is-harper.md"><strong>What is Harper</strong></a></td>
             <td>Learn about Harper, how it works, and some of its usecases</td>
             <td></td>
-            <td><a href="getting-started/what-is-harper.md">what-is-harper</a></td>
+            <td><a href="./getting-started/what-is-harper.md">what-is-harper</a></td>
         </tr>
         <tr>
-            <td><a href="getting-started/harper-concepts.md"><strong>Harper Concepts</strong></a></td>
+            <td><a href="./getting-started/harper-concepts.md"><strong>Harper Concepts</strong></a></td>
             <td>Learn about Harper's fundamental concepts and how they interact</td>
             <td></td>
-            <td><a href="getting-started/harper-concepts.md">harper-concepts</a></td>
+            <td><a href="./getting-started/harper-concepts.md">harper-concepts</a></td>
         </tr>
     </tbody>
 </table>

docs/getting-started/README.md

@@ -77,7 +77,7 @@ type Dog @table @export {
 }
 ```
 
-By default the application HTTP server port is `9926` (this can be [configured here](../deployments/configuration.md#http)), so the local URL would be http://localhost:9926/Dog/ with a full REST API. We can PUT or POST data into this table using this new path, and then GET or DELETE from it as well (you can even view data directly from the browser). If you have not added any records yet, we could use a PUT or POST to add a record. PUT is appropriate if you know the id, and POST can be used to assign an id:
+By default the application HTTP server port is `9926` (this can be [configured here](../deployments/configuration.md#http)), so the local URL would be `http://localhost:9926/Dog/` with a full REST API. We can PUT or POST data into this table using this new path, and then GET or DELETE from it as well (you can even view data directly from the browser). If you have not added any records yet, we could use a PUT or POST to add a record. PUT is appropriate if you know the id, and POST can be used to assign an id:
 
 ```json
 POST /Dog/
@@ -149,10 +149,9 @@ http://localhost:9926/Dog/?breed=Labrador
 http://localhost:9926/Dog/?breed=Husky&name=Balto&select(id,name,breed)
 ```
 
-Congratulations, you now have created a secure database application backend with a table, a well-defined structure, access controls, and a functional REST endpoint with query capabilities! See the [REST documentation for more information on HTTP access](../developers/rest.md) and see the [Schema reference](defining-schemas.md) for more options for defining schemas.
-
-> Additionally, you may now use GraphQL (over HTTP) to create queries. See the documentation for that new feature [here](../../technical-details/reference/graphql.md).
+Congratulations, you now have created a secure database application backend with a table, a well-defined structure, access controls, and a functional REST endpoint with query capabilities! See the [REST documentation for more information on HTTP access](../developers/rest.md) and see the [Schema reference](../developers/applications/defining-schemas.md) for more options for defining schemas.
 
+> Additionally, you may now use GraphQL (over HTTP) to create queries. See the documentation for that new feature [here](../technical-details/reference/graphql.md).
 
 ## Key Takeaway
 Harper's schema-driven approach means you can build production-ready APIs in minutes, not hours. Start with pure schema definitions to get 90% of your functionality, then add custom code only where needed. This gives you the best of both worlds: rapid development with the flexibility to customize when required.

docs/getting-started/first-harper-app.md

@@ -3,12 +3,12 @@
 As you begin your journey with Harper, there are a few concepts and definitions that you should understand.
 
 ## Components
-Harper components are a core Harper concept defined as flexible JavaScript based extensions of the highly extensible core Harper platform. They are executed by Harper directly and have complete access to the Harper [Global APIs](https://docs.harperdb.io/docs/technical-details/reference/globals) (such as Resource, databases, and tables).
+Harper components are a core Harper concept defined as flexible JavaScript based extensions of the highly extensible core Harper platform. They are executed by Harper directly and have complete access to the Harper [Global APIs](../technical-details/reference/globals.md) (such as Resource, databases, and tables).
 
-A key aspect to components are their extensibility; components can be built on other components. For example, a [Harper Application](https://docs.harperdb.io/docs/developers/applications) is a component that uses many other components. The [application template](https://github.com/HarperDB/application-template) demonstrates many of Harper's built-in components such as [rest](https://docs.harperdb.io/docs/developers/components/built-in#rest) (for automatic REST endpoint generation), [graphqlSchema](https://docs.harperdb.io/docs/developers/components/built-in#graphqlschema) (for table schema definitions), and many more.
+A key aspect to components are their extensibility; components can be built on other components. For example, a [Harper Application](../developers/applications/README.md) is a component that uses many other components. The [application template](https://github.com/HarperDB/application-template) demonstrates many of Harper's built-in components such as [rest](../developers/components/built-in#rest) (for automatic REST endpoint generation), [graphqlSchema](../developers/components/built-in#graphqlschema) (for table schema definitions), and many more.
 
 ## Applications
-Applications are a subset of components that cannot be used directly and must depend on other extensions. Examples include defining schemas (using [graphqlSchema](https://docs.harperdb.io/docs/developers/components/built-in#graphqlschema) built-in extension), defining custom resources (using [jsResource](https://docs.harperdb.io/docs/developers/components/built-in#jsresource) built-in extension), hosting static files (using [static](https://docs.harperdb.io/docs/developers/components/built-in#static) built-in extension), enabling REST querying of resources (using [rest](https://docs.harperdb.io/docs/developers/components/built-in#rest) built-in extension), and running [Next.js](https://github.com/HarperDB/nextjs), [Astro](https://github.com/HarperDB/astro), or [Apollo](https://github.com/HarperDB/apollo) applications through their respective extensions.
+Applications are a subset of components that cannot be used directly and must depend on other extensions. Examples include defining schemas (using [graphqlSchema](../developers/components/built-in#graphqlschema) built-in extension), defining custom resources (using [jsResource](../developers/components/built-in#jsresource) built-in extension), hosting static files (using [static](../developers/components/built-in#static) built-in extension), enabling REST querying of resources (using [rest](../developers/components/built-in#rest) built-in extension), and running [Next.js](https://github.com/HarperDB/nextjs), [Astro](https://github.com/HarperDB/astro), or [Apollo](https://github.com/HarperDB/apollo) applications through their respective extensions.
 
 ## Resources
 Resources in Harper encompass databases, tables, and schemas that store and structure data within the system. The concept is central to Harper's data management capabilities, with custom resources being enabled by the built-in jsResource extension. Resources represent the data layer of the Harper ecosystem and provide the foundation for data operations across applications built with the platform.

docs/getting-started/harper-concepts.md

@@ -22,17 +22,15 @@ What we realized is that networking systems together in this way is inefficient
 
 Start by running Harper locally with [npm](https://www.npmjs.com/package/harperdb) or [Docker](https://hub.docker.com/r/harperdb/harperdb).
 
-Since technology tends to be built around the storage, processing, and transfer of data, start by [defining your schema](developers/applications/#creating-our-first-table) with the `schema.graphql` file in the root of the application directory.
+Since technology tends to be built around the storage, processing, and transfer of data, start by [defining your schema](../developers/applications/#creating-our-first-table) with the `schema.graphql` file in the root of the application directory.
 
-If you would like to [query](developers/applications/#adding-an-endpoint) this data, add the `@export` directive to our data schema and test out the [REST](developers/rest.md), [MQTT](developers/real-time.md#mqtt), or [WebSocket](developers/real-time.md#websockets) endpoints.
+If you would like to [query](../developers/applications/#adding-an-endpoint) this data, add the `@export` directive to our data schema and test out the [REST](../developers/rest.md), [MQTT](../developers/real-time.md#mqtt), or [WebSocket](../developers/real-time.md#websockets) endpoints.
 
-When you are ready for something a little more advanced, start [customizing your application](developers/applications/#custom-functionality-with-javascript).
+When you are ready for something a little more advanced, start [customizing your application](../developers/applications/#custom-functionality-with-javascript).
 
-Finally, when it’s time to deploy, explore [replication](developers/replication/) between nodes.
+Finally, when it’s time to deploy, explore [replication](../developers/replication/) between nodes.
 
-If you would like to jump into the most advanced capabilities, learn about [components](developers/components/).
-
-For a more comprehensive deep dive, take a look at our [Getting Started Guide](getting-started.md).
+If you would like to jump into the most advanced capabilities, learn about [components](../developers/components/).
 
 {% hint style="warning" %}
 Need help? Please don’t hesitate to [reach out](https://www.harpersystems.dev/contact).
@@ -48,7 +46,7 @@ For use cases like e-commerce, real estate listing, and content-oriented sites,
 
 ### Data Delivery Networks
 
-For use cases like real-time sports updates, flight tracking, and zero-day software update distribution, Harper is rapidly gaining popularity. Harper’s ability to receive and broadcast messages while simultaneously handling application logic and data storage streamlines operations and eliminates the need for multiple separate systems. To build an understanding of our messaging system function, refer to our [real-time documentation](developers/real-time.md).
+For use cases like real-time sports updates, flight tracking, and zero-day software update distribution, Harper is rapidly gaining popularity. Harper’s ability to receive and broadcast messages while simultaneously handling application logic and data storage streamlines operations and eliminates the need for multiple separate systems. To build an understanding of our messaging system function, refer to our [real-time documentation](../developers/real-time.md).
 
 ### Edge Inference Systems
 

docs/getting-started/what-is-harper.md

@@ -34,7 +34,7 @@ async function getRecord() {
 }
 ```
 
-It is recommended that you [define a database](../../getting-started.md) for all the tables that are required to exist in your application. This will ensure that the tables exist on the `tables` object. Also note that the property names follow a CamelCase convention for use in JavaScript and in the GraphQL Schemas, but these are translated to snake\_case for the actual table names, and converted back to CamelCase when added to the `tables` object.
+It is recommended that you [define a database](../../developers/applications/defining-schemas.md) for all the tables that are required to exist in your application. This will ensure that the tables exist on the `tables` object. Also note that the property names follow a CamelCase convention for use in JavaScript and in the GraphQL Schemas, but these are translated to snake\_case for the actual table names, and converted back to CamelCase when added to the `tables` object.
 
 ## `databases`