-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: [es] Create docs/contributing/style-guide.md #6134
base: main
Are you sure you want to change the base?
Conversation
@krol3 All updated from my side, could you please review? TIA |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@krol3 All updated from my side, could you please review? TIA
Right, I'll be waiting for @krol3 or any @open-telemetry/docs-es-approvers to approve before I do a final review.
In the meantime, please address the GitHub build check(s) that are failing. In particular from https://github.com/open-telemetry/opentelemetry.io/actions/runs/13228099793/job/36923430459?pr=6134 you'll see these link failures to be fixed:
es/docs/contributing/pr-checks/index.html
hash does not exist --- es/docs/contributing/pr-checks/index.html --> ../style-guide/#opentelemetryio-word-list
hash does not exist --- es/docs/contributing/pr-checks/index.html --> ../style-guide/#markdown-standards
hash does not exist --- es/docs/contributing/pr-checks/index.html --> ../style-guide/#spell-checking
hash does not exist --- es/docs/contributing/pr-checks/index.html --> ../style-guide/#file-format
hash does not exist --- es/docs/contributing/pr-checks/index.html --> ../style-guide/#file-names
/fix:dict |
You triggered fix:dict action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/13229022742 |
IMPORTANT: (RE-)RUN
|
@mx-psi Hi, could you please review the Spanish content? Many thanks. |
- [Google Developer Guía de estilo de documentación](https://developers.google.com/style) | ||
- [Kubernetes Estilo de documentación](https://kubernetes.io/docs/contribute/style/style-guide/) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- [Google Developer Guía de estilo de documentación](https://developers.google.com/style) | |
- [Kubernetes Estilo de documentación](https://kubernetes.io/docs/contribute/style/style-guide/) | |
- [Guía de estilo de documentación de Google Developer](https://developers.google.com/style) | |
- [Guía de estilo de documentación de Kubernetes](https://kubernetes.io/docs/contribute/style/style-guide/) |
- [Google Developer Guía de estilo de documentación](https://developers.google.com/style) | |
- [Kubernetes Estilo de documentación](https://kubernetes.io/docs/contribute/style/style-guide/) | |
- [Google Developer Guía de estilo de documentación](https://developers.google.com/style) | |
- [Kubernetes Estilo de documentación](https://kubernetes.io/docs/contribute/style/style-guide/) |
Las siguientes secciones contienen orientación específica para el proyecto | ||
OpenTelemetry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Las siguientes secciones contienen orientación específica para el proyecto | |
OpenTelemetry. | |
Las siguientes secciones contienen indicaciones específicas para el proyecto | |
OpenTelemetry. |
Las siguientes secciones contienen orientación específica para el proyecto | |
OpenTelemetry. | |
Las siguientes secciones contienen orientación específica para el proyecto | |
OpenTelemetry. |
Muchos de los requisitos de nuestra guía de estilo se pueden aplicar mediante la | ||
ejecución de la automatización: antes de enviar un |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Creo que se puede hacer de forma algo más simplificada
Muchos de los requisitos de nuestra guía de estilo se pueden aplicar mediante la | |
ejecución de la automatización: antes de enviar un | |
Muchos de los requisitos de nuestra guía de estilo se pueden aplicar automáticamente: antes de enviar un |
[pull request](https://docs.github.com/en/get-started/learning-about-github/github-glossary#pull-request) | ||
(PR), ejecute `npm run fix:all` en su máquina local y confirme los cambios. | ||
|
||
Si se producen errores o [controles de PR fallidos](../pr-checks), lea nuestra |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Creo que queda algo más idiomático así
Si se producen errores o [controles de PR fallidos](../pr-checks), lea nuestra | |
Si se producen errores o [fallan las comprobaciones de su PR](../pr-checks), lea nuestra |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for your contributions, here some comments
@@ -0,0 +1,122 @@ | |||
--- | |||
title: Guía de estilo de documentación | |||
description: Terminología y estilo al escribir documentos de OpenTelemetry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
description: Terminología y estilo al escribir documentos de OpenTelemetry. | |
description: Terminología y estilo al escribir la documentación de OpenTelemetry. |
--- | ||
title: Guía de estilo de documentación | ||
description: Terminología y estilo al escribir documentos de OpenTelemetry. | ||
linkTitle: Estilo de documentación |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
linkTitle: Estilo de documentación | |
linkTitle: Guía de estilo |
Aún no tenemos una guía de estilo oficial, pero el estilo actual de la | ||
documentación de OpenTelemetry está inspirado en las siguientes guías de estilo: | ||
|
||
- [Google Developer Guía de estilo de documentación](https://developers.google.com/style) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- [Google Developer Guía de estilo de documentación](https://developers.google.com/style) | |
- [Guía de estilo de documentación para desarrolladores de Google](https://developers.google.com/style) |
documentación de OpenTelemetry está inspirado en las siguientes guías de estilo: | ||
|
||
- [Google Developer Guía de estilo de documentación](https://developers.google.com/style) | ||
- [Kubernetes Estilo de documentación](https://kubernetes.io/docs/contribute/style/style-guide/) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- [Kubernetes Estilo de documentación](https://kubernetes.io/docs/contribute/style/style-guide/) | |
- [Guía de estilo de Kubernetes](https://kubernetes.io/docs/contribute/style/style-guide/) |
|
||
{{% /alert %}} | ||
|
||
## OpenTelemetry.io lista de palabras |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
## OpenTelemetry.io lista de palabras | |
## Lista de palabras de OpenTelemetry.io |
Ejecute `npm run fix:markdown` para corregir problemas de formato relacionados | ||
con Markdown. | ||
|
||
## Corrección ortográfica |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
## Corrección ortográfica | |
## Revisión ortográfica |
@chalin @mx-psi Regarding the links checks failing, I'm not sure how to fix these. I'm always running fix all before pushing the changes but I see this doesn't fix it. Also the main doc: https://opentelemetry.io/docs/contributing/localization/ is not super clear about it. If you have some clear instructions how to fix this, please let me. Thank you for your support :) |
I am guessing these are the errors?
|
Indeed. |
Signed-off-by: Diana Todea <[email protected]>
Signed-off-by: Diana Todea <[email protected]>
Signed-off-by: Diana Todea <[email protected]>
Signed-off-by: Diana Todea <[email protected]>
Signed-off-by: Diana Todea <[email protected]>
Signed-off-by: Diana Todea <[email protected]>
Signed-off-by: Diana Todea <[email protected]>
Hi @didiViking. Let's consider this error:
It says that the file in the PR doesn't have an heading ID named
Some things are beyond the current capabilities of our fix commands. For example, our fix commands don't add heading IDs at the moment (though I'm thinking of doing so as soon as I can). I hope this helps clarify what is going on. |
Related issue: #5205