├── .gitignore ├── server ├── requirements.txt ├── README.md └── index.py ├── client ├── src │ ├── App.css │ ├── index.css │ ├── main.jsx │ ├── App.jsx │ └── assets │ │ └── react.svg ├── postcss.config.js ├── vite.config.js ├── .gitignore ├── index.html ├── README.md ├── .eslintrc.cjs ├── package.json ├── tailwind.config.js └── public │ └── vite.svg ├── LICENSE ├── schema └── resume.json ├── .github └── ISSUE_TEMPLATE │ ├── project-request.md │ ├── update-request.md │ └── bug-report.md ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md └── README.md /.gitignore: -------------------------------------------------------------------------------- 1 | *node_modules -------------------------------------------------------------------------------- /server/requirements.txt: -------------------------------------------------------------------------------- 1 | Jinja2 2 | latex 3 | -------------------------------------------------------------------------------- /client/src/App.css: -------------------------------------------------------------------------------- 1 | @tailwind base; 2 | @tailwind components; 3 | @tailwind utilities; 4 | -------------------------------------------------------------------------------- /client/src/index.css: -------------------------------------------------------------------------------- 1 | @tailwind base; 2 | @tailwind components; 3 | @tailwind utilities; 4 | -------------------------------------------------------------------------------- /client/postcss.config.js: -------------------------------------------------------------------------------- 1 | export default { 2 | plugins: { 3 | tailwindcss: {}, 4 | autoprefixer: {}, 5 | }, 6 | } 7 | -------------------------------------------------------------------------------- /client/vite.config.js: -------------------------------------------------------------------------------- 1 | import { defineConfig } from 'vite' 2 | import react from '@vitejs/plugin-react' 3 | 4 | // https://vitejs.dev/config/ 5 | export default defineConfig({ 6 | plugins: [react()], 7 | }) 8 | -------------------------------------------------------------------------------- /client/src/main.jsx: -------------------------------------------------------------------------------- 1 | import React from 'react' 2 | import ReactDOM from 'react-dom/client' 3 | import App from './App.jsx' 4 | import './index.css' 5 | 6 | ReactDOM.createRoot(document.getElementById('root')).render( 7 | 8 | 9 | , 10 | ) 11 | -------------------------------------------------------------------------------- /client/.gitignore: -------------------------------------------------------------------------------- 1 | # Logs 2 | logs 3 | *.log 4 | npm-debug.log* 5 | yarn-debug.log* 6 | yarn-error.log* 7 | pnpm-debug.log* 8 | lerna-debug.log* 9 | 10 | node_modules 11 | dist 12 | dist-ssr 13 | *.local 14 | 15 | # Editor directories and files 16 | .vscode/* 17 | !.vscode/extensions.json 18 | .idea 19 | .DS_Store 20 | *.suo 21 | *.ntvs* 22 | *.njsproj 23 | *.sln 24 | *.sw? 25 | -------------------------------------------------------------------------------- /client/index.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | Vite + React 8 | 9 | 10 |
11 | 12 | 13 | 14 | -------------------------------------------------------------------------------- /client/README.md: -------------------------------------------------------------------------------- 1 | # React + Vite 2 | 3 | This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules. 4 | 5 | Currently, two official plugins are available: 6 | 7 | - [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/README.md) uses [Babel](https://babeljs.io/) for Fast Refresh 8 | - [@vitejs/plugin-react-swc](https://github.com/vitejs/vite-plugin-react-swc) uses [SWC](https://swc.rs/) for Fast Refresh 9 | -------------------------------------------------------------------------------- /server/README.md: -------------------------------------------------------------------------------- 1 | # Python Backend 2 | 3 | - Our project structure is as follows: One folder for housing the temp json from the user and a temp file for compiling the resume with the user provided details 4 | - We will read input from the json file 5 | - Based on the json file, we will make a copy of the required template as a temp file that we can write to 6 | - We will use jinja to substitute blocks and values into the temp file. 7 | - Once the substitution is done, the temp file is then converted to a pdf and served to the user with the help of the Python latex library 8 | -------------------------------------------------------------------------------- /server/index.py: -------------------------------------------------------------------------------- 1 | # pip install requirements.txt - before making a change 2 | # place package name into requirements.txt file when downloaded 3 | 4 | from flask import Flask 5 | from flask_cors import CORS, cross_origin 6 | from jinja2 import FileSystemLoader 7 | from latex.jinja2 import make_env 8 | from latex import build_pdf 9 | 10 | app = Flask(__name__) 11 | CORS(app, resources={r"/*": {"origins": "*"}}) 12 | 13 | 14 | @app.route('/', methods=['GET']) 15 | def index(): 16 | return "

