Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Implement Documentation webpage: RADxMARS API ReportStream wrapper #17042

Open
10 tasks
jillian-hammer opened this issue Jan 10, 2025 · 1 comment
Open
10 tasks

Implement Documentation webpage: RADxMARS API ReportStream wrapper #17042

jillian-hammer opened this issue Jan 10, 2025 · 1 comment
Labels
engineering Work to be completed by an engineer experience Team label to flag issues owned by the Experience Team

Comments

@jillian-hammer
Copy link
Collaborator

jillian-hammer commented Jan 10, 2025 •
edited
Loading

Problem statement

The content written in Create Content Doc for adding NIH Wrapper guidance for MARS senders #16929 needs to be implemented on the website, so that users can easily reference it going forward.

What you need to know

  • Figma: use for design components and final content

Acceptance criteria

  • Page created with /documentation/radxwrapper URL path
  • Page design and content implemented per Figma design
  • "Last Updated" is the date the page will be deployed
  • Tag @jillian-hammer in PR for design & content QA
  • Add new page to sitemap.xml
  • E2E test for this page completed that checks for any user, logged in or not:
    • The page loads
    • If there is an error, the error is shown on the page
    • Page content loads without errors (including if the footer is showing, but not its functionality) (also, not checking the content itself, but just if it loads)
    • Components work as expected (eg, accordion expands/collapses, side nav, etc)
@jillian-hammer jillian-hammer added engineering Work to be completed by an engineer experience Team label to flag issues owned by the Experience Team needs-refinement Tickets that need refinement from the team labels Jan 10, 2025
@jillian-hammer jillian-hammer mentioned this issue Jan 10, 2025
Closed
2 tasks
@chris-kuryak
Copy link
Collaborator

Hey team! Please add your planning poker estimate with Zenhub @jpandersen87 @etanb

@chris-kuryak chris-kuryak removed the needs-refinement Tickets that need refinement from the team label Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
engineering Work to be completed by an engineer experience Team label to flag issues owned by the Experience Team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@chris-kuryak @jillian-hammer