![]() ![]() The second but related goal was to make it easy to attach existing functional code to new designs. How amazing would it be to update a design in Figma, and then click a button to sync those design changes to your website? This also means that we need to ensure updating your design doesn’t overwrite any custom code that we have written to make the website or app functional, and that it naturally lends itself to having Figma-generated design code and functional code live separately in neat compartments. ![]() One was to have the design for components we generate to live as much in Figma as possible. We wanted to solve two main problems when building Figma to React. (Too excited to read this blog post and want to play around with our read API right now? Check out our Developers page!) If you want to follow along, we’ve open sourced the code at GitHub. We’re loving the enthusiasm and thought we’d share our own attempt at a React converter, discuss some of the subtle design choices and technical solutions that went into its development, and expound on the vision that motivated its creation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |