Pmc-20251025-link-fixes (#7476) (#7507)

* fix bad links 1

* fix links

* more link fixes

* fix links in templates

* remove duplicate

* fix artifact_definitions

Co-authored-by: Pete Crocker <[email protected]>

Author: infrahub-github-bot-app[bot]

docs/_templates/dotinfrahub.j2

@@ -6,17 +6,17 @@ title: Repository configuration file
 
 The repository configuration file allows you to define multiple resources that need to be imported into Infrahub.
 
-The file should be formatted as a Yaml file, have the filename `.infrahub.yml` and should be stored at the root of the [repository](../topics/repository).
+The file should be formatted as a Yaml file, have the filename `.infrahub.yml` and should be stored at the root of the [repository](../topics/repository.mdx).
 
 :::info
 
-See [this topic](../topics/infrahub-yml) for more details on the available repository configuration options
+See [this topic](../topics/infrahub-yml.mdx) for more details on the available repository configuration options
 
 :::
 
 :::note
 
-To help with the development process of a repository configuration file, you can leverage the schemas we publish for validation within your [editor](../development/editor)
+To help with the development process of a repository configuration file, you can leverage the schemas we publish for validation within your [editor](../development/editor.mdx)
 
 :::
 {% for property in properties %}

docs/_templates/message-bus-events.j2

@@ -8,7 +8,7 @@ This document provides detailed documentation for all events used in the Infrahu
 
 :::info
 
-For more detailed explanations on how these events are used within Infrahub, see the [bus event handling](../topics/bus-event-handling) topic.
+For more detailed explanations on how these events are used within Infrahub, see the [bus event handling](../topics/bus-event-handling.mdx) topic.
 
 :::
 

docs/docs/development/backend.mdx

@@ -112,7 +112,7 @@ The `debug` flag allows the server to be reloaded when a change is detected in t
 Note that this will only make the backend service usable, the frontend will not be available. Only Swagger documentation should be available at http://localhost:8000/api/docs.
 GraphQL sandbox is available through the frontend.
 
-For running the frontend, please refer to its [dedicated documentation section](./frontend).
+For running the frontend, please refer to its [dedicated documentation section](./frontend/readme.mdx).
 
 ## Loading a new schema via CLI
 

docs/docs/development/docs.mdx

@@ -239,7 +239,7 @@ Please note the following important points:
 
 - Today, spelling (the `.vale` directory) is authoritative in the `infrahub` repository, not the `infrahub-docs` repository. If you need to add a spelling exception in another repository (i.e. `infrahub-demo-dc-fabric`), you have to add the exception to the `infrahub` repository.
 - All documentation URLs need to be relative:
-  - Do this: `[some page](../path/to/file)`
+  - Do this: `[some page](../path/to/file.mdx)`
   - Not this: `[some page](/absolute_path/to/file)`
 
 ## Organizing new pages
@@ -313,7 +313,7 @@ For a deeper dive into reference docs, refer to the [diátaxis reference page](h
 
 ## Application screenshots
 
-To ensure that Infrahub's screenshots remain up to date and to check that our guides work properly, we use [end-to-end (e2e) tests](./frontend/testing-guidelines#e2e-tests). You'll find the e2e tests specifically designed for tutorials located in `frontend/app/tests/e2e/tutorial`.
+To ensure that Infrahub's screenshots remain up to date and to check that our guides work properly, we use [end-to-end (e2e) tests](./frontend/testing-guidelines.mdx#e2e-tests). You'll find the e2e tests specifically designed for tutorials located in `frontend/app/tests/e2e/tutorial`.
 
 ### Updating all screenshots manually
 
@@ -350,7 +350,7 @@ The screenshots will be saved in `docs/docs/media`. You can then use them in our
 
 #### 1. Locate on which test the screenshot should be added
 
-If the test does not exist yet, create must create it first. Refer to the [write e2e tests](./frontend/testing-guidelines#writing-e2e-tests) for more information.
+If the test does not exist yet, create must create it first. Refer to the [write e2e tests](./frontend/testing-guidelines.mdx#writing-e2e-tests) for more information.
 
 #### 2. Add the screenshot
 

docs/docs/development/frontend/getting-set-up.mdx

@@ -34,7 +34,7 @@ npm install
 npm start
 ```
 
-You can access your local server at [http://localhost:8080/](http://localhost:8080/). If you are not familiar with Infrahub, follow our [tutorial](../../tutorials/getting-started).
+You can access your local server at [http://localhost:8080/](http://localhost:8080/). If you are not familiar with Infrahub, follow our [tutorial](../../tutorials/getting-started/readme.mdx).
 
 ## 3. Run all tests
 

docs/docs/development/frontend/testing-guidelines.mdx

@@ -6,7 +6,7 @@ title: Running & writing tests
 
 :::info Before we start
 
-If you have never run Infrahub tests before, we highly suggest following the [frontend guide](getting-set-up).
+If you have never run Infrahub tests before, we highly suggest following the [frontend guide](./getting-set-up.mdx).
 
 :::
 

docs/docs/development/git-best-practices.mdx

@@ -16,7 +16,7 @@ Before you begin, ensure you have:
 - Git 2.20+ installed with submodule support
 - SSH keys configured for GitHub access
 - Basic understanding of Git branching and merging concepts
-- Development environment set up per the [backend guide](../development/backend)
+- Development environment set up per the [backend guide](../development/backend.mdx)
 
 ## Working with submodules
 
@@ -442,7 +442,7 @@ git commit -m "temp: use local submodule changes"
 
 ## Further reading
 
-- [Understanding Git repositories in Infrahub](../topics/repository) - Repository integration concepts  
-- [Backend development guide](../development/backend) - Setting up the development environment
-- [How to connect external Git repositories](../guides/repository) - External repository setup
-- [Proposed changes](../topics/proposed-change) - Understanding Infrahub's change management
+- [Understanding Git repositories in Infrahub](../topics/repository.mdx) - Repository integration concepts
+- [Backend development guide](../development/backend.mdx) - Setting up the development environment
+- [How to connect external Git repositories](../guides/repository.mdx) - External repository setup
+- [Proposed changes](../topics/proposed-change.mdx) - Understanding Infrahub's change management

docs/docs/faq/faq.mdx

@@ -26,7 +26,7 @@ Infrahub is an open-source platform that enables infrastructure as code by provi
 - Integrations: Integrations with tools like NetBox, Nautobot, Ansible, and Nornir. Ability to build custom integrations.
 - Python SDK: Programmatically interact with Infrahub using a Python SDK.
 
-For more information, see our [Infrahub overview](../getting-started/overview).
+For more information, see our [Infrahub overview](../getting-started/overview.mdx).
 
 ### I'm just getting started with infrastructure automation. Do I need Infrahub?
 
@@ -36,7 +36,7 @@ Check out the [blog section on our website](https://opsmill.com/blog/) to learn
 
 ### How can I see Infrahub in action?
 
-You have many options to quickly try out Infrahub, please refer to the [Getting Started](../getting-started/quick-start) page for more details.
+You have many options to quickly try out Infrahub, please refer to the [Getting Started](../getting-started/quick-start.mdx) page for more details.
 
 Here are some quick ways to get started:
 
@@ -55,7 +55,7 @@ Common deployment types include:
 
 :::note
 
-Infrahub depends on several supporting services that must be installed either within the same environment or externally. See the [Overview](../getting-started/overview) page for more details.
+Infrahub depends on several supporting services that must be installed either within the same environment or externally. See the [Overview](../getting-started/overview.mdx) page for more details.
 
 Each deployment option comes with trade-offs. It's important to also consider your existing tools and processes when choosing the best fit.
 
@@ -65,13 +65,13 @@ We're also working on a managed cloud SaaS version of Infrahub. Please [subscrib
 
 ### How can I install Infrahub?
 
-Check out the [Installing Infrahub](../guides/installation) guide for detailed setup instructions.
+Check out the [Installing Infrahub](../guides/installation.mdx) guide for detailed setup instructions.
 
 ### I deployed Infrahub, now what?
 
 Once Infrahub is deployed, you can start using it to manage your infrastructure resources and begin your automation journey.
 
-Visit the [Next Steps](../getting-started/next-steps) section for practical examples.
+Visit the [Next Steps](../getting-started/next-steps.mdx) section for practical examples.
 
 ### What is the status of the project? Can I deploy Infrahub in production?
 
@@ -108,7 +108,7 @@ Infrahub is built on an open source foundation to allow for broad community acce
 - **Infrahub Community** - Infrahub is an open source project that delivers a unified system to model, store, version, validate, and generate infrastructure data and configurations.
 - **Infrahub Enterprise** - Get SLA-backed support, advanced integrations, and enhanced performance and high-availability. Gain the benefits of mature infrastructure automation with greater velocity and quality assurance.
 
-For a detailed comparison of features, use cases, and decision guidance, see our [Community vs Enterprise](../topics/community-vs-enterprise) documentation.
+For a detailed comparison of features, use cases, and decision guidance, see our [Community vs Enterprise](../topics/community-vs-enterprise.mdx) documentation.
 
 You can find pricing and feature details on [our website](https://opsmill.com/pricing/).
 

docs/docs/getting-started/concepts.mdx

@@ -13,9 +13,9 @@ A core feature of Infrahub is the ability to define a relational model to descri
 
 The schema provides an abstraction layer to the graph database, and as such no knowledge of database administration is needed for daily Infrahub usage.
 
-The schema is described in YAML format, and consists of nodes, attributes, relationships, and other descriptors. For more detail, see the [guide to creating a schema](../guides/create-schema).
+The schema is described in YAML format, and consists of nodes, attributes, relationships, and other descriptors. For more detail, see the [guide to creating a schema](../guides/create-schema.mdx).
 
-A new deployment of Infrahub will have no schema by default. It is up to the administrator of the system to define and load the initial schema. See the [commands to load a schema](../topics/schema#load-a-schema-into-infrahub) for more information.
+A new deployment of Infrahub will have no schema by default. It is up to the administrator of the system to define and load the initial schema. See the [commands to load a schema](../topics/schema.mdx#load-a-schema-into-infrahub) for more information.
 
 Example schemas can be found:
 

docs/docs/getting-started/next-steps.mdx

@@ -84,7 +84,7 @@ The most important file is the `.infrahub.yml` file, which defines how Infrahub
 
 You will need to push this repository to a remote location that Infrahub can access. It doesn't have to be a public repository as Infrahub supports authentication with private repositories. Depending on the provider you use (for example: GitHub, GitLab, Bitbucket), the process may vary slightly, but the general steps are the same:
 
-1. Create a new repository using the `infrahubctl repository init <directory>` command or manually. More details in the [related topic](../topics/developer-guide#initializing-an-infrahub-repository).
+1. Create a new repository using the `infrahubctl repository init <directory>` command or manually. More details in the [related topic](../topics/developer-guide.mdx#initializing-an-infrahub-repository).
 2. Push the repository to the remote location.
 3. Create a "Infrahub" access token with the required permissions to access the repository.
 
@@ -102,9 +102,9 @@ At this point, you have a running Infrahub instance with a schema, some data loa
 
 From here, depending on your use case and goals, you can:
 
-- [**Create your own schema**](../guides/create-schema) - Extend the existing schema to fit your organization's needs.
-- [**Generate artifacts**](../guides/artifact) - Use transformations to create meaningful files from your data such as startup configurations, documentation, cabling plans and more.
-- [**Build generators**](../guides/generator) - Automate the creation of infrastructure objects based on templates and user inputs.
+- [**Create your own schema**](../guides/create-schema.mdx) - Extend the existing schema to fit your organization's needs.
+- [**Generate artifacts**](../guides/artifact.mdx) - Use transformations to create meaningful files from your data such as startup configurations, documentation, cabling plans and more.
+- [**Build generators**](../guides/generator.mdx) - Automate the creation of infrastructure objects based on templates and user inputs.
 - [**Deploy artifacts to the field using Ansible**]($(base_url)ansible) - Deploy outputs where they're needed and apply your intended state to your infrastructure. You can also use other tools like [Nornir]($(base_url)nornir) to deploy your artifacts.
 
 If you need guidance with which feature to explore next or how to implement a specific use case, feel free to reach out to the community on our [Discord server](https://discord.gg/opsmill) or book a meeting with OpsMill.