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

When it comes to changing the title style or layout, there are indeed ways to modify it without writing template code: use visual template editing, describe the modification intention directly in the preview backend, and let AI assist in generating the modification on the template side, and then have a person confirm the result on the code. This approach is suitable for minor modifications on the presentation layer; once the modification involves the field itself - adding a new field, changing the structure of the content model, or sorting the list by a new dimension - it still needs to return to the content model and custom field definition, and the visual tool cannot replace this step.

What modifications are suitable to be made in the visual editor?

Changes that can be made in the visual editor are those that are 'visible results': title hierarchy and font size, spacing between text paragraphs and images, the sequence of modules on the page, button and label text styles. The common point of these changes is that the range of changes can be compared at a glance in the preview, without inference.

Changes that are not suitable also have common characteristics: they change the way data is organized rather than the way it is displayed. For example, adding a 'suitable scenario' field to an article or adding an additional filtering condition to a category list page. This type of requirement needs to define fields in the custom content model first, so that the visual editor can read it.

How to confirm after modification falls on the code

The output of visual editing is still template code, so the confirmation action should be done according to the code: first, check if the changes only fall within the expected template files, then see if the style has been written into the structure layer that should not be moved, and finally use another category or another article to verify that the change is reusable rather than a one-time patch.

The meaning of this step is to avoid the situation where 'the preview looks good, but the online version is not'. AnQiCMS's AI visual template editing supports direct modification of template code with AI assistance,配合内置的 AI Chat 与覆盖模板开发方向的 AI 技能，and the modification process can be reviewed at the code level, rather than just leaving a modified effect image.

Which modifications need to be returned to the field definition

Three types of changes must be returned to the field and model layer. The first type is the addition or adjustment of fields, which belongs to the category of custom content models; the second type is to involve fields in sorting, filtering, or aggregation, involving query structure; the third type is to reuse the same set of changes across sites, involving the corresponding relationship between templates and configurations across multiple sites.

By distinguishing these three types, we can avoid a common rework: simulating something that should be a field in the template with hard-coded methods, which may work in the short term, but will have to be rewritten when it comes time to filter by it.

How to roll back if it is broken

Keep a recoverable backup before modifying the template, this order is not exempt even if the change is small. Backup and recovery are a set of capabilities that cover data and static files, allowing for a complete rollback to the previous state in case of issues with template modifications; 'Snapshot before change + Clear change range' is more time-saving than rollback, and both are needed for a distinguishable rollback.

In practice, it is advisable to follow three fixed steps: first, make a backup, then only modify one template file and immediately compare it in the preview, and finally, expand the range of changes after confirming that everything is correct. This rhythm should be followed especially when adjusting batch styles, as the cost of locating issues will increase exponentially when changing multiple template files at once.

Common questions

Will the visual editing mess up the template structure?

There is this risk, which is why we need to confirm the rollback of code. The criteria are whether the changes only appear in the expected template files and within the expected selector range. If the structural layer is rewritten, it is better to roll back to the backup and start over.

Can I use it if I don't know how to write code?

Small style changes can be used because the intention of the changes can be described in natural language, and the results can be compared in the preview. However, for field and structural requirements, it is necessary to understand the definition method of the content model first, otherwise, the effects produced cannot be reused.

Which should be done first, changing styles or fields?

First do the fields. Fields determine what data can be presented, and style determines how it is presented; when the order is reversed, it is often the case that after the style is changed, there is no corresponding data to read.

Will the changes affect the published content?

Changes to the template will affect all pages that reference the template at the same time, which is both its value and its risk. Therefore, the range of changes should be controlled at the granularity of the template file, and recoverable backups should be kept to avoid one change affecting pages that should not change.