Support from Acquia helps fund testing for Drupal Acquia logo

Comments

kim.pepper’s picture

kim.pepper’s picture

kim.pepper’s picture

As there is only one tour.tour.block.yml file, this needs to wait until #1926294: Write tour integration for block_content.module is in.

kim.pepper’s picture

Actually, clarified with larowlan and #3 is incorrect.

kholloway’s picture

I will try to get to this task next once I finish with the Content Language module tour.

I am using this documentation:
https://www.drupal.org/node/1934442#tour-tips-tech-note

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.

ridhimaabrol24’s picture

Version: 8.9.x-dev » 9.1.x-dev
ridhimaabrol24’s picture

Status: Needs work » Needs review
FileSize
4.53 KB

Adding tour for Block layout page.

pankaj.singh’s picture

Assigned: Unassigned » pankaj.singh
pankaj.singh’s picture

FileSize
113.18 KB
107.53 KB
90.6 KB

Tested the patch given in #15 on 9.1.x-dev. Tour is now accessible on block layout page.
Please refer to the SS attached.

thalles’s picture

  1. 1
  2. 2
  3. Only local images are allowed.
  4. 3
  5. Only local images are allowed.
  6. Only local images are allowed.
thalles’s picture

thalles’s picture

Status: Needs review » Reviewed & tested by the community

#15 Works fine to me!

alexpott’s picture

Status: Reviewed & tested by the community » Needs review
  1. +++ b/core/modules/block/config/optional/tour.tour.block-layout.yml
    @@ -0,0 +1,47 @@
    +    body: 'Any custom or contributed block can be assigned to a particular region by clicking on a button Place block. A new block can also be created by clicking on Place Block'
    

    When reading this I'm left wondering what's the difference between assignment and creating. Isn't it that you click on place block and then you get a list of blocks you can place here. And in all cases you are creating new block configuration.

  2. +++ b/core/modules/block/config/optional/tour.tour.block-layout.yml
    @@ -0,0 +1,47 @@
    +    body: 'Assign or change the region of a block by clicking here. A dropdown list with all the regions will appear.You can place one block at multiple regions.'
    

    I think a block is placed "in" a region and not "at" a region.

thalles’s picture

Follow a new patch!

I replace at by in, and assigned by added

paulocs’s picture

Status: Needs review » Reviewed & tested by the community
FileSize
97.62 KB
110.73 KB
115.01 KB
110.71 KB
108.38 KB

Patch #22 looks good!

Tour1
Tour2
Tour3
Tour4
Tour5

alexpott’s picture

Status: Reviewed & tested by the community » Fixed

Committed 032661e and pushed to 9.1.x. Thanks!

It'd be great if this was the start of a new effort to add tours of the Drupal UI.

  • alexpott committed 032661e on 9.1.x
    Issue #2151001 by thalles, ridhimaabrol24, paulocs, pankaj.singh, kim....
thalles’s picture

Thanks @all!

thalles’s picture

@alexpott, can you give a look in the Welcome Drupal module?
Welcome Drupal tours

thalles’s picture

Assigned: pankaj.singh » Unassigned
paulocs’s picture

The welcome drupal is a nice module and there is a lot of tours that were already created.

thalles’s picture

Hey @bdias.ti!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

xjm’s picture

Issue tags: +9.1.0 highlights