Describe the bug
Most/all liquid tags render through markdown parser in the same preparation step articles/comments go through before saving and rendering. Content such as some code, HTML, etc. gets removed in the process, and methods are created to circumvent the parsing (typically using Regex). By using views to render liquid tags, we would not need such methods and methods that help with security can be imported and handled within the xyz_tag.rb.

Expected behavior
Changing how liquid tags render -- from going through markdown parser and the same process as how an article/comment is rendered to separately rendering on html.erb view. There are a few open liquid tag related issues that will and may be solved by this refactor.

Liquid Tag Tracker

• dev.to Comment devcomment liquid tag render utilize html.erb #2554 merged
• dev.to Article/Post dev link liquid tag render utilize html.erb #2619 merged
• dev.to User dev user liquid tag render utilize html.erb #2621
• dev.to Tag dev tag liquid tag render utilize html.erb #2641 merged
• StackBlitz Change StackBlitz to utilize ActionController #2664 merged
• dev.to Podcast dev podcast liquid tag render to html erb #2644
• Twitter Change Twitter liquid tag to utilize ActionController #2721
• Runkit Change Runkit liquid tag to utilize ActionController #2723
• Youtube and Vimeo Youtube/Vimeo liquid tag render to utilize ActionController #2728
• Repl.it
• JS Fiddle
• Codesandbox
• Codepen
• Instagram
• Speakerdeck
• Soundcloud
• Spotify
• Blogcast