Skip to content

Commit

Permalink
Merge branch 'main' into allison0034-patch-2
Browse files Browse the repository at this point in the history
  • Loading branch information
humancompanion-usds authored Dec 3, 2024
2 parents 88eb00c + b70d6d5 commit ee4b29c
Show file tree
Hide file tree
Showing 7 changed files with 174 additions and 39 deletions.
3 changes: 2 additions & 1 deletion src/_components/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,12 +42,13 @@ All teams must now be using the v3 versions of our web-components. The Design Sy
</div>
</va-alert>

### Governance rules for using v3-based components
### Governance rules for using components

v3-based versions of the components are designed to sit alongside our current v1 based components and the foundational elements of the Design System. Teams must use the new versions of our web-components and following these rules:

* Do not mix and match different versions (v1 vs. v3) of the same component on the same page. For example, if you were to use the v3-based version of the [accordion component]({{ site.baseurl }}/components/accordion) on a page, that version must be used throughout that page (and ideally throughout your application as soon as possible).
* Do not mix and match v1 and v3 based [form components]({{ site.baseurl }}/components/form/) in the same application flow. For example, if you were to use the v3-based version of the radio button component on the first step in an application, that version must be used on all subsequent steps throughout the flow.
* Most examples of design system components can be found in Storybook. If your team is using any component outside of the design system web components, that is considered an imposter component and will be listed as a violation at your Staging Review. This includes components that are coded to look and function like design system web components, but do not use the design system code.

{% include components-patterns-templates.md %}

Expand Down
210 changes: 172 additions & 38 deletions src/_templates/hub.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,79 +7,213 @@ intro-text: "Hub pages serve as a landing page for particular benefits."
figma-link: https://www.figma.com/design/4A3O3mVx4xDAKfHE7fPF1U/VADS-Templates%2C-Patterns%2C-and-Forms?node-id=2607-31366&t=1fh2gr46l2FEHw8n-1
anchors:
- anchor: About
- anchor: Guidance
- anchor: Example
- anchor: Structure
- anchor: Right-rail
---

## About

A hub page page does the following:
- Provides an executive summary of this hub
- Provides links to lead users to specific sections about that benefit
- Crosslink to related benefits
- Allows users to connect via social media
- Provides contact information for this benefit
A hub page provides an overview of what is included in the section, links to the top content pages in the section, crosslinks to related resources, and contact information.

## Guidance

### When to use

**Provide a landing page for a benefit or service category.**
Use a hub page as a parent page to a section of the site to provide an overview and navigation to the content and tools for the benefits or services offered within that section.

**Provide a landing page that includes all VA benefits available for a single core audience.**
Use a hub page to provide a list of all the benefits available for one of the 3 core audiences VA serves: Veterans, transitioning service members, and family members of Veterans.

### When to consider something else

**A landing page for a campaign.**
Don't use a hub template to create a landing page to support a campaign. Consider using a Campaign Landing Page for that purpose.

**A landing page for a custom mix of benefits and services.**
Don't use a hub template to create a landing page for a custom grouping of select benefits or services, for purposes such as a health condition or a small audience segment. Consider using a Campaign Landing Page or a Resources and support page.

### Usability guidance

**Don't link to every child page in the hub.**
Don't overload visitors by presenting everything available. Highlight the most important content and features within the hub/section and allow the visitor to drill down to explore more.

**Don't create content just to fill the template.**
Creating unnecessary content only creates an additional burden on visitors to sift through what's important. If you don't have enough content to fill the required sections, this template may not be the right one for your project.

**Don't add sections to the template.**
This template is designed to be a simple landing page that maximizes focus on the core tasks—applying, using, managing, and tracking—for a benefit or service category. Adding unnecessary sections or elements can create additional noise and distract from the core tasks.

**Follow section-specific guidance.**
Refer to the guidance below for the individual sections in the structure.


## Example

![Image of va.gov housing assistance hub page]({{site.baseurl}}/images/templates/hub/housing-assistance.png)
<a class="vads-c-action-link--blue" href="https://www.va.gov/disability/">View example: VA.gov Disability hub</a>

The hub page pattern can be broken down into an ordered set of components:
![Image of va.gov housing assistance hub page]({{site.baseurl}}/images/templates/hub/housing-assistance-markup.png)
![Screenshot of VA.gov disability benefits hub page]({{site.baseurl}}/images/templates/hub/benefit-hub-outline-desktop.png)

## Structure

We surface information that is important to Veterans first. The hierarchy of a hub page is as follows:
The hub page pattern can be broken down into an ordered set of components.

All sections are required unless specifically noted below as optional. All sections are required to appear in the hierarchical order and placement shown.

The hub page consists of:

