Where do we add all services groups tutorial to operate first website?

[pacospace]

AICoE/overlays-for-ai-pipeline-tutorial#4
AICoE/manage-dependencies-tutorial#4
AICoE/elyra-aidevsecops-tutorial#389

[MichaelClifford]

These tutorials seem like a good fit in under the Data Science section of the website. WDYT?

[pacospace]

These tutorials seem like a good fit in under the Data Science section of the website. WDYT?

Thanks @MichaelClifford sounds good to me :) can you point me to where do we need to add them to show up in the website? is there some doc for this? Thank you!!

[oindrillac]

hey @pacospace This part of the Readme pretty much sums up what you need for adding content to the repo and for it to show up on the left hand nav bar.

tldr;

1. you would need to add the repos as remote content here

2. Then you could alphabetically place the docs you wanna highlight in the nav bar list here
   we typically have such markdowns on display
   

3. to make it discoverable under this projects list, you can also add a short description here

4. Finally to test your changes locally you can

npm install
npm run dev

[pacospace]

hey @pacospace This part of the Readme pretty much sums up what you need for adding content to the repo and for it to show up on the left hand nav bar.

tldr;

1. you would need to add the repos as remote content here
2. Then you could alphabetically place the docs you wanna highlight in the nav bar list here
   we typically have such markdowns on display
   
3. to make it discoverable under this projects list, you can also add a short description here
4. Finally to test your changes locally you can

npm install
npm run dev

Thank you @oindrillac!! 🚀

[quaid]

Tagging @aakankshaduggal for making sure this is included in her data science community page

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[Gregory-Pereira]

@pacospace, can we close this issue?
/remove-lifecycle stale

[schwesig]

/assign @schwesig

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[sesheta]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[sesheta]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[sesheta]

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.