In AnQiCMS content operation, 'Content keyword replacement' is undoubtedly a powerful tool to improve efficiency and optimize content quality.It allows operators to globally adjust specific words or phrases in website content in bulk, whether for brand consistency, SEO optimization, or information updates.However, relying solely on the background replacement function may not be enough to meet the refined display needs of the front-end sometimes.At this time, cleverly combining AnQiCMS template filters can bring more flexibility and control to content display, achieving a better user experience.

AnQiCMS backend content keyword replacement feature overview

First, let's review the "Content Keyword Replacement" feature of the AnQiCMS backend.This feature is located under the "Content Management" module and allows you to define a series of replacement rules.The core advantage lies in:

  1. Global and batch processing: You can set up a pair of keywords for "Find" and "Replace", and the system can batch process the content of the entire site, greatly reducing the burden of manual modification.
  2. Supports regular expressionsFor complex replacement logic, such as matching specific formats of phone numbers, email addresses, etc., the system supports the use of regular expressions and provides powerful pattern matching capabilities.This makes the replacement operation more flexible and accurate.
  3. Built-in rules and convenient operations：AnQiCMS even pre-sets some common rules, such as matching for email, date, phone number, etc., allowing non-technical personnel to easily get started.

This feature is usually executed automatically when content is published or updated, directly affecting the content stored in the database, or processing it before the content is read from the database and rendered to the front end.Its goal is to ensure the consistency and accuracy of the website content.

The role and value of the template filter

Different from keyword replacement in the background, the template filter takes effect when the content is rendered to the front-end page by AnQiCMS's template engine. Its characteristics are:

  1. Processing on the display levelThe filter does not change the original content stored in the database. It only processes the data again according to preset rules when the content is presented to the user.
  2. Versatile: AnQiCMS template engine (similar to Django template engine) provides rich filters that can be used to format, truncate, concatenate, and judge various data types such as strings, numbers, and arrays.
  3. Lossless: As it does not touch the original data, even if the filter logic has problems, it only affects the front-end display and does not cause damage to the core data of the website.

Replacing the keywords in the background is considered 'root treatment' - it modifies the source of the content.Then, the template filter is a 'quick fix' - it fine-tunes and supplements the content during the display phase.The combination can achieve more efficient and personalized content operation.

Combine practice: Apply filters in front-end templates for validation or preprocessing

In AnQiCMS, the content keyword replacement has greatly improved the uniformity of the content.On this basis, we can use filters in the front-end template to perform more detailed 'front-end validation or preprocessing'.

1. Further beautify or format the replaced content

Assuming the background has replaced all "AnQiCMS" with "AnQi Content Management System", you may wish to highlight this brand word on the front-end or abbreviate it in specific scenarios.

  • Highlight/Style Enhancement You can use it in the template,replaceto replace the content processed by the backend again, in order to achieve the beauty of display.

    {{ archive.Content|replace:"安企内容管理系统","<strong>安企内容管理系统</strong>"|safe }}

    here,safeThe filter is necessary to ensure<strong>The tags can be parsed correctly by the browser instead of being displayed as plain text.

  • Dynamic content truncation and ellipsis: If the descriptive content replaced by the background becomes too long and affects the page layout, you can usetruncatecharsortruncatewordsthe filter for intelligent truncation.

    <p>{{ archive.Description|truncatechars:100 }}</p>

    This will automatically truncate and add an ellipsis when the description exceeds 100 characters, maintaining the page neat.

2. Conditional display based on content check.

BycontainThe filter checks whether the content contains specific keywords and then cooperatesifThe logical tag performs conditional rendering. This is very useful when backend replacement may not cover all complex logic.

  • Important information reminderFor example, you may want to display a prominent icon or text next to the article title when the article content contains a specific notification word (even if it has been standardized and replaced in the background).
    
<h3>
    {{ archive.Title }}
    {% if archive.Content|contain:"新政策发布" %}
        <span style="color: red; font-weight: bold;">[重要通知]</span>
    {% endif %}
</h3>

3. Cleaning or supplementing replacement may produce unnecessary characters

Although the background replacement feature is powerful, in some special cases, the replacement rules may cause extra characters, or you may need to further format some numbers, links.

  • Remove extra separators: If extra hyphens or spaces are inadvertently introduced during the background replacement process,cutThe filter can easily remove them.

    {{ archive.Title|cut:"-" }}

    For example, to标题-副标题Processed into标题副标题.

  • Dynamically generate and link processingAlthough AnQiCMS can generate links with keyword replacement in the backend, but on the front end,urlizeThe filter can automatically convert URLs in text to clickable hyperlinks and add them by defaultrel="nofollow"which is beneficial for SEO and user experience.

    <p>联系我们：{{ contact.Email|urlize|safe }}</p>

4. Front-end assistance for content security and compliance

Although AnQiCMS is built-in with sensitive word filtering function, but in specific display scenarios or as the final defense line, the front-end filter can also play an auxiliary role.

  • Front-end sensitive word desensitization(As an addition rather than a substitute): It is not recommended to handle core sensitive word filtering on the front-end, but if in some scenarios, you want to display specific words extra, you can do so in the template.
    
{% set displayed_content = archive.Content|replace:"公司内部名称","***" %}
{{ displayed_content|safe }}
    Please note that this is only a display-level desensitization and should not be used as the primary security measure.

Cautionary notes and **practice

  • Clear division of labor: Assign global, persistent, complex, and data-altering replacement tasks to background functions; assign lightweight, display-only, dynamically adjustable, and performance-insensitive processing tasks to frontend template filters.
  • Performance considerationAvoid using a large number of complex or nested filters in templates, especially within loops, as this may affect page loading speed. Prefer to complete performance-sensitive batch processing in the background.
  • Debugging and testingWhen applying filters, be sure to thoroughly test in the development environment to ensure that the display is as expected, and avoid unexpected format errors or data display issues. Especially when dealing with HTML content,|safeThe use of filters must be very cautious to prevent XSS risks.
  • maintainabilityKeep the filter logic concise and clear.