SEI-13992 Update Harness SEI Left-Hand Navigation Menu

[alai97]

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.

Description

• Please describe your changes: Updates the existing TOC structure for SEI to be more consistent with the standard template for Harness product modules. Discussion with Richard and Jyoti on Slack.

  Before:

  

  After:

  

• Jira/GitHub Issue numbers (if any): https://harness.atlassian.net/browse/SEI-13992

• Preview links/images (Internal contributors only): https://68ca1ef8f30e017c1ba90ba8--harness-developer.netlify.app/docs/software-engineering-insights

PR lifecycle

We aim to merge PRs within one week or less, but delays happen sometimes.

If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.

PRs must meet these requirements to be merged:

• Successful preview build.
• Code owner review.
• No merge conflicts.
• Release notes/new features docs: Feature/version released to at least one prod environment.

[bot-gitexp-user]

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://68ca1ef8f30e017c1ba90ba8--harness-developer.netlify.app

[joeyouss]

@alai97 just one suggestion: Since we have "Use SEI 2.0" as heading already then we have "SEI 2.0" under it, I feel that is a bit repetitive -> maybe we can remove the SEI 2.0 heading and directly expose the folders in it under "Use SEI 2.0"?

[alai97]

@alai97 just one suggestion: Since we have "Use SEI 2.0" as heading already then we have "SEI 2.0" under it, I feel that is a bit repetitive -> maybe we can remove the SEI 2.0 heading and directly expose the folders in it under "Use SEI 2.0"?

Hi @joeyouss, thanks for the suggestion! The wrinkle here is that users can toggle between SEI 1.0 and 2.0 in-app, so we've kept the headings consistent with the UI.

I agree the repetition between SEI 2.0 (Recommended) and SEI 1.0 (Legacy) dropdowns is a little noticeable, but my thought was to keep it explicit: SEI 2.0 is the recommended path for new users, while SEI 1.0 remains available for existing users as they transition into SEI 2.0.

Curious if that framing makes sense to you, or if you see another way we could highlight “recommended vs. legacy” without losing clarity.