# StrictMark: Markdown refactored **URL:** \ **Category:** Extensions\ **Created:** [January 29, 2021, 11:22am UTC](https://talk.commonmark.org/t/strictmark-markdown-refactored/3760 "2021-01-29T11:22:48Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![chrisalley](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/chrisalley/32/906_2.png) [@chrisalley](https://talk.commonmark.org/u/chrisalley)\ **Post date:** [February 5, 2021, 6:08am UTC](https://talk.commonmark.org/t/strictmark-markdown-refactored/3760/6 "2021-02-05T06:08:18Z")
Related discussion: > [@Style Guide for CommonMark](https://talk.commonmark.org/t/style-guide-for-commonmark/935/): > > I am developing a Markdown Style Guide at: [http://www.cirosantilli.com/markdown-style-guide](http://www.cirosantilli.com/markdown-style-guide) Comments and alternatives are very much appreciated. I started it before CommonMark was released, but I believe that it works well for CommonMark as well. I also recommend adding a style guide to the CommonMark project: I totally understand if you think this might be out of scope, but the bottom line is: if experienced users (read: CommonMark core devs, not me slight_smile ) don’t make those hard dec… You could set up your wiki to automatically clean up the Markdown with something like [Prettier](https://prettier.io/blog/2017/11/07/1.8.0.html) or a variation based on your StrictMark syntax. This would allow the inputted text to be compatible with non-strict Markdown, while still giving you a uniform version to save in the database. As @vas mentioned, one of the nice things about Markdown is that it’s forgiving for humans. --- _[View the full topic](https://talk.commonmark.org/t/strictmark-markdown-refactored/3760)._