[Benefits Taxonomy] Enable translation for MVP fields

[wesrowe]

Description

User story

AS A Content Editor I WANT to be able to enter translations for certain fields in the Benefits Taxonomy SO THAT the BT can support a translated experience in Veteran-facing products.

Engineering notes / background

• Fields marked as needing to be translated in the Drupal content model sheet.
• Translation on magic headers: need to determine whether this is / isn't in scope

CMS Team tie-in

• What is the state of documentation about how to enable field translations, in the new CMS translation world?
• Who is the CMS technical point of contact? (If not Tim)

Quality / testing notes

Acceptance criteria

• [ ] Translation enabled for fields specified in the spec spreadsheet
• [ ] Consulted with CMS engineer re: translations to ensure implementation is correct (need to define what our expectations and theirs should be)
• [ ] Confirmed translation workflow working as expected

[jilladams]

Pulled out of Sprint 87 to do more refining.

First step: confirm with CMS team if any documentation exists / where it lives, and if we can be the first to test drive it. Flagged for pre-refinement.

Then: need to decide if magicheaders is in scope or not when we pull it in again.

[wesrowe]

Pre-refinement – find out if documentation exists to guide this work.

If CMS team needs to create docs, make this ticket dependent on their doc ticket.

[wesrowe]

@timcosgrove, Can you please share: 1) Does documentation exist for implementing translation on fields such as Benefit Taxonomy? If so, can you provide a link? 2) If not, is it ticketed, and can you provide a link to that?

[FranECross]

I removed the previous estimate because there might be additional fields than originally estimated.