Does AnQiCMS support setting different comment forms for different pages or content models?

As an experienced website operations expert, I fully understand your emphasis on website interactivity and personalized experience.The comment form serves as an important bridge for users to communicate with the website, and its flexibility and specificity indeed greatly enhance user experience and data collection efficiency.About whether AnQiCMS supports setting different comment forms for different pages or content models?AnQiCMS through its powerful template engine and flexible content model mechanism, fully supports you in implementing differentiated comment forms for different pages or content models, although the implementation strategy may differ from what you imagine, defining a set of forms directly for each model.

Let's delve into how AnQiCMS achieves this goal.

The core of AnQiCMS's comment form mechanism: unified configuration and flexible rendering

AnQiCMS handles the form comments efficiently and flexibly. As can be seen from the provided documents, in AnQiCMSv2.0.0-alpha3The custom message field support has been added in the version, which lays a foundation for the personalization of the message form.

In particular, AnQiCMS provides a unified form configuration entry for comments.This means you can define all the message fields you might use in the background management system at once, such as "Name", "Email", "Phone", "Company Name", "Product Model", "Consultation Type", "Message Content", and so on.These fields have different types (such as text, number, multi-line text, radio, checkbox, dropdown selection), and can be set to be required and have default values.

In the front-end template, you can use{% guestbook fields %}This label, unifiedly gets all these留言 fields configured from the background. Here, thefieldsThe variable is an array object that includes detailed information about each field, such as the field name, variable name, type, whether it is required, and possible options.

However, simply unifying configuration fields is not enough to meet the need for setting different forms for different pages.The strength of AnQiCMS lies in its delegation of this differentiated logic to a flexible template engine.

Strategy one: Using intelligent condition rendering at the template level

AnQiCMS' template design is one of its core strengths.The document clearly mentions that it supports custom content models, separate document templates, category templates, and single-page templates.This means you can assign completely different template files to different parts of the website (such as product detail pages, article detail pages, about us pages, etc.).

The flexibility of this template is the key to realizing the differentiation of comment forms. When you call this template in a page template file,{% guestbook fields %}After obtaining all the fields configured in the background comments, you do not need to render them all. Instead, you can combine the context information of the current page (such as the content model ID, category ID, or single page ID) and use conditional judgments in the template ({% if %}Label) to determine which fields should be displayed and which should be hidden.

For example, you can design it like this in the product detail page template:

<form method="post" action="/guestbook.html">
    <h3>产品咨询表单</h3>
    {% guestbook allFields %}
        {% for item in allFields %}
            {% if item.FieldName == "姓名" or item.FieldName == "联系电话" or item.FieldName == "产品型号" or item.FieldName == "咨询内容" %}
                <div>
                    <label>{{item.Name}}：</label>
                    {# 根据item.Type渲染不同类型的输入框 #}
                    {% if item.Type == "text" or item.Type == "number" %}
                        <input type="{{item.Type}}" name="{{item.FieldName}}" {% if item.Required %}required{% endif %} placeholder="{{item.Content}}">
                    {% elif item.Type == "textarea" %}
                        <textarea name="{{item.FieldName}}" {% if item.Required %}required{% endif %} placeholder="{{item.Content}}"></textarea>
                    {# 更多类型判断... #}
                    {% endif %}
                </div>
            {% endif %}
        {% endfor %}
    {% endguestbook %}
    <button type="submit">提交咨询</button>
</form>

And the same background configuration of the message field, in the article detail page template, may only render "Name", "Email", and "Message Content":

<form method="post" action="/guestbook.html">
    <h3>文章评论或反馈</h3>
    {% guestbook allFields %}
        {% for item in allFields %}
            {% if item.FieldName == "姓名" or item.FieldName == "邮箱" or item.FieldName == "留言内容" %}
                <div>
                    <label>{{item.Name}}：</label>
                    {# 同样根据item.Type渲染输入框 #}
                    {% if item.Type == "text" %}
                        <input type="{{item.Type}}" name="{{item.FieldName}}" {% if item.Required %}required{% endif %} placeholder="{{item.Content}}">
                    {% elif item.FieldName == "邮箱" %} {# 特殊处理邮箱字段，可能需要特定的HTML5 input type #}
                        <input type="email" name="{{item.FieldName}}" {% if item.Required %}required{% endif %} placeholder="请输入您的邮箱">
                    {% elif item.Type == "textarea" %}
                        <textarea name="{{item.FieldName}}" {% if item.Required %}required{% endif %} placeholder="{{item.Content}}"></textarea>
                    {% endif %}
                </div>
            {% endif %}
        {% endfor %}
    {% endguestbook %}
    <button type="submit">提交反馈</button>
</form>

Through this method, you