Skip to content

[No QA] [TEST - DO NOT MERGE] Add Payments hub demo structure for help site restructuring#92620

Open
stephanieelliott wants to merge 3 commits into
mainfrom
helpsite-standardize-demo
Open

[No QA] [TEST - DO NOT MERGE] Add Payments hub demo structure for help site restructuring#92620
stephanieelliott wants to merge 3 commits into
mainfrom
helpsite-standardize-demo

Conversation

@stephanieelliott
Copy link
Copy Markdown
Contributor

Introduce placeholder Payments-Reimbursement-and-Banking hub with nested sections, archive wallet-and-payments for the demo, and hide the old hub from navigation.

Explanation of Change

Fixed Issues

$
PROPOSAL:

Tests

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

Introduce placeholder Payments-Reimbursement-and-Banking hub with nested
sections, archive wallet-and-payments for the demo, and hide the old hub
from navigation.

Co-authored-by: Cursor <cursoragent@cursor.com>
@stephanieelliott stephanieelliott requested a review from a team as a code owner June 4, 2026 06:24
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented Jun 4, 2026

Concierge reviewer checklist:

  • I have verified the accuracy of the article
    • The article is within a hub that makes sense, and the navigation is correct
    • All processes, screenshots, and examples align with current product behavior.
    • All links within the doc have been verified for correct destination and functionality.
  • I have verified the readability of the article
    • The article's language is clear, concise, and free of jargon.
    • The grammar, spelling, and punctuation are correct.
    • The article contains at least one image, or that an image is not necessary
  • I have verified the formatting of the article
    • The article has consistent formatting (headings, bullet points, etc.) with other HelpDot articles and that aligns with the HelpDot formatting standards.
    • The article has proper text spacing and breaks for readability.
  • I have verified the article has the appropriate tone and style
    • The article's tone is professional, friendly, and suitable for the target audience.
    • The article's tone, terminology, and voice are consistent throughout.
  • I have verified the overall quality of the article
    • The article is not missing any information, nor does it contain redundant information.
    • The article fully addresses user needs.
  • I have verified that all requested improvements have been addressed

For more detailed instructions on completing this checklist, see How do I review a HelpDot PR as a Concierge Team member?

cc @johncschuster

@melvin-bot melvin-bot Bot requested review from johncschuster and mjasikowski and removed request for a team June 4, 2026 06:24
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented Jun 4, 2026

@mjasikowski @johncschuster One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

title: Learn how Payments, Reimbursement and Banking work in Expensify
description: Demo article for help site restructuring preview.
keywords: [demo, payments, reimbursement, banking]
order: 1
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing required YAML field: The internalScope field is mandatory per HELP_AUTHORING_GUIDELINES.md Section 3. Every article must include it to define the audience, covered workflow, and explicit exclusions. Example:

internalScope: Audience is [workspace admins and members]. Covers [payments and reimbursement overview], does not cover [specific bank account setup].

@@ -0,0 +1,11 @@
---
title: Learn how Payments, Reimbursement and Banking work in Expensify
description: Demo article for help site restructuring preview.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Non-compliant description: Per HELP_AUTHORING_GUIDELINES.md Section 3, the description must be a "1-2 sentence summary of outcome" that reflects real search intent. "Demo article for help site restructuring preview" is a placeholder that does not describe the article's purpose for SEO or AI retrieval.

---
<div id="new-expensify" markdown="1">

_Demo placeholder — help site restructuring preview._
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing required article structure: Per HELP_AUTHORING_GUIDELINES.md Sections 4 and 6, every article must include: (1) exactly one # heading matching the article title, (2) task-based ## sections, and (3) at least one "How to..." heading for AI retrieval optimization. This article has no headings or substantive content beyond the placeholder line.

title: Learn about getting reimbursed in Expensify
description: Demo article for help site restructuring preview.
keywords: [demo, reimbursement]
order: 1
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing required YAML field: The internalScope field is mandatory per HELP_AUTHORING_GUIDELINES.md Section 3. Add it to define the target audience, covered workflow, and explicit exclusions.

@@ -0,0 +1,11 @@
---
title: Learn about getting reimbursed in Expensify
description: Demo article for help site restructuring preview.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Non-compliant description: The description must summarize the article's outcome for SEO and AI retrieval, not serve as a placeholder notice. Per HELP_AUTHORING_GUIDELINES.md Section 3.

title: Set up a personal bank account
description: Demo article for help site restructuring preview.
keywords: [demo, personal bank account]
order: 2
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing required YAML field: The internalScope field is mandatory per HELP_AUTHORING_GUIDELINES.md Section 3.

@@ -0,0 +1,11 @@
---
title: Set up a personal bank account
description: Demo article for help site restructuring preview.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Non-compliant description: The description must summarize the article's outcome, not serve as a placeholder. Per HELP_AUTHORING_GUIDELINES.md Section 3.

