feat: contributing guidelines page

package.json

@@ -20,6 +20,7 @@
     "preview": "astro preview"
   },
   "dependencies": {
+    "@algora/sdk": "^0.2.0",
     "@astrojs/markdown-remark": "^5.0.0",
     "@astrojs/rss": "^4.0.5",
     "@astrojs/starlight": "^0.24.0",

src/components/AlgoraCards.astro

@@ -0,0 +1,20 @@
+---
+import { LinkCard } from '@astrojs/starlight/components'
+import { algora } from "@algora/sdk";
+
+const { items, next_cursor } = await algora.bounty.list.query({ org: "tauri-apps", limit: 10, status: "active"  });
+console.log(items)
+console.log(next_cursor)
+const bounties = [
+    {title:"[request] Broken links", description:"$250 000", href:""},
+    {title:"[docs] Migrate Distribute Debian Package", description:"$100 000", href:""},
+    {title:"Add Bun to command groups and make casing consistent", description:"$50 000", href:""}
+]
+---
+
+{
+    bounties.map((bounty) => (
+      <LinkCard title={bounty.title} description={bounty.description} href={bounty.href} />
+    ))
+}
+

src/content/docs/about/Contribute/Repositories/tauri-docs/index.mdx

@@ -0,0 +1,108 @@
+---
+title: tauri-docs
+sidebar:
+  label: Overview
+---
+
+# Contributing
+
+Welcome to Tauri Docs! We're excited to have you 🥳
+
+[![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/#https://github.com/tauri-apps/tauri-docs/tree/v2)
+[![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/tauri-apps/tauri-docs/tree/v2)
+
+There are a number of ways to get involved:
+
+- See if there are any [good first issues](https://github.com/tauri-apps/tauri-docs/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) that catch your eye
+- [Write a guide or recipe](#write-documentation)
+- [Translating existing documentation](#translations-i18n)
+
+Reach out to us on [Discord](https://discord.com/invite/tauri) on the [`#docs` channel](https://discord.com/channels/616186924390023171/662624589037436928) if you have any questions!
+
+## Getting Started
+
+1. Clone this repo
+2. Run `pnpm i`
+3. Run `pnpm dev` to start the local server
+
+### Gitpod
+
+[Allow Gitpod to open new tabs](https://www.gitpod.io/docs/configure/user-settings/browser-settings) so you immediately when the environment is done loading get a new tab popping up with the documentation.
+
+## Write Documentation
+
+We have the following types of documents that roughly follow the types defined by [Diátaxis](https://diataxis.fr/):
+
+- **[Guide](#guide)**: Learning-oriented
+- **[Recipe](#recipe)**: Task-oriented
+- **[Reference](#recipe)**: Information-oriented
+- **[Blog Post](#blog-post)**: Understanding-oriented
+
+Use this chart to help you figure out where the right place for your content is:
+
+| If the content describes… | …and serves the user's… | …then it must belong to…  |
+| ------------------------- | ----------------------- | ------------------------- |
+| practical steps           | study                   | [a guide](#guide)         |
+| practical steps           | work                    | [a recipe](#recipe)       |
+| theoretical knowledge     | work                    | [a reference](#reference) |
+| theoretical knowledge     | study                   | [a blog post](#blog-post) |
+
+### Writing for Prerelease
+
+While Tauri 2.0 is still in the prerelease stage people follow these guidelines for writing documentation:
+
+- Refer to Tauri 2.0 as if it's released now (so that copy doesn't need to be updated upon release)
+- Write any code so that it works **now** but...
+- Annotate 2.0 code with `{/* FIXME: 2.0 */}` (.mdx files) or `<!-- FIXME: 2.0 -->` (.md files) so that we can easily find and fix any of those upon release (feel free to add in what the code should be upon release in additional comments)
+
+### Writing Style
+
+**Dictionary**
+
+| Word     | Description                          |
+| -------- | ------------------------------------ |
+| app      | A Tauri app, prefer over application |
+| web view | Where the UI is rendered             |
+
+- Use an [oxford comma](https://www.grammarly.com/blog/what-is-the-oxford-comma-and-why-do-people-care-so-much-about-it/) in paragraphs, but not in headings and titles
+- Use [title case](https://apastyle.apa.org/style-grammar-guidelines/capitalization/title-case) for headings and titles
+- Make headings as succinct as possible to help the reader quickly find the content they need
+- Use [simple present tense](https://www.grammarly.com/blog/simple-present/) for verbs
+
+### Guide
+
+Located in [`/src/content/docs/2/guide/`](https://github.com/tauri-apps/tauri-docs/tree/starlight/src/content/docs/2/guide)
+
+Guides are learning-oriented and take the reader through a specific journey such as starting a new project, and overview of a specific feature, or how to follow a specific flow such as building and bundling their app. They follow a similar philosophy to [tutorials in Diátaxis](https://diataxis.fr/tutorials).
+
+The reader should be familiar with the concepts covered by the end of the guide and should set them up with the knowledge required to being experimenting with that topic themselves.
+
+### Recipe
+
+Located in [`/src/content/docs/2/recipe/`](https://github.com/tauri-apps/tauri-docs/tree/starlight/src/content/docs/2/recipe)
+
+Recipes are designed to guide the reader through a specific task similar and have a clear outcome and objective. This could be something like setting up authentication using Firebase, adding a Python binary using sidecar, or requesting admin access on a user's machine. They are similar to [how-to guides in Diátaxis](https://diataxis.fr/how-to-guides) (not to be confused with our own guides mentioned above).
+
+The prerequisites for a recipe should be clearly stated. If there are a lot of steps required before getting into the relevant information about the recipe then you may want to link out to another guide, recipe, or external resource and state those as a prerequisite at the top of the recipe.
+
+### Reference
+
+Located in [`/src/content/docs/2/reference/`](https://github.com/tauri-apps/tauri-docs/tree/starlight/src/content/docs/2/reference), although they should be auto-generated when possible.
+
+References are where all the nuts and bolts of Tauri's API are documented. These should be generated from upstream repos when possible and written following the best practices described by [references in Diátaxix](https://diataxis.fr/reference).
+
+These should be as succinct and to the point as possible so that the reader can quickly find the relevant information.
+
+If you'd like to view the API references locally then you must run `pnpm dev:setup` before `pnpm dev` to initialize all of the submodules. Now the `http://localhost:3000/2/reference/` routes are available to preview.
+
+### Blog Post
+
+Not yet created, will be added in the future.
+
+Topics that are around understanding something can be written as a blog post (we welcome submissions to the Tauri blog from anyone). Blog posts are a good option because they help the reader understand that information is accurate at the time of writing (and of course can always be updated later if it becomes stale). Blog posts follow the goals of [explanation in Diátaxis](https://diataxis.fr/explanation), but not all blog posts necessarily fit this specific format.
+
+## Translations (i18n)
+
+Thanks for your interest in helping to translate the documentation! Visit the [translation status page](https://v2.tauri.app/contribute/translate-status) to see which docs are ready for translation, need updated, or need reviewed.
+
+Read the [Translating Guide](./TRANSLATING.md) for more information.

src/content/docs/about/Contribute/Repositories/tauri-docs/translate.mdx

@@ -0,0 +1,3 @@
+---
+title: Translate
+---

src/content/docs/about/Contribute/Repositories/tauri/index.mdx

@@ -0,0 +1,91 @@
+---
+title: tauri
+sidebar:
+  label: Overview
+---
+
+# Tauri Contributing Guide
+
+Hi! We, the maintainers, are really excited that you are interested in contributing to Tauri. Before submitting your contribution though, please make sure to take a moment and read through the [Code of Conduct](CODE_OF_CONDUCT.md), as well as the appropriate section for the contribution you intend to make:
+
+- [Issue Reporting Guidelines](#issue-reporting-guidelines)
+- [Pull Request Guidelines](#pull-request-guidelines)
+- [Development Guide](#development-guide)
+
+## Issue Reporting Guidelines
+
+- The issue list of this repo is **exclusively** for bug reports and feature requests. Non-conforming issues will be closed immediately.
+
+- If you have a question, you can get quick answers from the [Tauri Discord chat](https://discord.gg/SpmNs4S).
+
+- Try to search for your issue, it may have already been answered or even fixed in the development branch (`dev`).
+
+- Check if the issue is reproducible with the latest stable version of Tauri. If you are using a pre-release, please indicate the specific version you are using.
+
+- It is **required** that you clearly describe the steps necessary to reproduce the issue you are running into. Although we would love to help our users as much as possible, diagnosing issues without clear reproduction steps is extremely time-consuming and simply not sustainable.
+
+- Use only the minimum amount of code necessary to reproduce the unexpected behavior. A good bug report should isolate specific methods that exhibit unexpected behavior and precisely define how expectations were violated. What did you expect the method or methods to do, and how did the observed behavior differ? The more precisely you isolate the issue, the faster we can investigate.
+
+- Issues with no clear repro steps will not be triaged. If an issue labeled "need repro" receives no further input from the issue author for more than 5 days, it will be closed.
+
+- If your issue is resolved but still open, don't hesitate to close it. In case you found a solution by yourself, it could be helpful to explain how you fixed it.
+
+- Most importantly, we beg your patience: the team must balance your request against many other responsibilities — fixing other bugs, answering other questions, new features, new documentation, etc. The issue list is not paid support and we cannot make guarantees about how fast your issue can be resolved.
+
+## Pull Request Guidelines
+
+- You have to [sign your commits](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits).
+
+- It's OK to have multiple small commits as you work on the PR - we will let GitHub automatically squash it before merging.
+
+- If adding new feature:
+
+  - Provide convincing reason to add this feature. Ideally you should open a suggestion issue first and have it greenlighted before working on it.
+
+- If fixing a bug:
+  - If you are resolving a special issue, add `(fix: #xxxx[,#xxx])` (#xxxx is the issue id) in your PR title for a better release log, e.g. `fix: update entities encoding/decoding (fix #3899)`.
+  - Provide detailed description of the bug in the PR, or link to an issue that does.
+
+## Development Guide
+
+**NOTE: If you have any question don't hesitate to ask in our Discord server. We try to keep this guide to up guide, but if something doesn't work let us know.**
+
+### General Setup
+
+First, [join our Discord server](https://discord.gg/SpmNs4S) and let us know that you want to contribute. This way we can point you in the right direction and help ensure your contribution will be as helpful as possible.
+
+To set up your machine for development, follow the [Tauri setup guide](https://tauri.app/v1/guides/getting-started/prerequisites/) to get all the tools you need to develop Tauri apps. The only additional tool you may need is [Yarn](https://yarnpkg.com/), it is only required if you are developing the Node CLI or API packages (`tooling/cli/node` and `tooling/api`). Next, fork and clone this repo. It is structured as a monorepo, which means that all the various Tauri packages are under the same repository. The development process varies depending on what part of Tauri you are contributing to, see the guides below for per-package instructions.
+
+Some Tauri packages will be automatically built when running one of the examples. Others, however, will need to be built beforehand. To build these automatically, run the `.scripts/setup.sh` (Linux and macOS) or `.scripts/setup.ps1` (Windows) script. This will install the Rust and Node.js CLI and build the JS API. After that, you should be able to run all the examples. Note that the setup script should be executed from the root folder of the repository in order to run correctly.
+
+### Overview
+
+See [Architecture](../ARCHITECTURE.md#major-components) for an overview of the packages in this repository.
+
+### Developing Tauri Bundler and Rust CLI
+
+The code for the bundler is located in `[Tauri repo root]/tooling/bundler`, and the code for the Rust CLI is located in `[Tauri repo root]/tooling/cli`. If you are using your local copy of `@tauri-apps/cli` (see above), any changes you make to the bundler and CLI will be automatically built and applied when running the build or dev command. Otherwise, running `cargo install --path .` in the Rust CLI directory will allow you to run `cargo tauri build` and `cargo tauri dev` anywhere, using the updated copy of the bundler and cli. You will have to run this command each time you make a change in either package.
+
+### Developing The Node.js CLI (`@tauri-apps/cli`)
+
+`@tauri-apps/cli` is a wrapper to `tauri-cli` so most changes should be written on the Rust CLI. The `[Tauri repo root]/tooling/cli/node` folder contains only packaging scripts to properly publish the Rust CLI binaries to NPM.
+
+### Developing Tauri Core and Related Components (Rust API, Macros, Codegen, and Utils)
+
+The code for the Rust crates, including the Core, Macros, Utils, WRY runtime, and a few more are located in `[Tauri repo root]/core/tauri-(macros/utils)`. The easiest way to test your changes is to use the `[Tauri repo root]/examples/helloworld` app. It automatically rebuilds and uses your local copy of the Tauri core packages. Just run `cargo run --example helloworld` after making changes to test them out.
+
+#### Building the documentation locally
+
+You can build the Rust documentation locally running the following script:
+
+```bash
+$ RUSTDOCFLAGS="--cfg docsrs" cargo +nightly doc --all-features --open
+```
+
+### Developing the JS API
+
+The JS API provides bindings between the developer's JS in the Webview and the builtin Tauri APIs, written in Rust. Its code is located in `[Tauri repo root]/tooling/api`. After making changes to the code, run `yarn build` to build it. To test your changes, we recommend using the API example app, located in `[Tauri repo root]/examples/api`. It will automatically use your local copy of the JS API and provides a helpful UI to test the various commands.
+
+## Financial Contribution
+
+Tauri is an MIT-licensed open source project. Its ongoing development can be supported via [GitHub Sponsors](https://github.com/sponsors/tauri-apps) or [Open Collective](https://opencollective.com/tauri). We prefer GitHub Sponsors as donations made are doubled through the matching fund program.

src/content/docs/about/Contribute/bounties.mdx

@@ -0,0 +1,33 @@
+---
+title: Bounties
+tableOfContents:
+  minHeadingLevel: 2
+  maxHeadingLevel: 5
+---
+
+import AlgoraCards from '@components/AlgoraCards.astro'
+import {Steps} from '@astrojs/starlight/components'
+
+
+Help the community by resolving issues they consider worthy of a cash price!
+
+<Steps>
+1. ##### Create an account at Algora.io
+   Tauri has chosen to utilize Algora.io in order to provide this bounty feature. In order to claim your reward you must [create an account on their platform](https://console.algora.io/).
+
+1. ##### Find an issue you want to work on
+   You can either check the list below or [visit Algora.io directly](https://console.algora.io/org/tauri-apps/bounties).
+
+   Remember to check both the official bounties as well as the community bounties [here](https://console.algora.io/org/tauri-apps/bounties/community).
+
+1. ##### Write the code!
+   Bounties are collected by opening pull requests and getting them merged.
+</Steps>
+
+## Official
+
+<AlgoraCards />
+
+## Community
+
+<AlgoraCards />