Welcome to resume-latex

" 17 | 18 | 19 | if __name__ == '__main__': 20 | app.run() 21 | 22 | -------------------------------------------------------------------------------- /client/.eslintrc.cjs: -------------------------------------------------------------------------------- 1 | module.exports = { 2 | root: true, 3 | env: { browser: true, es2020: true }, 4 | extends: [ 5 | 'eslint:recommended', 6 | 'plugin:react/recommended', 7 | 'plugin:react/jsx-runtime', 8 | 'plugin:react-hooks/recommended', 9 | ], 10 | ignorePatterns: ['dist', '.eslintrc.cjs'], 11 | parserOptions: { ecmaVersion: 'latest', sourceType: 'module' }, 12 | settings: { react: { version: '18.2' } }, 13 | plugins: ['react-refresh'], 14 | rules: { 15 | 'react-refresh/only-export-components': [ 16 | 'warn', 17 | { allowConstantExport: true }, 18 | ], 19 | }, 20 | } 21 | -------------------------------------------------------------------------------- /client/package.json: -------------------------------------------------------------------------------- 1 | { 2 | "name": "client", 3 | "private": true, 4 | "version": "0.0.0", 5 | "type": "module", 6 | "scripts": { 7 | "dev": "vite", 8 | "build": "vite build", 9 | "lint": "eslint . --ext js,jsx --report-unused-disable-directives --max-warnings 0", 10 | "preview": "vite preview" 11 | }, 12 | "dependencies": { 13 | "latex.js": "^0.12.6", 14 | "react": "^18.2.0", 15 | "react-dom": "^18.2.0" 16 | }, 17 | "devDependencies": { 18 | "@types/react": "^18.2.15", 19 | "@types/react-dom": "^18.2.7", 20 | "@vitejs/plugin-react": "^4.0.3", 21 | "autoprefixer": "^10.4.16", 22 | "daisyui": "^3.9.2", 23 | "eslint": "^8.45.0", 24 | "eslint-plugin-react": "^7.32.2", 25 | "eslint-plugin-react-hooks": "^4.6.0", 26 | "eslint-plugin-react-refresh": "^0.4.3", 27 | "postcss": "^8.4.31", 28 | "tailwindcss": "^3.3.3", 29 | "vite": "^4.4.5" 30 | } 31 | } 32 | -------------------------------------------------------------------------------- /client/src/App.jsx: -------------------------------------------------------------------------------- 1 | import { useState } from 'react' 2 | import reactLogo from './assets/react.svg' 3 | import viteLogo from '/vite.svg' 4 | import './App.css' 5 | 6 | function App() { 7 | const [count, setCount] = useState(0) 8 | 9 | return ( 10 | <> 11 |
12 | 13 | Vite logo 14 | 15 | 16 | React logo 17 | 18 |
19 |

Vite + React

20 |
21 | 24 |

25 | Edit src/App.jsx and save to test HMR 26 |

27 |
28 |

29 | Click on the Vite and React logos to learn more 30 |

