Website updates MVP

[drew-usds]

Problem statement

We have a ton of content to roll out in the epic this issue is linked to, but we need to make some large, baseline changes first in order to make the rest happen.

What you need to know

• The below AC will help us get the content/layout ready for the homepage and top three main sections in the new IA.
• Let's try to reuse/remix as much existing content as possible. We can clean up and make the bigger improvements we have planned out in coming sprints.
• Existing work has been done on /contact in #4913 in this branch
• Working Figma File
• IA Mural

Acceptance criteria

Homepage

Content that covers high-level information about the product and drives folks to learn more or contact us.

• [x] Section that describes what ReportStream is (the current Hero may still work here)
• [x] Section that describes what we do for API senders + links to sender-focused overview under /product
• [x] Section that describes what we do for STLTs + links to receiver-focused overview under /product
• [x] Section for "where we're live" map, links to /where-were-live
• [x] Section for contacting us that links to /contact
• [x] Create a layout for above content sections

Product section

Content that helps a prospective user understand what RS does and how it can help them. The existing /how-it-works/overivew pages will most likely work here with minimal changes.

What's new/release notes content June 22

• [x] Product index page (?)
• [x] Overview page for API senders
• [x] Overview page for CSV senders
• [x] Have solid ideas for nav dropdowns/sidebars/etc we may need for this content

Resources section

Content that helps a user understand the more technical aspects of the project (ex the programmer's guide). We can consolidate and edit existing guides from /how-it-works/* for the MVP.

Referrral guide pdf content

• [x] Resources index
• [x] Existing guides are linked somewhere, including CSV guides/documentation
• [x] Programmer's guide PDF is linked from somewhere
• [x] Have solid ideas for nav dropdowns/sidebars/etc we may need for this content

Support

Content that helps a user understand common problems and reach out to get help.

• [x] FAQ page (can use existing content from #4913)
• [x] Support page (can use existing content from #4913)
• [x] Have solid ideas for nav dropdowns/sidebars/etc we may need for this content

ETC

• [x] Find something to do with the existing CSV user guides. If we launch this before we fully sunset that feature, that content needs to live somewhere.
• [ ] Catalog necessary redirects from existing URLs + create follow-on engineering ticket

To do

• [x] Put together a suuuuuper-basic wireframe (LIIIIIKE THE MOST BASIC EVER) to help visualize how this'll come together
• [x] Draft content outline in this doc
• [ ] ...

[BerniXiongA6]

Content outline is done and ready for review over here and is also housed under Issue # 5856

[HeatherRienks]

FYI - #5826 (Engineering ticket) should be worked at the same time!

[BerniXiongA6]

Content outline is saved in the above AC but for your convenience, I've also included the Shared Doc again here just in case.

[hannasage]

@drew-usds @BerniXiongA6 Working branch can be seen by checking out git checkout experience/5826-IA-shuffle or in the browser by navigating to our repository and selecting experience/5826-IA-shuffle from the branches dropdown.

Here is a link to where our working nav changes will live; when using new-ia feature flag, we will overwrite the navigation with a whole new navigation so we can really tinker with things. This will only overwrite public pages since below it we are still conditionally adding pages for logged in members.

[drew-usds]

Updates for sprint review 7/5

• Content is good for /resources and /help center
  • Pages are starting to be built out
• Work still in progress on home page and /product section
  • Andrea working on image ideas for home page
• Will need to carry this card over into the next sprint, but will be able to get this work published this coming sprint along with #5826 and #5859

[BerniXiongA6]

Hey @drew-usds I've updated the PPT deck with links to the content outline -- for "Product overview" section and "Support" overview section, see Versions B for links to both shared docs. Happy to update any other pieces of content for the MVP if needed, LMK. Thanks! cc: @a-chappelear

[hannasage]

Worked with @drew-usds to get the /resources page templated out so edits can be made in JSON rather than JSX

[drew-usds]

Am working on further cleanup on the templates for /resources and am duplicating some of that work over to /product and /support. Also am fleshing out the programmer's guide page where the PDF will live (for now).

Also have moved copies of our existing content to these new directories and appended Ia to thier constants so we can use them/make any needed edits without altering anything currently in prod.

[drew-usds]

Todo for 7/14:

• [x] Get Andrea's local env fully set up to be able to push/pull (was blocked by Docker setup, signed commits)
• [x] Get Kevin's help with /product section with mixed tsx and md content
• [ ] Kevin's help with redirects ex /contact to /support ... how can we make this work to future proof changes to paths as /support grows?
• [x] Kevin's help with breadcrumbs for /resources
• [x] Kevin's help: page titles working across templates/tsx/md files
• [x] Kevin: set up tests for routes to new pages (so we can eventually make this PR)
• [x] Andrea: paste in content to /product, format as MD (but don't worry about template perfection yet)
• [x] Andrea: paste in content to /built-for you, and format as MD (and don't worry about template perfection yet)
• [ ] Andrea: 2nd pass on /product pages, do we have parity with current product overview content? Is this section making sense? What quick edits do we need to make? Does the markdown formatting work?
• [x] Drew: Resources - add pdf to programmer's guide placeholder page
• [x] Drew: Resources - paste content to referral guide
• [ ] Drew: Template work on /product, /support
  • Is responsive
  • Is valid HTML (right Hx, right nesting, labels, accessible, etc)
  • Steps towards Figma mockups but doesn't have to be pixel perfect

Follow-on work

• [ ] Template work on /product content Andrea is working on