[Sanity] Create a schema plan

[dvd-lara]

[Sanity] Create a schema plan

[byfnoel]

Thinking of a participants table

Would it be necessary?

[dvd-lara]

Thinking of a participants table

Would it be necessary?

I don't believe it would be necessary at this moment. The schema plan should be for the minimum viable version of the website which simply displays information about the club, the programs and their events

[byfnoel]

Understood!

[jhern603]

Here is an image with two possible schema designs.

Ideally, we want to minimize the number of queries we make on the front-end so that the page has faster performance. One thing we will have to look into is lazy loading. I personally don't have much experience lazy loading, so this will be a learning experience for all of us.

What we want happening in the back-end is to be relating the different fields of the tables together, so that the front-end can achieve a minimum number of queries.

An example of this:

If you look at the schema in the bottom right of the image, the Program table may pull the title and the flyer for events from the Event table.

Ideally, this would make the query from the front end look like this:

(Query everything from the Event table)
*[_type == 'Event']
(Only display the Title, and the Flyer for each event)
*[_type == 'Event']{Title, Flyer}

SQL Equivalent: SELECT Title, Flyer FROM _schema WHERE type = 'Event'

We will have to make an experimental schema so we can see if cross-referencing is really this easy, though.

Once we agree on a schema design, and verify that cross-referencing is viable, I will design an ERD so we have a clear graphic on what the schema will look like.

[ZiadMalik1]

Based off my Understanding of Schemas, I feel that the more Compact and efficient they are, the more they serve their purpose of keeping organization. The Bottom Right Schema seems to be the one that in my opinion, is perfect for the job. Using SK and PK, we can create Queries that pull off of one another in different tables.