I really want to say something about this change from a view of a user of Joplin. This is an opinion from a user talking about the change of color style in the recent update.
The change to this making the Markdown text more like text instead of code to match its generated HTML views. It is also a good idea to let the newbie playing Joplin have a more consistent typing. It is a great thing to keep the concept of WYSIWYG that users know they are typing the right thing. But Joplin is already implemented Rich Text editor to handle the real WYSIWYG experience, for those users who may not like Markdown.
In real usage Markdown can handle a wide variety of types of things not only articles: Code blocks, tables, lists, and linked text, there are writing rules for those non-article texts to be used and we have to identify their difference not only when we reading from the view, and also when we need to change something from the editor that we need to find out where the text located.
It is not a suggestion just an opinion, MARKDOWN IS CODE because there is syntax there are rules, maybe the rules are not that strict as other real programming codes. But that makes us use Markdown for even more complex circumstances, not even jotting simple notes with a list of some links from a tutor or writing articles with multiple paragraphs in long sentences for wikis. If you try to handle a lot of data and try using those rules to keep the view simple, the color scheme from the old style in the editor is really a matter and the color difference and big contrast are helping us to deal finding my list, finding the level of the nested list and finding my link, my code, and my article.
Maybe there is a lot of suggestion about this, such as add an option to toggle the color scheme or add another select box for color scheme other than the whole app's style, but there should be a lot of codes to add and telling users to modify their
userchrome.css will be the fastest way and using the least effort. But for now, we need to write our own color scheme in CSS or copy those from a page in the forum that linked from another page talking about the code color in the update, which is linked from a reply in a pull request on GitHub, that is linked from the changelog on GitHub, that it is located at the page 4 in the releases. This is also not a good experience for the old users who want to find something to stay thing unchanged. And the pull request is locked down that I cannot reply which I need to sign up on the forum to say my thought.
Notes: I cannot include links so I removed links from the last paragraph, talking how I find the page of customizable CSS.