myprofile

[eerison]

Hello Hello @maxpowis

just to share with you, that you can generate your resume using github discussion with yaml syntax in myprofile project.

You will generate your resume like this: https://github.com/shield-wall/myprofile/discussions/723

[maxpowis]

Nice one thanks. I planned to turn mine into a yaml-based latex boilerplate. Would be nice to align it to a standard that it can be generated with different templates, including the myprofile project. Is that yaml aligned to or inspired by any sort of standard?

[eerison]

Hey @maxpowis I was already planning it hahaha

have different templates is quite nice, specially a simple one, like yours, it's really better for hr software read/extract information.

I had created an issue for this: https://github.com/shield-wall/myprofile/issues/741

if you check here: https://github.com/shield-wall/myprofile/tree/master/src/resumes, I already did the code thinking to implement multiple layouts, the idea is just add a new folder and implement the new template inside of there.

Note: I guess it can be improved, specially split somehow html from ts files, I was wondering how to use vuejs template, But I just want to use the template and not the whole framework :P, I don't know, it was just a thought.

[eerison]

Would be nice to align it to a standard that it can be generated with different templates, including the myprofile project

or do you mean, to use the myprofile template in this repo 🤔

[maxpowis]

I'd like to isolate the content of my resume to a yaml like you did in your implementation https://github.com/shield-wall/myprofile/discussions/new?category=resume and integrate it in my latex compiling process.

I already did start a similar implementation in another invoice generation project (still in progress, a bit on hold lately): https://github.com/maxpowx/invoice-boilerplate.

I think you have defined the structure of your yaml specifically for your implementation and I am wondering whether or not there exists some standard yaml structure for resume metadata. Anyhow, considering we would align on a shared yaml strcuture that would allow for reusing the same yaml for mytemplate and a updated version of my cv project converted to a boilerplate

[maxpowis]

Hereafter an example I just found of a yaml standard for resumes: https://yaml-resume.com/schema/

[eerison]

Is that yaml aligned to or inspired by any sort of standard

I just choose yaml template, because it's easier to parse to json, and it was inspired on https://github.com/salomonelli/best-resume-ever/blob/master/resume/data.yml

But I changed this in sections (SectionOne, SectionTwo), because I would like to reorder the block positions, like

sectionOne (it's the main content)

• content_1
• content_2

• content_3

  SectionTwo: (left column)

  • content_4
• content_5

• content_6

  this way I could move content like (certifications, experience and so on), between sections or remove, duplicate etc ...

  But I need to create a doc for this.

[eerison]

Hereafter an example I just found of a yaml standard for resumes: https://yaml-resume.com/schema/

But it's quite similar with mine. the difference that is inside of sections, for example, experiencies

    -   title: Experiences # you can choose the language for title, like (Experiences, Erfahrungen, Expériences ....)
        icon: work
        children:

            # >>>> here is the structure similiar from https://yaml-resume.com/schema/ <<<<<
            -   company: Company A
                position: Senior Software Engineer
                timePeriod:  Since jan 2023
                description: .
                photoUrl: https://user-images.githubusercontent.com/6358755/227289068-b6c3e1f3-1f63-47a0-a214-77b0297263dc.jpeg
                website: https://google.com

[maxpowis]

But I changed this in sections (SectionOne, SectionTwo), because I would like to reorder the block positions

I believe the yaml should not be about positionning but more explicit on which metadata fits into the sections. I.e. I mean "title: Experiences" should be converted to a 'experiences' structure and the template decides where the related data is positionned. Swapping columns in a tempalte left or right should be a parameter of the template (or a different template).

    -   title: Experiences # you can choose the language for title, like (Experiences, Erfahrungen, Expériences ....)

Also that would allow implementing internationalisation and adapt title dynamically based on some language file. I've implemented something similar in my invoicing project as found in here https://github.com/maxpowx/invoice-boilerplate/blob/master/internationalization.yml

[maxpowis]

have different templates is quite nice, specially a simple one, like yours, it's really better for hr software read/extract information.

Which hr software are you considering here? Those may have some interchange schema definition that you could base yourself upon.

Anyhow, I haven't looked much in term of industry standard but I wouldn't be surprise linkedin defined a format considering the number of integrations that already exist with several tools on the market to automatically fill in resume information during the application process. Could be worth having a look out there.

Thanks for the conversation anyway. Will follow-up more when I put more time into this project later!

[eerison]

I mean "title: Experiences" should be converted to a 'experiences' structure and the template decides where the related data is positionned.

I know what you mean, I already had this experience in the past, and I don't have flexibility into the template.

title: Experiences

It's a thing that I avoided, because I need to maintainer the languages.

what you mean I already had this experience :D : https://github.com/shield-wall/myprofile/blob/2.x/translations/messages.en.yml

and for this new version I don't want to go in this direction :)

[maxpowis]

Anyhow, I haven't looked much in term of industry standard

Couldn't stop looking :P. ChatGPT hinted me to look at https://jsonresume.org/schema/ as an industry standard. Probably the one I will adopt in a future release of this repo. ChatGPT claims they also provide a yaml specification but couldn't find one straight away. json->yaml conversion is simple though.

[maxpowis]

Btw, this could also be of interest for your project. https://jsonresume.org/themes/

[eerison]

Btw, this could also be of interest for your project. https://jsonresume.org/themes/

I saw this project, But not this theme section, maybe it could help somehow :)