What about this

Basically each module is a project and in each project each tab/feature is a file. I’m going to keep all uxr sessions in their own file and just link to it from the other files

We keep our files split at feature/flow level because a single team will have multiple files to prevent figma for slowing down.

What is local component?

Custom component used only by that team for that feature. Won’t be part of the core library of components unless it has widespread use.

Oh that’s a good idea

- Thumbnail - One-pager (used to do this on one specific team lol) - References (screenshots, etc) - Components - Mocks (ex: by device, flow, etc) - Prototypes - Archive

Curious why references needs to be on a separate page? Is this final or for hand-odd? I believe if not references are meant for rough ideations so should be on the same page with rough prototypes and other explorations.

It usually ends up being a mix of both - a separate page and in the context of designs.. It just depends

final / final final / actual final / do not build / ideas / rejects / playground / test site / archive / graveyard / notes / ideas 2

graveyard is the best

Graveyard is where the real spec is. I write my tickets like a scavenger hunt

Thumbnail page, component page, page for exploration/screenshots/junk, page separator, page-per-flow or task

Click through prototype page, screens organised into sections and fully annotated page, mess page. Component page if they’re not in used as library from a separate file. Mess page is the fun one

I like using pages for phases (changelog, ready for team, in progress, archive, playground). I’m a huge section fan and use those to organize flows per page. Setting up a table of contents is helpful, too. There’s a great plugin from the Discord team that I typically use.