From 1a343595b739337eba343bd99fca0108fed9e5c0 Mon Sep 17 00:00:00 2001 From: Pratik Gandhi Date: Thu, 1 Oct 2026 15:28:14 -0700 Subject: [PATCH] docs: fix broken links in developer guides --- .../content/docs/development/Guides/creating-node-pack.mdx | 2 +- docs/src/content/docs/development/Guides/creating-nodes.mdx | 4 ++-- docs/src/content/docs/development/Setup/dev-environment.mdx | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/src/content/docs/development/Guides/creating-node-pack.mdx b/docs/src/content/docs/development/Guides/creating-node-pack.mdx index 01a51afbcb5..1688a6678e6 100644 --- a/docs/src/content/docs/development/Guides/creating-node-pack.mdx +++ b/docs/src/content/docs/development/Guides/creating-node-pack.mdx @@ -132,7 +132,7 @@ class MyInvocation(BaseInvocation): return MyOutput(result=f"Processed: {self.input_text}") ``` -For full details on the invocation API, see the [Invocation API documentation](invocation-api.md). +For full details on the invocation API, see the [Invocation API documentation](/development/guides/api-development). ## Best Practices diff --git a/docs/src/content/docs/development/Guides/creating-nodes.mdx b/docs/src/content/docs/development/Guides/creating-nodes.mdx index 2f8456478b0..833e72c01ab 100644 --- a/docs/src/content/docs/development/Guides/creating-nodes.mdx +++ b/docs/src/content/docs/development/Guides/creating-nodes.mdx @@ -14,7 +14,7 @@ import { Steps, LinkCard } from '@astrojs/starlight/components'; 2. Make sure the node is contained in a new Python (.py) file. Preferably, the node is in a repo with a README detailing the nodes usage & examples to help others more easily use your node. Including the tag "invokeai-node" in your repository's README can also help other users find it more easily. - 3. Submit a pull request with a link to your node(s) repo in GitHub against the `main` branch to add the node to the [Community Nodes](../../../workflows/community-nodes) list + 3. Submit a pull request with a link to your node(s) repo in GitHub against the `main` branch to add the node to the [Community Nodes](/features/workflows/community-nodes) list Make sure you are following the template below and have provided all relevant details about the node and what it does. Example output images and workflows are very helpful for other users looking to use your node. @@ -57,7 +57,7 @@ If a node that also runs the denoiser, VAE, or other session-GPU work is marked ### Community Node Template -Append the following template to your pull request and the [Community Nodes](../../../workflows/community-nodes) page when submitting a node to be added to the community nodes list: +Append the following template to your pull request and the [Community Nodes](/features/workflows/community-nodes) page when submitting a node to be added to the community nodes list: ```md --- diff --git a/docs/src/content/docs/development/Setup/dev-environment.mdx b/docs/src/content/docs/development/Setup/dev-environment.mdx index c4349961117..e233ffe35a9 100644 --- a/docs/src/content/docs/development/Setup/dev-environment.mdx +++ b/docs/src/content/docs/development/Setup/dev-environment.mdx @@ -101,7 +101,7 @@ This will allow you to avoid restarting the server (and reloading models) in mos The backend tests require the `test` dependency group, which you installed during the initial setup. -See the [Tests](../tests) documentation for information about running and writing tests. +See the [Tests](/development/guides/tests) documentation for information about running and writing tests. ## Frontend Development