Azure-docs: Question: automatic pages index

[Tbohunek]

In the below screenshot you can see I'm looking at chapter How does the... but the automatic index still thinks I'm looking at Terminology because there's still a line or two left.

Is it possible to optimize the index with some offset? Naturally, humans read in like 2/3 of the text height, so somewhere in the system-assigned.. paragraph. Also, mouse over a text could dynamically highlight the respective section on the index.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 72861cc1-7081-cf6e-b7f9-e700a16faa9a
• Version Independent ID: c870872d-0559-6b77-280f-f478e8c84776
• Content: Managed identities for Azure resources
• Content Source: articles/active-directory/managed-identities-azure-resources/overview.md
• Service: active-directory
• Sub-service: msi
• GitHub Login: @MarkusVi
• Microsoft Alias: markvi

[shashishailaj]

@Tbohunek Thank you for your feedback . We will have this reviewed with the content team and will update the thread.

[shashishailaj]

@MarkusVi Could you please review the design suggestion provided by the customer on this ?

[Tbohunek]

Just to precise: this question goes for the entirety of MS Docs, not just the AD part, this somehow got added itself because I came from that document..

[daveba]

This should not be assigned to the author of the article since this is a site design question. Please route this to the appropriate engineering contact. We're responsible for the content, not design. #reassign:@shashishailaj

[shashishailaj]

@Tbohunek We have taken this feedback to the engineering team internally and are awaiting a response from their side. We will have this updated once we have a response from their side. They may respond this thread directly or I will update the thread with their response.

Thank you.

[jdanyow]

@Tbohunek thanks for the suggestion 👏👏 This definitely could be improved. I've added a task to our product backlog.

@shashishailaj please close, we're tracking this internally in devops.

[Tbohunek]

Thanks @jdanyow. Can I be anyhow informed when this is actually completed? If you close this issue now, I will never know.

[shashishailaj]

@Tbohunek Thank you for your patience. I am following the internal ticket and will update this ticket tagging you once this has reached a solution.

Thank you.

[shashishailaj]

@Tbohunek hope you are good. I thought to provide you an update on this that the UX team is reviewing this and doing a holistic review of the documentation as well. This may take longer to mitigate but we are on track at this point . Your recommendations is being discussed and I will further update when I have anything new here.

[shashishailaj]

@Tbohunek This has been fixed and the article is updated now.

Thank you.

[Tbohunek]

Hey,

thanks for the update @shashishailaj , really cool that it was done at all!
However I think now the index is a bit premature, it switches to new chapter when it's in like 1/2 of the screen. It would feel much more natural if it did when the appropriate section is at 2/3 of screen height. I believe now that the function exists, it's just a matter of changing a number.

Possible?
Thanks and good day!

[Tbohunek]

Hello @jdanyow, how's it going?
Thanks for having implemented this feature so quickly. It could be a little more optimized though: The paragraph switching happens at 1/2 of the screen while human eyes naturally look at 2/3 of (page) height.
Would it be too difficult to optimize that?

Cheers,
Tomas