In the ever-changing field of digital marketing, the efficient organization and management of website content is the cornerstone of success.As an expert in website operations for many years, I deeply understand the importance of a flexible and powerful content management system (CMS) for improving operational efficiency and user experience.AnQiCMS has won a good reputation in the industry with its excellent performance and rich features.Today, we will delve into a key issue frequently mentioned in content operation: Does the AnQi CMS document tag support marking and management across content models?
Anqi CMS: Tag, the universal language of content models
The answer is affirmative. The document tagging feature of AnQi CMS not only supports marking content under a single content model, but also boastscross-content model supportThe powerful capability allows you to uniformly manage tags for different types of content such as articles (archives) and products (products).This design greatly enhances the flexibility of content organization and retrieval, bringing unprecedented convenience to content operation.
The flexibility of the content model and the introduction of tags
One of the core strengths of AnQi CMS lies in its 'flexible content model'.The system allows users to customize various content structures based on business needs, such as creating an 'Article Model' to publish blog posts, news, or creating a 'Product Model' to display product details.This modeled design makes the content structure clear and management efficient.However, in actual operation, we often encounter such a scenario: a 'New Product Launch' tag may need to be associated with an article that introduces the new product features in detail, as well as directly linked to the new product page that has just been listed.
It is precisely to meet this cross-content type association requirement that AnQi CMS officially introduced and enhanced the tag function of the article and product models in version 2.1.0.This is when tags no longer just become exclusive attributes of a certain type of content, but evolve into a 'universal language' that connects different content models.
The 'Universality' of tags: Crossing the boundaries of the content model
The document of Anqi CMS explicitly states:The document tags are not classified by type or model, and the same tag can be assigned to documents of different content models simultaneously.This sentence is the key to understanding the flexibility of the AnQi CMS tags.This means that you can create a tag named 'Summer Promotion' and apply it simultaneously to the announcement articles of promotional activities, various products participating in the promotion, and related image materials.
This cross-model universality brings significant operational advantages:
- Unified management, efficiency multiplied: No need to create and maintain similar tag systems for different content models repeatedly. All tags are centrally managed, making updates and adjustments more convenient.
- Content association, enhancing user experience:When browsing content under a specific tag, users can not only see related articles but also discover corresponding products, forming a complete browsing path, enhancing the depth and breadth of the website's content.
- Strengthen SEO Effect:Tags, as an important method of content classification, can help search engines better understand the theme of the website content. Through a unified tag system, it can effectively enhance the weight and exposure of relevant content in search engines.
Tag Management and Application
In the AnQi CMS backend, the tag management interface is intuitive and easy to use.You can easily create new tags, set their names, index letters, custom URLs, SEO titles, and descriptions.When you are editing an article or product, simply enter or select existing tags in the "Tag label" field to complete the content marking.The system will automatically recognize and prompt you for existing tags, ensuring the standardization and consistency of tags.
Tag Calling in Templates: Realizing Flexible Presentation of Content
For the presentation of the website frontend, Anqi CMS provides powerful template tags, allowing developers and operators to flexibly call and display tags as well as associated content according to their needs.
For example:
tagListTags:Used to obtain the list of document tags. You can set it according to your needs.itemId(specify the document ID) orcategoryId(specify the category ID) to obtain specific content or tags under a category, or even throughitemId="0"Get all tags.tagDetailTags:Used to get the details of a specific tag, such as tag name, link, description, etc.tagDataListTags:This is the key to implementing cross-content model content aggregation. It allows you to based ontagId(Tag ID) to get the list of all documents under the tag. More importantly, it supports specifyingmoduleIdParameters torestricted content models, for example, you can specifymoduleId="1"List only the contents under the article model that have this tag, ormoduleId="2"List only the contents under the product model that have this tag.
This means that in your website template, you can easily build a feature module to 'view all related products under a certain tag' or 'view all related articles under a certain tag', and even mix them together.This fine-grained control makes the content presentation more diverse, further optimizing the user experience and the effectiveness of content marketing.
Summary
The document tagging feature of AnQi CMS surpasses the limitations of traditional CMS, achieving real cross-content model tagging and management.It not only simplifies the complexity of content operation, but also significantly improves the website's content strategy, SEO optimization, and user experience through flexible content association and powerful template calling capabilities.For a content operation team that追求 efficient and flexible, this feature of AnQi CMS is undoubtedly one of its core competitive advantages.
Common Questions (FAQ)
Question: What is the difference between tags and categories (Category) in Anqi CMS? In which scenarios should I use them?Answer: They are mainly different in structure and use. Classification is usuallytree-like structure and model bindingFor example, under the 'article' model, there are categories such as 'news dynamics' and 'industry analysis', and under the 'product' model, there are categories such as 'electronic products' and 'home appliances'. The categories have a hierarchical relationship. Tags areFlattened and cross-modelAn indicator such as 'New Arrival' can be applied to both articles and products simultaneously, used to describe the common attributes or themes of the content without following strict hierarchy.Generally, categories are used to organize the macro structure of content, while tags are used to describe the micro themes or keywords of content more flexibly, enhancing the horizontal correlation of content.
Question: Can I display both articles and products under the same tag on the tag page of AnQi CMS?Answer: Absolutely. By utilizing
tagDataListTemplate tags, you can first get a tag (tagId) and then get all related content under it. While iterating over these contents, you can use the content'sModuleIdTo determine whether it is an article or a product based on the (content model ID) and display them accordingly. For example, whenModuleIdis 1, it is displayed in the style of an article, whenModuleIdWhen the value is 2, it displays in product style. This way, a tab can gather relevant information from different content models, providing a more comprehensive user experience.Question: If I create a tag, can I make it only associated with the content of the 'Article' model and not the 'Product' model?Answer: The label itself is cross-model generic in AnQi CMS.That is to say, any tag you create theoretically can be used by any content model's content.
- Operation Norms:It is agreed within the team that certain tags are only used for specific content models.
- Template call control:Used in the template
tagDataListWhen specifying tags, be clear.moduleIdParameters to only retrieve the content under the article model that has the tag, so that other content models can be filtered out when displayed on the front end. For example,{% tagDataList archives with tagId="您的标签ID" moduleId="1" %}Only articles will be listed.