Ever tried linting and using prettier with markdown? While working with a team some use atom, some vscode editor? Different linters apply different rules. Ended up having to avoid advanced markup features like lists within lists. Which is annoying when you are writing a readme step-by-step document and need a step 2.b) for example.
This article suggests using XML. XML is based on an older markup language called standard generalised markup language ‘SGML’. Why not go the whole hog and use that?
I found this great little markup language descended from SGML, that is specifically designed for documentation and is great for the use case in this article of blog posts. (The markup language has support for links and is designed to work on screens of any size, all of this was baked in to the language from the start, not bolted on to a scientific paper markup language like LaTex.)
It’s called hypertext markup language or ‘HTML’.
Also, your document can be styled using a styling language called cascading style sheets or ‘CSS’. [But this is optional]. And you can change the styling of your document years later without changing the text.
For blogging, there is also a popular graphic user interface to ‘HTML’ and ‘CSS’ called Wordpress.
In 2019 it powers 1/3 of the Internet.
from Hacker News - New Comments: "WordPress" http://bit.ly/2IXHE0H
via IFTTT
No comments:
Post a Comment