Finding the information you need, when you need it
Using Drupal does not necessarily mean following official announcements or community discussions every day. Some people spend most of their time running a site or updating its content, with limited time to read technical information.
To help those users find what to check, which information relates to their Drupal environment, and what response to consider next, I brought explanations based on official sources together on this site and connected them through search.
Whether or not someone participates in official or community activities, I hope this can be a useful starting point for finding information and discussing it with a maintainer or developer.
Connecting learning resources with information about change
The collection brings together three kinds of resources with different roles.
| Resource | What it helps you check |
|---|---|
| Security advisories | Vulnerabilities, affected versions and configurations, fixed versions and additional actions |
| Releases for Drupal core | Changes in individual core releases and considerations when updating |
| Drupal User Guide | The concepts and basics of site building, configuration, operation and maintenance |
Security advisories and core releases are organized into weekly summaries. For the User Guide, you can choose detailed topic pages or shorter chapter summaries. The entry also links to summaries of the Evaluator Guide and Local Development Guide.
The aim is to make it easier to move between learning how Drupal works and checking what has changed.
Explore the official-source resource hub →
Reading guide topics alongside update information
A guide explanation may need to be read alongside release notes or security advisories, depending on the Drupal version and contributed modules in use.
I have compared the collected information with guide topics and added relevant update notes and source links. Source-based explanations, my supplementary material and update annotations are identified separately so that readers can follow the evidence.
For example, someone learning about permissions may also need to review permissions associated with a contributed module they use. Someone reading about installing modules may need to consider version compatibility and maintenance information. These are the connections I am working to make easier to follow.
The annotations describe the versions and conditions supported by the material reviewed. They do not cover every change or every site’s exposure. The chapter comparison status explains the review scope.
Searching by module name
A growing collection only helps if people can find what they need. The dedicated search looks across the official-source summaries, detailed explanations and update notes published on this site.
If you use Simple OAuth, for example, you can search by its name , then switch between resource types:
- Security to look for affected configurations, fixed versions and follow-up checks.
- Guides to read related concepts, configuration explanations and update notes.
- Core releases to look for related core changes.
Guide coverage can be narrowed to All, Details or Summaries. Results identify their type, such as Guide detail, Chapter summary, Glossary or Index. Some searches will not have matching material in every category.
This search covers the text collected on this site. It does not search the whole of Drupal.org or automatically inspect your Drupal installation.
Search Drupal source-based guides and summaries →
Relating the information to your own environment
A useful route from a search result to considering action is:
- Identify your installed core and module versions, along with relevant settings.
- Use the explanations here to find potentially relevant advisories, release notes and guide topics.
- Check the official sources for affected versions, conditions, fixes and additional actions.
- Discuss the applicable information, update plan and verification steps with your maintainer.
Finding the same module name does not, by itself, establish that your site is affected. Finding no result does not establish that it is safe. Names, versions and configuration conditions need to be considered together.
I also hope the collection can serve as shared reading material: something to bring to a conversation with a specialist, along with the questions that remain unanswered.
Building useful explanations around official sources
This is an unofficial effort by an individual who uses Drupal. It builds on the work of the original contributors through translation, abridgment and reorganization, with supplementary explanations and reference links. Individual pages record sources, review dates, attribution and licensing information.
The sources include Security advisories ↗ , Releases for Drupal core ↗ and the Drupal User Guide ↗ . Please consult official information before taking action. Not every procedure, including those in detailed guide pages, has been verified on a running Drupal site.
As update information is added, I intend to review relevant guide topics and improve the notes and references where needed. If you notice an error or an explanation that is difficult to follow, feedback through the contact page is welcome.
Whether you follow Drupal information regularly or only look things up when a question arises, I hope this becomes a useful place to understand your environment and consider your next step.