Skip to content

feat: add dismissible survey banner to docs site - #289

Merged
Philip-Larsen-Donnelly merged 2 commits into
masterfrom
docs/survey-feedback-banner
Sep 18, 2026
Merged

Philip-Larsen-Donnelly merged 2 commits into
masterfrom
docs/survey-feedback-banner

Conversation

@DavidCKen

Copy link
Copy Markdown
Contributor

Adds a site-wide, dismissible banner linking to the docs feedback survey. It renders between the domain link bar and the main header, above all page content, via the existing Material announce block so it appears on every page across all build configs that share the custom theme.

Dismissal is remembered per-browser via localStorage, keyed by a banner id so a future survey can be shown again just by bumping that id in theme/main.html.

Proposed to stay active until 8/10/26 and then will remove and revert back

Adds a site-wide, dismissible banner linking to the docs feedback
survey. It renders between the domain link bar and the main header,
above all page content, via the existing Material `announce` block
so it appears on every page across all build configs that share the
custom theme.

Dismissal is remembered per-browser via localStorage, keyed by a
banner id so a future survey can be shown again just by bumping that
id in theme/main.html.
@github-actions

Copy link
Copy Markdown

@sonarqubecloud

Copy link
Copy Markdown

Quality Gate Failed Quality Gate failed

Failed conditions
2 New issues
2 New Code Smells (required ≤ 0)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

@github-actions

Copy link
Copy Markdown

@Philip-Larsen-Donnelly Philip-Larsen-Donnelly left a comment

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.

Looks OK to me.

Ideally we could have made this configurable (both content and visibility) via parameters in the main mkdocs.yml. That would be nice for potential future use.

It's fine to hardcode for now, but perhaps when we disable it, instead of removing completely we could parameterise it?

@Philip-Larsen-Donnelly
Philip-Larsen-Donnelly merged commit a24f4bc into master Sep 18, 2026
3 of 4 checks passed
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.

2 participants