[Documentation] Missing Architecture and Code Path Analysis in Table of contents

[snitin315]

Environment

https://new.eslint.org/docs/latest/

What parser are you using?

Default (Espree)

What did you do?

• Go to https://new.eslint.org/docs/latest/
• Open the Developer Guide Section in the sidebar
• See no Architecture sub section like in old docs

What did you expect to happen?

To contain all sub-sections as old docs

What actually happened?

The docs actually exist but they are not visible. So the user will not be able to find the docs.

• https://new.eslint.org/docs/latest/developer-guide/architecture
• https://new.eslint.org/docs/latest/developer-guide/code-path-analysis

Participation

• I am willing to submit a pull request for this issue.

Additional comments

Is this intended?

[aladdin-add]

sounds an oversight.

[mdjermanovic]

The docs actually exist but they are not visible. So the user will not be able to find the docs.

• https://new.eslint.org/docs/latest/developer-guide/architecture
• https://new.eslint.org/docs/latest/developer-guide/code-path-analysis

I think Code Path Analysis is not in the menus/sidebar on both the current and the new site because it's only of interest for working with rules, and there are links to it on the Working with Rules page. This is the same as with the pages for Selectors and ScopeManager.

As for the Architecture page, I don't know. It seems to be the only page that we have in menus on the current site but not on the new site. (along with the missing Formatters page we're working on in #16018).

[nzakas]

Architecture should be in sidebar navigation. Code path analysis should not.

[harish-sethuraman]

I'd like to work on this issue 😄

[snitin315]

I'd like to work on this issue 😄

@harish-sethuraman just wait for some time before sending a PR for the author's reply, especially when I am willing to submit a pull request for this issue. is checked. This leads to duplicate efforts.

[harish-sethuraman]

just wait for some time before sending a PR for the author's reply especially when I am willing to submit a pull request for this issue. is checked.

Sure 👍🏻 acknowledged :)