Function Module

The core function module provided by AnQi CMS, helping you quickly build an enterprise website

Functional Icon

Feature Introduction

The function of automatically matching images for articles, what kind of content is not suitable for using it instead of manual selection

Automatic title image matching is suitable for large amounts of routine information with frequent updates, allocating images according to the title content can save repetitive actions; however, product detail images, illustrative diagrams that require factual accuracy, and charts with data still need to be manually selected. This article explains the sequence of image matching, AI automatic tagging, and TDK in the publishing process, as well as the explanatory text that needs to be added after the automatic image

AI capability Publishing process Automatic image matching
👁️ 6

Functional Icon

Feature Introduction

After distribution and order acceptance on the official website, which step is easy to be missed in financial reconciliation?

After distribution and order access to the official website, the most likely step that is easily missed in financial reconciliation is to align the change of distribution rules with the change of order status and leave a trace. This article sorts out the chain of WeChat public account connection, order, distribution, and finance, explaining why it is necessary to keep before-and-after snapshots of the rules and how the visibility of financial data is controlled according to user groups and VIP grouping.

Order Management Distributor management Financial reconciliation
👁️ 6

Functional Icon

Feature Introduction

When importing articles in bulk, should you use a compressed package or a table, and what scenarios are suitable for each format?

When importing articles in bulk, it is more suitable to use a compressed package for content with attachments and template resources, and using a table import for content with tidy fields is more convenient. AnQiCMS supports both ZIP compressed packages and Excel table batch import methods, and provides a dialectally consistent import interface for title duplicate checking. This article provides the adaptation scenarios, common failure points, and the order of using the recycle bin and backup as a fallback in case of import errors.

Site operations Content migration Batch import
👁️ 5

Functional Icon

Feature Introduction

Can editors post articles belonging to others, and should the role be divided in this way?

WordPress has six built-in default roles, among which editors can publish and manage content including others' articles, authors can only publish their own articles, contributors can write and manage their own articles but cannot publish, and subscribers can only manage their personal profiles. The control point behind this division is 'who can take effect externally.' Small teams can divide according to three questions: who can publish, who can modify others' drafts, and who can upload attachments. AnQiCMS covers the same needs with user group permissions, content review, and the status flow from drafts to the recycling bin.

Publishing process Permission management User Role
👁️ 4

Functional Icon

Feature Introduction

Add a hidden field and a layer of validation service to prevent spam comments enough

The hidden field blocks batch scripts that do not view the page, and the validation service blocks automated filling of forms. Together, the two layers still cannot prevent disguised promotional text from normal comments. It still needs content-side sensitive word filtering and manual review as a backup. This article gives the division of labor, the order of enabling the background, and the method of acceptance using the comment status.

Form protection Feature Introduction Comment anti-spamming
👁️ 3

Functional Icon

Feature Introduction

When filling in the main text in the background, I want to change the template easily. What method does not require writing code?

A small-scale title style, paragraph layout, and module sequence adjustment can be edited using an AI visualization template directly in the preview to complete the change intention, and then fall back to code confirmation; changes involving content model fields and page structure still need to return to field definition. This article explains the boundary and rollback methods of the two methods of change.

template editing Visualization Feature Introduction
👁️ 4

Functional Icon

Feature Introduction

What information can be placed in the custom fields of the content model, and how to use them on the list page

Custom fields are suitable for carrying structured, comparable, and filterable information, such as parameters, scope of application, time and contact information categories; long-form text, frequently changing marketing copy, and any certificate-type content are not suitable for putting into fields. There are usually two ways to use fields on the list page: directly outputting them by field name in the template, or participating as a filtering and sorting condition in the list generation, which has different requirements for field types

Content model Custom field list page
👁️ 4

Functional Icon

Feature Introduction

After batch link replacement, do we need to rebuild the static pages that have already been generated?

After replacing the link using the background full-site replacement, whether to rebuild the statically generated pages that have already been created depends on whether the site has enabled staticization. The replacement action falls on the data layer, the front-end address is determined by the pseudo-static rules and caching, and there is no need to rebuild for pure dynamic rendering. After staticization is enabled, it is necessary to rebuild during off-peak hours and perform sampling verification, and a 301 redirect should also be set up as a fallback.

SEO Content maintenance
👁️ 3

Functional Icon

Feature Introduction

Why can documents be recovered after being deleted, and how many states are there in total?

Documents can be recovered after being deleted because the deletion of formal documents is executed by moving them to the recycle bin instead of a physical deletion. The document status of AnQiCMS is divided into four types: formal documents, drafts, pending publication, and recycle bin, each corresponding to different visibility and flow paths. This article summarizes the conversion between the four states, the differences between draft previews and public releases, and the usage of scheduled release at a point in time.

Recycle Bin Document status
👁️ 7

Functional Icon

Feature Introduction

Will the anti-crawling interference code in the main text affect the search engine's understanding of the page?

The function of anti-crawling interference code is to increase the cost of the whole transfer, it inserts noise characters that do not produce semantic meaning for readers and layout, does not change the structure of the text and the page address, and therefore does not change the search engine's understanding of the page topic. This article explains the position of interference code insertion, the type of collection it can prevent and cannot prevent, and the way it coordinates with sensitive word filtering and content review level.

Anti-crawling Content protection
👁️ 4

Functional Icon

Feature Introduction

Which source is suitable for batch importing historical articles, compressed packages, and tables

When importing historical content in batches, archives with text and pictures are suitable for entering as compressed packages, and neatly formatted plain text content is suitable for entering as tables. The choice between the two entry methods depends on the proportion of resources and fields in the source. This article explains the fields that need to be checked before and after batch import, the arrangement of the status of importing drafts first and then publishing, and the method of rolling back after importing incorrectly, with the help of the recycle bin and interface query.

Content migration Batch import
👁️ 2

Functional Icon

Feature Introduction

Paid content is released according to membership groups, how should the permissions be layered

The permissions of paid content are layered according to user groups: first define the membership groups and corresponding content that can be viewed, and then entrust the payment relationship to order and financial management, avoiding using hidden links or drafts as permissions. The number of groups should be controlled between three to five levels, and the fewer the rules, the less likely there will be unauthorized access and cases of content not being released.

User group Member Permissions Content Monetization
👁️ 6