fixup

Ethan-Arrowood · Ethan-Arrowood · commit cce02d1eaa36 · 2025-06-30T08:52:11.000-06:00
diff --git a/docs/SUMMARY.md b/docs/SUMMARY.md
@@ -114,9 +114,9 @@
   * [Blob](technical-details/reference/blob.md)
   * [Content Types](technical-details/reference/content-types.md)
   * [Components](technical-details/reference/components/README.md)
-    * [Built-In](technical-details/reference/components/built-in.md)
+    * [Applications](technical-details/reference/components/applications.md)
+    * [Built-In Extensions](technical-details/reference/components/built-in-extensions.md)
     * [Configuration](technical-details/reference/components/configuration.md)
-    * [Managing Applications](technical-details/reference/components/managing-applications.md)
     * [Extensions](technical-details/reference/components/extensions.md)
     * [(Experimental) Plugins](technical-details/reference/components/plugins.md)
   * [Data Types](technical-details/reference/data-types.md)
diff --git a/docs/deployments/configuration.md b/docs/deployments/configuration.md
@@ -1108,7 +1108,7 @@ The name of the component. This will be used to name the folder where the compon
 
 `package` - _Type_: string
 
-A reference to your [component](../developers/components/managing.md#adding-components-to-root) package. This could be a remote git repo, a local folder/file or an NPM package. Harper will add this package to a package.json file and call `npm install` on it, so any reference that works with that paradigm will work here.
+A reference to your [component](../technical-details/reference/components/applications.md#adding-components-to-root) package. This could be a remote git repo, a local folder/file or an NPM package. Harper will add this package to a package.json file and call `npm install` on it, so any reference that works with that paradigm will work here.
 
 Read more about npm install [here](https://docs.npmjs.com/cli/v8/commands/npm-install)
 
diff --git a/docs/getting-started/harper-concepts.md b/docs/getting-started/harper-concepts.md
@@ -5,10 +5,10 @@ As you begin your journey with Harper, there are a few concepts and definitions
 ## 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](../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](../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.
+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](../technical-details/reference/components/built-in-extensions.md#rest) (for automatic REST endpoint generation), [graphqlSchema](../technical-details/reference/components/built-in-extensions.md#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](../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.
+Applications are a subset of components that cannot be used directly and must depend on other extensions. Examples include defining schemas (using [graphqlSchema](../technical-details/reference/components/built-in-extensions.md#graphqlschema) built-in extension), defining custom resources (using [jsResource](../technical-details/reference/components/built-in-extensions.md#jsresource) built-in extension), hosting static files (using [static](../technical-details/reference/components/built-in-extensions.md#static) built-in extension), enabling REST querying of resources (using [rest](../technical-details/reference/components/built-in-extensions.md#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.
diff --git a/docs/getting-started/what-is-harper.md b/docs/getting-started/what-is-harper.md
@@ -30,7 +30,7 @@ When you are ready for something a little more advanced, start [customizing your
 
 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/).
+If you would like to jump into the most advanced capabilities, learn about [components](../technical-details/reference/components/).
 
 {% hint style="warning" %}
 Need help? Please don’t hesitate to [reach out](https://www.harpersystems.dev/contact).
diff --git a/docs/technical-details/reference/README.md b/docs/technical-details/reference/README.md
@@ -7,9 +7,9 @@ This section contains technical details and reference materials for Harper.
 * [Blob](technical-details/reference/blob.md)
 * [Content Types](technical-details/reference/content-types.md)
 * [Components](technical-details/reference/components/README.md)
-  * [Built-In](technical-details/reference/components/built-in.md)
+  * [Applications](technical-details/reference/components/applications.md)
+  * [Built-In Extensions](technical-details/reference/components/built-in-extensions.md)
   * [Configuration](technical-details/reference/components/configuration.md)
-  * [Managing Applications](technical-details/reference/components/managing-applications.md)
   * [Extensions](technical-details/reference/components/extensions.md)
   * [(Experimental) Plugins](technical-details/reference/components/plugins.md)
 * [Data Types](technical-details/reference/data-types.md)
diff --git a/docs/technical-details/reference/components/README.md b/docs/technical-details/reference/components/README.md
@@ -12,13 +12,13 @@
 
 All together, the support for implementing a feature is the extension, and the actual implementation of the feature is the application.
 
-For more information on the differences between applications and extensions, refer to the beginning of the [Applications](../../../developers/components) guide documentation section.
+For more information on the differences between applications and extensions, refer to the beginning of the [Applications](../../../developers/applications/) guide documentation section.
 
 This technical reference section has detailed information on various component systems:
 
-- [Built-In Extenstion](./built-in.md)
+- [Built-In Extensions](./built-in-extensions.md)
 - [Configuration](./configuration.md)
-- [Managing Applications](./managing.md)
+- [Managing Applications](./applications.md)
 - [Extensions](./extensions.md)
 - [(Experimental) Plugins](./plugins.md)
 
diff --git a/docs/technical-details/reference/components/applications.md b/docs/technical-details/reference/components/applications.md
@@ -1,4 +1,4 @@
-# Managing Applications
+# Applications
 
 > The contents of this page predominantly relate to **application** components. Extensions are not necessarily _deployable_. The ambiguity of the term "components" is being worked on and will be improved in future releases. As we work to clarify the terminology, please keep in mind that the component operations are synonymous with application management. In general, "components" is the general term for both applications and extensions, but in context of the operations API it refers to applications only.
 
@@ -111,7 +111,7 @@ Furthermore, the `package` field can be set to any valid [npm dependency value](
 
 > When using git tags, we highly recommend that you use the semver directive to ensure consistent and reliable installation by npm. In addition to tags, you can also reference branches or commit numbers.
 
-These `package` values are all supported because behind-the-scenes, Harper is generating a `package.json` file for the components. Then, it uses a form of `npm install` to resolve them as dependencies. This is why symlinks are generated when specifying a file path locally. The following [Advanced](managing.md#advanced) section explores this pattern in more detail.
+These `package` values are all supported because behind-the-scenes, Harper is generating a `package.json` file for the components. Then, it uses a form of `npm install` to resolve them as dependencies. This is why symlinks are generated when specifying a file path locally. The following [Advanced](#advanced) section explores this pattern in more detail.
 
 Finally, don't forget to include `restart=true`, or run `harperdb restart target=<remote>`.
 
diff --git a/docs/technical-details/reference/components/built-in-extensions.md b/docs/technical-details/reference/components/built-in-extensions.md
@@ -2,7 +2,7 @@
 
 Harper provides extended features using built-in extensions. They do **not** need to be installed with a package manager, and simply must be specified in a config to run. These are used throughout many Harper docs, guides, and examples. Unlike custom extensions which have their own semantic versions, built-in extensions follow Harper's semantic version.
 
-For more information read the [Components, Applications, and Extensions](../../../developers/components) documentation section.
+For more information read the [Components, Applications, and Extensions](../../../developers/applications/) documentation section.
 
 - [Built-In Extensions](#built-in-extensions)
   - [fastifyRoutes](#fastifyroutes)
diff --git a/docs/technical-details/reference/components/configuration.md b/docs/technical-details/reference/components/configuration.md
@@ -1,6 +1,6 @@
 # Component Configuration
 
-> For information on the distinction between applications and extensions, refer to beginning of the [Applications](../../../developers/applications) documentation section.
+> For information on the distinction between the types of components (applications and extensions), refer to beginning of the [Applications](../../../developers/applications) documentation section.
 
 Harper components are configured with a `config.yaml` file located in the root of the component module directory. This file is how an components configures other components it depends on. Each entry in the file starts with a component name, and then configuration values are indented below it.
 
@@ -10,9 +10,9 @@ name:
   option-2: value
 ```
 
-It is the entry's `name` that is used for component resolution. It can be one of the [built-in extensions](./built-in.md), or it must match a package dependency of the component as specified by `package.json`. The [Custom Component Configuration](#custom-component-configuration) section provides more details and examples.
+It is the entry's `name` that is used for component resolution. It can be one of the [built-in extensions](./built-in-extensions.md), or it must match a package dependency of the component as specified by `package.json`. The [Custom Component Configuration](#custom-component-configuration) section provides more details and examples.
 
-For some built-in extensions they can be configured with as little as a top-level boolean; for example, the [rest](./built-in.md#rest) extension can be enabled with just:
+For some built-in extensions they can be configured with as little as a top-level boolean; for example, the [rest](./built-in-extensions.md#rest) extension can be enabled with just:
 
 ```yaml
 rest: true
@@ -80,6 +80,6 @@ static:
   files: 'web/**'
 ```
 
-Refer to the [built-in components](./built-in.md) documentation for more information on these fields.
+Refer to the [built-in components](./built-in-extensions.md) documentation for more information on these fields.
 
 If a `config.yaml` is defined, it will **not** be merged with the default config.
diff --git a/docs/technical-details/reference/components/extensions.md b/docs/technical-details/reference/components/extensions.md
@@ -14,7 +14,7 @@ If the plugin is being written in something other than JavaScript (such as TypeS
 
 ## Resource Extension
 
-A Resource Extension is for processing a certain type of file or directory. For example, the built-in [jsResource](./built-in.md#jsresource) extension handles executing JavaScript files.
+A Resource Extension is for processing a certain type of file or directory. For example, the built-in [jsResource](./built-in-extensions.md#jsresource) extension handles executing JavaScript files.
 
 Resource Extensions are comprised of four distinct function exports, [`handleFile()`](#handlefilecontents-urlpath-absolutepath-resources-void--promisevoid), [`handleDirectory()`](#handledirectoryurlpath-absolutepath-resources-boolean--void--promiseboolean--void), [`setupFile()`](#setupfilecontents-urlpath-absolutepath-resources-void--promisevoid), and [`setupDirectory()`](#setupdirectoryurlpath-absolutepath-resources-boolean--void--promiseboolean--void). The `handleFile()` and `handleDirectory()` methods are executed on **all worker threads**, and are _executed again during restarts_. The `setupFile()` and `setupDirectory()` methods are only executed **once** on the **main thread** during the initial system start sequence.
 
@@ -38,7 +38,7 @@ Any [Resource Extension](#resource-extension) can be configured with the `files`
 	- Note: `..` is an invalid pattern and will result in an error
   - Otherwise, the value here will be base url path. Leading and trailing `/` characters will be handled automatically (`/static/`, `/static`, and `static/` are all equivalent to `static`)
 
-For example, to configure the [static](./built-in.md#static) component to serve all HTML files from the `web` source directory on the `static` URL endpoint:
+For example, to configure the [static](./built-in-extensions.md#static) component to serve all HTML files from the `web` source directory on the `static` URL endpoint:
 
 ```yaml
 static:
@@ -50,7 +50,7 @@ If there are files such as `web/index.html` and `web/blog.html`, they would be a
 
 Furthermore, if the component is located in the `test-component` directory, and the `urlPath` was set to `'./static/'` instead, then the files would be served from `localhost/test-component/static/*` instead.
 
-The `urlPath` is optional, for example to configure the [graphqlSchema](./built-in.md#graphqlschema) component to load all schemas within the `src/schema` directory, only specifying a `files` glob pattern is required:
+The `urlPath` is optional, for example to configure the [graphqlSchema](./built-in-extensions.md#graphqlschema) component to load all schemas within the `src/schema` directory, only specifying a `files` glob pattern is required:
 
 ```yaml
 graphqlSchema:
diff --git a/docs/technical-details/reference/components/plugins.md b/docs/technical-details/reference/components/plugins.md
@@ -22,7 +22,7 @@ However, it is highly recommended to avoid event-loop-blocking operations within
 
 This is a functional example of how the `handleComponent()` method and `scope` argument can be used to create a simple static file server plugin. This example assumes that the component has a `config.yaml` with the `files` option set to a glob pattern that matches the files to be served.
 
-> This is a simplified form of the [static](./built-in.md#static) built-in extension.
+> This is a simplified form of the [static](./built-in-extensions.md#static) built-in extension.
 
 ```js
 export function handleComponent(scope) {
diff --git a/docs/technical-details/reference/resources/README.md b/docs/technical-details/reference/resources/README.md
@@ -94,7 +94,7 @@ This is the Resource base class. This can be directly extended for custom resour
 
 ### `server`
 
-This object provides extension points for extension components that wish to implement new server functionality (new protocols, authentication, etc.). See the [extensions documentation for more information](../../developers/components/reference.md#extensions).
+This object provides extension points for extension components that wish to implement new server functionality (new protocols, authentication, etc.). See the [extensions documentation for more information](../components/extensions.md).
 
 ### `transaction`
 
diff --git a/docs/technical-details/reference/resources/instance-binding.md b/docs/technical-details/reference/resources/instance-binding.md
@@ -70,7 +70,7 @@ This is the Resource base class. This can be directly extended for custom resour
 
 ### `server`
 
-This object provides extension points for extension components that wish to implement new server functionality (new protocols, authentication, etc.). See the [extensions documentation for more information](../../developers/components/reference.md#extensions).
+This object provides extension points for extension components that wish to implement new server functionality (new protocols, authentication, etc.). See the [extensions documentation for more information](../components/extensions.md).
 
 ### `transaction`
 
