#jsonresume — Public Fediverse posts

Here is my work-in-progress FEP for using JSON Resume with ActivityPub:

FEP-6158: ActivityPub 'Resume' Object: JSON Resume expressed as JSON-LD

https://codeberg.org/reiver/fep/src/branch/fep-6158/fep/6158/fep-6158.md

I prefer to write for clarity, so it still needs work.

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD #JSONResume #fep6158 #fep_6158

Here is my work-in-progress FEP for using JSON Resume with ActivityPub:

FEP-6158: ActivityPub 'Resume' Object: JSON Resume expressed as JSON-LD

https://codeberg.org/reiver/fep/src/branch/fep-6158/fep/6158/fep-6158.md

I prefer to write for clarity, so it still needs work.

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD #JSONResume #fep6158 #fep_6158

I may have written a JSON-LD schema for JSON Resume.

It is defined in terms of ActivityPub.
For example:

'Resume' is a sub-type of an ActivityPub 'Object'. There are some new fields defined. Etc.

...

Now the question is — where do I put it?

Do I create a pull-request to the JSON Resume resume-schema repo?

Do I create a FEP?

Do I put it somewhere else?

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD #JSONresume

I may have written a JSON-LD schema for JSON Resume.

It is defined in terms of ActivityPub.
For example:

'Resume' is a sub-type of an ActivityPub 'Object'. There are some new fields defined. Etc.

...

Now the question is — where do I put it?

Do I create a pull-request to the JSON Resume resume-schema repo?

Do I create a FEP?

Do I put it somewhere else?

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD #JSONresume

My personal desire would be to create a format from scratch (because you are in control, you get something bespoke to your needs, and it is personally satisfying), but —

I think there is probably an advantage to using something (such as JSON resume) that already has wide adoption.

I guess that makes me inclined towards the latter.

...

So, if I go that way, I would have to decide: plain JSON or JSON-LD.

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD #JSONresume

My personal desire would be to create a format from scratch (because you are in control, you get something bespoke to your needs, and it is personally satisfying), but —

I think there is probably an advantage to using something (such as JSON resume) that already has wide adoption.

I guess that makes me inclined towards the latter.

...

So, if I go that way, I would have to decide: plain JSON or JSON-LD.

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD #JSONresume

RE: https://mastodon.social/@reiver/116597879302607072

More on a resume / CV on the Fediverse on Social Web.

Another option could be to use something like "JSON resume":

https://jsonresume.org/

https://github.com/jsonresume/resume-schema/blob/master/job-schema.json

It seems to be popular.

It isn't JSON-LD. Although I think it would be straightforward to translate it to JSON-LD, if that was desired.

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD #JSONresume

RE: https://mastodon.social/@reiver/116597879302607072

More on a resume / CV on the Fediverse on Social Web.

Another option could be to use something like "JSON resume":

https://jsonresume.org/

https://github.com/jsonresume/resume-schema/blob/master/job-schema.json

It seems to be popular.

It isn't JSON-LD. Although I think it would be straightforward to translate it to JSON-LD, if that was desired.

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD #JSONresume

found a #hugo mod that lets me use #jsonresume as a data source

so my resume section on my website is starting to look good

check it out y'all

https://tsbarnes.com/resume/

Add microdata to your resume to make it super SEO friendly!

How to use JSON Resume and Schema.org to make your resume a machine-readable data object all about YOU.

https://dev.to/scottnath/make-your-resume-seo-friendly-using-json-resume-with-microdata-1kln

#jsonresume #seo #microdata

Not me forking JsonResume to add a `pronouns` field they don't wanna add :blobfox3c:

https://github.com/AverageHelper/resume-schema

#resume #JsonSchema #JsonResume #git #fork #foss

Does it also drive you crazy that your #resume and your job applications are not connected by an open data format? Do you feel antsy combining formatting and content in the same artifacts just so you can apply for jobs? Does building a continuous integration pipeline powered by Nix for your resume seem like a delightful use of time?

Have I got a fun project for you, featuring #Zola, #Nix, #JSONResume, and #Weasyprint.

https://ktema.org/articles/the-overengineered-resume/

53 promising themes have been reduced to the following 10:

```
@anthonyjdella/jsonresume-theme-anthonyjdella-kards
jsonresume-theme-edify
jsonresume-theme-github
jsonresume-theme-gnap
jsonresume-theme-hydejack
jsonresume-theme-kards
jsonresume-theme-noah
jsonresume-theme-onepageresume
jsonresume-theme-orbit
jsonresume-theme-papirus
```

#jsonresume #json #resume #cv #npm #theme #themes #nodejs #html

53 promising themes have been reduced to the following 10:

```
@anthonyjdella/jsonresume-theme-anthonyjdella-kards
jsonresume-theme-edify
jsonresume-theme-github
jsonresume-theme-gnap
jsonresume-theme-hydejack
jsonresume-theme-kards
jsonresume-theme-noah
jsonresume-theme-onepageresume
jsonresume-theme-orbit
jsonresume-theme-papirus
```

#jsonresume #json #resume #cv #npm #theme #themes #nodejs #html

After concocting the following little Bash script, I was able to successfully convert my JSON Resume to HTML with 298 different themes:

https://gist.github.com/asbjornu/7873be2713fcacc911be2035a482091d#file-convert-sh

Quite a few of the themes failed on installation, for various reasons. Many more failed before I wrote the script where only one theme is installed at once.

After reviewing the 298 converted resumes, I'm down to 53 themes that I feel are worth tinkering with:

https://gist.github.com/asbjornu/7873be2713fcacc911be2035a482091d#file-jsonresume-themes-best-txt

It's going to be fun reducing these from 53 to 1 and tweak it to my preference.

#resume #json #jsonresume #cv #themes #npm #nodejs #html

After concocting the following little Bash script, I was able to successfully convert my JSON Resume to HTML with 298 different themes:

https://gist.github.com/asbjornu/7873be2713fcacc911be2035a482091d#file-convert-sh

Quite a few of the themes failed on installation, for various reasons. Many more failed before I wrote the script where only one theme is installed at once.

After reviewing the 298 converted resumes, I'm down to 53 themes that I feel are worth tinkering with:

https://gist.github.com/asbjornu/7873be2713fcacc911be2035a482091d#file-jsonresume-themes-best-txt

It's going to be fun reducing these from 53 to 1 and tweak it to my preference.

#resume #json #jsonresume #cv #themes #npm #nodejs #html

My website is now entirely built with #Zola using #Nix including my resume which is created from a #Dhall configuration extending the #JSONResume schema !
Feel free to review my Nix files 🥰 https://github.com/gaelreyrol/dhall-resume/blob/main/flake.nix https://github.com/gaelreyrol/gaelreyrol.dev/blob/main/flake.nix