Written specifications are being created for all the pages pertaining to the PortaFly project.
This activity will help:

• make sure user experience details for a variety of behaviours available for any of the pages are correctly expressed, and deliverables are not misinterpreted
• the team identifying what data needs to be retrieved from the backend, thus inform the creation of an OAS

To make this process more streamlined we decided to break this information down into one file per component (toolbar specs, form specs, etc...) and store them in the porta repo.
The single files will then be linked in the Design notes that accompany the Mockups tickets.