Let everyone wait! The new markdown feature has been released until today... But whatever the case, it was released!
After the first version of the markdown feature was released in March, many park friends reported that it was very bad. Based on the feedback, we found that it was not only bad, but also bad. As a result, I decided to re-develop the markdown function.
This time, we used pandoc, the most powerful markdown engine. However, being decisive is easy and difficult to do. The biggest challenge facing us is how to use C # To Call Haskell? In addition, it is even harder to understand Haskell. After more than a month of hard work, I solved this problem and took a lot of detours. For details, see the problem of calling Haskell in C #, which plagued many days.
This markdown function has the same effect as using the pandoc-F markdown_github command, and has the same effect as the online Conversion Tool (from GitHub to HTML) of pandoc. The effects of code coloring are similar to those of GitHub.
Preview The New markdown function:
- Markdown function test: C ++ code coloring
- Markdown function test: Bash code coloring
- Markdown test: JavaScript code coloring
- Markdown function test: Table
This release is a new start for garden's support for the mardown function. Although there are still many problems, it is more embarrassing than the previous complaints. Now we can solve them gradually.
Note:
- To use mardown, you must first change the default editor to markdown in the blog background.
- A blog post written with markdown before the new version of markdown function is released. If it does not take effect because of the cache, you only need to enter the editing page to save it.