From #2126285: allow access to page to order book page's children:

Many of the documentation pages on d.org could to with rearranging to make the order more logical and comprehensible to readers.

Here is an example: https://drupal.org/documentation/modules/flag. The main documentation page for Flag module has a ton of child pages, which are in no particular order, and really ought to be.

However, changing the order of child pages like this requires all the weights to be set correctly in relation to one another. This requires each page to be edited. It's a slow and tedious job!

What would be much better would be a single admin page with weights for all the child pages.

I am leaving that other issue at the infrastructure queue because I think discussion is needed about adding a new module and security.

I'm filing a new issue here for the documentation team to discuss whether this is desirable from the docs POV.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

LeeHunter’s picture

Issue tags: +docs infrastructure

Yes! +1 to this.

LeeHunter’s picture

Issue tags: +Usability
jhodgdon’s picture

Component: Other documentation issues » Docs infrastructure
joachim’s picture

Priority: Normal » Major

This is still necessary with the new docs.

For example, I am now maintainer of https://www.drupal.org/docs/8/configuration-management. This consists of a top-level page, with several child pages below it. The child pages show as summaries on the top-level page.

AFAICT, the only way I can rearrange the child page summaries on the top-level page is by editing each one and setting their menu weights. This is incredibly fiddly!!

tvn’s picture

Priority: Major » Normal

That is not the only way, of course. You can modify the menu of the guide you maintain by opening the green Edit drop-down -> Admin -> Menus.
This and other things you can do as a guide maintainer have been documented at: https://www.drupal.org/drupalorg/docs/content/documentation#manage-menu
The page was linked to repeatedly in the 'Recruiting guide maintainers' issue, and I will also add it to the email template for notifications sent out when someone is added as a guide maintainer.

joachim’s picture

Ah ok! I had no idea that was there!

(Using the menu system seems like an odd choice BTW. I had assumed one of the reasons for ditching Books was to get away from the way that uses the menu for its hierarchy.)

jrockowitz’s picture

Yep, I just got hit pretty hard by this limitation when I migrated the Webform 8.x-5.x documentation.

I saw the menu settings at the bottom of the node edit form and assumed I nested menu links was supported and so I migrated the whole book at once.

.

I am little stumped on how I can fix Webform 8.x-5.x documentation's IA.

eojthebrave’s picture

@jrockowitz are you having issues being able to re-order things within the Webform guide? Or with nesting things more than one level deep? The new documentation system tries to encourage a flatter hierarchy in general. But, if you want to create a tree-like nested structure you'll need to create sub-guides to group pages under. The current setup only allows for a single level of depth within a guide, but each guide can contain guides, which can contain pages/guides ad infinitum.

jrockowitz’s picture

@eojthebrave The flat hierarchy is not working for me because I had a section filled with code snippets. A sub-guide for snippets would be perfect and a better approach than a nested hierarchy.

I am not sure where to go to create it.

Would I just create the Webform Snippets sub-guide here?

Will I be able to move existing documents from the Webform module guide to this new sub-guide?

eojthebrave’s picture

You can create it as a sub-guide of the existing Webform guide. It'll show up in the list of content and in the menu on this page https://www.drupal.org/docs/8/modules/webform just like a documentation page does. The quickest way I know would be to click the "Create documentation guide" link in the sidebar on this page https://www.drupal.org/docs/8/modules/webform, and then start adding new documentation pages to the new guide.

You should be able to add a guide from the link you posted as well, I would just recommend changing the parent guide to the Webform guide instead of the Contributed modules guide. I believe the idea is to have a single record in the Contributed Modules guide (https://www.drupal.org/docs/8/modules) for each project on Drupal.org. Resulting in something like:

Contrib Modules
- Webform
  - Introduction
  - Features
  - Code snippets
    - Super sweet snippet one
    - Super sweet snippet two

And yes, you can move a page to another guide. As long as the guide exists just use the autocomplete "Guide" field on a documentation page to move it.

jrockowitz’s picture

@eojthebrave That helped a lot. I was able to quickly and easily fix the Webform module's IA. It is now very clean and user friendly. Thanks.

https://www.drupal.org/docs/8/modules/webform

hansfn’s picture

Isn't this fixed? A guide maintainer can reorder the pages in the guide, right.

Or do we leave the issue open because of the non-migrate documentation?