I would call markdown an “85% solution”. Not disparaging it at all by calling it that either.
The ease of use it brings is incredibly valuable and, if it gets you rapidly through 85% of what you need done (and leaves you in a good spot to take on the remaining 15%) then it’s the right tool to have used in that moment.
Off the shelf seasoning mixes are another great example. 85% of the solution (a tasty meal) in a bottle that leaves you to focus on the remaining 15% (cooking the rest of the meal)
Markdown was the inspiration: easy to scan, consistent, doesn't support fluff, etc. Trying to avoid many of the typical SaaS site tropes that get in the way.
Oh, my bad, thought you meant it was built in markdown, like MDX or something.
I wish you could do all this in plain markdown; putting things side-by-side in a github readme can be tricky. Have to resort to sub/superscript hacks just to make image captions.
I would call markdown an “85% solution”. Not disparaging it at all by calling it that either.
The ease of use it brings is incredibly valuable and, if it gets you rapidly through 85% of what you need done (and leaves you in a good spot to take on the remaining 15%) then it’s the right tool to have used in that moment.
Off the shelf seasoning mixes are another great example. 85% of the solution (a tasty meal) in a bottle that leaves you to focus on the remaining 15% (cooking the rest of the meal)
Can you link the repo so we can see? This link doesn't really appear to have anything to do with markdown.
Markdown was the inspiration: easy to scan, consistent, doesn't support fluff, etc. Trying to avoid many of the typical SaaS site tropes that get in the way.
Oh, my bad, thought you meant it was built in markdown, like MDX or something.
I wish you could do all this in plain markdown; putting things side-by-side in a github readme can be tricky. Have to resort to sub/superscript hacks just to make image captions.
Anyway, looks nice.