3 ms·

Hmm, well, noted :) If you could point out some specific elements in the rendered version though, like "not enough spacing" or "that h3 should be an h2", that'd

Hmm, well, noted :) If you could point out some specific elements in the rendered version though, like "not enough spacing" or "that h3 should be an h2", that'd be extremely helpful!

mrweasel 11y ago
It's not really that simple. I'm not trying to be dick about, because I do think that resumes from markdown is a good idea. The grey borders/lines, they need to go. They serve no purpose. Contact information goes on top, not buried under the profile. Technologies, can go after the "job description". It makes sense to list them in relation to the jobs though. Know one cares how many time your project was stars or forks your project has. If that was relevant they would have contacted you :) Just link to your GitHub/Bitbucket/whatever- page. Writing and favourites can go, unless you a famous blogger, but then I would just list it as a job. The entire resume takes up to much space. It's country specific, I know, but I think it needs to fit on one A4 page. Personally, I just don't like the layout, sorry.
- awalGarg 11y ago
  > The grey borders/lines, they need to go. They serve no purpose. Completely agree. While I think it is fair to put a bit of blame of Github's bad rendering (the same markdown looks much better in stackedit's rendering, for instance [1]), but I'd still see how can I preserve the grouping without blockquoting things. I can see the reasoning for rest of the points as well, but to each his own :) [1]: https://stackedit.io/viewer#!url=https://gist.githubusercontent.com/awalGarg/a8e97b27b249f2c94f8e/raw/09e63fd69f2288cd631a492d392e8d114af7a432/res.md https://stackedit.io/viewer#!url=https://gist.githubusercont...
  - laurent123456 11y ago
    Rather than creating the markdown for a specific renderer, I think you should focus on creating markdown that can be easily read and edited - so no "######" headings, no quoted text or horizontal lines, basically no clutter. Then how it appears in HTML can be tweaked by the renderer and via CSS. Also I assume clean markdown would generally look better in most renderers.
  - mrweasel 11y ago
    >the same markdown looks much better in stackedit's rendering Link to that one as the example then ;) I think it's down to different markets wanting different things. A cool project, but maybe not so useful, would be a resume generator that from one data source (in Markdown perhaps) could generate resumes in the "correct" form for Europe, India, the US and so on.
    - awalGarg 11y ago
      Noted. I have added links to various rendered forms in the readme: https://github.com/awalGarg/cv-maker#example https://github.com/awalGarg/cv-maker#example
- rifung 11y ago
  > Know one cares how many time your project was stars or forks your project has. If that was relevant they would have contacted you :) Just link to your GitHub/Bitbucket/whatever- page. I assume you mean "no" instead of "know". But more on point, are you sure this is true? I have heard many companies (Google is one) look highly on projects you made which are very popular.

Hmm, well, noted :) If you could point out some specific elements in the rendered version though, like "not enough spacing" or "that h3 should be an h2", that'd be extremely helpful!

mrweasel 11y ago

It's not really that simple. I'm not trying to be dick about, because I do think that resumes from markdown is a good idea. The grey borders/lines, they need to go. They serve no purpose. Contact information goes on top, not buried under the profile. Technologies, can go after the "job description". It makes sense to list them in relation to the jobs though. Know one cares how many time your project was stars or forks your project has. If that was relevant they would have contacted you :) Just link to your GitHub/Bitbucket/whatever- page. Writing and favourites can go, unless you a famous blogger, but then I would just list it as a job. The entire resume takes up to much space. It's country specific, I know, but I think it needs to fit on one A4 page. Personally, I just don't like the layout, sorry.

awalGarg 11y ago
> The grey borders/lines, they need to go. They serve no purpose. Completely agree. While I think it is fair to put a bit of blame of Github's bad rendering (the same markdown looks much better in stackedit's rendering, for instance [1]), but I'd still see how can I preserve the grouping without blockquoting things. I can see the reasoning for rest of the points as well, but to each his own :) [1]: https://stackedit.io/viewer#!url=https://gist.githubusercontent.com/awalGarg/a8e97b27b249f2c94f8e/raw/09e63fd69f2288cd631a492d392e8d114af7a432/res.md https://stackedit.io/viewer#!url=https://gist.githubusercont...
- laurent123456 11y ago
  Rather than creating the markdown for a specific renderer, I think you should focus on creating markdown that can be easily read and edited - so no "######" headings, no quoted text or horizontal lines, basically no clutter. Then how it appears in HTML can be tweaked by the renderer and via CSS. Also I assume clean markdown would generally look better in most renderers.
- mrweasel 11y ago
  >the same markdown looks much better in stackedit's rendering Link to that one as the example then ;) I think it's down to different markets wanting different things. A cool project, but maybe not so useful, would be a resume generator that from one data source (in Markdown perhaps) could generate resumes in the "correct" form for Europe, India, the US and so on.
  - awalGarg 11y ago
    Noted. I have added links to various rendered forms in the readme: https://github.com/awalGarg/cv-maker#example https://github.com/awalGarg/cv-maker#example
rifung 11y ago
> Know one cares how many time your project was stars or forks your project has. If that was relevant they would have contacted you :) Just link to your GitHub/Bitbucket/whatever- page. I assume you mean "no" instead of "know". But more on point, are you sure this is true? I have heard many companies (Google is one) look highly on projects you made which are very popular.