Problem/Motivation

The node module has 3 different css files (node.admin.css, node.module.css, node.preview.css) that are all related to admin tasks.

Proposed resolution

Merge the 3 files into node.admin.css and remove any duplicated code.

Remaining tasks

1. Resolve questions raised in #35 @idbr

The issue summary indicates all 3 nodes.*.css files are merged into a single node.admin.css, but the patch leaves node.module.css. Is this on purpose?

node.admin.theme.css contains box-sizing, float, width attributes that deliver layout. This seems inconsistent with the SMACCS policy. Can you include a comment why these attributes are in a .theme file instead of a .module file?

User interface changes

Nil.


API changes

Nil.

Beta phase evaluation

Reference: https://www.drupal.org/core/beta-changes
Issue category Task because code cleanup
Issue priority Not critical because code cleanup
Unfrozen changes Unfrozen because it only changes CSS
CommentFileSizeAuthor
#81 interdiff_80-81.txt820 bytesravi.shankar
#81 2421365-81.patch4.07 KBravi.shankar
#80 interdiff_78-80.txt1.02 KBravi.shankar
#80 2421365-80.patch4.35 KBravi.shankar
#78 merge_node_css_files-2421365-78.patch4.59 KBameymudras
#58 merge_node_css_files-2421365-58.patch7.36 KBgoogletorp
#48 Screenshot 2015-04-18 14.03.37.jpg389.78 KBLewisNyman
#48 Screenshot 2015-04-18 13.43.48.jpg315.47 KBLewisNyman
#48 Screenshot 2015-04-18 13.43.41.jpg456.18 KBLewisNyman
#46 interdiff-2421365-34-46.txt3.51 KBakalata
#46 node-css-2421365-46.patch7.26 KBakalata
#43 Screenshot 2015-04-17 15.53.27.jpg486.06 KBLewisNyman
#43 Screenshot 2015-04-17 15.53.06.jpg486.92 KBLewisNyman
#42 interdiff-2421365-34-42.txt6.93 KBakalata
#42 node-css-2421365-42.patch6.75 KBakalata
#34 node-css-2421365-34.patch4.89 KBmortendk
#34 node-interdiff-29-34.txt4.63 KBmortendk
#29 node-css-interdiff.txt4.32 KBmortendk
#29 node-css-2421365-29.patch4.43 KBmortendk
#24 node-css-interdiff.txt467 bytesmortendk
#24 node-css-2421365-24.patch4.88 KBmortendk
#22 preview-before.png217.34 KBrteijeiro
#22 preview-after.png217.19 KBrteijeiro
#22 node-before.png220.74 KBrteijeiro
#22 node-after.png218.77 KBrteijeiro
#22 interdiff.txt618 bytesrteijeiro
#22 node-css-2421365-22.patch4.88 KBrteijeiro
#20 node-interdiff.txt4.28 KBmortendk
#20 node-css_0-2.patch4.88 KBmortendk
#17 node-css.patch4.39 KBmortendk
#15 merge_node_css_files-2421365-14.patch6.61 KBmortendk
merge_node_css_files-2421365-13.patch6.61 KBmortendk
node-css-before-edit.png122.22 KBmortendk
node-css-before-revision.png56.22 KBmortendk
node-css-before-preview.png70.34 KBmortendk
node-css-after-edit.png121.05 KBmortendk
node-css-after-revision.png82.06 KBmortendk
node-css-after-preview.png93.51 KBmortendk
node-css-notheme-edit.png102.59 KBmortendk
node-css-notheme-revision.png49.94 KBmortendk
node-css-notheme-preview.png69.48 KBmortendk
merge_node_css_files-2421365-12.patch4.39 KBmortendk
#8 node-css.patch6.02 KBmortendk
#5 interdiff-2-4.txt2.46 KBtadityar
#5 merge_node_css_files-2421365-5.patch5.3 KBtadityar
#4 merge_node_css_files-2421365-4.patch0 bytestadityar
#2 merge_node_css_files-2421365-2.patch3.17 KBmortendk

