JobSet website + docs

[danielvegamyhre]

What would you like to be added:
A polished website + docs, similar to what Kueue has: https://kueue.sigs.k8s.io/

Why is this needed:
We are graduating JobSet to v1 (#380) and we need polished, detailed docs that are commensurate with its level of maturity and production-readiness.

[moficodes]

Request for Netlify: kubernetes/org#4748
Request for CNAME entry: kubernetes/k8s.io#6406
Request for Logo: kubernetes/steering#279

[kannon92]

@moficodes and @danielvegamyhre can we get an update on this issue?

[kannon92]

@danielvegamyhre can you add a link to the https://jobset.sigs.k8s.io/ in our project description page?

I'd add it but I don't think I can.

[danielvegamyhre]

The last thing we are waiting on here is the JobSet logo I believe.

[danielvegamyhre]

@danielvegamyhre can you add a link to the https://jobset.sigs.k8s.io/ in our project description page?

Sorry what project description page are you referring to?

[kannon92]

On the github main site. top right. Look at Kueue. It links to the Kueue website.

We don't have any mention of the jobset site.

[kannon92]

https://github.com/kubernetes-sigs/kueue

[danielvegamyhre]

On the github main site. top right. Look at Kueue. It links to the Kueue website.

We don't have any mention of the jobset site.

Gotcha, added, thanks!

[kannon92]

@danielvegamyhre should we move this out of the must haves for release v0.5.0? We are waiting on a logo but the code for the website seems there. We even link to it.

[danielvegamyhre]

@danielvegamyhre should we move this out of the must haves for release v0.5.0? We are waiting on a logo but the code for the website seems there. We even link to it.

Yeah sounds good

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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-sigs/prow repository.

[kannon92]

/reopen

[k8s-ci-robot]

@kannon92: Reopened this issue.

In response to this:

/reopen

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-sigs/prow repository.