Skip to content

TWE: Dev: Design System: Create Typography #742

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

Open
19 tasks
joshfishman opened this issue May 7, 2025 · 2 comments
Open
19 tasks

TWE: Dev: Design System: Create Typography #742

joshfishman opened this issue May 7, 2025 · 2 comments

Comments

@joshfishman
Copy link
Member

Dependencies

[Find the dependency from this table https://github.com//issues/455#issuecomment-2057437256 and replace this text with the link to the issue in a bullet]

Overview

We need to create Design System Typography Component HTML and SASS / connect Figma design to finished code, and build microsite page so that developers can see and easily change component examples, states, code and location.

Assumptions

Action Items

  • Review the Microsite page mockup you will be working from (Resource 1.01)
  • Name the Branch you create Typography
  • Determine if any JS or CSS hacks need to be included to style this component (see Resource 1.02 for examples of prior hacks). If you need to use a hack, don't forget to update the examples.
  • Include necessary files in the /docs folder (Resource 1.03) and project config file mkdocs.yml (Resource 1.04)
  • Determine what variables are needed for this component and add them to variables.scss (Resource 1.05)
  • Code Microsite component page
    • file locations
      • md file goes into the /docs folder (Resource 1.03)
      • SASS file goes into the /docs/components/sass/components folder (Resource 1.06)
    • Create variables in sass sheet as necessary, add color varialbles with name determined by HTML Color Codes (Resource 1.07, 1.08)
    • Create component classes and states within the page
    • Include Files via code snippets to create the code section (see Resource 1.09 for details)
    • Add links to SASS and Markdown files below the code (see examples in Resource 1.10)
  • Review template frontend for errors
  • Make a PR
  • Once PR is merged
    • connect component in Figma to GitHub Files (Resource 1.10)
    • Add links to Resources gathered during the completion of this issue section
      • 2.01 MD file(s) created
      • 2.02 SASS file(s) created
      • 2.03 link to Header Microsite page on live site: If the site is live when this issue is worked on.

Resources

Resources for working on this issue

Resources gathered during the completion of this issue

  • 2.01 MD file(s) created: [Typography.md] - link the name to the file in the repo
  • 2.02 SASS file(s) created: [Typography.scss] - link the name to the file in the repo
  • 2.03 link to Header Microsite page on live site: Typography(Replace with - link to the live URL If the site is live when this issue is worked on.
@ExperimentsInHonesty
Copy link
Member

@bryanherrera72 I removed you from this issue, because it's in the new issue approval column and is not ready for prioritization.

@ExperimentsInHonesty ExperimentsInHonesty added draft ready for dev lead and removed Ready for product When the issue is ready for product team to review labels May 8, 2025
@ExperimentsInHonesty
Copy link
Member

@joshfishman The dependency on this issue has not been cleaned up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: New Issue Approval
Development

No branches or pull requests

4 participants