- [Intro section](#intro-section)
- [Hub icon and page title (1)](#1-hub-icon-and-page-title)
- [Intro text and On this page (2)](#2-intro-text)
- [Critical alert (optional)](#critical-alert-optional)
- [Spokes](#spokes)
- [Divider (3)](#3-divider)
- ['Get benefits' spoke (4)](#4-get-benefits-spoke)
- ['Manage benefits' spoke (5)](#5-manage-benefits-spoke)
- ['More resources' spoke (6)](#6-more-resources-spoke)
- [Related benefits (7)](#7-related-benefits)
- [Right rail](#right-rail)
- [Promo spot (8)](#8-promo-spot)
- [Ask questions accordion (9)](#9-ask-questions-accordion)
- [Not a Veteran accordion (optional)](#not-a-veteran-accordion--optional)
- [Connect with us accordion (10)](#10-connect-with-us-accordion)

### Intro section

### Page title (h1)
![Introduction section of mobile view of VA.gov disability benefits hub page]({{site.baseurl}}/images/templates/hub/benefit-hub-intro.png)

Tells the user what's on this page, is also important semantically for html, defined in Foundation [here]({{ site.baseurl }}/foundation/typography#headings)

### Intro text
#### 1. Hub icon and page title

Similar to the title, Intro text is an executive summary of page content, defined in Foundation [here]({{ site.baseurl }}/foundation/typography#paragraphs). Intro text is also important for SEO.
##### Icon
Each benefit or service hub is assigned a specific icon. This icon is utilized on the hub page, the top/primary navigation, and on the home page of VA.gov. The icon assigned to a benefit or service hub, should be consistently used.

### Jump link navigation (On this page)
For new benefit or service hubs, do not use an icon already in use.

Jump link nav serves two purposes: 1) It informs users what sections are on this particular page, and 2) it allows the user to jump to the section they wish to read.
Refer to approved [icons for benefit hubs]({{site.baseurl}}/foundation/icons#hub).

##### Page title

### Section breaks
The page title is the name of the benefit category or service category.

In order to be clear when a section begins, we use a "—★★★★★—" visual treatment documented [here]({{ site.baseurl }}/components/divider)
Refer to guidance on [page titles and section titles]({{site.baseurl}}/content-style-guide/page-titles-and-section-titles).

### Section 1 (h2)
#### 2. Intro text
This paragraph gives the user a high-level understanding of the benefit category and provides SEO-rich content.

The first section on a Hub page template contains information about how a Veteran might go about getting this benefit. Our h2s are defined in [Foundation]({{ site.baseurl }}/foundation/typography#headings)
#### On this page
Refer to guidance for the ['On this page' component]({{site.baseurl}}/components/on-this-page).

### Section 2 (h2)
#### Critical alert (optional)
This is an optional alert intended to provide critical information related to the benefit hub.
- There are only 2 alerts available for this placement - Help for visitors experiencing homelessness or help with mental health care
- Only 1 alert can be added to a hub page

The second section on a Hub page template contains information about how a Veteran might go about managing this benefit.
Over-using these alerts can result in "banner blindness" where users unconsciously ignore banner-like or commonly repeated information. Only include an alert if it is critical to the benefit hub. The alerts should never be on all benefit hubs, ideally, they would only be on 2 or 3 hubs at most.

### Section 3 — optional (h2)
This element uses a combination of a standard alert and an expandable alert, which is not approved for use outside of this use case.

The third section on a Hub page template contains information about how a Veteran might go about finding more information about this benefit.
Refer to guidance for the [Alert component]({{site.baseurl}}/components/alert) or the [Alert-Expandable component]({{site.baseurl}}/components/alert/alert-expandable).

### Link and teaser component
### Spokes

Each section contains a set of "link + teaser" components which takes the user to a particular subsection of the benefit (e.g. a page to see if they are eligible for health care, a page to apply for health care, etc). This component doesn't have a home in our design system yet.
![Spokes section of mobile view of VA.gov disability benefits hub page]({{site.baseurl}}/images/templates/hub/benefit-hub-spokes.png)

### Cross-reference / footnote component
Each hub is broken into sections referred to as "spokes". All content within a hub is then categorized into one of the spokes. These spokes are required in the side navigation of a hub but are not part of a page's URL or breadcrumb. A hub must have at least one spoke, and no more than 3 spokes.

At the bottom of every Hub page, we list benefits that are related to, but not part of, the current benefit the user is viewing. All of these links drive users to other hub pages, so we treat this section visually different than the Link and teaser component. This content also deserves to be component-ized.
#### Standard spokes
Hubs that feature a single benefit or service category use a set of standard spokes. Examples of this are health care, disability, or decision reviews. Labels for each of these spokes on the hub page are tailored to the appropriate terminology of that hub (i.e. "Get health care and benefits" in health care vs "Request a decision review" in decision reviews).
- Get benefits - content that supports applying or filing for a benefit or service
- Manage benefits - content related to using, tracking, or, managing a benefit or service
- More resources - helpful, related content or tools such as benefit rates, discovery tools, and resources and support pages

## Right rail
#### Exceptions
All uses of this template should follow the standard spokes, but there are some instances where the content within the hub doesn't work with that structure.

The right rail is the content area on the right side of the page. It is used to house additional information that is supplemental to the main content on the page. The right rail contains distinct blocks of content that can include headers, paragraphs, links, images, and accordions.
##### Multi-benefit hubs
- Hubs that feature multiple benefit or service groups may require different spokes since the visitor may be able to get or manage multiple types of benefits.
- In these cases, choose a categorical grouping that meets the needs of that hub.
- Examples:
- The [family member benefit hub](https://www.va.gov/family-and-caregiver-benefits/) only utilizes a single "Get benefits" spoke that includes links to each benefit category (health, disability, education, etc.).
- The 3 spokes in the [service member hub](https://www.va.gov/service-member-benefits/) are based on pre-transition, during-transition and after-transition assistance in order to emphasize the time-sensitive nature of some of the benefits.

### Promo spot
##### Benefit hubs with minimal content
- Hubs that have very little content to fill one of the standard spokes, may eliminate that spoke or replace it with something more meaningful to the category.
- Examples:
- Burials and memorials - This hub does not have benefits that you track and manage, so a spoke for content related to planning a burial replaces the standard manage spoke.

In the first position within the right rail, at the top, we include a Promo spot with a visual image that complements the main content on the page. The Promo spot is informational.
#### 3. Divider
A divider is used before and after each spoke.

### Accordion
Refer to guidance for a [divider]({{site.baseurl}}/components/divider).

In the second position within the right rail, we list accordions containing specific groups of content. These accordions are the lowest priority pieces of content on a hub page, and they are positioned as such—at the bottom of the page. Some examples of accordions are:
#### 4. 'Get benefits' spoke
This section contains only information related to what is required or how to get the benefits included in the hub.
- Spoke title: The title includes the word "Get" and the benefit category name.
- The spoke should include no more than 10 links.
- Each item in the spoke should include a link label and teaser text.
- The label should generally match the H1 of the destination page but may have additional words to be more descriptive if needed.
- Only include links to content and tools that live within the same hub.
- The only exception to this is a link to family member or caregiver benefits.
- Link order should follow this general pattern:
- Links related to the primary benefit of the hub (include pages as available)
- About the primary benefit
- Eligibility for the primary benefit
- How to apply for the primary benefit
- Apply online for the primary benefit
- A single link for each secondary benefit within the hub (may be more than 1)
- A single link for family or caregiver benefits (this will link to the family member hub)

#### 5. 'Manage benefits' Spoke
This section contains only information related to helping visitors use, track, or manage a benefit they have already applied for.
- Spoke title: The title includes the words "Manage your" and the benefit category name.
- The spoke should include no more than 10 links.
- Priority should be given to content or tools most frequently used.
- Each item in the spoke should include a link label and teaser text.
- The label should directionally match the H1 of the destination page but may have additional words to be more descriptive if needed.
- Links in this section may lead to content or tools outside of this hub.
- Link order is determined by frequency of use within this hub.

* "Ask questions" a short list of contact emails and phone numbers
* "Not a Veteran" helpful links for folks that aren't Veterans
* "Connect with us" social media links
#### 6. 'More resources' Spoke
This section contains links to other content pages or tools related to the benefit.
- Spoke title: The title is "More information and resources" in all hubs
- The spoke should include no more than 10 links.
- Priority should be given to content or tools most frequently used or referenced.
- This section should contain links to benefit rates, helpful tools and Resources and support pages related to the benefit hub.
- Each item in the spoke should include a link label and teaser text.
- The label should directionally match the H1 of the destination page but may have additional words to be more descriptive if needed.
- Link order should follow this general direction:
- Benefit rates page
- Tools that help users understand or evaluate the benefit, such as calculators, benefit specific search tools, or eligibility checkers
- All other links should be ordered by page views

#### 7. Related Benefits
This section helps veterans find other VA benefits that don't live within this benefit hub.
- Section title - "Other VA benefits and services"
- This section should contain no more than 5 links.
- Only include links to benefits that live outside of the current benefit hub.
- Link order is based on overall page views.

### Right rail

![Right rail/bottom section of mobile view of VA.gov disability benefits hub page]({{site.baseurl}}/images/templates/hub/benefit-hub-right-rail.png)

The right rail is the content area on the right side of the desktop view of the page. On mobile, the elements within the right rail are displayed at the bottom of the page before the footer. It includes information related to the administration that provides the benefits and services within the hub.

#### 8. Promo spot
The promo spot provides a space for business lines to highlight key information, or a specific service directly related to the benefit hub.
- The image, link, and supporting text is displayed in both the hub placement as well as in the top nav fly-out (desktop view only) for each benefit hub.
- The link label should directionally match the H1 of the destination page.
- Only content or services for Veterans or family members should be featured.

#### 9. 'Ask questions' accordion
- Provides key contact info for veterans and family members to get assistance with the hub's benefits or services.

#### 'Not a Veteran?' accordion (optional)
- Provides a space to place key links for visitors that are not Veterans or family members.
- Maximum of 3 links.
- The link label should directionally match the H1 of the destination page and include reference to the appropriate audience it serves.

#### 10. Connect with us accordion
- Provides links to social media accounts, an email subscription option (if applicable), and the website for the administration or VA's central office.
Binary file added src/images/templates/hub/benefit-hub-intro.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added src/images/templates/hub/benefit-hub-spokes.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit ee4b29c

Please sign in to comment.