# Design deliverables

###### tags: `manyverse`

epics are gitlab issues with [design phases]ttps://gitlab.com/staltz/manyverse/-/boards/4312427)
phases are also published on the [website]:
- **scoping**, **discovery**, **stakeholder review** and **dev** go on [ongoing](https://www.manyver.se/roadmap/) roadmap
- **near future**, **far future**, **upcoming** go on [upcoming](https://www.manyver.se/roadmap/) roadmap
- **complete** go on [features](https://www.manyver.se/features)

## publication guidelines

- work on all screens, till approval
- move stable design to its own figma file
- find or create epic (see above)
- export design from stable figma file as svg
- place on epic description, along with link to figma file

## Things to do in promotion phase

- which audience benefits from this feature?
- how to reach them?
- how we frame new feature?
- clean up documentation
- add locked design deliverables
- figma design export
- figma
- promote

## published phases

- ongoing
- upcoming

- define milestone on [gitlab issues](https://gitlab.com/staltz/manyverse/-/boards/4312427)
- can we deliver milestone alone? or is it blocked by other issues
3. design flow on [all screens](https://www.figma.com/file/wiC3zRrUWeLiLTmhltwwAv/all-screens?node-id=120%3A6418) figma file
4. iterate and approve