Website Improvement about kubevirt.github.io

[cwilkers]

Interesting, most of the website features should be straightforward to figure out; reach out if you need help understanding the CI/CD process we have here.

[aburdenthehand]

@reveurguy Thanks for the offer! Does this include size and placement of the vendor/integration/end user images on the main page?

[reveurguy]

Yeah, I would like to work on the complete website ( including the images part), starting with the homepage. I am running a bit busy for the last few weeks, will look to start from tomorrow and then we can discuss it going forward.
Will open a PR in the upcoming days with some initial changes

[FrankyV52]

Hi, my name is Frankie and I am a senior at UT Austin studying computer science. My group and I are interested in contributing to this issue. Is there anything in particular that we could get started with?

[cwilkers]

Hello @reveurguy and @FrankyV52 ,

One important design consideration is to ensure that changes to this repo are reflected also in the kubevirt/user-guide repo because the sites work seamlessly together. Right now there are some slight differences.

One nice feature request would be a banner for events (like KubeVirt Summit this week, Wednesday and Thursday!) that currently we only really announce via a blog.

I will be doing a tutorial session this Thursday for the KubeVirt Summit on getting started with updating our documentation. It's called Don't Knock the Docs: Contributing Documentation to the KubeVirt Project. Attendance to the conference is free and you can get started here: https://community.cncf.io/events/details/cncf-kubevirt-community-presents-kubevirt-summit-2023/

Note the times are UTC, so my session is noon CDT (I'm in Houston btw)

[reveurguy]

Hello @cwilkers . Sorry for so much delay, i got occupied with university exams and other stuff and completely forgot about this involvement.
I am currently giving my exams, so I will surely get started with my suggestions from around mid-June.

I also wanted to discuss if changing the website tech-stack would be a viable option. I know there would be a lot of stuff to change and manage with that. But I wanted to discuss whether moving the project to use React or Nextjs frameworks is something the maintainers are willing to discuss about.
There would be many improvements to the development process and managing as well if a change is made to a modern and latest framework.
I am willing to discuss upon this further.

If the change doesn't seem suitable, that's fine as well. I'll get started with the current environment only but from mid-June.

[reveurguy]

hello @cwilkers any updates on this?

[cwilkers]

There are a lot of moving pieces with changing the tech stack, there's a CI container image that currently holds together both the main website and user-guide (testable locally, so that's still viable) and there is also the Netlify CI setup that shows website previews for PRs.

That's not to say "no", but I would resist changing the mechanism if it results in an increase in complexity of that container image (actually a low-hanging fruit, it already includes complicated python and node.js stacks) OR if it is unable to work with Netlify and one of their standard container images.

There is also a thread going in the mailing list on how to re-arrange the user-guide to have a better flow of topics, and since that effort is underway (kubevirt/user-guide#684) already, it would be bad form to change the mechanism out from under the people volunteering for that cleanup.

[kubevirt-bot]

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

[kubevirt-bot]

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

[kubevirt-bot]

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

/close

[kubevirt-bot]

@kubevirt-bot: 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.