mirror of
https://github.com/blakeblackshear/frigate.git
synced 2026-05-06 05:27:44 +03:00
fix docs formatting
This commit is contained in:
parent
d75e04a378
commit
27fec3dbbe
@ -13,7 +13,7 @@ The community support boards framework allows a user in the community to be the
|
|||||||
|
|
||||||
## Getting Started
|
## Getting Started
|
||||||
|
|
||||||
1. Follow the steps from [the main contributing docs](development/contributing.md).
|
1. Follow the steps from [the main contributing docs](/development/contributing.md).
|
||||||
2. Create a new build type under `docker/`
|
2. Create a new build type under `docker/`
|
||||||
3. Get build working as expected, all board-specific changes should be done inside of the board specific docker file.
|
3. Get build working as expected, all board-specific changes should be done inside of the board specific docker file.
|
||||||
|
|
||||||
|
|||||||
@ -243,6 +243,6 @@ If you'd like to contribute translations to Frigate, please follow these steps:
|
|||||||
1. Fork the repository and create a new branch specifically for your translation work
|
1. Fork the repository and create a new branch specifically for your translation work
|
||||||
2. Locate the localization files in the web/public/locales directory
|
2. Locate the localization files in the web/public/locales directory
|
||||||
3. Add or modify the appropriate language JSON files, maintaining the existing key structure while translating only the values
|
3. Add or modify the appropriate language JSON files, maintaining the existing key structure while translating only the values
|
||||||
4. Ensure your translations maintain proper formatting, including any placeholder variables (like {{example}})
|
4. Ensure your translations maintain proper formatting, including any placeholder variables (like `{{example}}`)
|
||||||
5. Before submitting, thoroughly review the UI
|
5. Before submitting, thoroughly review the UI
|
||||||
6. When creating your PR, include a brief description of the languages you've added or updated, and reference any related issues
|
6. When creating your PR, include a brief description of the languages you've added or updated, and reference any related issues
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user