5 ms·
> 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 (t
by 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 agoRather 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 agoNoted. 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