Is the `Content` field other than text fields (such as introduction) supported to render Markdown?

As an AnQi CMS website operator, I fully understand the needs of content creators for content diversity and convenience.Markdown is a lightweight markup language that is widely popular for its simplicity and efficiency.Therefore, regarding the Anqi CMS inContentIs the text field outside the field supported to render Markdown (such as the introduction), which is a topic many users are concerned about.

In AnQi CMS, the core capability of Markdown rendering is mainly concentrated on the content body field.According to the official documentation I have reviewed, Anqi CMS indeed has built-in support for Markdown editors.In the system background, by enabling Markdown editor through "Content Settings" in "Global Settings".Once enabled,ContentThe field will support Markdown syntax during editing and will automatically convert it to HTML for display on the front end. This includes document content (archiveDetailofContentField), Category Content (categoryDetailofContentField), Single Page Content (pageDetailofContentField) and Tag Content (tagDetailofContentField). When calling the template tag, you can also specify throughrender=trueParameters explicitly indicate toContentField for converting Markdown to HTML.

However, forContentOther text fields outside the field, such as "Document Summary" (",DescriptionField),"Title" (Titlefield) "keyword" (Keywordsfield) as well as text type fields customized by users in the content model, the documentation does not mention that they support Markdown rendering functionality.These fields are usually designed to store plain text information, used to provide a brief summary, search engine optimization (SEO) metadata, or precise titles.

This means that if you are in the "document summary" or any other nonContentField input Markdown syntax, the system will not parse it and render it as HTML.On the contrary, these Markdown syntaxes may be treated as plain text and displayed directly, or in some cases, to ensure security or display consistency, the system may escape or filter them, thereby losing their expected formatting effects. For example,Descriptionfield is commonly used to generate the page's<meta name="description">Label content, this label is usually expected to be plain text description, not containing HTML tags.

In summary, the Markdown rendering capability of Anqi CMS is designed for the main content area, aiming to provide rich content display forms.The design concept for auxiliary text fields is to maintain plain text format to better serve their specific functions, such as SEO or concise information display.Therefore, it is recommended that you only use Markdown rendering in Anqi CMS if it is explicitly supportedContentFields use Markdown syntax, while other text fields use plain text.

Frequently Asked Questions

Ask: What will the front end display if I enter Markdown syntax in the 'Document Introduction' field? Answer: If you enter Markdown syntax in the "Document Summary" field, the front-end will usually display it as plain text and will not render it as HTML.This means the Markdown tag you entered (for example##/*/[]()Etc.) will be displayed as is, rather than converted to headings, lists, or links.

Ask: Does AnQi CMS support configuring or installing plugins for "Document Summary" and other non-ContentDoes the field enable Markdown rendering? Answer: According to the existing official documents, Anqi CMS does not provide background configuration or built-in plugins for "document introduction" and other nonContentThe field enables the Markdown rendering feature. The Markdown rendering capability is currently explicitly bound to the mainContentfield.

Why does AnQi CMS not provide Markdown rendering support for the 'Document Introduction' field? Answer: The 'document summary' field is typically used to provide a brief overview of the content or as search engine description information (meta description).Search engine optimization**Practical suggestions for meta description should be plain text, concise, and not contain HTML tags.Therefore, the system may limit it to plain text to ensure that its content remains consistent and effective across different platforms and scenarios.