[TASK] Design schema for PocketBase

[ricardo-sonda]

Description of task

PocketBase has to be the single access point from which the website retrieves relevant data, like images, descriptions, names of members, etc. I think it'd be very time consuming to migrate everything in one go, so I think it's sufficient to simply design a schema and update the tables continuously as we build the website.

This doesn't mean that absolutely everything displayed in the website has to come from PB, but that we have a single storage place to enforce consistency for future development

Suggested Workflow

• Define what data will be stored in PocketBase
• Design schema (e.g. tables like members, project, drones; drones contains a images and textual descriptions we should like to maintain, like technical specifications)

Specifications

• Documentation must include schema with descriptions on each table

Contacts

No response

Code Quality

• The code is documented on the wiki (provide link)