[ ] Refactor (change which changes the codebase without affecting its external behavior)
[x] 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
Previously, the Keystone UI involved users having to add to be parsed from the uclaradio.com frontend. It's now parsed as , probably because this is more intuitive. I just replaced that string in the relevant places. I also added a welcome header that allows users to checkout the old tumblr.
Approach
Replaced a bunch of strings.
Checklist
[x] My branch follows the branch naming scheme of UCLA Radio, and can merge into master without error.
[ ] 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
Previously, the Keystone UI involved users having to add to be parsed from the uclaradio.com frontend. It's now parsed as , probably because this is more intuitive. I just replaced that string in the relevant places. I also added a welcome header that allows users to checkout the old tumblr.
Approach
Replaced a bunch of strings.
Checklist
masterwithout error.