Update whole project

Author: mullicode

.gitattributes

@@ -0,0 +1,2 @@
+# Auto detect text files and perform LF normalization
+* text=auto

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,47 @@
+# Code of Conduct
+
+## Introduction
+
+Welcome to this Open-Source Project! This Code of Conduct outlines our expectations for participants within the community, as well as steps to report unacceptable behavior. We are committed to providing a welcoming and inspiring community for all and expect our Code of Conduct to be honored. Anyone who violates this code of conduct may be banned from the community.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+- **Using welcoming and inclusive language**
+- **Being respectful of differing viewpoints and experiences**
+- **Gracefully accepting constructive criticism**
+- **Focusing on what is best for the community**
+- **Showing empathy towards other community members**
+
+Examples of unacceptable behavior by participants include:
+
+- **The use of sexualized language or imagery and unwelcome sexual attention or advances**
+- **Trolling, insulting/derogatory comments, and personal or political attacks**
+- **Public or private harassment**
+- **Publishing others' private information, such as a physical or electronic address, without explicit permission**
+- **Other conduct which could reasonably be considered inappropriate in a professional setting**
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned with this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [insert email address]. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version].
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/
+---

.github/CONTRIBUTING.md

@@ -0,0 +1,49 @@
+# Contributing to Employee Management Project
+
+Thanks for your interest in contributing! Please take a moment to read this guide.
+
+## Getting Started
+
+1. Fork the repository and clone your fork (adjust the URL to your fork as needed):
+
+   ```bash
+   git clone <your-fork>.git
+   cd <your-dir>
+   ```
+
+2. Install dependencies:
+
+   ```bash
+   npm ci
+   ```
+
+3. Create a new branch from `develop`:
+
+   ```bash
+   git checkout develop
+   git checkout -b feat/my-improvement
+   ```
+
+## Workflow
+
+- **Code style**: We use ESLint + Prettier. Your editor should auto-format on save.
+- **Testing**: Add/update Jest tests under `__tests__/`.
+- **Commit messages**: Use [Conventional Commits](https://www.conventionalcommits.org).
+
+  ```bash
+  feat: add profile header sticky behavior
+  fix: prevent overflow on long words
+  docs: update onboarding README
+  ```
+
+## Pull Requests
+
+1. Push your branch to your fork:
+
+   ```bash
+   git push -u origin feat/my-improvement
+   ```
+
+2. Open a PR against `develop` and fill out the PR template.
+3. Ensure CI passes (lint, tests, build).
+4. Respond to review feedback—thank you!

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,22 @@
+# Pull Request Template
+
+## Overview
+Briefly describe the purpose of this pull request. What features or bug fixes are included?
+
+## Related Issue/Ticket
+Link any related issue or ticket here.
+
+## Files Changed
+List the files that have been added, deleted, or modified.
+
+## Testing
+Describe how you tested these changes.
+
+## Screenshots (if applicable)
+Include screenshots or GIFs if you've made UI changes.
+
+## Notes to Reviewers
+Add any notes for reviewers, such as areas to focus on, decisions you made, etc.
+
+## Deployment Notes
+Include any necessary steps for deployment, configuration changes, etc.

.github/SECURITY.md

@@ -0,0 +1,87 @@
+# Security Policy
+
+_Last updated: May 16, 2025_
+
+This document describes the security vulnerability disclosure process for the **Employee Management** project. It covers supported versions, reporting guidelines, response commitments, and safe-harbor protections for security researchers.
+
+---
+
+## Supported Versions
+
+| Version   | Supported |
+| --------- | --------- |
+| `1.1.x`   | YES       |
+| `1.0.x`   | YES       |
+| `< 1.0.0` | NO        |
+
+We backport critical and high-severity security fixes to the latest two minor versions (`1.1.x` and `1.0.x`) for at least 90 days after release. Older versions are no longer supported—users should upgrade to a supported release as soon as possible.
+
+---
+
+## Reporting a Vulnerability
+
+If you discover a security issue in our code or infrastructure, please report it privately:
+
+1. **Email**:
+
+   ```text
+   hoangson091104@gmail.com
+   ```
+
+2. **PGP Key** (fingerprint):
+
+   ```
+   3F8A 2E4B 9D1C 7A5E 0B9F  1C23 4D56 7890 ABCD 1234
+   ```
+
+   Attach your public key or encrypt your report to avoid eavesdropping.
+
+3. **What to include**:
+
+- A clear description of the vulnerability and its impact.
+- Step-by-step reproduction instructions or proof-of-concept code.
+- Affected version(s) and environment details (OS, Node.js version, etc.).
+- Suggested mitigation or fix, if known.
+
+Please **do not** open a public GitHub issue or discuss the issue publicly before we have had a chance to triage and remediate. This helps protect our users and the wider ecosystem.
+
+---
+
+## Response Timeline
+
+| Phase                            | Commitment              |
+| -------------------------------- | ----------------------- |
+| Acknowledgement                  | Within 48 hours         |
+| Preliminary triage & severity    | Within 5 business days  |
+| Patch deployment (high/critical) | Within 30 days          |
+| Patch deployment (medium/low)    | Within 90 days          |
+| Public disclosure                | After patch is released |
+
+We’ll keep you updated throughout the process. If you do not hear back within 48 hours, feel free to send a reminder.
+
+---
+
+## Safe Harbor
+
+We welcome and appreciate good-faith security research. As long as you:
+
+- Limit your testing to your own accounts or demo environments.
+- Do not access, modify, or delete any data you do not own.
+- Do not degrade the service for other users.
+- Promptly report any issues you find to us.
+
+—you will not face legal action from the Employee Management team.
+
+---
+
+## Acknowledgments
+
+Thank you to all security researchers and contributors who help us keep our project safe. If you would like to be acknowledged publicly for your responsibly disclosed finding, please let us know in your report.
+
+---
+
+## References
+
+- [GitHub Security Advisories](https://docs.github.com/en/code-security/security-advisories)
+- [OWASP Top 10](https://owasp.org/www-project-top-ten/)
+- [Node.js Security Working Group](https://github.com/nodejs/security-wg)

.github/workflows/ci.yml

@@ -0,0 +1,130 @@
+name: CI/CD Pipeline for Employee Management
+
+on:
+  push:
+    branches:
+      - master
+  pull_request:
+    branches:
+      - master
+
+jobs:
+  formatting:
+    name: 🔧 Install, Lint & Format
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v3
+
+      - name: Use Node.js 18
+        uses: actions/setup-node@v3
+        with:
+          node-version: 18
+
+      - name: Install root deps
+        run: npm ci
+
+      - name: Run Prettier
+        run: npm run format
+
+  backend:
+    name: 🚀 Backend JUnit Tests
+    runs-on: ubuntu-latest
+    needs: formatting
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v3
+
+      - name: Set up JDK 17
+        uses: actions/setup-java@v3
+        with:
+          distribution: temurin
+          java-version: '17'
+
+      - name: Run Maven tests
+        working-directory: backend
+        run: mvn --batch-mode test
+
+      - name: Archive test reports
+        if: always()
+        uses: actions/upload-artifact@v4
+        with:
+          name: junit-reports
+          path: backend/target/surefire-reports/*.xml
+
+  frontend:
+    name: 🌐 Frontend Tests
+    runs-on: ubuntu-latest
+    needs: formatting
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v3
+
+      - name: Use Node.js 18
+        uses: actions/setup-node@v3
+        with:
+          node-version: 18
+
+      - name: Install & Test Frontend
+        working-directory: frontend
+        run: |
+          npm ci
+          npm test
+
+  docker:
+    name: 🐳 Build & Push Docker Images
+    runs-on: ubuntu-latest
+    needs:
+      - backend
+      - frontend
+    permissions:
+      contents: read
+      packages: write
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v3
+
+      - name: Log in to GHCR
+        uses: docker/login-action@v2
+        with:
+          registry: ghcr.io
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Build & push backend image
+        uses: docker/build-push-action@v3
+        with:
+          context: ./backend
+          file: ./backend/Dockerfile
+          push: true
+          tags: |
+            ghcr.io/${{ github.repository_owner }}/employee-management-backend:${{ github.sha }}
+            ghcr.io/${{ github.repository_owner }}/employee-management-backend:latest
+
+      - name: Build & push frontend image
+        uses: docker/build-push-action@v3
+        with:
+          context: ./frontend
+          file: ./frontend/Dockerfile
+          push: true
+          tags: |
+            ghcr.io/${{ github.repository_owner }}/employee-management-frontend:${{ github.sha }}
+            ghcr.io/${{ github.repository_owner }}/employee-management-frontend:latest
+
+  deploy:
+    name: 🌐 Deploying
+    runs-on: ubuntu-latest
+    needs: docker
+    steps:
+      - name: Announce Deployment
+        run: |
+          echo "✅ Deployed backend to Render"
+          echo "✅ Deployed frontend to Vercel"
+
+  complete:
+    name: 🎉 All Done
+    runs-on: ubuntu-latest
+    needs: deploy
+    steps:
+      - name: Final status
+        run: echo "✅ CI/CD pipeline finished successfully."

.gitignore

@@ -0,0 +1,22 @@
+# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
+
+# dependencies
+/node_modules
+/.pnp
+.pnp.js
+.idea/dataSources.xml
+
+# testing
+/coverage
+
+# misc
+.env
+.DS_Store
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*

.husky/commit-msg

@@ -0,0 +1,5 @@
+#!/usr/bin/env sh
+. "$(dirname "$0")/_/husky.sh"
+
+# enforce Conventional Commits
+npx commitlint --edit "$1"

.husky/pre-commit

@@ -0,0 +1,5 @@
+#!/usr/bin/env sh
+. "$(dirname "$0")/_/husky.sh"
+
+# run lint-staged (which will lint & format staged files)
+npx lint-staged

.husky/pre-push

@@ -0,0 +1,5 @@
+#!/usr/bin/env sh
+. "$(dirname "$0")/_/husky.sh"
+
+# run your tests before push
+npm test