[ ] Refactor (change which changes the codebase without affecting its external behavior)
[ ] Non-breaking change (fix or feature that would causes existing functionality to work as expected)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Purpose
This PR adds the ability for a user to specify a future date in the Published at field in Keystone in order to schedule a blog post to be added at that point in time. Note that no updates to uclaradio-blog are required; the post will still be added to Keystone's database, but the website will only pull posts whose publishedAt fields (if defined) are before the current date/time.
Checklist
[x] My branch follows the branch naming scheme of UCLA Radio, and can merge into master without error.
[x] My code follows the code style of this project, and I have linted it to confirm this.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] My change requires a change to the documentation and I have updated the documentation accordingly.
Types of changes
Purpose
This PR adds the ability for a user to specify a future date in the Published at field in Keystone in order to schedule a blog post to be added at that point in time. Note that no updates to
uclaradio-blogare required; the post will still be added to Keystone's database, but the website will only pull posts whosepublishedAtfields (if defined) are before the current date/time.Checklist
masterwithout error.Link to Issue
435