Skip to content
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

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

Closed
7 tasks
ExperimentsInHonesty opened this issue Dec 23, 2020 · 3 comments
Closed
7 tasks
Labels
Complexity: Missing CoP: Product feature : guide creation milestone: missing Phase: 1 - Gather Examples Solo size: missing status: 1.1 needs wiki examples Gathering examples by checking each team's wiki status: 1.2 needs issues examples Gathering examples by checking each team's issues status: 1.3 needs project board examples Gathering examples by checking each team's project board cards status: 1.4 needs slack examples Check each team's slack channel for examples

Comments

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Dec 23, 2020

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.

Resources/Instructions

HackforLA.org Style Guide and Design System example
100 Automations

Projects to Check

This issue has been replaced with the design systems team efforts and issue # hackforla/design-systems#109

Tasks

  • This is where you will copy instructions from the wiki page for the step you are currently on.
@ExperimentsInHonesty
Copy link
Member Author

This issue has been replaced with the design systems team efforts and issue # hackforla/design-systems#109

@fchan218
Copy link
Member

fchan218 commented Oct 9, 2024

Prior version of issue

Overview

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

Action Items

  • Review the existing examples project Style Guides and Design Systems
  • Create your version in your project's figma
  • add a link to your Communication Guide to list of Work in Progress versions below
  • Review with Bonnie Design Systems team and revise as appropriate based on notes
  • Finalize Guide and move link to finished resources

Resources

Finished

Work in Progress

HackforLA.org Style Guide and Design System example
100 Automations

@fchan218
Copy link
Member

fchan218 commented Oct 9, 2024

Assignee, Labels, Project Board Placement, and Milestones for this issue in the Product Repo:

Screenshot 2024-10-09 at 5 06 21 PM

@fchan218 fchan218 transferred this issue from hackforla/product-management Oct 16, 2024
@fchan218 fchan218 added Phase: 1 - Gather Examples Solo status: 1.1 needs wiki examples Gathering examples by checking each team's wiki status: 1.3 needs project board examples Gathering examples by checking each team's project board cards status: 1.2 needs issues examples Gathering examples by checking each team's issues status: 1.4 needs slack examples Check each team's slack channel for examples size: missing milestone: missing Complexity: Missing labels Oct 16, 2024
@fchan218 fchan218 moved this to Needs to be Triaged in P: Guides: Knowledgebase Content Tracker Oct 25, 2024
@fchan218 fchan218 changed the title Create a Guide: Website Style Guide and Design System Create a Guide/Template: Website Style Guide and Design System Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Missing CoP: Product feature : guide creation milestone: missing Phase: 1 - Gather Examples Solo size: missing status: 1.1 needs wiki examples Gathering examples by checking each team's wiki status: 1.2 needs issues examples Gathering examples by checking each team's issues status: 1.3 needs project board examples Gathering examples by checking each team's project board cards status: 1.4 needs slack examples Check each team's slack channel for examples
Projects
Status: Needs to be Triaged
Status: Needs to be Triaged
Development

No branches or pull requests

4 participants