Skip to content

docs: fix broken links in developer guides #9638

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
pratikgx wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: fix broken links in developer guides #9638

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/src/content/docs/development/Guides/creating-node-pack.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
4 changes: 2 additions & 2 deletions docs/src/content/docs/development/Guides/creating-nodes.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down Expand Up @@ -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
---
Expand Down
2 changes: 1 addition & 1 deletion docs/src/content/docs/development/Setup/dev-environment.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
Loading