hackforla
Create a Guide: Figma Effective Practices
Overview
We need to create a guide to how to use emojis, indentation and coversheet in your figma file so that it is easy for team members to find what they are looking for.
Action Items
- [ ] Gather examples of how other Hack for LA projects have done, adding each example as a link in the resources section
- [ ] Once done, remove the "TG: Gather Examples" label and add the "TG: Draft Template" label
- [ ] Create a draft template, either in markdown format in this issue or a google doc in the ~old product management google drive~ new product management google drive>Product Management Guides
- [ ] Once done, remove the "TG: Draft Template" label and add the "TG: Create Guide" label
- [ ] Create a guide on how to use the template
- [ ] Once done, remove the "TG: Create Guide" label and add the "TG: Review Guide" label
- [ ] Review the guide with product management communities of practice
- [ ] Once done, remove the "TG: Review Guide" label and add the "TG: Leadership Review" label
- [ ] Present to Hack for LA leadership team for sign off
- [ ] Once approved, remove the "TG: Leadership Review" label and add the "TG: Place Guide" label
- [ ] Possibly create an issue template on .github
- [ ] Include link to template under resources if you add it as a template in .github
Resources
- Refer to #123 for how to write a guide and the guide template
- Update issue #128 with the name of item you are working
- Former writeup of issue
Requirements
- [ ] All figmas need the following
- [ ] Cover sheet
- [ ] Icons for sections - if you have a lot of pages, putting icons on just the sections can help you keep it organized.
- [ ] Get and confirm icons are cross platform compatible Emojipedia
- [ ] see design system team for additional requirements
Proposed Iconography
Section and Page examples (we are providing all the icons for all potential pages, so that depending on which you have, you can use an icon consistent with other projects, so that we can make a guide).
- ✅ Final pages (if the site is small this might just be one page, if the site is large this is a section header for various features to have their final pages - see drafts section below for work in progress)
- 📔 Style Guide
- 🏗️ Components
- 🎨 Colors
- T Typography
- ™️ Branding and Logo
- 📣 Press Kit
- ⭐ Social Media Preview
- 🛬 Landing Page
- 📃 About Us
- 📐 Drafts
Examples
Cover sheet and icons on sections example from 100 Automations
100 Automations Figma file
Hack for LA website Figma file
Design Systems team
Working on sorting out some details on the civic tech index project. Project Figma should be updated to add classes soon
Overview
In addition to some basic setup above, we also need guidance on how to use styles, etc in order to be able to create /export .css or .scss files
Articles to read
Two articles I found sounds like they have sorted out how material and Figma should be used together to make styles:
- https://www.figma.com/blog/material-design-figma-styles/
- https://www.figma.com/best-practices/components-styles-and-shared-libraries/styles-and-style-tips/
Plugins and other export tools
Here are some tools that we should try, so that we can see what happens when we export now, and be able to check if our changes in what ends up being exported
No plug in needed:
Figma SCSS Generator (these links might be the same thing, or two different tools that look the same)
- details: https://figma-scss.now.sh/
- details: https://www.figma.com/resources/api-and-extensions/figma-scss/
Plug ins Here are some plugins for converting from figma to scss or css that might be worth experimenting with:
UIKIT to SCSS
- details: https://www.figma.com/community/plugin/843123176259183001/UIKIT-to-SCSS
- code: https://github.com/caffeinalab/figma-uikit-to-scss
- video: https://www.youtube.com/watch?v=YCIgE8IEkBQ
CSSGen
- details: https://www.figma.com/community/plugin/742750636238601912/CSSGen
figma-sass-less-plugin
- details: http://www.lib4dev.in/info/oriziv/figma-sass-less-plugin/202340402
Previous issue Description/Top portion
Overview
We need to standardize our Figmas as well as encourage innovation to make the best use of the tool for teams. The guide will be informed by all teams current practices and ideas for how to improve.
Action Items
- [x] Send proposed iconography to all teams to get feedback
- [x] Make relevant changes
- [ ] All figmas need the following
- [ ] Cover sheet
- [ ] Style Guide
- [ ] Components
- [ ] Colors
- [ ] Typography
- [ ] Icons for sections - if you have a lot of pages, putting icons on just the sections can help you keep it organized.
- [ ] Visual representation of classes or classes defined in the Layers (layers is easier)
- [ ] Create an empty figma for people to use as a template with a sample page for each type of resource recomended
Proposed Iconography
Section and Page examples (we are providing all the icons for all potential pages, so that depending on which you have, you can use an icon consistent with other projects, so that we can make a guide).
- ✅ Final pages (if the site is small this might just be one page, if the site is large this is a section header for various features to have their final pages - see drafts section below for work in progress)
- 📔 Style Guide
- 🏗️ Components
- 🎨 Colors
- T Typography
- ™️ Branding and Logo
- 📣 Press Kit
- ⭐ Social Media Preview
- 🛬 Landing Page
- 📃 About Us
- 📐 Drafts
Resources/Instructions
Emojipedia
Cover sheet and icons on sections example from 100 Automations
100 Automations Figma file
Hack for LA website Figma file