Re-design Information Architecture (content, how it is categorised, and how features are structured)

OVERVIEW

This issue focuses on clarifying the product’s structure and story so users quickly understand what TFA is, who it’s for, and how its two core capabilities (AI Chat and Letter Generator) relate to each other. This includes refining key messaging (what TFA is, why it exists, connection to Oregon Law Help Center, and why use it vs. ChatGPT or other AI chat bots), defining how content is categorised across landing and supporting pages (About, FAQ), and ensuring privacy and disclaimer information is clearly highlighted in the right places with the right level of prominence.

Scope

value proposition, Oregon-only scope messaging.

ACTION ITEMS

• Define and clarify the core product story and it's main features (Chat and Letter)
  • What is Tenant First Aid? Make it explicit in the product story that TFA is not just a chatbot but also a letter generating tool.
  • What is the main value of the product? Why use our chat vs ChatGPT and other general AI tools? E.g., describe that TFA uses a specific library/knowledge base and the value of that.
  • Explain how TFA is connected to the Oregon Law and CodePDX
• Possibly create and structure “Who is this tool for?” content with specific value bullets for tenants.
• Create short privacy summary
• Create FAQ sections. Potential Qs could be:
  • What is TFA?
  • Who is it for?
  • How do we protect your privacy?
  • I live outside of Oregon, can I still use it?
  • Seeing error? Direct them to CONTACT US
  • Questions that were not answered? Direct them to CONTACT US
• Create short, high-impact summaries for landing page of the same information that users can access in the top and bottom menu where the information is more detailed.