Yes, I did like this.
usersyle.css
/* For styling the rendered Markdown */
/* Render horizontal lines (made with \-\-\- or \*\*\*) as an actual line across the editor. */
.cm-hr {
border-top: 3px solid #777;
display: block;
line-height: 0px;
}
/*make markdown tokens for list into dots*/
.cm-overlay.cm-rm-list-token.cm-overlay.cm-rm-em-token
{
color: transparent !important;
background-color: #DECB6B!important;
height: 6px;
width: 6px;
border-radius: 50%;
display: inline-block;
vertical-align: bottom;
margin: 0 0px 8px 8px;
}
/*lists*/
.cm-variable-2, .cm-variable-3, .cm-keyword {
color: green !important;
}
.cm-rm-link {
text-decoration:underline
}
.cm-strong {
color:red!important;
font-weight: bolder!important;
}
/*strikethrough checked boxes*/
span.cm-rm-checkbox.cm-property + span.cm-rm-checkbox ~ span.cm-rm-checkbox {
text-decoration: line-through;
color:#5B5B5B!important;
}
/*HEADER STYLES*/
.cm-header-1{
color: #794BBB!important;
font-weight:bold;
}
.cm-header-2{
color: #BD93F9!important;
}
.cm-header-3, .cm-header-4, .cm-header-5, .cm-header-6 {
color:#CBBBE1!important;
font-style:italic;
}
.cm-header-1 {
/* line-height: 200% !important;*/
display: inline-block;
margin-top:.8em;
margin-bottom:.3em;
}
and userchrome.css
/* For styling the entire Joplin app (except the rendered Markdown, which is defined in `userstyle.css`) */
/* removes the WYSIWYG (MARKDOWN/RICH TEXT) button */
/* …old method (Joplin 3.0.z and older) */
/*div.editor-toolbar div button {
display: none !important;
}*/
/* …new method (Joplin 3.1.z and newer) */
div.editor-toolbar div button[title="Toggle editors"] {
display: none !important;
}