[No QA] Docs updates for E/A#90029 Update Spend page filter popover UI docs

[MelvinBot]

Summary

• Updates the Getting Started with the Spend Page help article to reflect the new advanced filter UI introduced in Update advanced filters button to open filters popover #90029
• Documents the new popover-based filter experience on web (hover to see options, Apply for text/date/amount filters)
• Documents the full-screen filter experience on mobile with Apply and Reset buttons
• Adds separate web and mobile step-by-step instructions per HelpDot naming conventions
• Updates keywords to include new filter-related terms

Changes

• docs/articles/new-expensify/reports-and-expenses/Getting-Started-with-the-Spend-Page.md: Updated the "How to Use Filters" section with platform-specific instructions for the new advanced filter UI, added cross-link to search operators article, and updated heading to be task-based per authoring guidelines.

@bernhardoj, please review the files changed and confirm they reflect the current behavior. Then mark this PR Ready for review.

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR updates the "Getting Started with the Spend Page" article to document the new advanced filter popover UI introduced in PR #90029. It adds platform-specific (Web/Mobile) step-by-step instructions, updates keywords, improves a heading to be task-based, and adds a cross-link to the search operators article. The changes are well-scoped and generally align with governance standards, with a few items to address.

Scores Summary

• Readability: 8/10 - Steps are clear, sequential, and action-oriented. The Web/Mobile split is easy to follow. Minor concern: step 3 on web ("A popover opens showing available filters") is descriptive rather than action-oriented, which slightly breaks the step flow.
• AI Readiness: 7/10 - The new heading "How to apply advanced filters in New Expensify" is well-formed and task-based. However, the file is missing the internalScope YAML field required by HELP_AUTHORING_GUIDELINES.md Section 3. Additionally, there is no ## Who can use section, though this may be acceptable given the article pre-dates this PR. The heading "How filtering works on the Spend page" starts with an action verb and includes the feature name, which is good.
• Style Compliance: 8/10 - UI elements are properly bolded (e.g., Filters, Apply, Reset, Spend). The Web/Mobile split follows HELPSITE_NAMING_CONVENTIONS.md navigation rules. The cross-link uses descriptive anchor text and a relative link placed outside of numbered steps, per cross-linking standards.

Key Findings

Positive aspects:

• Correctly separates Web and Mobile instructions per governance navigation standards rather than merging them
• New heading "How to apply advanced filters in New Expensify" is properly task-based with the feature name included
• Keywords updated with relevant filter-related terms (filter popover, apply filters, reset filters, advanced filters)
• Cross-link to search operators article uses proper descriptive anchor text and relative path
• Steps are sequential and action-oriented

Items to address:

• The internalScope YAML metadata field is missing. Per HELP_AUTHORING_GUIDELINES.md Section 3, every article must include this field. While this was already missing before this PR, this is a good opportunity to add it.
• Web step 3 ("A popover opens showing available filters") is a system response description, not a user action. Consider removing it or integrating the information into step 2 (e.g., "Click the Filters button to open the filter popover.").
• The heading was changed from ## How Filtering Works to ## How filtering works on the Spend page -- good improvement adding the feature name, but note lowercase "filtering" vs the capitalized version. This is correct per sentence case rules.

Recommendations

1. Add internalScope to YAML frontmatter - e.g., internalScope: Audience is all Members and Admins. Covers viewing, filtering, and managing expenses on the Spend page. Does not cover creating expenses or configuring workspace settings.
2. Revise Web step 3 to be action-oriented rather than descriptive, or merge the popover detail into step 2.
3. Consider whether "advanced filters" is the exact UI terminology used in the product. If the UI simply says "Filters," the heading and body text should match precisely per HELPSITE_NAMING_CONVENTIONS.md core rules.

Files Reviewed

• docs/articles/new-expensify/reports-and-expenses/Getting-Started-with-the-Spend-Page.md - Updated filter section with platform-specific instructions, improved heading, added keywords and cross-link. Generally well-written with minor items noted above.

Review based on governance files: HELPSITE_NAMING_CONVENTIONS.md, HELP_AUTHORING_GUIDELINES.md, and TEMPLATE.md.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6acb03f406

ℹ️ 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".

[stephanieelliott]

The existing page describes the behavior as it is, I don't think this update is needed.

[stephanieelliott]

Eh decided to edit to more accurately represent how to search

[OSBotify]

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

Updated articles:

• articles/new-expensify/reports-and-expenses/Getting-Started-with-the-Spend-Page

[sakluger]

LGTM!

[OSBotify]

🚀 Deployed to staging by https://github.com/sakluger in version: 9.4.10-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

• Android
• iOS

[OSBotify]

🚀 Deployed to staging by https://github.com/sakluger in version: 9.4.12-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

• Android
• iOS

[OSBotify]

🚀 Deployed to staging by https://github.com/sakluger in version: 9.4.14-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

• Android
• iOS

[OSBotify]

🚀 Deployed to production by https://github.com/puneetlath in version: 9.4.14-1 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