Issue fork drupal-2421365

Command icon Show commands

Start 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:

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dmitrii’s picture

Library drupal.node.admin (node.admin.css) - contains theme css, used for overview table of older revisions of a node.
Libraries form, drupal.node (node.module.css) - contains layout css, used for node form.
Library drupal.node.preview (node.preview.css) - contains theme css, used for single node in preview.
It look logical to keep all three files.

mortendk’s picture

Status: Active » Needs review
FileSize
3.17 KB

Following the css code standards seperate the css files into 3 types:
Module: bare essentials, to make the module work
Admin: css used for admin part
Theme: visual enhanchemenrs for theme
[#1887922]

node form is admin, preview is admin -> all goes into node.admin.css

LewisNyman’s picture

Status: Needs review » Needs work

It seems like the layout this code is duplicated in node.module.css? We could remove a lot of code from there as well.

tadityar’s picture

Status: Needs work » Needs review
FileSize
0 bytes

The Proposed resolution in the IS is to merge all 3 of them. So I removed node.module.css instead.

tadityar’s picture

... Ignore #4

LewisNyman’s picture

Issue tags: +Needs screenshots

Thanks! We need screenshots in Stark/Seven/Bartik to show everything still looks right, as we need a screenshot of Stark without any of the .theme.css styling to show that it is still functional.

mortendk’s picture

Assigned: Unassigned » mortendk
mortendk’s picture

FileSize
6.02 KB

found an issues the library file wasnt changed to only call node.admin.css
uploaded new patch that adds the node.admin.css

I have changed the call to node.admin.css that but not changed the different libraries that are added so it needs a bit more work in node.libraries.yml

LewisNyman’s picture

Status: Needs review » Needs work

Now we have four libraries that all call the same one file, maybe we can merge them together into one library?

mortendk’s picture

yup thats my next step - actually i do think we should have preview to be node.theme.css as its only colors, so a seperation would be in order.

mortendk’s picture

Issue summary: View changes
mortendk’s picture

Issue summary: View changes
Status: »
Issue tags:

Status: Needs review » Needs work

The last submitted patch, merge_node_css_files-2421365-13.patch, failed testing.

mortendk’s picture

Issue summary: View changes

screenshots:
Before patch


After patch


No theme


mortendk’s picture

Status: Needs work » Needs review
FileSize
6.61 KB

Status: Needs review » Needs work

The last submitted patch, 15: merge_node_css_files-2421365-14.patch, failed testing.

mortendk’s picture

FileSize
4.39 KB

lets try this again

mortendk’s picture

Status: Needs work » Needs review
rteijeiro’s picture

Status: Needs review » Needs work

Sorry for the following nitpicks >:P

+++ b/core/modules/node/css/node.admin.theme.css
@@ -73,3 +68,26 @@
+/* node preview conttainer is places*/

Maybe we should rephrase and fix typo in this comment. Also comments should start with capitals, end with a period and have an space between comment tags.

+++ b/core/modules/node/css/node.admin.theme.css
@@ -73,3 +68,26 @@
+/* revision color */

Comments should start with capitals and end with a period.

mortendk’s picture

Status: Needs work » Needs review
FileSize
4.88 KB
4.28 KB
mortendk’s picture

Assigned: mortendk » Unassigned
rteijeiro’s picture

Issue summary: View changes
FileSize
4.88 KB
618 bytes
218.77 KB
220.74 KB
217.19 KB
217.34 KB

Fixed a missing period in a comment block and removed periods in inline comments. Not sure if they should have periods or not. I haven't found any info about it. Any ideas?

The rest of the patch seems to be ok and it works as expected. Check screenshots:

Preview BEFORE

Preview AFTER

Node BEFORE

Node AFTER

LewisNyman’s picture

Status: Needs review » Needs work

@rteijeiro Doxygen recommends full stops on the first line of a comment. I think the easiest rule to follow here is to put a full stop on every comment.

I've updated the CSS coding standards examples so they consistently use a full stop.

mortendk’s picture

added the missing dots - patch uploaded & interdiff

mortendk’s picture

Status: Needs work » Needs review
LewisNyman’s picture

Status: Needs review » Reviewed & tested by the community

Thanks for all the screenshots. It looks like we've fixed all the concerns here. I manually tested it again then just to make sure we didn't loose any styling. It looks good.

mortendk’s picture

cheers!
think this might be "patch of the year with most screenshots" ;)

