Spoke: Support white-listed emojis in scripts/canned messages

Created on 15 Feb 2018  路  4Comments  路  Source: MoveOnOrg/Spoke

Note: we should only use emojis which have been standardized across platforms:
https://www.twilio.com/blog/2015/08/common-sms-problems-unicode-twilio.html

To start, we would like to add some emoji insert buttons on the Admin page for canned answers and when editing a script.

After that, we would like to make it so admins for can white-list specific emojis for a particular campaign (i.e. it's a campaign setting) where it would expose the same insert buttons to the campaign's texters.

The first part is a good-first-issue though this will require a little familiarity with unicode

A-Admin UUX A-Texter UUX A-client side (react) S-in progress S-needs ui good first issue

Most helpful comment

All 4 comments

I'm cleaning up our good first issuess and want to check in on the status of this. This hasn't been implemented has it?

@schuyler1d
Sounds like this should actually be broken into 3 issues:

2 Good First Issues:

  1. Add an emoji palette to the interaction script editor in the Campaign creation page
  2. Add an emoji palette to canned responses in the Campaign creation page

and then a meatier issue:
3. Add ability to add an emoji safe-list to a campaign.
with the subtasks of:
- Acquire design for where in the create campaign page we would add this safelist and how it could be constructed (perhaps a task for a Progressive HackNight design inclined person)
- Implement the admin facing safelist creator
- If that safelist exists, provide a safe-list approved emoji palette to the texter view

Does that seem right? If so, can I close this with links out to the 3 new smaller issues?

I think that's the right breakdown of tasks. Except maybe the third -- For the third, it's probably that we should error or warn on saving (or writing) emoji that aren't cross-platform, if that's possible (and forward-compatible).

As far as splitting the tasks -- I'm ambivalent -- e.g. I don't think we need two separate emoji palette components for (1) and (2) so they seem pretty interconnected. If a single one is done first, and then the other uses the work from that one to move forward, then that's fine -- but why not just have 3 PRs that link to this issue (and have checkboxes or something)

Was this page helpful?
0 / 5 - 0 ratings