In #3572350: Disable the default /node listing view and add a better default front page for new installs we are making /node not even enabled by default. It is already a configurable view that may or may not be the front page. So the "promoted to front page" feature is immediately confusing and a lie when /node is not the front page. But that issue makes that the default experience that /node will not be the front page. So the name of that feature will immediately not be true.
Because that issue already changes a lot of things, decided to break out this terminology change to its own issue. #3572350: Disable the default /node listing view and add a better default front page for new installs renames the "Frontpage" view to the "Promoted content" view, so the "promoted" checkbox / feature aligns with that. This rename is better for all sites where the /node is not the front page (which is most sites), regardless of whether #3572350: Disable the default /node listing view and add a better default front page for new installs happens or not.
When creating content type:
When managing content type form:
When adding content:
When editing the /node view (without any other core changes applied):
The "Promoted to front page" feature is now renamed to "Promoted".
LLM was used to accelerate the development of this MR, everything was deeply reviewed though.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | Screenshot 2026-06-02 at 17.04.08.png | 562.48 KB | gábor hojtsy |
| #5 | Screenshot 2026-06-02 at 17.06.15.png | 330.3 KB | gábor hojtsy |
| #5 | Screenshot 2026-06-02 at 17.05.18.png | 439.49 KB | gábor hojtsy |
| #5 | Screenshot 2026-06-02 at 17.04.53.png | 389.67 KB | gábor hojtsy |
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes, plain diff MR !15965
Comments
Comment #3
gábor hojtsyComment #4
gábor hojtsyAdding LLM disclosure as I did use LLM to generate the MR. I reviewed all changes line by line and also independently grepped my Drupal checkout after creating the changes that there seem to be no mention of promotion in relation to front page left in the codebase.
Please review :)
Comment #5
gábor hojtsyComment #6
gábor hojtsyTypo in release note snippet made it sound like the opposite of what is happening :D
Comment #7
gábor hojtsyUpdated issue summary with explanation of terminology and lack of API changes and data model changes, which is a big plus IMHO :)
Comment #8
gábor hojtsyComment #9
gábor hojtsyComment #10
macsim commentedSuper small comment but this is looking good to me.
Comment #11
smustgrave commentedApplied the MR locally
Searched for the phrase "Promote to front page" using
grep -rE 'Promote to (the )?front page' coreVerified field on a content type is called Promoted
This is a nice little cleanup.
For the template change since it's a comment not sure if it needs a CR? Going to mark regardless.
Comment #12
macsim commentedApplied the 2 suggestions I had left on the MR to improve consistency with the rest of the changes
RTBC+1
Comment #13
macsim commentedI might be wrong but I think we need a Change Record for this issue. Several user-facing translatable strings have been renamed. On non-English sites, existing translations for these strings will no longer match and will fall back to English. Site owners with custom translations and translation teams on localize.drupal.org need to be aware of these changes.
Node.php,NodeTypeForm.php)NodeViewsData.php)NodeViewsData.php)PromoteNode.php)DemoteNode.php)get-started.html.twig)system.action.node_promote_action.yml)system.action.node_unpromote_action.yml)views.view.frontpage.yml)views.view.frontpage.yml)Comment #14
gábor hojtsyI created a change record based on the list you provided converted to a HTML table to make it easier to read :) https://www.drupal.org/node/3593641 I don't know if this would be backported to 11.5 or not, I think the impact depends on that. We can easily update the change record though :)
Comment #15
catchCommitted/pushed to main and 11.x - I think it makes sense to backport, less time to maintain two versions of the translation and keeps tests in sync.
Comment #20
berdirHappy with this change, it did bypass some other open issues and discussions there though. There is #3538655: Remove promote/sticky fields from Node which is only 10 months old and a follow-up of the 20 year old and now fixed #29338: Hide Promoted/Sticky fields by default in Form display. I'll cross-reference this, I still think we should keep those two fields.
Comment #21
catchYes me too at least until there's a way to put configurable boolean fields on entity base tables or something along those lines.