Can Markdown features be independently enabled or disabled for different types of documents (such as articles, products)?

As an experienced CMS website operation personnel, I am well aware of the importance of content creation and publishing efficiency, and understand how to meet various operational needs through refined functional control.About the independent control problem of Markdown function in APT CMS, I will elaborate in detail with the documents you provided.

In the AnQi CMS, the enablement and disablement of the Markdown function are mainly reflected at two levels: one is the global setting of the backend editor, and the other is the rendering control of the front-end template content.

Firstly, the Safe CMS provides global enable and disable options for the Markdown editor.According to the document instructions, the website administrator can select whether to enable Markdown editor in 'Security CMS background -> Global Settings -> Content Settings'.This setting is global, meaning that once enabled, all content types (such as articles, products, single pages, etc.) that use the default content editor will provide Markdown input support.If disabled, the content will be edited and stored through other rich text editors (usually WYSIWYG editors).This ensures consistency at the content input level, allowing all content creators on the entire site to follow unified editing standards.

However, enabling Markdown editor globally does not mean that all content must be rendered in Markdown format on the frontend.The design of Anqi CMS considers the flexibility of content display.Even if the background editor enables Markdown functionality uniformly, the final rendering method of the content can still be finely controlled through front-end template tags.Contentall fields support onerender参数。This parameter acceptstrueorfalsetwo values, explicitly indicating whether the template should convert Markdown to HTML when rendering content.

This means that even if your editor is writing content in Markdown format in the background, the front-end template can still decide whether this part of the content is output as raw Markdown text or converted to HTML first before displaying.This separation control mechanism brings great convenience to operation.render=trueMake sure the Markdown content is correctly parsed and rendered into rich HTML. For certain product introductions or brief single-page websites, you can omit the Markdown in the template even if the content was originally written in Markdown.render=true，或者明确设置render=falseLet it be displayed as plain text or after other processing to avoid unnecessary rendering costs or style conflicts.

Therefore, although the Markdown editor of Anke CMS is globally enabled, it can be disabled through the front-end template.render

---

Frequently Asked Questions (FAQ):

Q1: Can I enable Markdown editor for articles and disable it for products? A1:According to the existing security CMS document, the enable/disable of the Markdown editor is a global setting in the background, which takes effect at the same time for all document types that use the default content field (including articles and products).That is to say, you cannot directly enable the Markdown editor separately for "Articlesrender参数，independent control of different content types in Markdown content rendering behavior on the page.

Q2: If I enable the Markdown editor in the background but do not want a specific document content to be rendered as HTML, what should I do? A2:You can find the tag calling its content field (such asarchive.Content) in the front-end template used for the specific document.render=falseparameters. For example,{% archiveDetail archiveContent with name="Content" render=false %}{{archiveContent|safe}}，这样即使内容是Markdown编写的，也不会在前端被自动转换为HTML。

Q3: How to ensure that mathematical formulas and flowcharts are displayed normally when displaying Markdown content on the front-end page? A3:The Markdown editor of AnQi CMS supports inserting mathematical formulas and flowcharts, but the correct display of these elements on the front-end page requires the support of third-party plugins. You need to add the plugin to your website template'sbase.htmlIntroduce the corresponding CDN resources (such as MathJax and Mermaid libraries) in the documenthelp-markdown.mdAs described. This will ensure that these special elements can be recognized and correctly presented by the browser when the Markdown content is rendered as HTML.