Marked 2 detects changes and updates faster than ever. Marked has both pre-processor and processor options. In the remaining 10%, you can use other processors or custom scripts to get exactly the results you need. It normalizes most syntax differences, so even if you usually work in other formats, Marked works out of the box in 90% of use cases. It has the latest version of MultiMarkdown built in, with the option to render using Discount.
Whether you’re blogging, authoring a book, writing a report or editing a GitHub README file, Marked has you covered. With intelligent writing features, flexible options and a wide range of support for various markup formats, editing tools and publishing platforms, Marked is a smart addition to any writer’s arsenal. I will continue to improve it in the future.Marked 2 is the result of hundreds of hours of working to bring you the ultimate writing tool. You can see there are still issues, some of them require additional implementation at this side, and others are caused by bugs in MacDown and Hoedown. I’ve attached MacDown’s help.md file as a post so that you can get an idea how compatible this thing is currently. I am fairly satisfied with the current result, and might talk more about it in detail in the future, given the time. I also decided to build the functionality myself instead of using an existing service/library, hoping to provide some ideas if somebody wish to make his/her own blogging/CMS platform compatible with MacDown. This way I can talk about topics on MacDown and Markdown-related things in general, in English, at a dedicated space. So, I decided that MacDown should have a blog. I haven’t tried many other online services, but as far as I know there’s nothing that fits the asker’s requirement (which is not saying those platforms are bad-they are just incompatible).
While the configuration does somehow resemble MacDown’s, they are still different, and at times incompatible with each other. I host my own personal site/blog, and it uses a custom renderer to process Markdown. One particular instance is when I got asked whether I can recommend a blogging platform that supports extensions MacDown has. Some of them have been added as FAQ, but there are more that don’t fit, and they need a good place to the public. For those I can answer (not a lot, really), many are common enough that I got asked multiple times. But I am by no means an expert on Markdown, let alone many other topics people ask me about, and I’m sorry I can’t answer many of your questions. I love them, and have tried (and will continue to try) answering them the best I could. I have also received a lot of emails/tweets/DMs recently for MacDown. So I figured that it’d be better to find somewhere else in the future. And the post doesn’t really fit well with other posts there either, as my personal blog targets more toward Chinese audience. But it seems a bit queer, to say at least, to use my personal blog for that purpose. Back when I released MacDown 0.2 I felt that we have too much to fit inside the release note, so I wrote a blog post for it.
0 kommentar(er)
