Change "Page header" to "Header"

[natalia-fitzgerald]

Propose changing "Page header" to "Header

For the sake of simplicity and clarity, I would like to propose renaming "Page header" as "Header".

• This aligns with the cf.gov code <header class="o-header>
• Header is the standard name for this component across other Design Systems, like the USWDS and UK.gov, Carbon Design System, and VA.gov
  • USWDS calls this component "Header", UK.gov calls it "Gov.UK Header," Carbon calls it "Global header, and "VA.gov" calls it "Header."
  • Both USWDS and VA.gov use "Header" so it is reasonable that we align with that approach
• This makes "Header" parallel with "Footer" (we don't say page footer)
• If we add this to the DS in the future it will be called Header to align with the code <header class="o-header>, conventional naming, and USWDS
• Including the word "page" could confuse a user and suggest that it is a variant of "Header" rather than the "Header itself.

Here's a link to the component:
Page header: https://cfpb.github.io/design-system-react/?path=/docs/components-draft-page-header--overview

Are there any concerns with making this change? I so realize that a number of projects use this component so there would be some implementation work to making this change.

@flacoman91 @virginiacc @billhimmelsbach

[virginiacc]

I'd be fine with this change, although I wonder if having a modifier is useful to clarify the type of header this component is since sometimes the term "header" is used generally (instead of heading, etc).

Edit: Since other gov design systems like USWDS and VA.gov use Header, I think it makes sense for us to follow that pattern. Thanks for providing those examples, @natalia-fitzgerald!

[natalia-fitzgerald]

@virginiacc @billhimmelsbach @flacoman91
I can go ahead and make this change on the stories page (documentation content) but I will also want us to rename this component on the component side. For my understanding, can you share here what that process looks like? Would this mean a change on the DSR side and then on the code side for the projects that pull in this component?

[billhimmelsbach]

Yeah @natalia-fitzgerald, it would require a change on the component, the exports, and the projects that implement it. I'd probably include a dev in on it.

[natalia-fitzgerald]

We've completed this change and it is live in the DSR.