vrbtm.co development stream | Week VIII
Getting back to the flow, resend passcode(s) to recipient(s), Zendesk message integration and expanded content status
Not sure what this is, start here with our README, or catch up on the last stream, vrbtm.co development stream | Week VI.
You might’ve noticed that I didn’t publish a Week VII stream. That’s because I didn’t work on this for a full week. I guess it’s a little over a full week now. Anyway, Wes articulates why in his Week VII stream. We’re trying to prevent burnout by taking much deserved breaks.
I’m giving myself three tickets to do this week:
- Resend passcode(s) to recipient(s). We’re giving recipients a lot more functionality that revolves around a single passcode received via email. Let’s make this a little more forgiving. This one is leftover from my last stream.
- Zendesk message integration to enable customer support.
- Expanded content status. We’re starting to have a lot of different states for content. Going to define these a better way to allow for representation across multiple views.
Another minor update is available for Meteor. This time it’s v1.4.1.3 to v1.4.2. Going to update that real quick before moving on. Apparently this is all about rebuild performance, which is a much needed enhancement.
With that out of the way, I’m going to tackle the passcode resend mechanism.
On the back-end, that consists of adding a public method for that takes in a contentID and an email. It then sends an email notification via Sendgrid with the path and passcode to the email that was passed in. Had to make a quick Sendgrid template for that, but that was very straightforward.
As for the front-end, we don’t have a design for this yet. The implementation of the Content Detail page is outdated design-wise, so just tacking on a resend button to the recipients isn’t very smart. The only place we list the list of recipients in the new design is within the feedback conversation thread, within the first activity message. I’m not sure if we want to add interactivity within the message thread that isn’t feedback-specific.
In the mean-time, Wes got back to me about the Zendesk integration and it was just a matter of pasting a script tag within our head. ez pz.
Back to the front-end implementation of the passcode resend mechanism. I’m going to go for the tack-on approach for now and fix it later when I have to implement all the new designs. Basically just an icon that appears next to the email list, that goes away if set.
Content status tracking mostly consists of tracking email events. I know Sendgrid keeps track of email opens and clicks, so that’s how we’ll implement delivery and open receipts. It looks like the only way to get access to Sendgrid stats is over WebHooks, which is probably overkill for what we want to do.
WakaTime was 1hrs 55mins. Due to the elections, I once again didn’t get as much work done as I wanted. Lots of catch up to be made for next week.
Read the other half of this week with Wes’ VRBTM Diminishing Returns| Week VIII where he wraps up design and starts thinking about on-boarding.
We’d love to hear from you…
Get in touch at Founders@vrbtm.co, talk with us on twitter @vrbtm.co, and read our story on medium.
Wes Jones is on Twitter @WesJonesCo
Nick Dandakis is on Twitter @Dandakis
