Closed tbaker1026 closed 3 months ago
Hi @tbaker1026 @rachelshearerux, here is the IA spec with some of the entry points we have proposed for the this form. We are recommending this form lives in the Records hub with entry points on the hub page and left nav. When someone clicks on it, it will take them directly into the form flow. As mentioned during our sync, @megzehn and I plan to do a Drupal audit that includes this form so the entry points listed in the IA spec may not be exhaustive yet. The spec isn't finalized yet with a confirmed URL, but we have documented breadcrumb path. Let me know if there's any questions! Happy to chat some more.
@jennymayoco Do we have the final URL and breadcrumbs for this form?
Hi @tbaker1026 @rachelshearerux @megzehn - here is the finalized IA spec. We also added additional guidance for redirects and best bets in the future. Let me know if there's any questions!
Hi @tbaker1026 @rachelshearerux , @megzehn and I have added an entry point for this form in the Supporting Forms page and this has been documented in the IA spec. This update is so that we can add a react widget to a static page since the entry point for this form goes directly into the flow. The true home will still be in Records so this doesn't impact URL or breadcrumbs. Let me know if there are any questions!
@jennymayoco @megzehn We will first add it to the Supporting Forms page with the react widget on and only add it to the other pages once we are 100% live with the form - right?
Yes, exactly, @tbaker1026
I confirmed with @tbaker1026 that the form is 100% live, so we can add the additional entry points now. I've reviewed all planned entry points in the IA Spec, and summarized the needed work at the top of the spec. There's two types of work here:
About your team
CAIA Support Request
Describe what you need in a few sentences:
Examples
Which are you doing?
Types of Support
What areas does your team need support in? Check all that apply.
Content
Accessibility
IA
Multilingual content
Timeframe
We guide and work alongside teams across nearly every OCTO digital product. We also work with partners across VA to lead content migration and manage all unauthenticated content on VA.gov. And we're always working to expand the VA.gov content style guide and our IA and accessibility documentation. We need to prioritize all intake requests based on our overall workload and VA and OCTO priorities.
Tell us about your product's timeline. And we'll work with you to meet timeline needs as best we can.
Have you worked with CAIA before?
What's your team’s next step and its timing?
Timing for your next step:
Is this timing related to a specific event or Congressionally mandated deadline?
If you're conducting research, when is that starting?
Provide date if available: xx/xx/xxxx
Will you release this new product incrementally (for example, release to 25% of users to start)?
Note: If you checked yes, we’ll reach out to discuss details about the content in the react widget (we use these widgets to display entry points for new products to a certain percentage of users who visit our static pages).
When do you expect to launch your product to 100% of users?
Please provide an estimated date so our team can create other relevant tickets.
Collaboration Cycle
Will this work be going through the Collaboration Cycle?
If no ...
If yes ...
Please provide the link to your Collaboration Cycle ticket:
Please check all of the phases in the Collaboration Cycle you have completed:
For planning purposes, please check all of the phases in the Collaboration Cycle you feel you might need CAIA support and guidance:
Design Intent
Midpoint
Staging
Supporting artifacts
Please provide links to supporting artifacts as available.
Additional Support: Collaborative Sessions
Have you already worked with someone from OCTO leadership?
How do you plan to work with us on this request?
Accessibility Help in Slack
The #accessibility-help channel in the DSVA Slack, is also available to you as a resource. Everyone is welcome to ask questions or get help from our a11y (accessibility) specialists. Tag
@Terry Nichols
to get a11y help asap.Next steps
Once you’ve submitted this ticket, please post a link to this issue in the #sitewide-content-ia Slack channel and tag
@Terry Nichols
.If you also need engineering support from the Public Websites team, fill out their intake request form.
If you need a page/URL redirected, a URL changed or a vanity URL set up, please submit a Redirect, URL change, or vanity URL request
If you are requesting a11y support for user research, please complete this form, next.