Create a standalone Figma file for USWDS page templates

[pglevy]

What it should have:

• Only the "published" versions of our page templates that have been reviewed and ready for release.
• Any necessary titling, branding, or instructions.

What we want to be able to do with it:

• Make it available as a community file on the Figma platform.
• Track versions.
• Link to existing libraries (like the Truss USWDS library).
• Manage our own variations of USWDS symbols.
• Create new symbols as needed.
• Link to specific frames from our USWDS Page Templates site.

[kbchumley]

https://www.figma.com/file/QVPduB8h6DIENYULFVCism/USWDS-Page-Templates?node-id=5%3A0

• getting started page
• intro page
• individual templates page
• cover page

[bnaolu]

Guide for publishing to the Figma community, version control, and accepting updates.

From our recent conversations with @kbchumley and through additional research, seems like we won't be able to automatically get updates from the Truss Library until further notice from Figma themselves. As Truss publishes new updates, we'll have to continue to duplicate their files for the most current version. This applies to our own community files when they get published to the Figma community.

Publishing our local components and variations to a library

Once our local components are published, it will be usable across Bixal HCD.

NOTE: Since local components are our own, anyone in HCD Bixal using our component library will be able to manage updates as we make changes. Anyone who is 'Duplicating' our files from the Figma Community will NOT receive these updates. As stated previously, they will have to reduplicate the file.

1. Create local components
2. Publish local components
3. Toggle new component library on

Publishing files to the Figma Community

Our files can also be published to the entire Figma community.

1. Create a file (can be a mix of libraries, wireframes, templates, etc.)
2. Publish to the Figma Community through the 'Share' button

Publishing new changes and viewing version history

Any changes added to the file can be published and will be made available in the current version. Past versions can be viewed or restored by clicking on the filename drop down arrow.

Review and accept updates from libraries

[bnaolu]

What we can do:

• [x] Make it available as a community file on the Figma platform.
• [x] Track versions.
• [x] Link to existing libraries (like the Truss USWDS library) but NO updates.
• [x] Manage our own variations of USWDS symbols.
• [x] Create new symbols as needed.
• [ ] Link to specific frames from our USWDS Page Templates site.
  • need clarification

[bnaolu]

@pglevy, would like your review on these two pages I added to the USWDS Page Templates file in Figma:

• Rapid Response Components
  • This page would store all of Rapid Response's own variations of the USWDS components.
• Page Templates
  • This page houses only the "published" templates as you stated previously. If we keep this, we may need to change the Figma links in the template markdowns.

[bnaolu]

Figma Community and Duplicate files

The purpose of Figma Community files

What's a Duplicate file?

Can we add the USWDS duplicate file to our local file and will this be updated?

Yes, but we wouldn’t be able to add any of their updated duplicate file as a 'page' in our local file for future progress.

Best solution (for now)?

I think it's best to stick to what we're doing now: a single version of the USWDS components (currently 2.12) and linking our page template to this (externally). By adding any future updated duplicates from Truss will involve tedious relinking of components.

[bnaolu]

Finished relinking templates (except Teams page; need to fix the bug in GH) in Figma. Please take a look and review, @pglevy and @kbchumley 😊

[pglevy]

Working out of this file now.