Portfolio-2

The main goal of this repository is to document three prior submissions from the second year:

• JavaScript Frameworks project
• Semester Project 2
• Project Exam 2

Portfolio

Link to Portfolio

Brief

• CA

Process

• create a README.md file for each of these projects:

  • JavaScript Frameworks project
  • Semester Project 2
  • Project Exam 2

• create a README.md for your profile:

  • personal GitHub profile

• create a portfolio page that lists the 3 projects with the following format:

  • a list of the the 3 projects as cards
  • each card must have: the project title, the description, a screenshot of what the project looks like while running, and a link to the GitHub repository and a live website if it's online

Resources

• Template
• GitHub guide

Marking criteria

• can correctly document a project
• can create a personal GitHub profile README
• has created a personal portfolio webpage

Development Setup

Prerequisites

Ensure the following tools are installed on your system:

• Node.js and npm
• Git

Clone the Repository

1. Clone the repository and navigate to the project folder:

   git clone https://github.com/FP22FD/FP22FD-portfolio.git
   cd FP22FD-portfolio
   

2. Install the required dependencies

   npm install
   

3. Start Development Server

   npm run dev
   

4. Generate a production-ready build

   npm run build

Deploying to GitHub Pages

1. Open the Settings of this repository on GitHub.
2. Go to Pages under the Code and Automation tab.
3. Select the gh-pages (or main) branch and the /root directory for deployment.
4. Save changes and wait for the deployment to complete.

Automated Deployment Using gh-pages

1. Install the gh-pages package

   npm install gh-pages --save-dev
   

2. Add the following scripts to package.json:

   {
     "homepage": "https://fp22fd.github.io/FP22FD-portfolio/",
     "scripts": {
       "predeploy": "npm run build",
       "deploy": "gh-pages -d dist"
     }
   }

3. Deploy using:

   npm run predeploy
   npn run deploy

New Improvements: Hotjar Integration

This portfolio website includes Hotjar integration to enhance user experience tracking and analysis.
Hotjar allows us to:

• Analyze User Behavior: Understand how users interact with the portfolio.
• Collect Feedback: Identify usability issues and improve the design iteratively.
• Heatmaps and Session Recordings: Gain insights into user navigation patterns.

How It Works

• The Hotjar script is implemented globally in the project via a Hotjar React component.
• This component initializes Hotjar with a unique hjid (Hotjar ID) to connect it to the account.
• It is included at the root of the application, ensuring it tracks user activity on all pages.

How to Replace the Hotjar ID

1. Open the Hotjar.tsx file in src/components.
2. Replace 5259025 with the unique ID provided by your Hotjar account.

h._hjSettings = { hjid: YOUR_HOTJAR_ID, hjsv: 6 };

New Improvements: Bundle size Performance

1️⃣ Uso do Vite Bundle Visualizer The npx vite-bundle-visualizer command is used to visualize the size and contents of the bundles produced during the build process. It helps identify which packages take up the most space, allowing optimization of the application load time by splitting bundles or removing unnecessary dependencies.

The npx vite-bundle-visualizer command is a tool that generates a graphical visualization of the size and contents of the bundles produced by Vite during the build process. It is useful for identifying which packages are taking up the most space, allowing for optimization of the application load time, either by splitting the bundles or removing unnecessary dependencies.

1. Run the following command in the terminal:

   npx vite-bundle-visualizer

2️⃣ Uso de Suspense e lazy This allows certain components to be loaded on demand rather than at initial load.
Result: Less code in the initial bundle, faster loading, and better performance.

In the application, Suspense and lazy are used in the router to load components on demand instead of loading them at the initial page load. This helps to improve performance by reducing the initial bundle size.

3️⃣ Placing images and icons in the public folder Static files like images and icons are served directly by the server, without being processed by the bundler.
Result: Better caching, shorter build times, and smaller final bundle size.

• public/
  • logo.png (Served directly by the server)
• src/
  • assets/
    • logo.png (Bundled by the bundler)

4️⃣ Importing only the necessary parts of a large package Instead of importing an entire heavy package, you choose only the small module you need.

The react-world-flags package has been replaced with svg-country-flags in this project. Unlike the previous package, svg-country-flags allows for a more modular approach where you can import only the specific flag(s) you need, reducing the bundle size.

Instead of importing the entire package, you can import specific flags individually to keep your bundle optimized. Follow these steps:

1. Install the required flag package:

   npm install svg-country-flags

Resource

• Icons: React Icons
• SVG: Editing SVG files
• Images: Image size optimization
• Tailwind CSS Color Generation: uicolors
• The Open Graph protocol: MDN metadata
• Accessibility: a11y
• Accessibility: WCAG 2.1
• Accessibility: WAVE