Welcome to Hook! This isn't just any project, it's the culmination of our learning journey. It's the result of countless hours of coding, debugging, and coffee. We're excited to share it with you. Dive in and explore our end-of-studies project! 🚀👩💻👨💻
Ever felt like finding the right internship or alternance position is like searching for a four-leaf clover? That's exactly why we built Hook.
We're here to shake things up in the world of recruitment. No more endless scrolling, no more mismatched opportunities. Just you, your preferences, and a list of opportunities that feel like they've been handpicked just for you.
How do we do it? One word: Machine Learning. Hook learns from you, understands what you're looking for, and does all the heavy lifting.
The result? A process that's as smooth as a well-oiled machine, saving you time and energy.
So, whether you're a student ready to take on the world, or a recruiter on the hunt for fresh talent, Hook's got your back.
To clone this project to your local machine, follow these steps:
- Open your terminal.
- Navigate to the directory where you want to clone the project.
- Run the following command:
git clone https://github.com/LucasWerey/Hook- This will create a new directory named after the repository. Navigate into it by running
cd Hook- Now you have the project on your local machine and you can start working on it.
This repository contains both the frontend and the backend of the Hook project.
The frontend is built with Vue.js, a progressive JavaScript framework for building user interfaces. We've also used a personal component library, DSLIB-PFE, to ensure a consistent and high-quality user experience.
You can find the frontend code in the frontend directory.
The backend is primarily written in Rust, a language that offers high performance and safety. It handles all the business logic and database interactions. However, our AI model is implemented in Python, a language known for its strong support for scientific computing and machine learning.
You can find the backend code in the backend directory.
This way, you can work on the frontend and backend separately, but they're both part of the same project and repository. This makes it easier to coordinate changes and keep everything in sync.
As our project continues to evolve, there are several enhancements and features we're planning to implement:
Setup the front end and the back endSetup MongoDb with all collectionsImplement API paths for all collectionsLanding PageMake the sign in and sign up
We adhere to the Conventional Commits specification for our commit messages. This leads to more readable messages that are easy to follow when looking through the project history.
A commit message consists of a header, body and footer. The header has a special format that includes a type, a scope and a description:
Must be one of the following:
feat: A new featurefix: A bug fixdocs: Documentation only changesstyle: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)refactor: A code change that neither fixes a bug nor adds a featureperf: A code change that improves performancetest: Adding missing tests or correcting existing testschore: Changes to the build process or auxiliary tools and libraries such as documentation generation
The scope should be the name of the npm package affected (as perceived by the person reading the changelog generated from commit messages.)
The description is a short description of the change:
- use the imperative, present tense: "change" not "changed" nor "changes"
- don't capitalize the first letter
- no dot (.) at the end