31 | 32 | ) 33 | } 34 | 35 | export default App 36 | -------------------------------------------------------------------------------- /client/tailwind.config.js: -------------------------------------------------------------------------------- 1 | /** @type {import('tailwindcss').Config} */ 2 | export default { 3 | content: [ 4 | "./index.html", 5 | "./src/**/*.{js,ts,jsx,tsx}", 6 | ], 7 | theme: { 8 | extend: {}, 9 | }, 10 | plugins: [require("daisyui")], 11 | daisyui: { 12 | themes: ["night"], // true: all themes | false: only light + dark | array: specific themes like this ["light", "dark", "cupcake"] 13 | darkTheme: "dark", // name of one of the included themes for dark mode 14 | base: true, // applies background color and foreground color for root element by default 15 | styled: true, // include daisyUI colors and design decisions for all components 16 | utils: true, // adds responsive and modifier utility classes 17 | rtl: false, // rotate style direction from left-to-right to right-to-left. You also need to add dir="rtl" to your html tag and install `tailwindcss-flip` plugin for Tailwind CSS. 18 | prefix: "", // prefix for daisyUI classnames (components, modifiers and responsive class names. Not colors) 19 | logs: true, // Shows info about daisyUI version and used config in the console when building your CSS 20 | }, 21 | } 22 | 23 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2023 GDSC PESU 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /schema/resume.json: -------------------------------------------------------------------------------- 1 | { 2 | "template": 1, 3 | 4 | "about": { 5 | "name": "", 6 | "email": "", 7 | "phone": "", 8 | "website": "", 9 | "location": "" 10 | }, 11 | 12 | "education": [ 13 | { 14 | "institution": "", 15 | "location": "", 16 | "course": "", 17 | "score": "", 18 | "from": "", 19 | "to": "" 20 | } 21 | ], 22 | 23 | "skills": [ 24 | { 25 | "name": "", 26 | "desc": "" 27 | } 28 | 29 | ], 30 | 31 | 32 | "experiences": [ 33 | { 34 | "company": "", 35 | "location": "", 36 | "role": "", 37 | "website": "", 38 | "from": "", 39 | "to": "", 40 | "desc": "" 41 | } 42 | ], 43 | 44 | "references": [ 45 | { 46 | "referent":"", 47 | "contact":"", 48 | "company":"", 49 | "role":"" 50 | } 51 | ], 52 | 53 | "awards": [ 54 | { 55 | "title": "", 56 | "date": "", 57 | "awarder": "", 58 | "summary": "" 59 | } 60 | ], 61 | 62 | "projects": [ 63 | { 64 | "name": "", 65 | "desc": "", 66 | "link": "" 67 | } 68 | ] 69 | } 70 | 71 | -------------------------------------------------------------------------------- /client/public/vite.svg: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/project-request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Project Request 3 | about: If you want to propose a project idea that can be added to the repository 4 | title: "[PROJECT PROPOSAL]" 5 | labels: "" 6 | assignees: "" 7 | --- 8 | 9 | ## Project Request 10 | 11 | 12 | 13 | --- 14 | 15 | | Field | Description | 16 | | ------ | --------------------------------- | 17 | | About | A short Description about project | 18 | | Github | Your Github name | 19 | | Email | | 20 | | Label | Project Request | 21 | 22 | 23 | 24 | --- 25 | 26 | **Define You** 27 | 28 | - [ ] Hacktober Fest Contributor 29 | 30 | 31 | 32 | # Project Name 33 | 34 | 35 | 36 | ## Description 37 | 38 | 39 | 40 | [Description of the project, its goals, and expected outcomes] 41 | 42 | ## Scope 43 | 44 | [The project's boundaries, including its objectives, deliverables, and constraints] 45 | 46 | ## Timeline 47 | 48 | [The project's estimated start and end dates, milestones, and deadlines for deliverables] 49 | 50 | ## Video Links or Support Links 51 | 52 | [Links that can support the project in anyway] 53 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/update-request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Update Request 3 | about: If you want to make any updates to a project 4 | title: "[UPDATE]" 5 | labels: "" 6 | assignees: "" 7 | --- 8 | 9 | 10 | 11 | --- 12 | 13 | | Field | Description | 14 | | ------ | --------------------------------- | 15 | | About | A short Description about project | 16 | | Github | Your Github name | 17 | | Email | | 18 | | Label | Update request | 19 | 20 | 21 | 22 | --- 23 | 24 | **Define You** 25 | 26 | - [ ] Hacktober Fest Contributor 27 | 28 | 29 | 30 | **Is your feature request related to a problem? Please describe.** 31 | 32 | 33 | 34 | **Describe the solution you'd like...** 35 | 36 | 37 | 38 | **Describe alternatives you've considered?** 39 | 40 | 41 | 42 | **Approach to be followed (optional):** 43 | 44 | 45 | 46 | **Additional context** 47 | 48 | 49 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/bug-report.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: BUG REPORT 3 | about: If you find any bugs in the repository use this template to report them 4 | title: "[BUG]" 5 | labels: "" 6 | assignees: "" 7 | --- 8 | 9 | # Bug Report 10 | 11 | 12 | 13 | --- 14 | 15 | | Field | Description | 16 | | -------- | ----------------------------------------- | 17 | | About | Explain in detail the bug you experienced | 18 | | Name | Your GitHub name | 19 | | Email | | 20 | | Label | Bug Report | 21 | | Assignee | '' | 22 | 23 | 24 | 25 | --- 26 | 27 | **Define Yourself** 28 | 29 | - [ ] Hacktober Fest Contributor 30 | 31 | 32 | 33 | **Describe the Problem** 34 | 35 | 36 | 37 | **Expected Behavior** 38 | 39 | 40 | 41 | **Actual Behavior** 42 | 43 | 44 | 45 | **Screenshots** 46 | 47 | 48 | 49 | **Possible Solution (optional)** 50 | 51 | 52 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Code of Conduct 2 | 3 | ### Our Pledge 4 | 5 | In the interest of fostering an open and welcoming environment, we as 6 | contributors and maintainers pledge to make participation in our project and 7 | our community a harassment-free experience for everyone, regardless of age, body 8 | size, disability, ethnicity, gender identity and expression, level of experience, 9 | nationality, personal appearance, race, religion, or sexual identity and 10 | orientation. 11 | 12 | ### Our Standards 13 | 14 | Examples of behaviour that contributes to creating a positive environment 15 | include: 16 | 17 | - Using welcoming and inclusive language 18 | - Being respectful of differing viewpoints and experiences 19 | - Gracefully accepting constructive criticism 20 | - Focusing on what is best for the community 21 | - Showing empathy towards other community members 22 | 23 | Examples of unacceptable behaviour by participants include: 24 | 25 | - The use of sexualized language or imagery and unwelcome sexual attention or 26 | advances 27 | - Trolling, insulting/derogatory comments, and personal or political attacks 28 | - Public or private harassment 29 | - Publishing others' private information, such as a physical or electronic 30 | address, without explicit permission 31 | - Other conduct which could reasonably be considered inappropriate in a 32 | professional setting 33 | 34 | ### Our Responsibilities 35 | 36 | Project maintainers are responsible for clarifying the standards of acceptable 37 | behaviour and are expected to take appropriate and fair corrective action in 38 | response to any instances of unacceptable behaviour. 39 | 40 | Project maintainers have the right and responsibility to remove, edit, or 41 | reject comments, commits, code, wiki edits, issues, and other contributions 42 | that are not aligned to this Code of Conduct, or to ban temporarily or 43 | permanently any contributor for other behaviours that they deem inappropriate, 44 | threatening, offensive, or harmful. 45 | 46 | ### Scope 47 | 48 | This Code of Conduct applies both within project spaces and in public spaces 49 | when an individual is representing the project or its community. Examples of 50 | representing a project or community include using an official project e-mail 51 | address, posting via an official social media account or acting as an appointed 52 | representative at an online or offline event. Representation of a project may be 53 | further defined and clarified by project maintainers. 54 | 55 | ### Enforcement 56 | 57 | Instances of abusive, harassing, or otherwise unacceptable behaviour may be 58 | reported by contacting the project team at [Email Address]. All 59 | complaints will be reviewed and investigated and will result in a response that 60 | is deemed necessary and appropriate to the circumstances. The project team is 61 | obligated to maintain confidentiality concerning the reporter of an incident. 62 | Further details of specific enforcement policies may be posted separately. 63 | 64 | Project maintainers who do not follow or enforce the Code of Conduct in good 65 | faith may face temporary or permanent repercussions as determined by other 66 | members of the project's leadership. 67 | 68 | ### Attribution 69 | 70 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, 71 | available at [http://contributor-covenant.org/version/1/4][version] 72 | 73 | [homepage]: http://contributor-covenant.org 74 | [version]: http://contributor-covenant.org/version/1/4/ 75 | -------------------------------------------------------------------------------- /client/src/assets/react.svg: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | **Contribution.md** 2 | 3 | # 🎇 Contributing Guidelines 4 | 5 | Thank you for considering contributing to the resumeLaTeX project. We welcome contributions from all 6 | 7 | skill levels. Whether you're a beginner or an experienced developer, your help is valuable to us. Here are some guidelines to get you started: 8 | 9 | ## 💻 Before Contributing 10 | 11 | Before sending your contributions, please read these guidelines thoroughly. If you have any doubts, don't hesitate to reach out. 12 | 13 | ## 🙌 Contribution 14 | 15 | We accept contributions of all kinds, from small bug fixes to significant feature additions. Please follow these steps to contribute: 16 | 17 | ### 🔖 Steps to Contribute 18 | 19 | 1. **Fork** the repository to your own GitHub account. 20 | 2. **Clone** your forked repository to your local machine. 21 | 3. **Add an upstream link** to the main branch in your cloned repository: 22 | ``` 23 | git remote add upstream https://github.com/dscpesu/resumeLaTeX.git 24 | ``` 25 | 4. **Keep your fork up to date** by pulling from upstream (this avoids merge conflicts later): 26 | ``` 27 | git pull upstream main https://github.com/dscpesu/resumeLaTeX.git 28 | ``` 29 | 5. Create a new branch for your feature or bug fix: 30 | ``` 31 | git checkout -b 32 | ``` 33 | 6. Make your changes, add and commit them: 34 | ``` 35 | git commit -m "Write a meaningful but concise commit message" 36 | ``` 37 | 7. Push your changes to your fork: 38 | ``` 39 | git push origin 40 | ``` 41 | 8. Create a **Pull Request (PR)** on GitHub. Make sure to provide a clear and detailed description of your changes and why they are necessary. 42 | 43 | ### 🔨 Note 44 | 45 | - Please avoid editing or deleting someone else's code in this repository. You can only insert new files/folders. 46 | - Give meaningful names to the files or folders you add (e.g., `your-feature-name.ipynb`). 47 | - Always create a PR from a branch other than `main`. 48 | - Make sure your solution is better in terms of performance and other parameters compared to the previous work. 49 | - We encourage learning and growth, so don't hesitate to ask for help or guidance from mentors or the community. 50 | 51 | ## 🧲 Pull Request Review Criteria 52 | 53 | 1. Fill out the **[PR Template]** properly when creating a Pull Request. 54 | 2. Add your code (e.g., `.ipynb` files) to the respective folders. 55 | 3. Ensure that your work is original, not copied from other sources. 56 | 4. Comment your code where necessary. 57 | 5. For frontend changes, share screenshots and work samples before sending a PR. 58 | 6. Follow proper [style guides](https://google.github.io/styleguide/) for your work. 59 | 7. Feel free to discuss any queries or issues with us. 60 | 61 | ## 📍 Other Points to Remember 62 | 63 | We aim to make your work readable by others, so please consider the following: 64 | 65 | - Use snake_case for your file and folder names. 66 | - Avoid creating new directories if possible; try to fit your work into the existing structure. 67 | - The basic project folder should have two subfolders: Dataset and Model. 68 | - The `README.md` file should be concise and clear about the project's purpose. 69 | - Document your work briefly to help others understand it. 70 | 71 | ## 📖 Resources 72 | 73 | Here are some helpful resources to get you started: 74 | 75 | - [Markdown Cheat-Sheet](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet) 76 | - [Git Videos to Get Started](https://www.youtube.com/watch?v=xAAmje1H9YM&list=PLeo1K3hjS3usJuxZZUBdjAcilgfQHkRzW) 77 | - [Git Cheat Sheet](https://www.atlassian.com/git/tutorials/atlassian-git-cheatsheet) 78 | - [PEP 8 Style Guide](https://pep8.org/) 79 | 80 | ## 🤔 Need More Help? 81 | 82 | If you're new to open source or have any questions, refer to these articles on the basics of Git and GitHub. You can also contact our project admins or mentors if you get stuck: 83 | 84 | - [Forking a Repo](https://help.github.com/en/github/getting-started-with-github/fork-a-repo) 85 | - [Cloning a Repo](https://help.github.com/en/desktop/contributing-to-projects/creating-an-issue-or-pull-request) 86 | - [How to Create a Pull Request](https://opensource.com/article/19/7/create-pull-request-github) 87 | - [Getting Started with Git and GitHub](https://towardsdatascience.com/getting-started-with-git-and-github-6fcd0f2d4ac6) 88 | 89 | 🎉 🎊 😃 Happy Contributing 😃 🎊 🎉 90 | 91 | ``` 92 | 93 | ``` 94 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 |

2 | 3 |

4 | 5 |
6 |

resumeLaTeX 📄

7 |

Automatic LaTeX Resume Generator

8 |
9 | 10 |
11 | 12 | ![GitHub contributors](https://img.shields.io/github/contributors/dscpesu/resumeLaTeX?style=for-the-badge&color=blue) 13 | ![GitHub Closed issues](https://img.shields.io/github/issues-closed-raw/dscpesu/resumeLaTeX?style=for-the-badge&color=brightgreen) 14 | ![GitHub PR Open](https://img.shields.io/github/issues-pr/dscpesu/resumeLaTeX?style=for-the-badge&color=aqua) 15 | ![GitHub PR closed](https://img.shields.io/github/issues-pr-closed-raw/dscpesu/resumeLaTeX?style=for-the-badge&color=blue) 16 | ![GitHub language count](https://img.shields.io/github/languages/count/dscpesu/resumeLaTeX?style=for-the-badge&color=brightgreen) 17 | ![GitHub top language](https://img.shields.io/github/languages/top/dscpesu/resumeLaTeX?style=for-the-badge&color=aqua) 18 | ![GitHub last commit](https://img.shields.io/github/last-commit/dscpesu/resumeLaTeX?style=for-the-badge&color=blue) 19 | ![GitHub Maintained](https://img.shields.io/badge/Maintained%3F-yes-brightgreen.svg?style=for-the-badge) 20 | ![Github Repo Size](https://img.shields.io/github/repo-size/dscpesu/resumeLaTeX?style=for-the-badge&color=aqua) 21 | 22 |
23 | 24 | --- 25 | 26 | ## 📄 Welcome to resumeLaTeX! 27 | 28 | Welcome to resumeLaTeX, your go-to tool for generating professional LaTeX resumes effortlessly. Whether you're a seasoned LaTeX user or a newcomer, this project simplifies the process of creating stunning resumes. Say goodbye to the complexities of LaTeX and hello to your beautifully formatted resume! 29 | 30 | ## 🌟 Key Features 31 | 32 | - 📝 User-Friendly Interface: Our intuitive web-based interface makes resume creation a breeze. 33 | - 📚 Multiple Sections: Easily add sections for academics, skills, work experience, and more. 34 | - 🚀 Seamless LaTeX Integration: Get LaTeX-ready resumes with just a few clicks. 35 | - 💡 Beginner-Friendly: Perfect for those new to LaTeX or open source contributions. 36 | - 🌐 Open Source: Contribute to our project and enhance your skills. 37 | 38 | ## 🛠️ Getting Started 39 | 40 | To start using resumeLaTeX: 41 | 42 | 1. Visit our [resumeLaTeX Project](https://github.com/dscpesu/resumeLaTeX) on GitHub. 43 | 2. Fork the repository to your own GitHub account. 44 | 3. Clone your forked repository to your local machine. 45 | 4. Create or modify your resume using our user-friendly web interface. 46 | 5. Generate the LaTeX version of your resume with ease. 47 | 6. Share your beautifully formatted resume with the world! 48 | 49 | ## 💪 How to Contribute 50 | 51 | We welcome contributions from everyone, regardless of your experience level. Here's how you can get started: 52 | 53 | 1. Check out the existing [Issues](https://github.com/dscpesu/resumeLaTeX/issues) section to find tasks you'd like to work on. 54 | 2. Comment on an issue to express your interest, and we'll assign it to you. 55 | 3. Fork the repository, clone your fork, and create a new branch for your work. 56 | 4. Make your changes, commit them, and push to your fork. 57 | 5. Create a pull request, following our guidelines in the Contribution.md file. 58 | 6. Wait for review and feedback from our maintainers. 59 | 7. Once approved, your contribution will be merged into the project. 60 | 61 | ## 🤔 New to Open Source? 62 | 63 | If you're new to open source or LaTeX, don't worry! We have resources to help you get started: 64 | 65 | - [Learn about LaTeX](https://www.latex-project.org/) 66 | - [How to Fork a Repo](https://help.github.com/en/github/getting-started-with-github/fork-a-repo) 67 | - [How to Clone a Repo](https://help.github.com/en/desktop/contributing-to-projects/creating-a-pull-request) 68 | - [How to Create a Pull Request](https://opensource.com/article/19/7/create-pull-request-github) 69 | - [Getting Started with Git and GitHub](https://towardsdatascience.com/getting-started-with-git-and-github-6fcd0f2d4ac6) 70 | 71 | ## 👨‍💼 Project Admin 72 | 73 |
74 | 75 | 76 | 77 | 78 | 79 |

Adithya S Kolavi
💻
Karthik Namboori
💻
80 |
81 | 82 | ## ✨ Top Contributors 83 | 84 | Thanks to these amazing contributors. Your contributions make this project better! 🚀 85 | 86 | 87 | 88 | 89 | 90 | 91 | 92 | 93 | 94 | 95 | 96 | 97 | 98 | 99 | ## ⭐ Show Your Support 100 | 101 | If you find this project helpful or have learned something from it, please consider giving it a star. Your support means a lot to us! ⭐ 102 | 103 | [![GitHub followers](https://img.shields.io/github/followers/dscpesu.svg?label=Follow%20dscpesu&style=social)](https://github.com/dscpesu/) 104 | 105 | ## 📬 Connect with Us 106 | 107 | If you have any questions or need support, feel free to reach out to us at **dsc@pes.edu**. 108 | 109 |

110 | 111 | Star History Chart 112 | 113 |

114 | 115 |
116 |

Happy Resume Building! 📄

117 |
118 |
119 | 120 |

(Back to top)

121 | 122 |
123 | --------------------------------------------------------------------------------