The core function module provided by AnQi CMS, helping you quickly build an enterprise website
Functional Icon
When managing multiple brand websites with a single backend, the boundaries of shared and independent layers are divided into three: the operation layer (deployment instances, listening ports, cache) is usually shared, the structure layer (content model, classification, template) is configured independently per site, and the data layer (documents, attachments, users and permissions) is isolated according to the site's ownership. Shared instances do not mean shared data; to determine whether to split the site or use the content model, consider whether the brand differences affect the structure and data layers.
Functional Icon
How often does the background login status expire, essentially weighing two directions: the longer the session, the smoother the operation, but the longer the window of opportunity for stolen credentials to be used. The signature token itself has an expiration semantics, combined with the interface exposure range set according to the intent domain and round-level operation confirmation, can bring the risk of long sessions back to an acceptable range. In a high-risk repair, it is necessary to rotate the server signature key and change the administrator's password at the same time, changing only one item is equivalent to leaving half a door open.
Functional Icon
Will the link of a draft or pending publication content with preview parameters be caught by a spider, depending on three things: whether the address can be guessed, whether the crawling rules cover it, and whether the server checks the status when reading the details. The crawling exclusion rules are just suggestions and cannot block the addresses that have already been shared; the real closure should be based on the status check and the preview parameters only taking effect in authorized sessions. After making changes, use the search engine site information to check for missing pages.
Functional Icon
Using AI to modify templates, changes need to be rolled back to the site template file and verified immediately to take effect. There are four types of demand sources within the site: visual template editing, skills, AI Chat, and external clients connected through MCP. The common steps are to describe the requirements, generate or modify code, check the disk, and then verify the homepage and list page; the skill layer covers two types of tasks: template development and API development.
Functional Icon
This kind of full-site operation interface for backup and upgrade is not opened by default, and it receives the risk of 'affecting the entire site once called.' The default is not to close a certain function, but the level of full-site actions, which needs to be explicitly opened. The internal tool side is converged according to the directory of intent, write operations are merged and confirmed in one round, the high-risk areas are closed by default and opened as needed, and the call surface is minimized.
Functional Icon
The landing page should use a single page or a custom content model, depending on three boundaries: whether similar pages will be generated repeatedly, whether filtering by fields is needed, and whether it needs to be integrated into navigation or reused across multiple sites. For one-time event pages, single-page management is sufficient; for batch production and structured field-organized scheme pages and list pages, hand them over to the custom content model and its custom fields, with each type handling its own segment.
Functional Icon
Content review is stuck in the state transition - judgment by humans before the draft turns into a formal document; sensitive word filtering and keyword replacement act on the content itself, which is unrelated to whether the human passes. Only when both are separated will there be no omissions: if the content imported or collected in bulk is directly turned into a formal document, the step of human review is skipped. The reasonable approach is to automatically process expressions, manually control the transition, and use the pending release status to accommodate scheduling.
Functional Icon
Content station member tiering and online order acceptance, the background needs to be equipped with four native capabilities: user groups and VIP grouping determine who can see what and according to which grade to complete transactions; order management leaves a record of completed transactions; financial management is responsible for accounting; distribution and WeChat official account integration answers where the transaction comes from. The implementation should first set visibility, then proceed with transactions, and finally trace the source. Reversing the order will lead to manual maintenance of permissions for a long time.
Functional Icon
Watermarks and anti-capture interference codes cannot replace access control; their role is to increase the cost of transfer and leave evidence of ownership. Image watermarks solve the problem of 'who owns this picture', and text interference codes solve the problem of 'can the source be restored after the text is moved away'. Both should be placed in a position that does not affect the normal reading of the reader. The real order to reduce the loss of transfer is: first, make the source identifiable, then make bulk extraction expensive, and finally, it is the arrangement of the release rhythm.
Functional Icon
When updating the website and notifying subscribers, email subscription and email reminder are two different capabilities: email subscription is aimed at readers, consisting of a front-end entry, confirmation action, and unsubscribe processing; email reminder is aimed at in-site managers, responsible for internal notifications such as publishing exceptions, navigation, and inspection of friend links. The list affiliation, sending time, and maintenance responsibilities of both should be separately configured, and mixing them on a single list is the most common operational incident.
Functional Icon
When importing articles in bulk, whether the images can be included depends on which path is taken: compressed package import can package the resource directory and text together, table import only carries text, and attachment upload on the interface side is submitted as base64, suitable for small files to be completed within a single request. The applicable quantities and points of the three paths are different, and the most likely to cause problems when mixed is when the image address in the text points to a location that has not yet fallen into the media library.
Functional Icon
When letting AI perform batch background operations through an interface, the confirmation step should be placed before execution and merged by rounds: read operations should return directly, and write operations should be summarized into one confirmation within the same round before being implemented. Round-level approval refers to this level, not individual pop-up confirmations.
