feat(dashboard): decouple Pages sections + single deployer, add pip nav link#888
Open
WangLingxun wants to merge 3 commits into
Open
feat(dashboard): decouple Pages sections + single deployer, add pip nav link#888WangLingxun wants to merge 3 commits into
WangLingxun wants to merge 3 commits into
Conversation
…av link - Aggregate independent static sections via a declarative manifest (tools/backend_gap_report/pages-sections.json): 'sections' are mounted as subpaths, 'links' are nav-only entries (e.g. the pip index). The builder emits sections.json; the shell renders nav generically with no hardcoded section/link. Replaces the hardcoded (and mis-pathed, silently-skipped) projection copy. - Homepage 'Explore' nav is data-driven; the pip index link is probed and shown only when ./simple/ is present. - Single Pages deployer: remove deploy-projection.yml (it competed for the one Pages site); projection now publishes via the aggregator, and pre-merge preview is done by running the deploy workflow manually on a dev branch. - Delete migrated dashboard data under docs_deprecated/ (now on the dashboard-data branch).
WangLingxun
marked this pull request as ready for review
July 20, 2026 10:30
WangLingxun
requested review from
Xiaoming-AMD,
limou102 and
wenxie-amd
as code owners
July 20, 2026 10:30
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Make the Primus engineering dashboard's Pages publishing decoupled and single-deployer.
Report content now lives on a dedicated orphan
dashboard-databranch (weekly/monthly/backend-gap), pushed separately; tooling + site shell stay onmain. The deploy workflow overlays the data branch'sdocs/before building, so routine report runs never touchmain. Sibling static sites (e.g. the DeepSeek-V4 projection) are aggregated as subpaths via a declarative manifest instead of a second, clobbering Pages deployer.Commits
feat(dashboard): decouple Pages sections + single deployer, add pip nav link— addtools/backend_gap_report/pages-sections.json(sections= static dirs mounted at/<name>/;links= nav-only links such as the pip index);build_site_bundle.pyaggregates them and emitssections.json; the homepage nav is data-driven (probes./simple/so the pip link shows only when present). Removes the hardcoded (mis-pathed, silently-skipped) projection copy. Deletesdeploy-projection.yml(it competed for the single Pages site) — projection now publishes via the aggregator, and pre-merge preview is done by running the deploy workflow manually on a dev branch. Deploy workflow overlays thedashboard-databranch and drops the daily schedule (a companion workflow on the data branch auto-dispatches on push). Deletes the migrated dashboard data underdocs_deprecated/.docs(skill): note backend-gap data lives on the dashboard-data plane— trim the backend-gap skill to a one-line data-location note (branch/commit/deploy orchestration is owned by the caller, not the skill).Notes
dashboard-databranch is already pushed with the migrated reports; it also carriesnotify-dashboard-deploy.yml(auto-dispatch on data push). Merge order: merge this PR tomainfirst, so a data-branch push dispatches the new overlay-based deploy.workflow_dispatch) temporarily replaces production until the next normal deploy.release-build-wheel.ymlis independent; the/simple/pip index step is preserved.