title: Learn about managing bank accounts in Expensify
description: Demo article for help site restructuring preview.
keywords: [demo, bank accounts]
order: 1
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing required YAML field: The internalScope field is mandatory per HELP_AUTHORING_GUIDELINES.md Section 3.

title: Delete your personal bank account
description: Demo article for help site restructuring preview.
keywords: [demo, delete bank account]
order: 2
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing required YAML field: The internalScope field is mandatory per HELP_AUTHORING_GUIDELINES.md Section 3.

title: Share your business bank account
description: Demo article for help site restructuring preview.
keywords: [demo, share bank account]
order: 3
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing required YAML field: The internalScope field is mandatory per HELP_AUTHORING_GUIDELINES.md Section 3.

title: Learn about reimbursing employees in Expensify
description: Demo article for help site restructuring preview.
keywords: [demo, reimburse employees]
order: 1
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing required YAML field: The internalScope field is mandatory per HELP_AUTHORING_GUIDELINES.md Section 3.

title: Learn about reimbursing employees internationally
description: Demo article for help site restructuring preview.
keywords: [demo, international reimbursement]
order: 1
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing required YAML field: The internalScope field is mandatory per HELP_AUTHORING_GUIDELINES.md Section 3.

title: Set up a CAD business bank account
description: Demo article for help site restructuring preview.
keywords: [demo, Canada, CAD]
order: 4
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing required YAML field: The internalScope field is mandatory per HELP_AUTHORING_GUIDELINES.md Section 3.

title: Set up a SGD business bank account
description: Demo article for help site restructuring preview.
keywords: [demo, Singapore, SGD]
order: 5
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing required YAML field: The internalScope field is mandatory per HELP_AUTHORING_GUIDELINES.md Section 3.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 4, 2026

HelpDot Documentation Review

Overall Assessment

This PR restructures the "Wallet & Payments" hub into a new "Payments, Reimbursement & Banking" hub with a deeper nested hierarchy. It archives 17 existing articles into _demo-hidden/, creates 14 new placeholder (demo) articles, adds 6 new hub HTML pages, updates _routes.yml references, and renames the hub index. The new articles are all placeholder stubs with no real content, which limits the depth of content-quality assessment, but the structural and metadata choices can still be evaluated against governance standards.

Scores Summary

  • Readability: 5/10 - All 14 new articles contain only a single italic placeholder line ("Demo placeholder -- help site restructuring preview.") with no actionable content, steps, or explanations. While this is expected for a structural demo, the articles as proposed are not useful to any reader or AI retrieval system. The hub description update in _routes.yml ("Get reimbursed, pay employees, and manage bank accounts in Expensify.") is clear and well-written.
  • AI Readiness: 4/10 - YAML frontmatter is present on all new articles with title, description, keywords, and order, which is good. However, internalScope is missing from every new article -- this is a mandatory metadata field per HELP_AUTHORING_GUIDELINES.md Section 3. The description fields are all identical generic text ("Demo article for help site restructuring preview.") rather than outcome-focused summaries that reflect search intent. Keywords use "demo" as the primary keyword, which does not match real user search queries.
  • Style Compliance: 7/10 - The hub naming ("Payments, Reimbursement & Banking") and article titles follow naming conventions well. Titles like "Set up a US business bank account" and "Learn about getting reimbursed in Expensify" are task-based and use appropriate action verbs. The _routes.yml description update uses clear, user-facing language. No prohibited language or incorrect UI references were found in the changed content.

Key Findings

  • Missing internalScope metadata: All 14 new articles lack the mandatory internalScope field. Per HELP_AUTHORING_GUIDELINES.md Section 3, every article must include internalScope defining the audience, covered workflow, and explicit exclusions.
  • Generic descriptions: Every new article uses the identical description "Demo article for help site restructuring preview." This does not satisfy the metadata requirement for a "1-2 sentence summary of outcome" that reflects real search queries.
  • Placeholder keywords: Keywords like [demo, reimbursement] and [demo, personal bank account] include "demo" as a keyword, which will not match real user search intent. Even for a demo, these should model production-quality keywords.
  • Good structural hierarchy: The nested folder structure (e.g., Reimburse-Employees/Reimburse-Employees-Internationally/) is logical and well-organized for future content expansion.
  • Clean archive approach: Moving old articles to _demo-hidden/ preserves content while keeping the live site clean during the transition.
  • Route updates are consistent: The _routes.yml changes correctly point to the new hub landing article and update the hub title and description.

