Skip to content
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

migration: Move from vanilla JS to Next.JS #16

Merged
merged 1 commit into from
Nov 4, 2024

Conversation

a1icja
Copy link
Contributor

@a1icja a1icja commented Oct 21, 2024

tl;dr - The dashboard has been rebuilt using Next.js, TailwindCSS, and PrimeReact (components library) to provide a better overall user and developer experience.


This PR reimplements the features found in the dashboard using Next.js. It is not intended to be used for adding new features or fixing old bugs.

Please see the README.md file included in this PR for a general overview of how the project is formatted as well as information for how to setup a development environment.

A live version of this dashboard with additional improvements and features (coming in future PRs) can be found here.


In order for this PR to be merged successfully, a couple things must happen:

  1. The GitHub Pages settings for this repository must be changed to use GitHub Actions as the source.
  2. The "Fetch CI Nightly Data" action must be run manually once following this PR being merged

Due to the significant changes present in this PR, please review each file carefully.

@a1icja a1icja changed the title [WIP] general: Convert from base HTML/CSS/JS to Next.js general: Convert from base HTML/CSS/JS to Next.js Oct 21, 2024
@a1icja a1icja marked this pull request as ready for review October 21, 2024 21:29
@a1icja a1icja requested a review from arc9693 October 28, 2024 18:03
@sprt sprt changed the title general: Convert from base HTML/CSS/JS to Next.js migration: Move from vanilla JS to Next.JS Oct 29, 2024
Copy link
Collaborator

@sprt sprt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @a1icja and team! I left a few comments.

One ask - if you scroll down to the bottom of the PR page, you'll find that we're failing the commit message check. Can you follow the contributing guidelines (the whole section up until Reviews, not just the first heading) and fix your PR? TLDR: Squash your commits into one, update the commit subject to match the new PR title, add a description and a signoff.

One question - do you know how hard it would be to be able to set up a staging website per PR to be able to test PRs publicly before merging them? Otherwise folks would have to manually checkout feature branches to test changes.

Copy link
Collaborator

@sprt sprt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a couple more comments. Very close, thanks!

This PR reimplements the features found in the dashboard using Next.js, TailwindCSS, and PrimeReact.
It is not intended to be used for adding new features or fixing old bugs.

Fixes kata-containers#14

Signed-off-by: Alicja Mahr <[email protected]>
@sprt sprt merged commit 9b993f0 into kata-containers:main Nov 4, 2024
1 check passed
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.

5 participants