alexpott’s picture

Status: Reviewed & tested by the community » Needs work

The new css has lots of additional css. Surprising.

mortendk’s picture

Status: Needs work » Needs review
FileSize
4.43 KB
4.32 KB

somehow the diff didnt get the removal of node.module.css :(

new patch added - with interdiff

joelpittet’s picture

This looks great, just a couple of questions:

  1. +++ b/core/modules/node/css/node.admin.theme.css
    @@ -73,3 +68,26 @@
    +@media only screen and (min-width: 36em) {
    +  .node-preview-container .form-type-select {
    ...
    +/* Revision color. */
    +.revision-current {
    +  background: #ffc;
    +}
    

    Should this go above the @media query? Not sure the pattern we are using here again...

  2. +++ b/core/modules/node/node.libraries.yml
    @@ -2,7 +2,7 @@ drupal.node:
         layout:
    -      css/node.module.css: {}
    +      css/node.admin.theme.css: {}
    

    Shouldn't this be in a theme library category or something? Just guessing...

mortendk’s picture

1. nope its only if they are related to each other .node-preview-container .form-type-select & .revision-current isnt related
2. afaik we don't use theme libraries for admin.theme.css ?

joelpittet’s picture

2. I don't know the rules around *.theme.css and theme: in yaml Maybe there is a rule you or @LewisNyman can point me to?

mortendk’s picture

Status: Needs review » Needs work

@joel 2. yup it should be theme library sets it back to needs work

mortendk’s picture

Status: Needs work » Needs review
FileSize
4.63 KB
4.89 KB

fixed layout to theme in lib

idebr’s picture

Status: Needs review » Needs work
Issue tags: +Needs issue summary update
  1. The issue summary indicates all 3 nodes.*.css files are merged into a single node.admin.css, but the patch leaves node.module.css. Is this on purpose?
  2. node.admin.theme.css contains box-sizing, float, width attributes that deliver layout. This seems inconsistent with the SMACCS policy. Can you include a comment why these attributes are in a .theme file instead of a .module file?
  3. @LewisNyman in #3

    It seems like the layout this code is duplicated in node.module.css? We could remove a lot of code from there as well.

    There is still a lot of duplicated css between node.module.css and node.admin.css.

mortendk’s picture

node.module should only have "stuff thats absolutely nessesary" for the module to work. So it a themer kills every css file there is and leaves *.module.css sutff still works but looks like crap ;)

yeah node.module.css should be killed in the diff, or did my git-fu fail me again

mortendk’s picture

Issue tags: +dclondon
njbarrett’s picture

Assigned: Unassigned » njbarrett

I am at the drupal south sprint and going to update the issue summary

njbarrett’s picture

Assigned: njbarrett » Unassigned
Issue summary: View changes

I applied the patch in #34 and noticed that node.module.css still exists, this should be removed.
The only file that remains then is node.admin.theme.css, which seems inconsistent with the issue summary, should this be called node.admin.css ?

njbarrett’s picture

Issue summary: View changes
Issue tags: -Needs issue summary update
njbarrett’s picture

Issue summary: View changes
akalata’s picture

Status: Needs work » Needs review
Issue tags: +drupaldevdays
FileSize
6.75 KB
6.93 KB

Fixing which CSS files are created/named/deleted.

LewisNyman’s picture

Issue summary: View changes
Status: Needs review » Needs work
FileSize
486.92 KB
486.06 KB

It looks like this introduces a problem with the node preview bar. Because the node preview page is is not an admin page, moving the CSS into the admin theme breaks the layout of the node preview bar. I think we should keep node preview in it's own file and just convert node.module.css to node.admin.css.

Before:

After:

akalata’s picture

In reading up on the docs to answer #43, I've realized that my change in #42 to answer #39 is actually incorrect -- the file should be named node.admin.theme.css (point 4 on [#2016305]).

Keeping node.preview.css breaks the naming conventions from what I could see. I think the correct answer would be to fix the preview page so that it loads the admin CSS.

LewisNyman’s picture

I am worried that if we load all the admin CSS on a frontend page we might introduce loads of regressions. What if we put the preview CSS inside a node.theme.css file?

akalata’s picture

FileSize
7.26 KB
3.51 KB

That sounds like a good compromise. I've basically renamed node.preview.css to node.theme.css, updated node.libraries.yml, and removed node.module.css that #34 missed.

akalata’s picture

Status: Needs work » Needs review
LewisNyman’s picture

Issue summary: View changes
Status: Needs review » Reviewed & tested by the community
FileSize
456.18 KB
315.47 KB
389.78 KB

Ok, I've taken screenshots of the node preview bar in Bartik and the node edit form in Seven and Classy to show there are no UI changes and added them to the issue summary. Thanks.



alexpott’s picture

Status: Reviewed & tested by the community » Needs review

Creating a node is not an necessarily an administrator task - i'm not sure that node.admin.css is the correct name.

akalata’s picture

I don't think the designation is role based, it's mode/screen based. The node module's primary function is to create, manage, and display nodes. Following the guidelines outlined at https://www.drupal.org/node/2016305:

  • the node.theme.css is to "make the functionality aesthetically pleasing" - in this case, the functionality is the node Preview bar, which will interact with the non-admin theme
  • the node.admin.theme.css is to "make the module's admin screens aesthetically pleasing" - in this case, I don't think it's much of a stretch to call the node create and edit pages the "admin side" of node.module.
alexpott’s picture

Status: Needs review » Reviewed & tested by the community

@akalata yep I can buy that.

alexpott’s picture

Status: Reviewed & tested by the community » Needs review

So whilst I buy it - I don't completely.

The preview code is in node.theme.css after this patch. Because it appears in the main theme - but the same can be true of the node edit css.

mortendk’s picture

Status: Needs review » Reviewed & tested by the community

@alex yes it can sometimes be true for the editing of a node. but the normality (if i can use that word in drupal) is that we dont use the main theme for editing, its more the exception :)

oooh my if we didnt have this fussy level between admin & edit & enduser & whathave we not ;)

