Skip to content

Commit

Permalink
fix: use correct urls
Browse files Browse the repository at this point in the history
  • Loading branch information
Darkflame72 committed Dec 12, 2024
1 parent 64ea17a commit ea90653
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion src/content/docs/tuhura-tech/contribute.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ Modifying existing content is straightforward as it can be done through the GitH

Adding new content is a bit more involved then modifying new content as you have to create the required folder if needed and then add the new files into `astro.config.mjs`.

Check out the [Style Guide](../style) for contribution style best practices
Check out the [Style Guide](/tuhura-tech/style) for contribution style best practices

<details>
<summary>Adding new <ins>tutorial</ins> content...</summary>
Expand Down
6 changes: 3 additions & 3 deletions src/content/docs/tuhura-tech/style.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ There are two main types of contributions you'd be wanting to make:
Depending on what you're adding, some things will change, but we'll cover everything!

:::note[Getting set up]
For more information on how to get set up to contribute, take a look at the [Contribute doc](../contribute)
For more information on how to get set up to contribute, take a look at the [Contribute doc](/tuhura-tech/contribute)

Also take a look at the [Contribution Manual](https://github.com/Tuhura-Tech/wiki/blob/main/CONTRIBUTING.md) on our Github.
:::
Expand All @@ -45,7 +45,7 @@ One of the best approaches to writing this kind of material is the [Diátaxis ap
In most of our resources, we're taking the **Tutorial approach** as outlined by Diátaxis. This means that the learner, the person engaging with your resource, should learn through **Doing.** They should come out the other end with something they've **Made** with your resource serving to guide them through the process of this creation.
However, we should never be withholding information under the guise of the reader "Figuring it out themselves." Our role as resource creators is to provide a structured and safe environment for the reader to learn and create. Often even identifying potential mistakes or pitfalls the reader could encounter, and addressing them in the tutorial.

You'll also find **Reference** style pages on the wiki (Such as the page on [Classes and object oriented programming](../../python/classes)) Which contain direct, clear and referenceable information about a particular topic.
You'll also find **Reference** style pages on the wiki (Such as the page on [Classes and object oriented programming](/python/classes)) Which contain direct, clear and referenceable information about a particular topic.

You may even find pages that fit best under the **How-To guide** category (This page for example) or the **Explanation** category!

Expand Down Expand Up @@ -345,4 +345,4 @@ Take a look at other pages on the wiki, and see how they work! Remember, changin

If you have any questions about contributing, or need help with anything, everyone in [our Discord](https://discord.com/invite/PNxh7cwKfQ) would be more than happy to give you some pointers!

Also remember to read the documentation! The [Starlight](https://starlight.astro.build/) and [Astro docs](https://docs.astro.build/en/getting-started/) have a ton of information about how to build wiki pages.
Also remember to read the documentation! The [Starlight](https://starlight.astro.build/) and [Astro docs](https://docs.astro.build/en/getting-started/) have a ton of information about how to build wiki pages.

0 comments on commit ea90653

Please sign in to comment.