Move placeholder uuids from file to database

[llewelld]

Summary

Currently the uuids and image filenames for the story carousel on the home page are read from the carousel.json file.

Although it makes sense (I think) to store the placeholder stories in a file (because they should be available for use even if the database is cleared) it would make much more if the uuids for the real stories were stored in the databse.

This has two benefits:

1. They could be easily updated using the admin interface.
2. If the story is wiped from the databse the uuid could be automatically removed as well.

What needs to be done?

• [ ] Create a model to capture story uuids and image filenames. There doesn't have to be any associated form or UI.
• [ ] Switch the get_carousel_stories() helper method to use the database entries rather than reading them from the stories entry in carousel.json.

Who can help?

• Anyone will to hack the code.

[gedankenstuecke]

I think I might have missed the image part (I guess the proposed changes include having little images for the carousel), but regardless of that: I had assumed we'd just need to store the UUIDs (which could have been in env variables) and then use a fixed-in-template placeholders otherwise.

Having said that, I have no strong opinion in either direction, but just wanted to offer an alternative solution that could avoid creating a model if we prefer to not have one 🙂