catch’s picture

Status: Reviewed & tested by the community » Needs review

If we put the edit CSS in admin, we should put preview in too. Preview can only be got to from edit.

Status: Needs review » Needs work

The last submitted patch, 46: node-css-2421365-46.patch, failed testing.

LewisNyman’s picture

Issue tags: +Needs reroll
googletorp’s picture

Status: Needs work » Needs review
Issue tags: -Needs reroll
FileSize
7.36 KB

Rerolled patch

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev
quietone’s picture

Category: Bug report » Task
Issue tags: +Bug Smash Initiative

From reading the IS, this is a task not a bug.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

anoopsingh92’s picture

Assigned: Unassigned » anoopsingh92
anoopsingh92’s picture

Assigned: anoopsingh92 » Unassigned
anoopsingh92’s picture

#58 patch failed for me.

Lenovo@LAPTOP-PDE747K8 MINGW64 /c/xampp/htdocs/drupal-2421365 (2421365-merge-node.css-files)
$ git apply -v merge_node_css_files-2421365-58.patch
Checking patch core/modules/node/css/node.admin.css...
Checking patch core/modules/node/css/node.admin.theme.css...
Checking patch core/modules/node/css/node.module.css...
error: while searching for:
/**
 * @file
 * Styles for administration pages.
 */

/**
 * Node add/edit form layout
 */

