The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Problem/Motivation
The online glossary describes terminology and acronyms used in Drupal: https://www.drupal.org/glossary.
Drupal 8 introduces new terminology and where necessary these need to be added.
Some existing terms (such as for example entity) need to be rewritten
Proposed resolution
Checking pages such as https://www.drupal.org/node/2182165 and the Drupal 8 user interface for new terms and adding them where necessary.
Comparing existing entries with definitions given in recently edited wording, such as for example in the hook help texts that have been committed for Drupal 8.
Comments
Comment #1
jhodgdonMoving to Documentation issues
Comment #2
ifrikAdditional sources of terms are mentioned is #2494037: Add new key terms on the glossary page.
"As few more new terms has been arrived in Maintainers.txt like Framework Manager,Product Manager,BDFL,Release Manager,etc that should be added on the glossary page."
Comment #3
ifrikIn general we should focus on any documentation issues that still can go into Core before RC1, but this strikes me as a useful issue to have fixed before people start adding D8 documentation and refer to the glossary for wording.
It's also a suitable issue when somebody has little time. Therefore I'm tagging it for DrupalCon Barcelona
Comment #4
amber himes matzWe discussed this in a core documentation triage meeting (https://drupal.slack.com/archives/C220WV2TW/p1663030400116659) and the consensus we reached was that there should be 1 glossary docs page that applies to all versions of Drupal, and that a more appropriate place for the glossary should be decided upon. (Currently, it resides in the Drupal 7 Wiki.)
I think the updates to this glossary https://www.drupal.org/docs/7/understanding-drupal/glossary can be discussed here and a separate issue can be opened for moving the page to a more appropriate place.
Comment #5
eojthebraveAs a start, should we move the existing page (https://www.drupal.org/docs/7/understanding-drupal/glossary) to here https://www.drupal.org/docs and make the URL effectively https://www.drupal.org/docs/glossary - and the page more version agnostic?
There's also a Glossary of mostly site builder related terms from the UI in the User Guide - https://www.drupal.org/docs/user_guide/en/glossary.html that we could either link to, or pull into this one.
Comment #6
quietone commentedI moved the guide and converted the heading but I no longer have access to adding it to the menu.
Comment #7
quietone commentedAs a next step how about remove some items? These are candidates for removal because they are not specific to Drupal. Any on-line search can be used to learn more about these.
Comment #8
hansfn commentedThx for taking a stab at this. I have added it to the menu. (You fix "This is a Drupal 7 version of the glossary"?)
I agree that we can remove terms that aren't Drupal specific, but it would help if we could link to a really good resource for programming / computer terms in general. Not a stopper for starting cleaning up.
Comment #9
hansfn commentedNot sure about the placement at the root - see bottom of the docs root page. Maybe under Understanding drupal is better, but more hidden? We can keep the short URL.
Comment #10
quietone commentedI did forgot remove that reference to Drupal 7. I have done so now, and removed some of the words in #7. \
I agree that under "Understanding drupal" is better than my choice.
However, I am not keen on the linking to general docs on programming. I think the primary goal of Drupal documentation is to document Drupal not all the other things one needs to know. I'd rather we trust that people know how to search the internet for what they need. Also, it will be difficult to decide what is a good resource due to the diversity of the way people learn and it is yet thing to maintain. Just my two cents.
Comment #11
quietone commentedLooking at the list now I think the following can be removed as well as they are not Drupal specific.
API
branch maintainers
breadcrumb
cache
camp
child
clean URL
CMS
code freeze
cron
HEAD
parent
published
queue
theme
unpublished
What else is there to do here?
Comment #12
quietone commentedI made a few more tweaks,
I recommend that this issue be closed and further changes can be made by the community as needed.
Comment #13
quietone commentedIt has been 8 months since I made changes to the page and there has been no further discussion. I am going to be bold and set this to RTBC.
Comment #14
avpaderno