academicpages / academicpages/academicpages.github.io

Generate structured CV from standardly formatted json data structure

Abierto
#2,883 5 comentarios 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
SCSS
Estrellas
17.6k
Forks
9.2k
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

Suggestion overview

While the [current CV format/Page](https://academicpages.github.io/cv/) is certainly sufficient and gets the job done, it may be possible to improve the structure and aesthetics of the page *while also* streamlining the process of updating this page. Specifically, **there may be value in developing a standardized format for CVs (i.e., json based) and an associated CV page style and formatting script**.

As an example of what can be achieved with this, folks can take a look at what I've tinkered up for my CV:

[![Image](https://github.com/user-attachments/assets/dd3096cc-99ba-4d42-b2a9-867b25c133bd)](https://dannbullock.github.io/cv/)

Foreseen Task Breakdown and Challenges

I fully recognize that it is highly unlikely that a single standard would meet all needs. I tried to find an existing CV/resume format or standard that could fulfill this role (e.g., something that works with USAjobs.gov) but nothing seemed viable. To that end I developed what I felt was a fairly generalized and extensible json framework (example [here](https://github.com/DanNBullock/DanNBullock.github.io/blob/master/_data/curriculumVitae.json)) and a [corresponding html template](https://github.com/DanNBullock/DanNBullock.github.io/blob/master/_pages/cv-html-template_2.html) to make use of this content.

Although the examples I provided may prove to be of use as a starting point, I don't expect them to be what the majority of the community here needs. To that end, I suspect **there will need to be some coordinated process of developing an acceptable generalized and extensible framework for _both_ the data structure and the css/html layout**.

Admittedly, the use of a intermediary json data structure may not be to many user's liking and so it may be warranted to have a failover condition that presents the conventionally produced and structured markdown-based CV in the event that no appropriate json CV data structure is found.

Closing

If I can be of assistance with this process just let me know--I've greatly appreciated the resource that this repo/page has provided and I would be quite pleased if I could contribute back.

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.