Need to display a maintenance message, important information, or a temporary announcement on your Drupal site? With Info Banner, we have turned a recurring need observed among our clients into an open source module that is easy to manage and gives editorial teams greater autonomy.
There are features that almost every website ends up asking for.
Display a maintenance message. Inform visitors of an exceptional closure. Notify about a service change. Announce an event. Or simply highlight temporary information across all pages of the site.
Indeed, with each new project, the same need often comes up: that ofadding an information banner at the top of the site, without requiring specific development.
Naturally, we decided to make it a full-fledged Drupal module.
A universal need
All organizations communicate periodically with their users.
A city hall announces roadworks. A university informs about an enrollment period. A company notifies of maintenance. An association shares news about an event.
In many projects, this banner is developed specifically and then never evolves.
A few months later, no one really knows how to modify it, or where it is configured.
We wanted a simple solution, reusable and flexible enough to meet both the simplest needs and more advanced communication scenarios.
An administrable banner without development
Le principe d'Info Banner is intentionally simple.
From the Drupal administration, teams can create one or more information banners and manage them independently.
No more need to modify a template, deploy code or ask a developer to announce scheduled maintenance for the next day.
The information becomes editorial. And this is precisely what Drupal does best.
A banner... or several
If a global banner already meets many needs, some projects require going further.
That's why Info Banner also comes with a submodule that allows you to manage multiple independent banners.
Each banner can be configured separately to address different communication needs: technical maintenance, temporary information about a section of the site, or an announcement specific to a given context.
This approach provides more flexibility while maintaining simple administration for editorial teams.
Better autonomy for contributors
The goal was not simply to industrialize a recurring need.
We also wanted to avoid situations where urgent communication depends on a technical intervention.
By giving this autonomy to communication teams or webmasters, important information can be published immediately.
Why publish this module?
Because we encountered this need regularly.
And as is often the case in the Drupal universe, when a feature comes up in several projects, it's likely that it deserves to be shared.
Rather than repeating the same development for each of our clients, we preferred to create an open source module, document it and share it.
Other teams can thus reuse it, develop it further, or suggest improvements.
That’s the whole point of the Drupal ecosystem: every contribution benefits the entire community.
Contributing is part of our profession
Developing open source modules takes time.
You need to design a solution that is generic enough, document it, maintain it, and keep up with Drupal's changes.
However, we have made this choice for many years. Not only because we use Drupal every day, but also because we believe an open source CMS improves thanks to the contributions of those who actively use it.
Have you identified a recurring need on your Drupal project? Let's talk about it. We develop advanced and sustainable Drupal solutions and, when they can benefit everyone, we share them with the open source community.
