Add Contribute to docs as a proper child of the Extend section.

[georgewallace]

No description provided.

[theletterf]

I think this has to do with the way the section is laid out in the nav: it's mostly a mix of assembled and docs-content, and that doesn't bode well with selecting the order of each item.

[shainaraskas]

I don't think this will render correctly unless we create another toc at https://github.com/elastic/docs-content/tree/main/extend/contribute or something. or else, we'll forever get this double nav weirdness.

the reason it is behaving strangely is because the index you're referencing here is the same index that sits at extend

[georgewallace]

There is a toc.yml file here https://github.com/elastic/docs-content/blob/main/extend/toc.yml, it is just up a level and that is the problem? I'll look into this more. We really need to get docs-builder to be able to preview builds like this without guessing.

[theletterf]

This is from our navigation.yml file (docs-builder repo):

  ##########
  # EXTEND #
  ##########
  # I didn't touch this section (yet?)
  - toc: extend
    children:
      - toc: kibana://extend
        path_prefix: extend/kibana
      - toc: logstash://extend
        path_prefix: extend/logstash
      - toc: beats://extend
        path_prefix: extend/beats
      - toc: elasticsearch://extend
        path_prefix: extend/elasticsearch
      - toc: integrations://extend
        path_prefix: extend/integrations

The first item, toc: extend, loads up this file: https://github.com/elastic/docs-content/blob/main/extend/toc.yml

The expectation, I think, is that the Contribute section should appear first and contain the rest of items. Instead, it's appended the last, the name of the section repeated.

I wonder if #1615 would solve this, @elastic/docs-engineering.

[shainaraskas]

There is a toc.yml file here elastic/docs-content@main/extend/toc.yml, it is just up a level and that is the problem? I'll look into this more. We really need to get docs-builder to be able to preview builds like this without guessing.

yes. you can look at the way we do the reference section (tocs in all of the child folders, as well as the root) for an idea of how this should be done.

[theletterf]

This is the best I could get:

PRs:

• Rearrange nav for Extend and Contribute #1760
• Fix extend contribute nav docs-content#2664