TWE: Dev: Design System: Create Snackbar

未关闭
  • 哪里不对？
#827 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
65/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
css, html, markdown, sass, scss, yaml
领域
design, documentation, frontend

调研方向

先从 Snackbar 微站页面 mockup 和 Material Design Kit 开始，然后查看 CONTRIBUTING.md、mkdocs.yml 以及 /docs/components/sass/components 中的现有文件。将 /docs/snackbar.md 和 /docs/components/sass/components/_snackbar.scss 作为预期的入口点，并在实现前检查变量文件和 JavaScript 指南。组件页面、样式、所需的 token 和状态、代码链接以及与 Figma 的连接均完成文档记录并在 PR 中提交后，即可视为完成。

由索引模型根据 Issue 内容生成。

描述

complexity: medium feature: board / google drive / tools feature: design system Participant Type: TWE Team Member role: engineering size: 2pt
Dependencies

#464

Overview

We need to create Design System Snackbar 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)
  • Review the Material Design Kit and identify the relevant component, variants, and states (Resource 1.13)
  • Review Code Standards before starting implementation
  • Name the Branch you create snackbar
  • Determine if any JavaScript needs to be included to style this component (see Resource 1.02 for examples of included JavaScript). If you do need to use JS, don't forget to update the wiki page
  • Include necessary files in the /docs folder (Resource 1.03) and project config file mkdocs.yml (Resource 1.04)
  • Determine what tokens are needed for this component
    • Reuse existing tokens where possible
    • Add new tokens only if necessary
  • 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 tokens as necessary, reusing existing tokens where possible; add new color tokens only if required and name them using HTML Color Code conventions (Resources 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: [snackbar.md] - link the name to the file in the repo
  • 2.02 SASS file(s) created: [snackbar.scss] - link the name to the file in the repo
  • 2.03 link to Header Microsite page on live site: [Snackbar] (Replace with - link to the live URL If the site is live when this issue is worked on.
主要语言
CSS
星标
20
派生
6
30 天内没有已合并 PR

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

hackforla/internship 的其他 Issue

查看 hackforla/internship 的全部 Issue

相似的 Issue

更多 Design Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。