Skip to content

πŸ“– dashboard: refresh the FAQ section - #12441

Merged
hivecommons-hive[bot] merged 2 commits into
v5from
docs/dashboard-faq-refresh
Oct 16, 2026
Merged

hivecommons-hive[bot] merged 2 commits into
v5from
docs/dashboard-faq-refresh

Conversation

@clubanderson

Copy link
Copy Markdown
Member

Closes #12439

What changed

src/pkg/dashboard/static/index.html β€” #faq-section / #faq-panel:

Audited against today's v5 docs/code β€” rewritten

  • What do L3–L6 allow? β€” the L6 bullet claimed a requires_human/reject verdict "pulls a PR out of the auto-merge lane". Per acmm-policy-matrix.md and running-at-level-6.md#does-the-hive-reviewer-stop-a-merge, the App auto-merge sweep does not read reviewer verdicts; the answer now says so and points at hold / branch rules. Also notes adjudicator/dedupe recommend only.
  • How do I move from L2 to L3? β€” names the level chip in the top bar as the dialog.
  • Advisory Digest / colors / ordering β€” trimmed, "bead" defined on first use, links to dashboard-sections.md#advisory-digest.
  • Timezone β€” now links its source (settings.md).
  • Spend / cadence / first day / where did the money go β€” kept; the "cadence vs run length" paragraph became its own question; the cost answer links dashboard-sections.md#cost; dropped the unsourced quota-publisher aside.
  • Footprint β€” the attribution-trailer sentence moved to its own question; links github-write-surface.md.
  • Two contributor-relay.md#run-stage-assignments-… anchors pointed at a heading that does not exist; now link the page.

Removed: nothing wholesale β€” every prior topic survives, but duplicated prose was folded into the questions above.

Added (each ≀ 4 sentences, one or more doc links, verified against code/docs)

Structure

  • Seven <section class="faq-group"> with <h3 class="faq-group-title">; every question is <details class="faq-q" id="faq-…"><summary>…</summary>…</details>.
  • #faq-filter ("Filter questions…", data-input-action="faqFilter") hides non-matching <details>, hides emptied groups, opens matches, shows "N of M" and a #faq-empty note.
  • "Was this answered?" footer β†’ Discord / in-dashboard feedback form / open an issue.
  • renderFAQ() collapsed summary now shows "N questions".
  • id="faq-section" and data-dashboard-section unchanged; layout/reorder/collapse tests untouched.

Style ratchet: all inline style= in the panel moved to token-based .faq-* classes. webstatic/style_ratchet_test.go baselines lowered (never raised): inlineStyles 1491β†’1432, rawFontSizes 630β†’603, rawBorderRadii 175β†’174.

Tests: new pkg/dashboard/faq_ui_test.go β€” section ids, filter input, every .faq-q has exactly one <summary>, every answer has an href, no inline styles in #faq-panel, no <details> without faq-q, stale-claim guard. Existing TestFAQConfigKeysExistInSchema still passes (all <code>dotted.keys</code> exist in config.Config).

Docs: dashboard-sections.md FAQ entry rewritten (first sentence == DASHBOARD_SECTION_HELP help text, ≀ 25 words); dashboard.md FAQ paragraph updated; nav title on the FAQ sidebar row updated. Changelog fragment changelog.d/changed-dashboard-faq-refresh.md.

Nothing here reads into or alters merge eligibility / auto-merge (RFC #12062 non-goals): the FAQ is static text plus a client-side filter.

cc @mrbobbytables

Re-audit every FAQ answer against current v5 behaviour, add the questions
people hit now (Evidence card, N behind, release channels, hold labels,
shadow mode, Model Gateway, Experiment Lab, attribution trailer, section
layout, audit log, pausing, mobile profile menu), make each question a
collapsible <details>, add a client-side filter and a 'Was this answered?'
footer, and move every inline style in the panel to token-based .faq-*
classes (style ratchet lowered 1491β†’1432 inline styles).

Closes #12439

Signed-off-by: Andy Anderson <andy@clubanderson.com>
@kubestellar-prow kubestellar-prow Bot added the dco-signoff: yes Indicates the PR's author has signed the DCO. label Oct 16, 2026
@kubestellar-prow

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign nicholasjackson for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubestellar-prow kubestellar-prow Bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Oct 16, 2026
@github-actions

github-actions Bot commented Oct 16, 2026 •

Copy link
Copy Markdown
Contributor

Open PR overlap check

Base branch: v5

Conflicts are checked with every PR merged onto the current tip of v5, so a PR that only needs a rebase is not reported as conflicting with its siblings.

PR Title Relation Files
#12388 ✨ dashboard: Evidence panel 4 β€” boundary enforcement (attempted vs blocked writes per tier; sentinel hits/week) same files src/pkg/dashboard/static/index.html
#12415 ✨ feat(dashboard): add evidence maintainability trend panel same files src/pkg/dashboard/static/index.html
#12332 ✨ feature: Add cadence templates for quickly setting cadence for all agents (#12300) same files src/pkg/dashboard/static/index.html
#12434 ✨ labels: stage/N state-machine labels for issues and PRs same files src/pkg/dashboard/static/index.html

…answer

TestStaticNoStrategyLabCopy pins the rename; link the dashboard-sections
entry instead of the legacy-named guide file.

Signed-off-by: Andy Anderson <andy@clubanderson.com>
@hivecommons-hive
hivecommons-hive Bot merged commit f130346 into v5 Oct 16, 2026
61 of 62 checks passed
@hivecommons-hive

Copy link
Copy Markdown
Contributor

merged by Hive trusted-author auto-merge: author @clubanderson holds role owner and GitHub permission admin on repo; CI green at 92c347a.

@kubestellar-prow
kubestellar-prow Bot deleted the docs/dashboard-faq-refresh branch October 16, 2026 15:28
@github-actions

Copy link
Copy Markdown
Contributor

Thank you for your contribution! Your PR has been merged.

We'd love to hear how your experience was: share feedback

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

Labels

dco-signoff: yes Indicates the PR's author has signed the DCO. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

πŸ“– dashboard: refresh the FAQ section β€” current, useful, one question per thing people actually ask

1 participant