What is the difference and usage of the `Title` and `Name` fields in the content model in practice?

In the daily operation of AnQiCMS (AnQiCMS), we often encounter content models and fields.Among the two fields named "Title" and "Name" which seem similar, they carry completely different responsibilities in practice.As an experienced website operations expert, I fully understand the importance of understanding these subtle differences for efficient content management, optimizing website structure, and improving user experience.Today, let's delve deeply into the content model of Anqi CMS.TitleandNameField, see what roles they play individually.

Unveiling the 'Title' and 'Name' of the AnQiCMS content model: A deep conversation on user experience and system logic

AnQi CMS, with its flexible content model, endows the website with strong adaptability and scalability.Whether it is articles, products, activities, or any custom content type, we can build personalized content structures according to business needs.However, behind this powerful customization ability, there is a particular understanding of some core fields,TitleandNameIt is often the place where many operators feel confused. Let's clear up the fog and clarify their logic.

“Title” field: The title facing the user, the core identifier of the content

When we create or edit any content in the Anqi CMS backend, whether it is documents, categories, single pages, or tags, the most intuitive and most important input item is often the 'title'. This 'title' in the context of Anqi CMS usually corresponds toTitlefield.

TitleThe responsibilityAs the name implies, it is the name displayed to the outside world. It is the most recognizable information that users see directly on the website front end. For example:

• of a news article'sTitleThis is the summary of the news.
• A productTitleThis is the name of the product.
• A category of a websiteTitleThis is the name of the category, such as 'Company Profile', 'Latest News'.
• a label'sTitle, is the text of the label, such as "SEO optimization", "Go language development".

From the perspective of operation,TitleThe importance of the field is self-evident. It is directly related to:

1. User Experience: A clear and attractive title can guide users to click and read.
2. Search Engine Optimization (SEO): Pagemetain the labeltitle、Contenth1The title in the tag is a key factor in search engines determining the theme and relevance of a page. A well-optimized oneTitlecan significantly enhance the visibility of the content in search results.
3. Content recognitionIn content lists, breadcrumb navigation, and so on,TitleIt is the basis for users to quickly understand the context of the content.

In the template call of Anqi CMS, we directly go throughitem.TitleorarchiveDetail/categoryDetailetc. tags to specifyname="Title"To obtain and display the main title of the content. For example,{% archiveDetail with name="Title" %}It will output the title of the current document. In addition, there is a setting item called "Title Name" when the custom model is created, which actually defines the main title of the content under the model in the background editing interface.Tag NameFurther emphasized the importance of its user experience level.

The "Name" field: the logical name within the system, the cornerstone of structure.

Visible to the user.Titledifferent,NameThe field plays a more internal, programmed logical identifier role in the system.It does not directly face the end user, but serves for the identification, classification, and data interaction within the system.In AnQi CMS,NameThe usage of the field exists at different levels, reflecting its structured and programmed characteristics:

1. The name of the content model itself (model name)When we define a completely new content model, such as "product model" or "service case model", we will specify a "model name" for it. This name (such as "article model", "product model") is the name of the model itself.Name. ThisNameUsed for marking the model in the background management interface, as well as certain template tags thatmoduleIdormodelNamespecify which content model's data needs to be operated on.

2. The field (FieldName) called in the content model custom fieldThis isNameThe other important application scenario. When we add "custom fields" to the content model (for example, adding "price", "inventory", etc. to the product model), we need to specify a "parameter name" for each custom field (this is the field label seen by the user in the backend, more like aTitle) and a 'call field' (this is the field used by the developer in the template or API to access this fieldactual name, that isFieldNamethis 'call field' is typicalNameit must be english lowercase letters, as column names in data tables or keys in programs, to ensure that the system can accurately identify and access data. for example,item.priceor{% archiveDetail with name="price" %}ofpricethis is itFieldName.

3. URL alias (URL Alias)Although the document mentions that the "URL alias" is more倾向于 the unique identifier of the content, rather than a directNamefield, but it is related to the content model'sName(Model table name or URL alias) are closely related. The "URL alias" of the model is usually in lowercase English, used to construct the module part of the static URL (for example/article/or/product/It defines the access paths for different types of content at the system level.

NameThe core function of the fieldLies in:

• Data structure definitionIt defines the classification of the content model and the programmatic identification of each field within the model, which is the skeleton of the website data architecture.
• Template invocation and data interactionDevelopers throughName(For example, custom fields)FieldNameExtract data accurately in the template or transmit data through the API.
• System internal processingIn database storage, routing resolution, permission control, and other background logic,Nameprovides a unique, program-friendly identifier.

Difference and summary of use: one graph, two roles

We can combineTitleandNameThe relationship is compared to 'a person's name' and 'this person's ID card number.'

• TitleLike 'a person's name':

  • function: A term used for external address, convenient for interpersonal communication, with emotion and meaning.
  • Features: Can contain Chinese, with high freedom, focusing on readability and descriptiveness.
  • Application scenario: Website front-end display, SEO title, content list, etc.

• NameThe field is like 'This person's ID on the ID card':

  • function: System internal identifier, ensures uniqueness, facilitates machine recognition and management.
  • FeaturesThe value is usually English, numbers, or underscores, with strict naming conventions (such as lowercase letters), emphasizing programmability and logic.
  • Application scenario: An identifier for the content model itself, the database key name of custom fields, the parameter name of template tags, a part of the URL path, etc.

Understanding this distinction can help us better utilize the powerful functions of AnQiCMS. When designing content models and custom fields, we provide users with friendly "parameter names" (that is,TitleA description of the level, while allocating a standardized "call field" (i.e. 层面的描述），同时为系统分配规范的“调用字段”（即NameThe indicator of the level). This makes the content presentable to the user in an easy-to-understand manner, and can be managed and processed by the system in an efficient and structured way.

FAQs (