---
# System prepended metadata

title: 'Tauri Docs 2.0: 15 Aug 2023'

---

# Tauri Docs 2.0: 15 Aug 2023

## Agenda

- Started getting some community PRs into `next` already:
    - [We captured a PR from the Astro maintainers](https://github.com/tauri-apps/tauri-docs/pull/1381)
    - [Gentoo Linux dependency fix](https://github.com/tauri-apps/tauri-docs/pull/1385)
    - [Migration guide plugin fix](https://github.com/tauri-apps/tauri-docs/pull/1383)
- i18n update from @DK Liao (below): https://github.com/tauri-apps/tauri-docs/pull/1393
    - @lorenzo-lewis: I also [talked to the Astro peeps](https://discord.com/channels/830184174198718474/1139489973708529755) about turning the i18n dashboard builder into a package/action and they're working on that as a side project :eyes: 
    - @DK to run a test PR
- Where do we want to point people to for plugins? (below)
- Features, Recipes, and sidebar revision (below)
- Can we push the [Notification Guide PR](https://github.com/tauri-apps/tauri-docs/pull/1379) through for the next round of feedback/revisions?
- @Simon: show off `rustdoc-json` output
    - @Simon Going to open a PR to look through the implementation
- @Simon: show off `3d-hero` and briefly discuss choice of 3D framework (three.js vs zdog vs babylon vs something else) and possibly adding mermaid.js
- @lorenzo-lewis Index page game plan
    - @Alve had a good point about identifying the personas and users and what's important to them. Can Alve help get this together?
- 1.0 docs issue triage and priority?
    - Will talk through next time

## Action Items

- @DK to to a trial run for a translation PR
- @Simon to open a draft PR to let us see the `rustdoc-json` approach he walked through
- @Simon to continue on the Notification PR for the next iteration
- @Alve to start some user personas to guide us through the index page design process
- @Lorenzo going to talk to upstream about a way to show "outdated" translations inline in the docs
- @Lorenzo to loop in Security for feedback on commit signing in docs
- @Lorenzo going to update the git module for the plugins (`v2`)

## i18n 
- Allow partial translation? Or full translation only?
    - Encouraging a translation fork and merge a full page pull request only?
        - Can the i18n dashboard support partial translation?
        - Talk through ideas upstream to see about partial translations, but only accept full translations for now
    - If partial translation is allowed, then how do we handle it?
    - @lorenzo-lewis talk to upstream about a way to highlight "outdated translations"
- Is it possible to setup a per language terminology file to help with the translation consistency?
    - Would definitely help but then again we didn't actually use it in back in Crowdin and seems fine.....?
    - Build this as we need in the i18n guide
- From Lorenzo: Do we require commit signing?
    - What does signing give us that's valuable in docs?
    - Also need to consider this could be distributed via a Docs app
    - Also thinking about Gitpod, Codespaces, etc.
    - Lorenzo to prod Chip and Tillmann on this
- i18n style guide? Or Style Guide in general?
    - Per Lorenzo's suggestion, probably a separate Style Guide, but then some i18n specific guide here linked out to the Style Guide (if applicable)

## Plugin Landing Pages

- Docs site as primary place? `2/guide/authenticator`
- From docs page we can link to the repo, npm, cargo, etc.
- What repo/branch do we point people to for plugins?
    - point to monorepo, point to `v2` branch (@lorenzo update the git modules)
- I don't think I want to copy/paste the READMEs, I'd rather be more flexible to keep things in docs so we can update/revise as we get feedback.

**Inspo:**

https://docs.astro.build/en/guides/integrations-guide/svelte/

![](https://hackmd.io/_uploads/S1ataTw23.png)

## Features, Recipes, and Sidebar Revision

[PR](https://github.com/tauri-apps/tauri-docs/pull/1390) - [Deploy Preview](https://deploy-preview-1390--tauri-docs-starlight.netlify.app/2/guide/) - [Simon's original HackMD](https://hackmd.io/Yfh1J9chQkuBDl224cQv7g)

- Move `recipe` to be under the `guide` directory/slug
    - Hoping that makes it easier to understand that recipes are build ON TOP of existing guides/features?
- **Workflow** / Lifecycle (section name?)
    - Contains:
        - Develop
        - Debug
        - Test
        - Build
        - Distribute
        - Treat each as a "landing" page and revise to see which categories make the most sense
- Revise `reference` routes/sidebar:
    - Contains:
        - Tauri CLI
        - Tauri Config
        - JavaScript API (index for all packages/plugins)
        - Rust API (index for all packages/plugins)
    - Sounds like plan
- Features & Recipes
    - Contains:
        - List of Features & Recipes
        - Authenticator
        - Autostart
        - etc.
---

# Get Involved

1. First, read the contributor's guide on the `next` branch: https://github.com/tauri-apps/tauri-docs/blob/next/.github/CONTRIBUTING.md#write-documentation
2. Next, check the [Roadmap issue](https://github.com/tauri-apps/tauri-docs/issues/1344) for a higher-level understanding of the current status and see if there's anything you're interested in.
3. Lastly, check the [2.0 doc issues](https://github.com/tauri-apps/tauri-docs/issues?q=is%3Aopen+is%3Aissue+label%3A%22tauri+2.0+docs%22) and feel free to jump in and contribute there

Feel free to ask any questions in Discord in the `#docs` channel.

---