Skip to content

[Due for payment 2026-08-25] Clean up page header styles #98459

Closed

Description

@shawnborton

Right now we have a variety of page header styles throughout the app: some use h1 styles, some use h2 styles, some use simple illustrations, etc.

Let's clean up the majority of our page headers to use a simple, clean h2 style with no simple illustration. This will give us a few benefits:

  • consistency ftw
  • on mobile, removing the simple illustration makes the page titles feel less crammed
  • when we have h1 styles in the page content, this will give us a nicer feeling page hierarchy
  • on mobile, the h2 size feels a bit more appropriate as a page header as well

cc @dannymcclain @dubielzyk-expensify @JmillsExpensify @trjExpensify

Upwork Automation - Do Not Edit
Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. self-assigned this
    on Aug 12, 2026
  2. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Aug 12, 2026
  3. melvin-bot commented on Aug 12, 2026

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @truph01 (External)

  4. melvin-bot commented on Aug 12, 2026

    @melvin-bot
  5. changed the title [-]Clean up page header styles[/-] [+][Due for payment 2026-08-25] Clean up page header styles[/+] on Aug 18, 2026
  6. melvin-bot commented on Aug 18, 2026

    @melvin-bot

    @truph01

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.54-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2026-08-25. 🎊

    The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]

  7. melvin-bot commented on Aug 21, 2026

    @melvin-bot

    @truph01 Whoops! This issue is 2 days overdue. Let's get this updated quick!

  8. melvin-bot commented on Aug 24, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  9. melvin-bot commented on Aug 24, 2026

    @melvin-bot

    Payment Summary

    Resolving PRs:

    BugZero Checklist (@mallenexpensify)

    • I have confirmed assignees, roles, and Upwork contracts look correct
    • I have paid out Upwork contracts / manual NewDot requests
    • [BugZero Assignee] I have created a GH issue for creating/updating the regression test once above steps have been agreed upon
  10. mallenexpensify commented on Aug 26, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @truph01 due $250 via NewDot

    @truph01 plz complete the BZ checklist and tag me in a post once you have. I think QA might want to check this monthly, as they do with other design-related test cases.

  11. truph01 commented on Aug 28, 2026

    @truph01
    Contributor

    Contributor+ Checklist:

    • [Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to the comment on the PR:
      Link to the comment on the Issue:

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion:

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    Regression Test Proposal

    Precondition:

    Test:

    1. Open any Account settings page (e.g. Profile, Preferences, Security, Wallet, About), any Workspace page (e.g. Overview, Members, Categories, Accounting), and any Domain page (Admins, Members, Groups, SAML).
    2. Verify each page's header title renders at the h2 headline size (smaller than the previous larger title) and that no decorative illustration appears next to the title.
    3. Open the Workspace editor and Domain editor and verify the LHN title (workspace/domain name) renders using the h2 headline style.
    4. Verify the top-bar page title (e.g. Inbox/Reports) renders at the h2 size.

    Do we agree 👍 or 👎

  12. garrettmknight commented on Sep 7, 2026

    @garrettmknight
    Contributor

    $250 approved for @truph01

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionDailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions