this switches the site metadata model to use a single data field where the field names and values are stored as JSON.
I'll update the tinycms & frontend to parse the JSON when working with this data. I think this is the right way to approach this info, as it'll probably change from client to client, and over time, and we won't want to have to edit and redeploy the API every time. Or manage the diffs between client API models.
this switches the site metadata model to use a single
datafield where the field names and values are stored as JSON.I'll update the tinycms & frontend to parse the JSON when working with this data. I think this is the right way to approach this info, as it'll probably change from client to client, and over time, and we won't want to have to edit and redeploy the API every time. Or manage the diffs between client API models.