Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/levg34/private-cv
This project aims to create a website for presenting a CV without personal information.
https://github.com/levg34/private-cv
cv privacy resume solidjs
Last synced: about 7 hours ago
JSON representation
This project aims to create a website for presenting a CV without personal information.
- Host: GitHub
- URL: https://github.com/levg34/private-cv
- Owner: levg34
- License: gpl-3.0
- Created: 2023-08-03T17:34:56.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2024-01-11T21:21:51.000Z (10 months ago)
- Last Synced: 2024-01-12T04:38:12.081Z (10 months ago)
- Topics: cv, privacy, resume, solidjs
- Language: TypeScript
- Homepage: https://levg34.github.io/private-cv/
- Size: 234 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 8
-
Metadata Files:
- Readme: README.md
- License: LICENSE.md
Awesome Lists containing this project
README
# Private CV
[](https://github.com/levg34/private-cv/actions/workflows/backend.yml)
[](https://github.com/levg34/private-cv/actions/workflows/frontend.yml)
[](https://codecov.io/gh/levg34/private-cv)
[](https://github.com/prettier/prettier)
This project aims to create a website to present a CV without any personal information. Recruiters can make a request to access the information they want to see by adding it to a cart. The owner of the CV will approve or reject the request, and if approved, the recruiter will receive a token valid for 48 hours to access the requested information. Otherwise, the information will be blurred, like a skeleton CV. Recruiters can click on the sections they want to read and add them to the cart before sending their request. Recruiters must connect with an OTP to send a request. There will also be a contact form if the recruiter wants to contact the owner of the CV without adding any information to the cart. In addition to these features, the recruiter can download a PDF version of the CV containing only the information they requested and that the owner authorized. It will also be possible to do a mini-tutorial to discover the owner's last name without session validation. To do this, the recruiter can add the last name to the cart and then validate the cart.
## Project Status
⚠️ **Warning:** This project is in the very early stages of development and is not yet functional. I am working alone on this project and welcome contributions from the community. Please note that the project is still in its early stages and may undergo significant changes as development progresses.
You can see the result of the latest build [here](https://levg34.github.io/private-cv/).
## Motivation
In today's digital age, it's crucial to have an online presence to connect with potential employers and collaborators. However, the online world also comes with concerns about privacy and data security. This project was initiated to strike a balance between showcasing your professional background and protecting your personal information.
The primary motivation behind this project is to provide a secure and privacy-focused platform for individuals to present their CVs to recruiters and collaborators. Key motivations include:
1. **Privacy Protection:** Unlike platforms like LinkedIn, which often require users to share extensive personal information, this platform emphasizes privacy protection. You can present your professional background without exposing your personal data to the public.
2. **Selective Information Sharing:** LinkedIn offers limited control over the information users share. In contrast, this platform allows you to select and share specific details relevant to your audience, ensuring a tailored and secure experience.
3. **Control Over Data:** You have full control over who can access your data. You can approve or reject requests, providing transparency and security.
4. **Efficient Recruitment:** LinkedIn provides a wide range of data, making it challenging for recruiters to find specific information. This platform streamlines the recruitment process by allowing recruiters to request and access only the data they need.
5. **Secure Communication:** The platform facilitates secure communication between job seekers and recruiters. Recruiters can send messages through a contact form without compromising personal information.
6. **PDF CV Generation:** Unlike LinkedIn, which may not provide easy PDF generation options, this platform allows you to generate a professional PDF CV containing only the approved information.
7. **Education and Training:** While emphasizing privacy, the platform also promotes responsible data handling. Users can test the system by attempting to discover your last name, highlighting the importance of data protection.
By addressing these motivations, this project aims to redefine how professionals present themselves online, ensuring privacy, control, and efficiency in the process. The project is committed to continuous improvement and the expansion of features to better serve users.
## Table of Contents
- [Introduction](#introduction)
- [Installation and Usage](#installation-and-usage)
- [Features and Functionality](#features-and-functionality)
- [Examples and Screenshots](#examples-and-screenshots)
- [License](#license)
- [Acknowledgments](#acknowledgments)
## Introduction
This project aims to create a website to present a CV without any personal information. Recruiters can make a request to access the information they want to see by adding it to a cart. The owner of the CV will approve or reject the request, and if approved, the recruiter will receive a token valid for 48 hours to access the requested information. Otherwise, the information will be blurred, like a skeleton CV. Recruiters can click on the sections they want to read and add them to the cart before sending their request. Recruiters must connect with an OTP to send a request. There will also be a contact form if the recruiter wants to contact the owner of the CV without adding any information to the cart. In addition to these features, the recruiter can download a PDF version of the CV containing only the information they requested and that the owner authorized. It will also be possible to do a mini-tutorial to discover the owner's last name without session validation. To do this, the recruiter can add the last name to the cart and then validate the cart.
## Installation and Usage
TODO
## Features and Functionality
- Recruiters can make a request to access the information they want to see by adding it to a cart.
- The owner of the CV will approve or reject the request, and if approved, the recruiter will receive a token valid for 48 hours to access the requested information.
- Otherwise, the information will be blurred, like a skeleton CV.
- Recruiters can click on the sections they want to read and add them to the cart before sending their request.
- Recruiters must connect with an OTP to send a request.
- There will also be a contact form if the recruiter wants to contact the owner of the CV without adding any information to the cart.
- The recruiter can download a PDF version of the CV containing only the information they requested and that the owner authorized, if they are authentified by OTP.
- It will also be possible to do a mini-tutorial to discover the owner's last name without session validation.
## Examples and Screenshots
TODO
## Contributing
Your contributions to this project are greatly appreciated. Before you submit a contribution, please follow these guidelines to ensure a smooth collaboration:
### Branch Naming Convention
- **Frontend Features:** When working on frontend features, please create a branch with the following format: `frontend/feature-name`.
- **Backend Features:** When working on backend features, please create a branch with the following format: `backend/feature-name`.
- **Fullstack Features:** When working on fullstack features, please create a branch with the following format: `fullstack/feature-name`.
- **Modules Features:** When working on other modules features, please create a branch with the following format: `module-name/feature-name`.
For the rest, use common sense: `doc/feature-name` for documentation, `ci/feature-name` for CI, etc..
### Code Quality and Testing
- Ensure that the project's CI/CD pipeline is green before submitting a pull request. This includes passing tests, adhering to linting standards, and meeting coverage requirements.
### Pull Request Guidelines
1. Create a pull request with a clear and descriptive title, use [this PR Template](.github/PULL_REQUEST_TEMPLATE.md).
2. In the pull request description, provide a detailed explanation of your changes and their purpose.
3. Mention any issues or features related to the pull request.
4. Ensure your code is well-documented and follows coding standards.
5. If your pull request introduces new modules, follow this rule for branch names: `module-name/feature-name`.
### Getting Started
1. Fork the repository and create your branch from the `main` branch.
2. Clone your forked repository to your local machine.
3. Make your changes and ensure they pass tests and linting.
4. Push your changes to your fork on GitHub.
5. Create a pull request to the `main` branch of the original repository.
Your contributions are valuable in advancing this project. Thank you for your interest and support in making it better.
## License
This project is licensed under the GPLv3 license. See the LICENSE file for details.
## Acknowledgments
- None yet