• @TrickDacy@lemmy.world
    link
    fedilink
    English
    21 month ago

    I have enjoyed switching mine to HTML format which I then generate a PDF from. The only downside is that different browsers can render stuff slightly different, but that’s normally fixable with one line css change. And it’s not like I need to update my resume constantly on different machines.

    • @ulterno@lemmy.kde.social
      link
      fedilink
      English
      6
      edit-2
      1 month ago

      I was on Word, then LibreOffice Writer.
      Now thinking of making it a markdown source, with CSS styling to get an HTML based PDF. This way, the same source can be used on a webpage with different generation code.

      This seems to me, to be simpler than LATEX, but still good enough for a resume.

      • @justme@lemmy.dbzer0.com
        link
        fedilink
        English
        41 month ago

        There is a standard called json-resume with a lot of generators for html and pdf or react-resume which is more like a CMS (not entirely sure about spelling, to lazy to search for it now)

        • @ulterno@lemmy.kde.social
          link
          fedilink
          English
          1
          edit-2
          1 month ago

          kramdown and discount are 2 fun little tools.

          • kramdown is more fully featured and is a Ruby Gem.
          • discount is made in C and is more suitable if you are using it in an on-the-fly render process (∵ lesser CPU cycles), but it has lesser functionality features.