Recommendations

  1. Add internalScope to all new articles -- Even as placeholders, this field should be populated to model the expected final structure. Example: internalScope: Audience is employees. Covers getting reimbursed via Expensify, does not cover reimbursing others or admin bank account setup.
  2. Replace generic descriptions with outcome-focused summaries -- Each article should have a unique description reflecting what the final article will cover, not a generic demo label.
  3. Replace "demo" keywords with realistic search terms -- Model production keywords now so the structure demonstrates real AI retrieval readiness. For example, [reimbursement, get reimbursed, personal bank account, direct deposit] instead of [demo, reimbursement].
  4. Consider adding a note or comment in articles indicating these are structural placeholders -- this helps future authors understand the intent without relying solely on the PR description.
  5. Verify that deeply nested paths (e.g., 5 levels deep for international reimbursement articles) will render correctly in the Jekyll site and do not create navigation usability issues.

Files Reviewed

  • docs/_data/_routes.yml -- Route updates are clean and consistent with the new hub structure.
  • docs/articles/new-expensify/Payments-Reimbursement-and-Banking/Learn-how-Payments-Reimbursement-and-Banking-work-in-Expensify.md -- Hub landing article; placeholder only; missing internalScope.
  • docs/articles/new-expensify/Payments-Reimbursement-and-Banking/Get-Reimbursed/*.md (2 files) -- Placeholder stubs; missing internalScope.
  • docs/articles/new-expensify/Payments-Reimbursement-and-Banking/Manage-Your-Bank-Accounts/*.md (3 files) -- Placeholder stubs; missing internalScope.
  • docs/articles/new-expensify/Payments-Reimbursement-and-Banking/Reimburse-Employees/*.md and subdirectories (8 files) -- Placeholder stubs; missing internalScope.
  • docs/new-expensify/hubs/Payments-Reimbursement-and-Banking/*.html (6 files) -- Standard Jekyll hub pages; correctly structured.
  • 17 renamed files (wallet-and-payments -> _demo-hidden/) -- Content preserved, clean archive.

Note: Since all new articles are structural placeholders with no substantive content, a full content-quality review (step formatting, cross-linking, FAQ structure, heading hierarchy within articles) is not applicable at this stage. Scores reflect the metadata and structural aspects that can be evaluated now.

title: Set up a UK/GBP business bank account
description: Demo article for help site restructuring preview.
keywords: [demo, UK, GBP]
order: 2
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing required YAML field: The internalScope field is mandatory per HELP_AUTHORING_GUIDELINES.md Section 3.

title: Set up an AUS business bank account
description: Demo article for help site restructuring preview.
keywords: [demo, Australia]
order: 3
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing required YAML field: The internalScope field is mandatory per HELP_AUTHORING_GUIDELINES.md Section 3.

title: Learn about reimbursing employees in the US
description: Demo article for help site restructuring preview.
keywords: [demo, US reimbursement]
order: 1
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing required YAML field: The internalScope field is mandatory per HELP_AUTHORING_GUIDELINES.md Section 3.

title: Set up a US business bank account
description: Demo article for help site restructuring preview.
keywords: [demo, US business bank account]
order: 2
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing required YAML field: The internalScope field is mandatory per HELP_AUTHORING_GUIDELINES.md Section 3.

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7ba37c0d14

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread docs/_data/_routes.yml Outdated

- href: wallet-and-payments
title: Wallet & Payments
- href: Payments-Reimbursement-and-Banking
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Add redirects before removing wallet pages

When this docs deploys, existing bookmarks, search results, and still-present internal links that point at /new-expensify/hubs/wallet-and-payments or /articles/new-expensify/wallet-and-payments/... will 404 because the hub href is changed here and the old article files were moved under docs/_demo-hidden (which Jekyll does not publish); I also checked docs/redirects.csv and there is no new mapping for these URLs. Please add redirects or keep aliases for the old hub and article URLs before switching the route.

Useful? React with 👍 / 👎.

Keep existing article URLs working without redirects by bringing back
wallet-and-payments next to Payments-Reimbursement-and-Banking.

Co-authored-by: Cursor <cursoragent@cursor.com>
@github-actions github-actions Bot changed the title [TEST - DO NOT MERGE] Add Payments hub demo structure for help site restructuring [No QA] [TEST - DO NOT MERGE] Add Payments hub demo structure for help site restructuring Jun 4, 2026
@OSBotify

This comment has been minimized.

@OSBotify

This comment has been minimized.

Move Payments hub first on New Expensify, use custom titles and order via
_section.yml, read article titles from front matter, and center section
cards by matching article-card styling.

Co-authored-by: Cursor <cursoragent@cursor.com>
@OSBotify
Copy link
Copy Markdown
Contributor

OSBotify commented Jun 4, 2026

A preview of your ExpensifyHelp changes have been deployed to https://4b7a7ca6.helpdot.pages.dev ⚡️

Updated articles:

@stephanieelliott stephanieelliott added the HelpDot Apply this label if the issue relates to ExpensifyHelp label Jun 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

HelpDot Apply this label if the issue relates to ExpensifyHelp

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants