- QA on staging
- Submit PR for feedback
- Make necessary changes
- Deploy changes
- Run rake task to copy necessary information to new db columns
- Make changes in Hymnal to formats
- Add in video code to add support for video trackers
- Change ad.clickThrough to ad.clickthrough
- Submit follow-up PR to remove the MetricsInstrumentation table, and necessary leftover columns from HymnalAd, Tracker, and PublishedAd
- Update documentation
dssa |
Backend of app:
- migrations (changing tracker & hymnal ad table)
- fixing models
- Tests (3 days)
Hymnal UI
- Fixing form (1 day)
Publishing
- Make sure trackers are added correctly when ad is published (timing tbd)
- A metric starts its journey being added on the frontend, in Hymnal, as an impression tracker
(in the tracker sidepanel, views/hymnal_ads/_sidebar_tracking.html.erb). You can add as many trackers as you want per ad.
- Separately, a clickthrough url is added in the Click-through url field, and notably, there is only one of these per ad.
- Potential opportunity to simplify: In the refactor, we'll need to update how clickthrough urls are handled, since currently they're handled by metrics_instrumentation. However, since there's only one per ad, it makes more sense to make this a column on HymnalAd.
- We'll also need to update the rake task I wrote to migrate the current clickthrough_urls over to HymnalAds, from Me
Process Notes | |
Why choose Vue? | |
- First, why choose a framework at all? This app is super tiny and not very complex, but it’s just complex enough (and, also, I can imagine it fitting into a larger ecosystem one day) so building it within the structure of a framework makes it easier to manage and maintain | |
- Vue a light framework, and this is a tiny app. Good to be able to choose which pieces you need vs having to load an entire framework | |
- It’s well maintained, has good performance, and seems intuitive | |
- Seems kinda irresponsible to bring another Angular app into this world | |
Beginning Steps: | |
- Reading a lot of documentation |
#Spacemacs (Vim mode) Cheatsheet (adapted from: https://simpletutorials.com/c/3016/Spacemacs%20Cheatsheet)
###Introduction For project searching, create an empty file named .projectile in your project root directory. For text searching, install AG (the silver searcher) and create an .agignore file to avoid searching certain directories. When searching for files or text in Spacemacs, you can use ctrl-j to go down, ctrl-k to go up, and page up/down.
This sheet assumes you’re using the VIM mode of Spacemacs. When you open a file, you will be in the command mode of the editor. The command mode is not an edit mode; it's just for typing commands. Insertion mode is where you can type text normally (e.g. like in Microsoft Word).
function gcsubl () { | |
git clone $1; | |
cd `basename $1 .git`; # in bash, everything between backticks | |
open . -a /Applications/Sublime\ Text.app; # will be replaced with the output of the command. | |
# basename chops off the path from the file name | |
} # .git removes the file extension |