[Website]: Next button should point to the section called out on the page and not Stack Monitoring

[jakommo]

Type of issue

None

What documentation page is affected

https://www.elastic.co/docs/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected

What happened?

The "Next" button links to "Stack Monitoring" but I would expect it to link to the next topic in this section like "How to connect your self-managed cluster to AutoOps" etc

Additional info

No response

[jakommo]

Just wanted to add that this happens on all pages linked in the "Section overview". I.e. https://www.elastic.co/docs/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops has "stack monitoring" too as "next".

[shainaraskas]

these pages are currently hidden and not part of our standard IA because this feature is in beta (or limited tech preview?). I'd expect some suboptimal UX because of this.

IA looks like this, which is why stack-monitoring is being chosen as the next page. it's the next unhidden page.

  - file: monitor.md
    children:
      - file: monitor/autoops.md
        children:
          - file: monitor/autoops/ec-autoops-how-to-access.md
          - file: monitor/autoops/ec-autoops-events.md
            children:
              - file: monitor/autoops/ec-autoops-event-settings.md
              - file: monitor/autoops/ec-autoops-notifications-settings.md
          - file: monitor/autoops/views.md
            children:
              - file: monitor/autoops/ec-autoops-overview-view.md
              - file: monitor/autoops/ec-autoops-deployment-view.md
              - file: monitor/autoops/ec-autoops-nodes-view.md
              - file: monitor/autoops/ec-autoops-index-view.md
              - file: monitor/autoops/ec-autoops-shards-view.md
              - file: monitor/autoops/ec-autoops-template-optimizer.md
          - hidden: monitor/autoops/ec-autoops-dismiss-event.md
          - file: monitor/autoops/ec-autoops-regions.md
          - file: monitor/autoops/ec-autoops-faq.md
          - hidden: monitor/autoops/cc-autoops-as-cloud-connected.md
          - hidden: monitor/autoops/cc-connect-self-managed-to-autoops.md
          - hidden: monitor/autoops/cc-connect-local-dev-to-autoops.md
          - hidden: monitor/autoops/cc-manage-users.md
          - hidden: monitor/autoops/cc-cloud-connect-autoops-faq.md
          - hidden: monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md
      - file: monitor/stack-monitoring.md

I expect we don't actually want the prev/next pages to navigate cleanly between hidden pages, because it might expose something the reader is actually not supposed to access. We could consider improving our "beta" experience, but we have very few of these actually publish (and for a very short-lived timeframe), so I don't think this would be worth the engineering effort. longer-term efforts to do personalization (so we can understand whether a user is part of a beta) might assist with this in future.

@jakommo unless you have any concerns about this after this clarification, I'd like to close this issue

[jakommo]

Ah yes, that makes sense, thanks for clarifying. I know it's not GA yet, but didn't know it was hidden.
The structure you shared looks good to me, I'm closing this. Sorry for the noise 🙈