Function Module

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

Functional Icon

Feature Introduction

When you don't want the content within the site to be moved to a full page, where does the interception occur, at the crawling layer or the display layer?

Both layers are in effect, with different scopes. The crawling layer is expressed by the Robots file, determining whether the crawling parties willing to comply with the rules can obtain the addresses; the anti-crawling interference code of the display layer acts on the batch collection that has reached the page, making the content moved out of the page lose its direct usable form. Robots is a de facto standard rather than a means of access control, whether it is observed depends on the other party, therefore, the collection that has already entered relies on interference code processing.

Anti-crawling Content protection
Eye 10

Functional Icon

Feature Introduction

Can the title, keywords, description, tags, and images be automatically generated together when posting an article?

Can. When creating an article, there are three automatic generation capabilities that can be used simultaneously: AI TDK generates titles, keywords, and descriptions, AI automatically generates article tags, and AI painting and automatic title matching is responsible for matching the images. Among them, automatic title matching is based on the content of the title to assign images. These capabilities are based on the AI writing provided since April 2023. The three results will fall into the corresponding fields, leaving room for manual review and rewriting, and not necessarily to accept them as they are.

AI creation Article posting process
👁️ 5

Functional Icon

Feature Introduction

When the form is repeatedly submitted by a robot, where should the verification step be added, and what kind of preliminary configuration is needed?

The human verification should be added at the step of submitting to the server for verification: the form fields themselves should not be changed, and the verification credentials obtained by the front-end should be submitted together with the request. The backend will check with the verification service whether to allow passage. The pre-configuration is to fill in the website key and communication key in the backend verification settings and turn on the switch. The verification will not take effect if either of the two credentials is missing. The verification blocks automated batch submissions, and the content risk after a successful submission still needs to rely on sensitive word filtering and content review processing.

Form security Anti-Spam
Eye 10

Functional Icon

Feature Introduction

What will happen if documents in the recycle bin are not cleared for a long time, and what should be confirmed before recovery?

Deleting formal documents is moving them to the recycle bin instead of a physical deletion, so the recycle bin will accumulate historical entries for a long time; irregular cleaning will bring problems such as accidental recovery and old drafts reappearing in lists and statistics. This article explains the visibility of formal documents, drafts, pending publication, and the recycle bin in four states, and provides the categories, aliases, and site ownership that must be confirmed before recovery.

Recycle Bin Content status
Eye 10

Functional Icon

Feature Introduction

When multiple sites share a single template, how to separately cover styles and configurations

Under multi-site management, the public template carries the structure and common components, the site-level carries color matching, navigation, and site information, and the order of coverage determines whether a change will affect other sites. This article provides the approach of layered principles, naming and coverage order, and how to first verify in low-risk sites when using AI to modify templates, and then check the homepage and list pages of each site one by one.

Multi-site Template development
👁️ 12

Functional Icon

Feature Introduction

The only thing that the site description file really enforces is one level one title, to what extent can the rest be saved?

llms.txt The mandatory parts in the proposal are only first-level headings, used to write the name of the project or site; abstract blocks, descriptive paragraphs, grouped links, and optional sections can be chosen as needed, while the file itself should remain small enough to fit into the context. This article divides the mandatory and optional sections of the original proposal, explaining what it manages with the site map, the crawl exclusion file, and what to pay attention to when automatically generated within the site.

GEO Large model crawl
👁️ 8

Functional Icon

Feature Introduction

Should the site description file for large models indicate the content validity, and how should it be coordinated with scheduled publishing?

Whether or not to mark the timeliness of content item by item in the site description file depends on whether it serves as navigation or conclusion. It is more like a directory for the model, where entries only need to clarify what is in this section and when it is worth taking. What really determines when content becomes visible to the outside world is the timing release and time factor within the site. This article introduces three ways to position timeliness information, as well as the refresh order between the description file and the timing release and site map.

GEO Content operation
👁️ 12

Functional Icon

Feature Introduction

How to design custom fields for the content model so that you don't have to change the table halfway through.

The design of the content model's custom fields is not appropriate, and the common consequence is that you have to change the table halfway. This article proposes a three-step method: first, list the answer fields that need to be referenced separately, then define the field type and whether it is required, and finally confirm whether these fields can be read by the batch import and public interface. And explain the three most common points that are most likely to require a redo - frequent changes in field names, embedding display logic in fields, and ignoring the readability of interfaces.

Content Management Modeling
👁️ 12

Functional Icon

Feature Introduction

Is preventing data collection interference and rejecting scraping two separate things, and where do they each stand?

Preventing scraping interference code and rejecting crawling are not the same thing; they block at different levels. Rejecting crawling acts on request admission: depends on protocol declaration and server frequency limiting to decide whether to allow crawling. Interference code acts on the content layer: making the copied text not directly available. This article clarifies the differences in the objects covered by both, the scenarios where they fail, and the configuration cooperation between robots, interference code, and content review within the site.

Content protection Safety
👁️ 8

Functional Icon

Feature Introduction

Multiple sites share a single backend, which configurations and data should be isolated between sites?

Multiple sites share a common backend, the natural isolation is content and classification, which must be manually confirmed are domain and redirection, template and site parameters, and interface and high-risk operation permissions. This article decomposes the isolation boundaries into four layers: content layer is divided by site database tables or classification dimensions, display layer is bound by domain template, redirection layer avoids cross-domain redirection to cover each other, and permission layer tightens the whole site operations to explicit enable, and provides a configuration checklist for multi-brand and multi-language site scenarios.

Multi-site Site isolation
Eye 10

Functional Icon

Feature Introduction

What content should be written in the site description document for large models, and what are the rigid requirements for the format?

Write the site description document for large models according to the llms.txt specification. The strict requirement for the format is only one: there must be a paragraph of a first-level title containing the project or site name, and the rest of the text paragraphs, lists, descriptions, and link sections are optional. This specification was proposed by Jeremy Howard and is still an open proposal for community feedback, not a formal standard. The site supports automatic generation of this document, and before going online, it is necessary to check the name section, key content list, and update time.

llms.txt Large model index
Eye 10

Functional Icon

Feature Introduction

Before modifying the template, consider leaving a rollback. Where should the template backup cover to?

A feasible method to leave rollback records before modifying the template is to do layered backups: template files, data, and static resources cover different recovery granularity. Anqi CMS supports backing up data along with static files, and since version 3.6.5, template backups have entered an independent background record. This article provides the three things that may be damaged by modifying the template, a layered table of backup objects, and the minimum rollback process before and after modification.

Backup Template development
👁️ 8