hackforla / hackforla/knowledgebase-content
Create a Guide/Template: Effective Practices for working with developers
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 2
- Forks
- 1
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
### Overview
We need to create a guide about effective practices for designers working with developers for designers to reference and learn from, and to promote smooth communication and collaboration between design and development on Hack for LA teams.
### Action Items
- [x] Research existing information about effective communication between designers and developers in relevant resources, online articles, etc.
- [x] Once done, remove the "Guide: Research" label and add the "Guide: Gather Examples" label
- [x] Gather examples of effective practices from other projects during a community of practice brainstorming session
- [x] Once done, remove the "Guide: Gather Examples" label and add the "Guide: Draft Guide" label
- [x] Create a draft guide, either in markdown format in this issue or a google doc in the [ux/ui google drive]
- [x] Once done, remove the "Guide: Draft Guide" label and add the "Guide: Review Guide" label
- [x] Review the guide with UX/UI community of practice
- [x] Once done, remove the "Guide: Review Guide" label and add the "Guide: Leadership Review" label
- [x] Present to the Hack for LA leadership team for sign off
- [x] Once approved, remove the "Guide: Leadership Review" label and add the "Guide: Place Guide" label
### Resources
Update issue hackforla/knowledgebase-content#97 with the name of item you are working on
Guide: [Developers & Designers: Effective Communication Practices Guide](https://docs.google.com/document/d/1YlACBPOXVzFyrk1vCwXyC9ylp5KwATJ2NlR5VlMpk6Y/edit)
Guía de contribución
Línea de trabajo
Revisa primero la “Developers & Designers: Effective Communication Practices Guide” enlazada y el issue #97 de knowledgebase-content al que se hace referencia. Confirma el estado actual de la guía y si queda pendiente alguna ubicación o seguimiento; el trabajo estará terminado cuando la guía aprobada esté disponible en la ubicación prevista de la base de conocimiento del proyecto.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Área
- content, documentation
- Tipo de issue
- Documentación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 20/100