We haven't updated this since announcing Forem. This isn't a
comprehensive change, but it links to some more information and is more
current that the old message.
* Extract Welcome Broadcast styling into its own stylesheet
- Adds a stylesheet, notifications-welcome-broadcast.scss, for broadcasts
- Adds notifications-welcome-broadcast to minimal.scss
- Removes .broadcast-content from notifications.scss
- Adds TODOs for team-delightful to both stylesheets for future work
* Adjust TODO to be more team-specific for future greps
* Create "blank" EmailSubscriptionTag
* Refactor liquid_tags_used with spec
* Create /user_subscriptions#create
- Update liquid tag name to UserSubscriptionTag
* Add rate limiting and specs
* Add counter_culture for user_subscriptions
* Update /async_info/base_data
- Alphabetize user_data
- Add email
- Add subscription_source_article_ids
- Cache subscription_source_article_ids on User model
* Add stale email check and specs
* Change user_email to subscriber_email for clarity
* Restrict UserSubscriptionTag
* Rename RESTRICTED_TAGS to RESTRICTED_LIQUID_TAGS
* Make TODO comment more clear
* Refactor error responses and update specs
* Update type to source_type in error message
* Use constantize over safe_constantize
* Add check for active source
* Refactor checking of current_user's subscriptions
- Remove data from async_info
- Create a new service to fetch/cache a user's existing subscriptions
* Restrict email in base_data to admin roles
* Oops! Rename liquid tag file
* Change error back to result...oops!
* It's not goodbye, it's see you later. RIP email :/
* Add current_email to /user_subscriptions/base_data
* Revert adding current_email
* Undo async_info_controller changes/fix conflict
* Move params to constant
* Refactor SubscriptionCacheChecker
* Remove duplicate status code in JSON response
* Remove duplicate status code for #subscribed
* Use response.parsed_body
* Remove user guard in SubscriptionCacheChecker
Ensures that we don't create new visits for non-logged-in users, bots,
and users with cookies disabled on every site visit. This will only
allow server-side visits when there is an event to be tracked.
* Move contributing guide to the docs
I think it makes sense to address this information on the docs site, but
I also think the CONTRIBUTING.md convention is important.
In order to avoid duplicating the documentation for contributors, I
think it is a good idea to link people from the repo's contributing
guide to a document on the documentation site.
* Document difficulty labels
* Use Forem in place of DEV
* Notify Honeybadger when no id can be found for a welcome notification
Also add the event's target's text to the tracking data for a welcome notification's click event.
* Destructure text and title from event.target
