Cleanup Guide template: Figma for developers (written by their friends at UI/UX) #27

[SheIsBukki]

Dependency

move this out of the icebox and into review on 2021-11-12 - see comment at bottom of this issue.

Overview

We need to cleanup this create a guide issue so that it has the current structure of guide issues.

Action Items

• Review the guide and identify how it is different from our template
  • Add a link to How to write a Guide doc
  • Add a link to ADD SCREENSHOTS & GRAPHICS TO YOUR GUIDE
• Check to see if she has responded.
  • If not, reach out on slack.
• Provide more guidance until finished
• Signoff on Guide
• Send Guide to Website Team

Resources/Instructions

• Related Community of Practice: UI/UX
• Guide issue: Create a Guide/Template: Figma for developers knowledgebase-content#125
• Link to Guide: https://docs.google.com/document/d/1Is5Ah0tUH07kWYG_J6HTo0RF8Z9Foi2l/edit
• Link to the Figma resource: https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website?node-id=1548%3A1967
• comments from Hana and Danielle: Agenda for week of August 16th 2021 design-systems#53 (comment)

[SheIsBukki]

Guide: Figma for developers (written by their friends at UI/UX) hackforla/knowledgebase-content#125

Overview

We need to create a guide for Figma for developers, so that new developers on Hack for LA teams can learn how to view and analyze designs, and export assets, on Figma.

Action Items

• Research existing information about Figma for developers in relevant resources including Figma's youtube videos and articles
  • Once done, remove the "Guide: Research" label and add the "Guide: Gather Examples" label
• Gather examples of how other projects or volunteers have trained their developers in Figma (if applicable), adding each example as a link in the resources section below
  • Once done, remove the "Guide: Gather Examples" label and add the "Guide: Draft Guide" label
• Create a draft guide, either in markdown format in this issue or a google doc in the [ux/ui google drive]
  • Once done, remove the "Guide: Draft Guide" label and add the "Guide: Review Guide" label
• Review the guide with UX/UI community of practice
  • Once done, remove the "Guide: Review Guide" label and add the "Guide: Leadership Review" label
• Present to the Hack for LA leadership team for sign off
  • Once approved, remove the "Guide: Leadership Review" label and add the "Guide: Place Guide" label

Resources

Update issue hackforla/knowledgebase-content#97 with the name of item you are working on

https://www.youtube.com/watch?v=XA4fM5I4GvQ&list=PL7e8VJ_ZN6epq-oiYOufiuPI-fpDC2Mby&ab_channel=GregorySchmidt
https://www.figma.com/best-practices/tips-on-developer-handoff/
https://www.youtube.com/watch?v=B242nuM3y2s&ab_channel=Figma
https://www.smashingmagazine.com/2020/09/figma-developers-guide/
https://www.figma.com/best-practices/guide-to-developer-handoff/

Link to Issue #27

[SheIsBukki]

Train of Communication So Far

Hana and Danielle said:
"This guide does not relate to what we are currently working on."

[ExperimentsInHonesty]

We reviewed the guide and provided guidance to the author hackforla/knowledgebase-content#125

[ExperimentsInHonesty]

author has not responded

[ExperimentsInHonesty]

left author another message

[ExperimentsInHonesty]

Author said she is moving and still wants to work on the issue and will have an update on the 19th
hackforla/knowledgebase-content#125

[ExperimentsInHonesty]

Sent her another message hackforla/knowledgebase-content#125