Feature preview
It is important to back up before opening the template editor, not after making changes. AnQiCMS's AI visual template editor can directly modify template code, and the larger the changes, the more necessary it is to have a rollback snapshot; the backup covers data and static files, starting from v3.6.5, it also expanded the template backup table, use it to store an original template first, then let the AI take over.
Where to place the backup when editing a template with AI assistance? The backup is before editing, specifically before opening the template file, not after the changes are made and before going online. The reason is that the scope of effect of template changes is determined by the reference relationship, and it may affect the list page, detail page, and navigation after the site-wide effect of a seemingly minor section of editing.
The changes in the template layer are divided into three categories, with increasing impact. The first category is the local style of a single page, which only affects this place; the second category is the common segment, such as list items, article cards, and sidebars, which will take effect on all pages that call it after one change; the third category is the site structure and navigation, with the widest range of impact, and it is more appropriate to use a site-wide replacement tool in this scenario - changing keywords or links goes through the data layer in bulk, without having to modify the template code.
It is very simple to determine which category you belong to: count how many positions this segment is referenced before making changes. Only the first category can be changed directly without any hesitation, while the latter two categories require a rollback method first.
AnQiCMS's backup and restore cover data and static files, templates are within the rollback range, and version 3.6.5 also expanded the table for template backup. These two facts determine the correct position of the backup: save a copy before the editing action occurs, recover directly if it is damaged; backup after finishing the edit, the saved one is the already damaged copy.
In order, divide it into three steps. First, trigger a backup and confirm that the backup file is generated and can be read elsewhere; then enter the edit mode; after making changes, only do local verification and do not rush to publish the entire site. If a rollback is needed, go through the recovery entry instead of manually pasting the code back, as manual pasting is prone to missing other modified segments at the same time.
The value of AI visual template editing is that you don't have to memorize the template syntax, you can modify the template code by describing the requirements. But because it directly modifies the code, the broader the instructions, the wider the changes. There are three actionable approaches: narrow down the target, clarify which part of the segment and which element is modified; propose only one change at a time, do not simultaneously adjust color, spacing, and copywriting in the same instruction; after making the changes, first diff to see the range, confirm that there are no连带 modifications before saving.
Involves keyword or link changes in the main text, prefer to use site-wide replacement instead of letting AI modify the template, the former acts on data, the impact is controllable, and the latter will mix the content layer with the display layer.
Do not rush to inspect the homepage. Choose the shortest path that references the modified segment: first open a single detail page to confirm that the segment is correct, then open a list page to confirm that there are no errors in multiple entries, and finally check the navigation and the site-wide entry. The purpose of this sequence is that if there is a problem with the segment itself, it can be found in the smallest range, rather than waiting until the entire site cache is refreshed to know.
After the template is modified, if the content layer text also needs to change, first confirm whether it is a display issue or a data issue, if it is a display issue, return to the template, and if it is a data issue, use the site-wide replacement tool to process.
Changes to common segments and site structure should be made every time; for single-page local styles, you can only save once before and after the change.
Use the restore entry to rollback to the template snapshot before editing, do not modify while trying, to avoid the second error overwriting the available version.
Copywriting and link batch changes belong to the data layer, using a full-site replacement; layout and element position belong to the display layer, only template changes.
Preview
Whether the abstract is exposed depends on which field is taken from the list page, not the visible range written on the title. AnQiCMS uses user management and VIP grouping to set access permissions for different user groups, and the permissions need to be received at three places: list data acquisition, detail page, and interface return. Hiding only the detail page means that the abstract is still exposed in the list, and the first few paragraphs of the text can still be read.
Preview
Whether the push needs to be rerun after the rescheduling depends on whether this document has appeared in a formal state before. If it is only a draft changed to a later time, the URL has not entered the site map and has not been actively pushed, there is no need to rerun; once the document has been launched or pushed, the rescheduling must be rescheduled according to the order of the site map and link push.
Preview
When multiple sites share a content model, how to prevent fields from interfering with each other? Limit the common aspects to the structure layer, and leave the differences in the value layer: the model and field names should be consistent across sites, default values and options should be configured separately for each site, and the keyword library should also be maintained separately for each site. Before making changes, confirm which templates and interfaces refer to the fields, and then verify the rendering results separately for each site to avoid affecting multiple brand pages at the same time.
