My resume.json Project with Resume Schema

[neviaumi]

Greetings

Hi everyone! 👋
I wanted to take a moment to share a project I’ve been working on, **resume.json **, which leverages the power of modern tooling to structure resumes in a JSON-friendly format. It might be a useful resource or inspiration for others working with the resume-schema.

Overview of the Project

resume.json is a personal project where I structure my professional resume using JSON. Alongside this, I’ve built a web interface for viewers to browse the resume in a structured and visually appealing format.
Here's what the project offers:

• Integration with GitHub Actions: Automatic deployment to GitHub Pages using CI/CD pipelines for seamless updates.
• Web-based Version: A live website to showcase the resume content – [View Live Project Here](https://neviaumi.github.io/resume.json/).
• Custom Web Components: I’ve created modular web components (json-resume) for reusable resume elements.
• Tech Stack: It uses Vite.js, TailwindCSS, PostCSS, and supports strict standards enforcement with ESLint and Prettier.

Example Usage of json-resume Web Component

The json-resume web component provides functionality to customize the navigation and footer of your resume. It includes three main slots for usage:

1. pdf-version-navigate-link
   This slot allows navigation to the PDF version of the resume.
2. web-version-navigate-link
   This slot allows navigation to the web (HTML) version of the resume. However, this link is only visible during @media print mode to guide users printing from the web version.
3. footer
   A self-explanatory slot where you can add any HTML element to appear at the bottom of your resume page or section.

Here is an example usage of the footer slot.
These navigations make it easier for users to switch between PDF and HTML renderings seamlessly while maintaining clear printability and responsive capabilities.

Current Limitations (Work in Progress)

One outstanding challenge I’m tackling relates to ATS (Applicant Tracking System) compatibility. Here’s the issue in detail:

• Problem: In the current implementation, ATS sometimes struggles to parse certain sections of the resume where there are no nearby labels for context. For example, the work experience section isn't always properly parsed by ATS systems.
• Planned Solution: I plan to explore a function that renders the resume schema into LaTeX. This would help generate an ATS-friendly version of the resume while preserving the intended design.

How It Relates to Resume Schema

The structure of my JSON resume draws from schema-based workflows like resume-schema. Leveraging these standards has helped me maintain consistency, portability, and ease of validation.
I’d love feedback from the community on aligning even further with the resume-schema standards or advice on handling the AST-related problem.

Closing Note

Let me know your thoughts or suggestions for improvement! I see this as an evolving project and welcome input from the amazing contributors in the resume-schema community. A special thanks to the maintainers here for standardizing how resumes can be structured and shared 👏.
Feel free to check out and contribute to resume.json. 🚀