tauri-apps / tauri-apps/tauri-docs
Refactor components into fragments where possible
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 1.1k
- Forks
- 887
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 48
Description
For ease of use and i18n reasons we'd prefer using markdown files over Astro components as much as possible. This task is related to going through pages to find instances of us having used components where fragments could be used instead, usually identified by the lack of functionality added, purely visual components.
This should not be worked on before 2.0 stable is done!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Do not start until the 2.0 stable release is complete. Review the documentation pages for purely visual Astro components and identify where markdown files or fragments can replace them without losing functionality or i18n support; no specific files or tests are named, so completion requires reviewing the relevant pages and confirming the replacements work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- documentation
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100