Skip to content

New feat banner - #2761

Closed
amazingphilippe wants to merge 0 commit into
mainfrom
new-feat-banner
Closed

amazingphilippe wants to merge 0 commit into
mainfrom
new-feat-banner

Conversation

@amazingphilippe

@amazingphilippe amazingphilippe commented Aug 18, 2026 •

Copy link
Copy Markdown
Contributor

Summary | Résumé

Adding a prototype for a new-feature banner that we can anchor to any part of the UI, or insert as a flowing container where needed.

How it works:

  • Add the new feature banner anywhere. We don't want it to hide content (for a11y), so it has to position in the document flow.
  • If we plan this well, we can add an optional CSS anchor on a specific element. A caret will point to that anchor for some visual interest.
  • Set a lifespan so that the banner stops showing up.
  • There is a script to find expired banners so that we can easily clean up periodically

Test instructions | Instructions pour tester la modification

  • Check any email template where file attachments is enabled.
  • Refresh the page, the banner should persist
  • Hide the banner
  • Refresh the page, the banner should not show up

@github-actions

Copy link
Copy Markdown

@github-actions

Copy link
Copy Markdown

@amazingphilippe
amazingphilippe requested review from andrewleith, jzbahrai and smcmurtry and removed request for andrewleith September 16, 2026 12:44

@smcmurtry smcmurtry 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.

The new component looks good! Could we leave leave it off the template page until we get section links working on the "new features" page?

{{ new_feature(
title=_("Upload attachments without the API"),
cta=_("About file attachments"),
cta_link="/new-features",

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.

It would be better if we could link directly to the relevant section on this page with a /new-features#ui-file-attachments link. But it looks like that page doesn't have ids on each section. Also the formatting of the new-features page looks a bit off. Not really related to the new component, but it would be good to fix that before this goes live.

url_for('main.template_attachment_status', service_id=current_service.id, template_id=template.id),
url_for('main.download_template_attachment', service_id=current_service.id, template_id=template.id)
) }}
{{ new_feature(

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.

Could you move this above the "Attached files" component? It seems more natural to me that you would read the "new feature" banner before you see the new feature.

Comment thread scripts/check_expired_banners.py Outdated

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.

I don't think we need this new script - if we can remember to run the script we can remember to do a "find in project" for new_feature( banners and check the lifespans.

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