Framework: Creating a more connected design system with Code Connect

Поделиться
HTML-код
  • Опубликовано: 18 апр 2024
  • At Framework, we announced Code Connect, our newest Dev Mode capability - now available in beta. Code Connect delivers code from your design system to Dev Mode, helping developers build with consistency and speed. In this session, Jake Albaugh, Figma developer advocate, shares an overview of Code Connect and some tips on how to get started.
    Everything we launched at Framework → www.figma.com/blog/what-we-la...
    More about Code Connect → www.figma.com/blog/introducin...
    Get started with Code Connect → github.com/figma/code-connect
    Figma is free to use. Sign up here: bit.ly/3msp0OV
    ____________________________________________________
    Find us on ⬇️
    X (formerly Twitter): / figma
    Instagram: / figma
    LinkedIn: / figma
    Figma forum: forum.figma.com/
    ____________________________________________________
    #Figma #Config #FigJam #Tutorial #NothingGreatIsMadeAlone #design #tips #DesignSystems
  • НаукаНаука

Комментарии • 19

  • @dandenney3046
    @dandenney3046 Месяц назад +10

    On top of being excited for the feature, I think this is the best product demo I've seen. Jake clearly outlined the problem, shared how Code Connect fixes it, and used it live to demonstrate it

  • @mryechkin
    @mryechkin Месяц назад

    This is so awesome. Seriously. I'm so excited to see where you guys take this, the opportunities this opens up are nearly endless.
    I was playing around with creating a simple codegen plugin for Dev Mode earlier, but the solution ended up being too convoluted for my liking, so I kind of gave up on the idea.
    Code Connect not only solves this out of the box, but it does it so elegantly, and with so much more to offer. Best part, I don't need to create and manage a separate plugin. Amazing job, team!

  • @peppapig807
    @peppapig807 Месяц назад +3

    another thing we struggle with in terms of having figma components match the way things are structured in code is that we can't put components inside other components e.g. we have a Card component, but if I want to put something inside that card, i have to detach the instance. I know there are workarounds by adding invisible "slots" in the Card, but that workaround is messy and also sometimes doesn't work (wonky autolayout behaviours)

  • @tomasdohnal
    @tomasdohnal Месяц назад

    Great explanation and walkthrough! really glad to see that you went beyond the most basic example and showed how to handle more complex ones as well!

  • @angelozodda4449
    @angelozodda4449 Месяц назад +1

    So cool!!.... This helps so much... Pushes UX and UI designers to think a bit more as developers and blends that line... is the right way to be more involved a good product creation process..

  • @suvadeepmajumdar4920
    @suvadeepmajumdar4920 19 дней назад

    This seems kind of what storybook offers. But great demo

  • @selinovaldes
    @selinovaldes Месяц назад

    That was Fig-tastic! Where can we find more information on the Storybook implementation, though? 🔍

  • @Jon88938
    @Jon88938 Месяц назад

    this is awesome, will it be come to Teams plans after beta?

  • @berrynut7035
    @berrynut7035 Месяц назад

    What is the difference between Code Connect and Code Snippet Editor plugin by figma? Both allow us to see the corresponding code for the components. So what makes Code Connect different than Code Snippet Editor?

  • @imohanreddy
    @imohanreddy Месяц назад

    Will it be coming to angular?

  • @saoirsethewanderer
    @saoirsethewanderer Месяц назад +1

    Having all kinds of trouble with the URL from Figma. It doesn't escape things properly and then when I escape it, it still gives errors for reserved characters. Any ideas how to get a URL from Figma for my component that actually works.

  • @haraldskogland8630
    @haraldskogland8630 Месяц назад

    So.. only for Enterprise plans???

    • @Cathal678
      @Cathal678 21 день назад

      Code Connect is be available in beta for Figma Organization and Enterprise plans :)

  • @skeletoncr
    @skeletoncr Месяц назад

    I have some problems who can successfuly publish something?

  • @MirkoSaugo
    @MirkoSaugo Месяц назад

    a dream

  • @MaxWeir
    @MaxWeir Месяц назад

    Why is the sound so bad?

  • @nicholasprice5137
    @nicholasprice5137 23 дня назад

    Source of truth question:
    Has anyone figured out a way to always sync relevant figma design files with the visual portions of components in the code base, and vice versa, such that the design files and code base can be synced, regardless of whether it’s updated from the visual design file or from the code itself?
    I want the figma design file and ui portions of my code to be “two sides of the same coin” that are always in sync/reference the same source of truth.
    Is there a way for edits to xyz designs to be pushed from figma to the code base, too?
    Or is there a way to achieve that sync with storybook, or some other integration?
    More specially, here’s what would be magic:
    Authorized change to a figma design file can be pushed to relevant parts of ui component code in the code base.
    And
    Authorized changes to ui portions of code within a component can be pushed to the Figma design file.
    This way, the design portions of a component in Figma always reflect the ui portions of code in the code base, and vice versa.
    Obviously, I realize this introduces version control/auth issues, but if there’s a way to do it, I’m sure any third party CI/CD pipeline and repo could be utilized to handle all the version control and auth issues.
    Has anyone found a way to achieve such a sync? And/or does code connect provide the missing piece to push from repo to design file, and there’s some other feature or software that can push design file updates into xyz repo?
    Thanks all!!