Skip to content

SCS: Docs Restructuring #10552

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 12 commits into
base: main
Choose a base branch
from
Open

SCS: Docs Restructuring #10552

wants to merge 12 commits into from

Conversation

lavakush07
Copy link
Contributor

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

Description

  • Please describe your changes: __________________________________
  • Jira/GitHub Issue numbers (if any): ______________________________
  • Preview links/images (Internal contributors only): __________________

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
Copy link

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://6848146100c71ef263c9a9d7--harness-developer.netlify.app

@dewan-ahmed
Copy link
Collaborator

Thanks for this change @lavakush07
For large docs restructuring, it's useful to start with an information architecture. Do you have an IA that the team agreed on? This will avoid future changes to the structure in the short term.

@lavakush07
Copy link
Contributor Author

lavakush07 commented Jun 10, 2025

Thanks for this change @lavakush07 For large docs restructuring, it's useful to start with an information architecture. Do you have an IA that the team agreed on? This will avoid future changes to the structure in the short term.

Hi @dewan-ahmed ,
Yes, we planned the SCS docs restructuring and we set up a plan, went through a few iterations with Monish before finalizing it. The restructuring was done with a long-term sight in mind and is aligned with Forrester and Gartner standards.

@dewan-ahmed
Copy link
Collaborator

Excellent! Please have the module-PM (or similar stakeholder) 👀 the preview and approve and then other CODEOWNERS can move this PR forward.

@lavakush07
Copy link
Contributor Author

Excellent! Please have the module-PM (or similar stakeholder) 👀 the preview and approve and then other CODEOWNERS can move this PR forward.

Yes @dewan-ahmed , That's the plan ✅

@bot-gitexp-user
Copy link

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://6849b60d157c344796fd0193--harness-developer.netlify.app

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants