Set up Content & Language System

[thejoefriel]

Summary
Even though we are just creating a static front end app right now, there are two future features we need to consider:

• Ability to change the language
• Ability to edit the steps and the content within the steps (so basically CMS functionality)

This means we should put:

• Put all the content into a constants file system
• Put into a language system

Further information
Refer to the language setup we built on Tempo as that works well and will suit our needs on this

---

Acceptance Criteria:

REMEMBER THAT WHOEVER WORKS ON THIS ISSUE MUST TICK OFF ALL THE POINTS IN THIS LIST UNLESS THERE IS CLEAR AGREEMENT IN THE COMMENTS TO SAY OTHERWISE. DO NOT REVIEW A PR INVOLVING THIS ISSUE UNLESS THIS HAS BEEN DONE

• Create constants file for content
• Ensure the content is split into languages (just have english for now as the default)
• Each step (to consider in the content) includes
  • title (e.g. Check eligibility)
  • subtitle (e.g. You can check your...)
  • External button title (e.g. eligibility calculator)
  • External link
  • Check list of items (each with a title)
• Create language helper (always defaults to english)