Skip to content

[No QA] Split AgentZero upcoming-features roadmap into focused per-feature pages#94400

Draft
MelvinBot wants to merge 2 commits into
mainfrom
claude-splitAgentZeroUpcomingFeatures
Draft

[No QA] Split AgentZero upcoming-features roadmap into focused per-feature pages#94400
MelvinBot wants to merge 2 commits into
mainfrom
claude-splitAgentZeroUpcomingFeatures

Conversation

@MelvinBot

Copy link
Copy Markdown
Contributor

Explanation of Change

Splits the single AgentZero "Upcoming Features" reference page (docs/articles/Unlisted/AgentZero-Upcoming-Features.md) into 30 focused, per-feature reference pages, and converts the original page into a links-only index.

Why: The original page listed ~30 features across 10 categories in one file. AgentZero's help-doc retrieval embeds each .md file as a single vector, so a 30-feature page produced one "averaged" embedding that ranked poorly for specific queries. In the reported example, a "Certinia integration" question retrieved the top-10 most-similar accounting articles but the roadmap page ranked below #10 and was never seen by the model — so AgentZero answered that Certinia wasn't planned, even though it was on the page. (Full root-cause analysis: https://github.com/Expensify/Expensify/issues/651798#issuecomment-4785559358.)

Giving each upcoming feature its own tightly-scoped page means a focused query now matches a page whose entire embedding is about that one feature. Each page also front-loads product names and synonyms (e.g. Certinia / FinancialForce, Rillet, Puzzle.io, Dynamics 365 Business Central) into the title, keywords, and body to further strengthen retrieval.

What changed:

  • Added 30 new docs/articles/Unlisted/Upcoming-*.md pages — one per planned/in-development New Expensify feature — each preserving the original noindex: true, sitemap: false, and internalScope frontmatter so they remain AgentZero-referenced but excluded from public search.
  • Replaced the body of AgentZero-Upcoming-Features.md with a categorized, links-only index pointing to the focused pages (so there's still a single human hub, but it no longer competes with the focused pages in semantic search).

This is a docs-only change (markdown content under docs/articles/Unlisted/). These pages are served by direct URL and are not part of the hub routing system, so routes.yml does not change.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/651798
PROPOSAL: https://github.com/Expensify/Expensify/issues/651798#issuecomment-4785559358

Tests

// TODO: The human co-author must fill out the tests performed before marking this PR "ready for review".

  1. Confirm each docs/articles/Unlisted/Upcoming-*.md page renders and is reachable by direct URL.
  2. Confirm AgentZero-Upcoming-Features.md renders as an index and every link resolves to its focused page.
  3. After merge, confirm AgentZero retrieves a focused page for a feature-specific query (e.g. ask whether a Certinia integration is planned).
  • Verify that no errors appear in the JS console

Offline tests

N/A — static help-site documentation content.

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
  • 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

Screenshots/Videos

N/A — documentation-only change.

Co-authored-by: Stephanie Elliott <stephanieelliott@users.noreply.github.com>
@MelvinBot MelvinBot requested a review from a team June 24, 2026 04:47
@github-actions github-actions Bot changed the title Split AgentZero upcoming-features roadmap into focused per-feature pages [No QA] Split AgentZero upcoming-features roadmap into focused per-feature pages Jun 24, 2026
@OSBotify

This comment has been minimized.

Co-authored-by: Stephanie Elliott <stephanieelliott@users.noreply.github.com>
@MelvinBot

Copy link
Copy Markdown
Contributor Author

Fixed the failing spellcheck check.

The check failed on a single unknown word — HMRC (His Majesty's Revenue and Customs, the UK tax authority) — in docs/articles/Unlisted/Upcoming-Mileage-Rate-Effective-Dates.md:4. Since it's a valid acronym introduced by this PR's content, I added it to the project dictionary (cspell.json).

@OSBotify

Copy link
Copy Markdown
Contributor

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

Updated articles:

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants