Markdown is (subjectively) ugly

compare srht vs gist

  • code block after "Word Header" gets .trim()ed or something?
  • tables should have either spacing or lines
  • headings need a bit more space
Assigned to
1 year, 3 months ago
11 months ago
No labels applied.

~sotirisp 1 year, 2 months ago

I especially agree on the heading part. More space before headers would make sections much easier to distinguish.

Some way to differentiate code blocks from normal text, such as the background color used in Github, would also be nice.

~dkellner 1 year, 1 month ago

+1. Additionally, heading levels 2 and 3 look too similar in my opinion.

~noepoch 11 months ago

I appreciate the minimalism, but completely agree. Margins and some way to distinguish between code blocks and prose would be great for accessibility.

Something similar to the .event class already used throughout would maybe work to keep things stylistically cohesive.

~noepoch 11 months ago

I just noticed, the markdown is rendered differently between sr.ht's project summary0 and git.sr.ht1 using the same md file. I'm not sure why this would be intentional, but the margins and code blocks are much better in the project summary.

Register here or Log in to comment, or comment via email.