Usar plantilla de tema predeterminada para características y errores

Contribuir Comentarios del sitio
1

Hola,

desde que aprendí aquí que las categorías ya proporcionan plantillas de temas, me gustaría sugerir su uso para las categorías Contribute > Feature y Contribute > Bug aquí en meta.discourse.org.

No estoy seguro del todo sobre su formato, así que simplemente tomé una plantilla de incidencia de Github de Icinga y la modifiqué un poco para Discourse.

Contexto

Por mi experiencia, no siempre queda lo suficientemente claro sobre qué problema estamos hablando realmente. El juego del “ping-pong” para descubrir el entorno, las posibles herramientas involucradas e ideas que solo existen en la “mente” del usuario consume tiempo y a veces es agotador.

Podría imaginar que una plantilla de tema predeterminada como esta podría ayudar aquí, para recordar a los usuarios qué detalles son importantes o cómo dar formato general a su “historia”.

En general, prefiero el uso de capítulos y encabezados al describir un problema. Esto permite que todos sigan el hilo y seleccionen los detalles relevantes. Especialmente el contexto y la información adicional sobre versiones e insights específicos del navegador ayudan mucho.

Una cosa que resulta complicada con la plantilla es que a veces no se entiende cómo funcionan los comentarios HTML y por qué se ocultan en la vista principal. Aunque he visto a muchos usuarios simplemente adoptarla y dejarla tal cual.

Ejemplo

<!--- Provide a general summary of the issue in the Title above -->

<!-- Please make sure to read https://meta.discourse.org/t/how-to-request-new-features-for-discourse/32986?source_topic_id=11 first -->

## Expected Behavior
<!--- If you're describing a bug, tell us what should happen -->
<!--- If you're suggesting a change/improvement, tell us how it should work -->

## Current Behavior
<!--- If describing a bug, tell us what happens instead of the expected behavior -->
<!--- If suggesting a change/improvement, explain the difference from current behavior -->

## Possible Solution
<!--- Not obligatory, but suggest a fix/reason for the bug, -->
<!--- or ideas how to implement:  the addition or change -->

## Steps to Reproduce (for bugs)
<!--- Provide a link to a live example, or an unambiguous set of steps to -->
<!--- reproduce this bug. Include configuration, logs, etc. to reproduce, if relevant -->
1.
2.
3.
4.

## Context
<!--- How has this issue affected you? What are you trying to accomplish? -->
<!--- Providing context helps us come up with a solution that is most useful in the real world -->

## Your Environment
<!--- Include as many relevant details about the environment you experienced the problem in -->
* Version used (Admin - Dashboard):
* Enabled plugins (Admin - Plugins):
* Browser name and version:
* Developer tools errors:
2 Me gusta
2

Topic templates aren’t particularly effective in my experience – they are certainly no magic bullet. The type of people you would want to read them, rarely do, and for those that know what they are doing, they get in the way.

I would only do this if there are certain very mandatory things you need in each topic, like serial number or something.

3 Me gusta
3

Hi,

I get your point, the many who feel disturbed by such a template will just ctrl+a&del the content. I do that sometimes as well, when the structure doesn‘t fit.

I know too little about this community til now. From reading threads I‘d say you do not really need it, as this platform has a totally different conversation “flow” and is more a chat than issue discussions. I love to hear what others think, and won‘t be sad if you do not apply it :slight_smile:

Still, I hope such a template helps others who might have been looking into the same for their setup. It took me quite a while to find the perfect template for github, you likely have only one shot amongst established readers :wink:

Cheers,
Michael