Home & Agency Index - Update homepage copy + Create Agency text variables

[vykster]

Update home page copy to be more concise for users.

Acceptance criteria

• Draft English Copy written
• Copy ready for translation vendor
• Spanish copy added to app
• Execute/ test new process for updating copy and working with content localization vendor

Definition of "Done"

• New homepage copy published in English
• New homepage copy published in Spanish

Links to user research, designs and resources

• Finalized Figma file Desktop
• Finalized Figma file Mobile

[vykster]

See details on: #1121

[machikoyasuda]

Update:

Today, I sent a request to iBabbleOn for the homepage and agency homepage text.

These are the strings I sent in the request:

And sent these screenshots and links for context:

The redesigned pages -

Just for context, I sent the current Spanish translations as well -

And I sent these links for more context: https://benefits.calitp.org/help and https://docs.calitp.org/benefits/.

[machikoyasuda]

This morning, I received an email from Salim at iBabbleOn.

• He updated my spreadsheet format to what they need:

• Feedback on the inclusion of screenshots: The screenshots you sent look great and give us the context we need to translate these correctly.

And he sent a link to an Invoice with this note:

I estimate it will take 2 business days from time of payment. Payment can be made securely online with any major credit/debit card, e-Check, Apple Pay, or PayPal. Just press the green Pay button. It even works from your phone.

Payment options look like this:

Now, I will either need to pay the invoice myself, or have @indexing or @vykster or @thekaveman or someone else do it. I am not sure what credit card to use or how to pay for things for Benefits.

[machikoyasuda]

Status: Invoice is paid. Receipt was sent to my email and I forwarded to Vyki

Now, awaiting response of the translated strings from iBabbleOn.

[machikoyasuda]

Update: Thursday, May 4th - 11AM, received results:

English	Spanish
Get reduced fare on public transportation when you tap to ride	Obtenga una tarifa reducida en el transporte público cuando toque para viajar
Cal-ITP Benefits connects your transit benefit to your contactless card	Cal-ITP Benefits conecta su beneficio de tránsito con su tarjeta sin contacto
Get reduced fare on MST public transportation when you tap to ride	Obtenga una tarifa reducida en el transporte público MST cuando toque para viajar
Get reduced fare on SacRT light rail when you tap to ride	Obtenga una tarifa reducida en el tren ligero SacRT cuando toque para viajar
Choose your provider	Elija su proveedor

[indexing]

@srhhnry I propose we use this initial set of translated strings as the basis for the copy master for Spanish. When I request the full translation from our translation service in #1410 , I will exclude these strings.

@machikoyasuda Product will take over the work of getting copy translated by our vendor going forward. Once we finalize some additional copy this month, I will submit as complete a set of strings as possible. Do you want to add the translated copy in this issue to the app and close it or wait until we have all changes and do them as a batch?

[machikoyasuda]

@indexing If the engineers have extra time during the upcoming sprint, after all the sprint tickets are completed, I'd love to add the following minor improvement tickets:

• Home & Agency Index - Update homepage copy + Create Agency text variables #1386 (Effort level 1)
• This UI change is not created as a ticket yet, but this one too: Adding an illustration (already created) on the Success page (Effort level 1)

• Deploy these changes (Effort level 3)

Since the next sprint is all back-end prep work - it can be deployed without affecting the production app - we simply will not turn the Veteran EligibilityType, EligibilityVerifier, AuthProvider options on. It would, however, still be good to deploy to get the changes from security/package updates #1424 into production, and also, it would be nice for the users to get some user-focused small design/copy changes in as well. Or if devs are allowed to code and deploy low-effort level issues during the post-sprint cooldown period, we could work on these 2 ticketes then, too. In general, I think a good goal would be to have at least 1 user-improvement ticket deployed per sprint, even when we're 99% focused on back-end tickets for another larger feature set.

[indexing]

Thanks for the suggestion @machikoyasuda. Having "stretch" work in every sprint is a great idea, as well as always including some small, user-focused fix. In addition to adding this issue to the sprint, I also included #1432 as part of implementation of the veterans enrollment flow.

[machikoyasuda]

Started working on this and realized that we do not have a programmatic way to determine if an agency needs copy that specifies transit mode (e.g. light rail vs. public transportation).

[srhhnry]

I added that question to this google doc of agency onboarding questions we need for configurable string copy (question 3). I think it makes total sense to default to "public transportation" unless an agency specifies (i.e. SacRT and light rail).

My hope is that a future iteration of the admin interface (which is either agency or customer service facing) would be the place to capture/update that information (e.g. if SacRT adds transit bonuses to buses, then they are responsible for that information being updated on Benefits).

[indexing]

@srhhnry Thanks for noting this gap AND for adding a question to our documentation. @o-ram and I are now working to create a single document to guide agency onboarding: Cal-ITP Benefits Transit Provider Onboarding

After a quick review, it appears the questions in the doc you link to above and the questions in the document above are similar or the same. Can I ask a favor? Please add the new question to the official onboarding doc and deprecate (or preferably delete) the separate doc.

[srhhnry]

No prob! On second read my comment was totally not clear. That question HAD been added back in April as part of a broader process to onboard new agencies. The new doc is certainly more up to date, as this doc was never meant to be client facing and was only to document our needs (and is part of this issue)

I'll go ahead and delete it.

[machikoyasuda]

Full list of fields to add to Transit Agency:

• [transit type || transit options] - public transportation, light rail
• [action] - reduces
• [rate of discount] - 50%
• [affected service] - fixed route
• [transportation type] - bus, light rail
• [card functionality] - tap this card

Fields for Eligibility Verifier for Agency Card:

• [agency card] - Courtesy Card
• [optional qualifier] - "Courtesy Card or an MST RIDES Eligibility card"
• [qualifier] - "you will need to know the number"
• [qualifier] - "The number starts with a number sign (#) followed by five digits."
• [ID number type] - "number"
• [identity marker] - "last name"
• [qualifer] - "This is a 5-digit number on the front and back of your card."

[machikoyasuda]

Separating this out into 3 tickets:

• Creating variables and django.po strings for each Agency
• Using variables in new copy (for Home and Agency Index)

• Creating variables and django.po strings for each Agency Card EV

• Using variables in existing copy (currently awaiting Spanish translation)

[machikoyasuda]

Validating on dev-benefits.calitp.org