/* Narrow screens */
.layout-region {
  box-sizing:         border-box;
}

/* Wide screens */
@media
  screen and (min-width: 780px),
  (orientation: landscape) and (min-device-height: 780px) {

  .layout-region-node-main,
  .layout-region-node-footer {
    float: left; /* LTR */
    width: 65%;
    padding-right: 2em; /* LTR */
    box-sizing: border-box;
  }

  [dir="rtl"] .layout-region-node-main,
  [dir="rtl"] .layout-region-node-footer {
    float: right;
    padding-left: 2em;
    padding-right: 0;
  }

  .layout-region-node-secondary {
    float: right; /* LTR */
    width: 35%;
  }

  [dir="rtl"] .layout-region-node-secondary {
    float: left;
  }

  /* @todo File an issue to add a standard class to all text-like inputs */
  .layout-region-node-secondary .form-autocomplete,
  .layout-region-node-secondary .form-text,
  .layout-region-node-secondary .form-tel,
  .layout-region-node-secondary .form-email,
  .layout-region-node-secondary .form-url,
  .layout-region-node-secondary .form-search,
  .layout-region-node-secondary .form-number,
  .layout-region-node-secondary .form-color,
  .layout-region-node-secondary textarea {
    box-sizing:         border-box;
    width: 100%;
    max-width: 100%;
  }
}

/**
 * The vertical toolbar mode gets triggered for narrow screens, which throws off
 * the intent of media queries written for the viewport width. When the vertical
 * toolbar is on, we need to suppress layout for the original media width + the
 * toolbar width (240px). In this case, 240px + 780px.
 */
@media
  screen and (max-width: 1020px) {

  .toolbar-vertical.toolbar-tray-open .layout-region-node-main,
  .toolbar-vertical.toolbar-tray-open .layout-region-node-footer,
  .toolbar-vertical.toolbar-tray-open .layout-region-node-secondary {
    float: none;
    width: auto;
    padding-right: 0;
  }
}

error: patch failed: core/modules/node/css/node.module.css:1
error: core/modules/node/css/node.module.css: patch does not apply
Checking patch core/modules/node/css/node.preview.css...
error: while searching for:
/**
 * @file
 * Styles for node preview page.
 */

.node-preview-container {
  position: fixed;
  z-index: 499;
  width: 100%;
  padding: 10px;
  box-sizing: border-box;
}

@media only screen and (min-width: 36em) {
  .node-preview-container .form-type-select {
    margin-left: 25%; /* LTR */
  }
  [dir="rtl"] .node-preview-container .form-type-select {
    margin-right: 25%;
    margin-left: 0;
  }
}

error: patch failed: core/modules/node/css/node.preview.css:1
error: core/modules/node/css/node.preview.css: patch does not apply
Checking patch core/modules/node/css/node.theme.css...
Checking patch core/modules/node/node.libraries.yml...
Hunk #2 succeeded at 13 (offset -2 lines).
Checking patch core/modules/node/src/Controller/NodeController.php...
error: while searching for:
      '#rows' => $rows,
      '#header' => $header,
      '#attached' => array(
        'library' => array('node/drupal.node.admin'),
      ),
    );


error: patch failed: core/modules/node/src/Controller/NodeController.php:241
error: core/modules/node/src/Controller/NodeController.php: patch does not apply

amin.ankit’s picture

Assigned: Unassigned » amin.ankit
amin.ankit’s picture

Assigned: amin.ankit » Unassigned
smustgrave’s picture

Status: Needs review » Needs work
ameymudras’s picture

Status: Needs work » Needs review
FileSize
4.59 KB

Re rolled the above patch for Drupal 9.4.x

smustgrave’s picture

Status: Needs review » Needs work
Issue tags: +Needs issue summary update

Patch failed. Don't see any answer for #35 in the issue summary.

ravi.shankar’s picture

Fixed Drupal CS issues of patch #78, still needs work for issue summary update.

ravi.shankar’s picture

Fixing Drupal CS issues of patch #80.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.