Joplin Specific: Joplin's in-app CSS file is ~/.config/joplin-desktop/userstyle.css
max-width: 38rem; padding: 2rem; margin: auto; }
max-width: 38rem;
padding: 2rem;
margin: auto;
}
<style>main{margin:40px auto;padding:0
10px;max-width:60em;line-height:1.25;font-size:12pt}h1{line-height:1}footer hr{border-top:1px solid
#ccc}footer p{font-size:8pt;color:#777}footer p a{color:#66a}</style>
main{ margin:40px auto; padding:0 10px; max-width:60em; line-height:1.25; font-size:12pt } h1{line-height:1} footer hr{border-top:1px solid #ccc} footer p{font-size:8pt;color:#777} footer p a{color:#66a}
main{
margin:40px auto;
padding:0 10px;
max-width:60em;
line-height:1.25;
font-size:12pt
}
h1{line-height:1}
footer hr{border-top:1px solid #ccc}
footer p{font-size:8pt;color:#777}
footer p a{color:#66a}
Summarized from here.
<pre> - puts text in monospace and respects linebreaks
<code> - not sure what what this is for, but best practice seems to be <pre><code> ...code.. </pre></code>
<kbd> - for demarking keyboard input. Just puts text in monospace
<samp> - for demarking sample program output. Again, just puts text in monospace
Minimal HTML Tips - cool stuff about what you can actually do in practice, and an explanation of the mobile viewport thing