I've had more time to think about this, and I think I want to create a plugin system for content types akin to Drupal's. You'd declare config files in JSON, which hopefully is fast enough to read...however, it is not a good idea for me to flesh this out now since hardcoding a Post will do for now.
I have decided that storing Clodinary data in JSON fields is fine as there is no MVP plan for a media library. I hope users can use the integrated Dropbox/Google Drive feature to essentially have a media library there.
Also, I think using a version of Drupal's Paragraphs module is best for content writing. The Post will still have to have things like tags, slug, and main image that don't fit into the content view.
The Post model comes from the IR20 project. It was called a "Story" there, but it is really an article, or it could be called a Post, which might be a better name. I think the Article is bound by a date...so I'll stick to Post...
Within adding this content type, there are some media fields and a WYSIWYG field so new dependencies will be needed for that functionality. For this issue, creating the model is probably enough...and then we can see how to apply the database changes upstream on Heroku.
Acceptance Criteria
[x] Post model is added to prisma.schema
[x] Cloudinary media reference stored in an Image model
[x] Users can add/edit images via Cloudinary for Space models
I've had more time to think about this, and I think I want to create a plugin system for content types akin to Drupal's. You'd declare config files in JSON, which hopefully is fast enough to read...however, it is not a good idea for me to flesh this out now since hardcoding a Post will do for now.
I have decided that storing Clodinary data in JSON fields is fine as there is no MVP plan for a media library. I hope users can use the integrated Dropbox/Google Drive feature to essentially have a media library there.
Also, I think using a version of Drupal's Paragraphs module is best for content writing. The Post will still have to have things like tags, slug, and main image that don't fit into the content view.
The Post model comes from the IR20 project. It was called a "Story" there, but it is really an article, or it could be called a Post, which might be a better name. I think the Article is bound by a date...so I'll stick to Post...
Within adding this content type, there are some media fields and a WYSIWYG field so new dependencies will be needed for that functionality. For this issue, creating the model is probably enough...and then we can see how to apply the database changes upstream on Heroku.
Acceptance Criteria
prisma.schemaImagemodel