Initialize project and refine Dashboard Overview layout (#12) ### Project Infrastructure - Initialized the repository structure and directory layout. - Configured build and deployment settings to enable local development. ### UI & Dashboard - Integrated foundational UI components and global styling configurations. - Refined the Dashboard Overview layout through multiple iterations of styling and layout adjustments to improve visual hierarchy. [v0 Session](https://v0.app/chat/2tqoPgihDyU) (#26)#27
Initialize project and refine Dashboard Overview layout (#12)
### Project Infrastructure
- Initialized the repository structure and directory layout.
- Configured build and deployment settings to enable local development.
### UI & Dashboard
- Integrated foundational UI components and global styling
configurations.
- Refined the Dashboard Overview layout through multiple iterations of
styling and layout adjustments to improve visual hierarchy.
[v0 Session](https://v0.app/chat/2tqoPgihDyU) (#26)#27Huynhthuongg wants to merge 33 commits into
Conversation
…ct-setup Stabilize RKix project setup
Signed-off-by: Huỳnh Thương <252359928+Huynhthuongg@users.noreply.github.com>
Signed-off-by: Huỳnh Thương <252359928+Huynhthuongg@users.noreply.github.com>
Signed-off-by: Huỳnh Thương <252359928+Huynhthuongg@users.noreply.github.com>
Signed-off-by: Huỳnh Thương <252359928+Huynhthuongg@users.noreply.github.com>
Generated by v0 [v0 Session](https://v0.app/chat/2tqoPgihDyU)
- Updated navigation logic to automatically reset to the default branch after a branch is deleted - Improved user experience by preventing broken or "not found" states when a branch no longer exists [v0 Session](https://v0.app/chat/2tqoPgihDyU)
Generated by v0 [v0 Session](https://v0.app/chat/2tqoPgihDyU) <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Initialize the repository with a base project structure and configuration. Sets up build and deployment defaults to unblock local development. <sup>Written for commit b5ae85d. Summary will update on new commits.</sup> <a href="https://cubic.dev/pr/Huynhthuongg/Terkix/pull/7?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a> <!-- End of auto-generated description by cubic. -->
- Initialized the repository with a base project structure and directory layout. - Configured build and deployment defaults to enable local development. - Integrated initial UI components and configuration generated via v0. [v0 Session](https://v0.app/chat/2tqoPgihDyU)
### Project Setup - Initialized the repository with a base project structure and directory layout. - Configured build and deployment defaults to enable local development. ### UI & Components - Integrated initial UI components and configuration generated via v0. [v0 Session](https://v0.app/chat/2tqoPgihDyU)
### Project Infrastructure - Initialized the repository structure and directory layout. - Configured build and deployment settings to enable local development. ### UI Foundation - Integrated foundational UI components and styling configuration. [v0 Session](https://v0.app/chat/2tqoPgihDyU)
Co-authored-by: Huỳnh Thương <252359928+Huynhthuongg@users.noreply.github.com>
### Project Infrastructure - Initialized the repository structure and directory layout. - Configured build and deployment settings to enable local development. ### UI & Dashboard - Integrated foundational UI components and global styling configurations. - Refined the Dashboard Overview layout through multiple iterations of styling and layout adjustments to improve visual hierarchy. [v0 Session](https://v0.app/chat/2tqoPgihDyU)
- Implemented automatic reset to the default branch when the current active branch is deleted. [v0 Session](https://v0.app/chat/2tqoPgihDyU)
* Updated branch navigation to automatically reset to the default branch if the currently active branch is deleted. [v0 Session](https://v0.app/chat/2tqoPgihDyU)
Generated by v0 [v0 Session](https://v0.app/chat/2tqoPgihDyU)
### Project Infrastructure - Initialized the repository structure and directory layout. - Configured build and deployment settings to enable local development. ### UI & Dashboard - Integrated foundational UI components and global styling configurations. - Refined the Dashboard Overview layout through multiple iterations of styling and layout adjustments to improve visual hierarchy. [v0 Session](https://v0.app/chat/2tqoPgihDyU) (#26)
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ee030a1fbc
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| uses: actions/upload-pages-artifact@v3 | ||
| with: | ||
| # Upload entire repository | ||
| path: '.' |
There was a problem hiding this comment.
Deploy the Vite build output to Pages
This Pages workflow uploads the repository root without running npm run build, but index.html still points at /src/main.tsx, so GitHub Pages will serve raw TSX and bare imports instead of the bundled Vite assets whenever this deployment runs. Build first and upload dist (or remove this workflow in favor of a Vite Pages workflow) so the hosted site can actually load.
Useful? React with 👍 / 👎.
| - name: Build | ||
| run: | | ||
| npm install | ||
| npx webpack |
There was a problem hiding this comment.
Replace the webpack CI step with the Vite build
This repository's build script is Vite-based and a repo-wide search only finds this workflow for webpack; there is no webpack config, webpack dependency, or src/index.js. Webpack's documented no-config default entry is ./src/index.js, so this matrix will fail on every PR/push instead of validating the app. Run npm run build here, or add the missing webpack setup intentionally.
Useful? React with 👍 / 👎.
| "typescript": "~5.8.2", | ||
| "vite": "^6.2.3" | ||
| } | ||
| "vite": "^6.2.3", |
There was a problem hiding this comment.
Keep Vite available for production starts
For production installs that omit devDependencies, npm start will crash before reaching the NODE_ENV branch because server.ts imports vite at module scope and the build command uses --packages=external, leaving package imports to be resolved at runtime. Since vite is now only a devDependency, a prebuilt dist/server.cjs run with npm ci --omit=dev cannot resolve it; either keep Vite in dependencies or lazy-import it only in the development path.
Useful? React with 👍 / 👎.
| push: | ||
| branches: ["main"] |
There was a problem hiding this comment.
Use a single Pages deployment workflow
This new Jekyll Pages workflow triggers on the same main pushes and deploys to the same github-pages environment as .github/workflows/static.yml, with both using the pages concurrency group and cancel-in-progress: false. A single push can therefore queue two independent deployments, and whichever deploy job finishes last overwrites the published artifact with a different build path; keep only one Pages deployment pipeline for this app.
Useful? React with 👍 / 👎.
| Start the production build: | ||
|
|
||
| ```bash | ||
| npm start |
There was a problem hiding this comment.
Set NODE_ENV for the documented production start
When users follow this new README sequence (npm run build then npm start) from a normal shell, the start script does not set NODE_ENV, so server.ts takes the process.env.NODE_ENV !== "production" development branch and starts Vite middleware instead of serving the built dist assets. Update the documented command or the script to set NODE_ENV=production so this actually validates the production build.
Useful? React with 👍 / 👎.
No description provided.