You can always contribute to the system; this is a shared language for all of us.


If you have a better suggestion for the appearance and function of an existing component, we can discuss it and, based on our decision, you can work on it to include it in our current component (or pattern) list.

You can learn more about how the component design process works in detail from here.


The design system documentation is an ongoing process, and there are always things that need to be explained. If you want to get involved in our documentation processes, there are a few points you need to pay attention to:

  • Make sure to maintain the existing documentation language. The tone and voice should be consistent with other documentation on the website.
  • Ensure the structure and headings of the documentation are the same or similar. Follow the current documentation for guidance. However, at least, you must include the following information:
    • Component overview: A short sentence directly defining the component (this can also be a pattern).
    • Component structure: Describe the component atoms, supporting with images.
    • Component types or states: If the component has different types, you must define each one separately. If the component is an interactive element, you need to define its states.
    • Behavioral elements: If the component has interactive states, these should be detailed.

If you want to create a draft for documentation, you can start by creating a FigJam file within the Frame Design System project in Figma, named {component-name}[doc-draft].

You can always be a contributor as a team member, helping make any decisions for the system or participating in the workshop hours for FDS also means a lot.

  • You can reach out for any inquiries at #frame-design-system on Slack (internal).
  • You can check out our Jira board for the current backlog (internal).
  • Also, preview the latest roadmap for FDS in the Confluence project (internal).