hackforla / hackforla/knowledgebase-content

Create a Guide/Template: Website Style Guide and Design System

Abierto
#75 4 comentarios 0 reacciones 0 asignados Ver en GitHub
Complexity: Missing CoP label: checked CoP: Content CoP: Design CoP: Product dependency feature : guide creation milestone: missing Phase: 1 - Gather Examples Solo Ready for Bonnie Triage size: missing status: 1.1 needs wiki examples status: 1.2 needs issues examples status: 1.3 needs project board examples status: 1.4 needs slack examples
Lenguaje dominante
Sin datos de lenguaje
Estrellas
2
Forks
1
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

### Dependency
- [ ] When the Internship team is done making a universal design system

### Details
This guide will be a getting started guide on how to interact with the universal project design system and will probably have sub guides
- How to create a publishable Style Guide from the design system
- with examples from
- TDM Calculator
- Get Your Refund
- https://github.com/hackforla/knowledgebase-content/issues/94

### Overview
Product Managers, Designers and Developers need a style guide to make sure the website created is consistent.

### Action Items
The phases in the guide-making process are listed below. Each phase displayed in blue is linked to a wiki page with instructions on how to complete that phase. Open the wiki page in a new tab, copy the instructions for each part into the section labeled 'Tasks' at the bottom of this issue, and complete each task listed.
- [ ] [Gather Examples Solo](https://github.com/hackforla/guides/wiki/How-to-Gather-Examples:-Solo) (open in a new tab)
- [ ] [Gather Examples Collaboratively](https://github.com/hackforla/guides/wiki/Phase-2-%E2%80%90-Gather-Examples-Collaboratively)
- [ ] [Create a Guide Draft](https://github.com/hackforla/guides/wiki/How-to-Draft-a-Guide)
- [ ] If needed, create a template
- [ ] [Have your guide peer reviewed](https://github.com/hackforla/guides/wiki/Peer-Reviews-for-Guides)
- [ ] [Present your guide for leadership review](https://github.com/hackforla/guides/wiki/Submitting-Your-Guide-for-Leadership-Review)
### Resources/Instructions

- Google Drive Folder for this Guide’s documents and shortcuts (to documents in other locations) [0075 [DRAFT] Website Style Guide and Design System](https://drive.google.com/drive/folders/1dBFdq3hm5TygkHS56PCMi1l_sc7qjWKa)
- [HackforLA.org Style Guide and Design System example](https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website?node-id=3464%3A3)
- [100 Automations](https://www.figma.com/file/zGyhV8Z6sLohatYAnFoxQm/100Automations-Project-Board?node-id=243%3A363)

### Projects to Check
This issue has been replaced with the design systems team efforts and issue # https://github.com/hackforla/design-systems/issues/109

### Tasks
- [ ] This is where you will copy instructions from the wiki page for the step you are currently on.

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

No empieces este issue: indica que el trabajo ha sido reemplazado por el trabajo del equipo de sistemas de diseño en el issue #109. Si revisas el alcance original, empieza por la dependencia vinculada del sistema de diseño universal y, después, consulta las fases de la wiki indicadas y la carpeta de Google Drive y los ejemplos de Figma. Para darlo por terminado habría sido necesario contar con una guía revisada y aprobada por el liderazgo, pero el issue no proporciona una vía de implementación activa.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Área
documentation
Tipo de issue
Documentación
Dificultad
5/5
Tiempo estimado
Más de una semana
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
15/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.