A method, device, equipment and storage medium for generating a content page
By receiving page request instructions, generating content request interface addresses, and standardizing content module data, the problem of slow content page generation speed is solved, the dependence on multiple data interfaces is reduced, and the content page generation process is optimized.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- GUANGDONG PACIFIC HULIANWANG INFORMATION SERVICE CO LTD
- Filing Date
- 2022-11-24
- Publication Date
- 2026-06-12
AI Technical Summary
When generating content pages, asynchronous requests to multiple data request interfaces result in slow speeds and put pressure on the application server.
By receiving page request instructions, parsing the page content information ID, generating the content request interface address, obtaining and standardizing the content module data, and rendering the content module data in the client page in sequence, the dependence on multiple data interfaces is reduced.
This reduces the likelihood of slow content page generation and alleviates the pressure on application servers.
Smart Images
Figure CN115905751B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of Internet technology, and more specifically, to a method, apparatus, device, and storage medium for generating content pages. Background Technology
[0002] With the rapid development of internet and mobile terminal device technologies, information and news are exhibiting diversified characteristics, and rich and real-time information is attracting the attention of a wide range of users. Each application needs to generate a content page when providing information to users. This content page contains content data from different content modules, which are managed by a content component module system. This system has a data request interface for each piece of content data, and each piece of content data is transmitted to the user's end through this interface, thus aggregating various information content onto the content page.
[0003] However, when reading content data from different content modules, different data request interfaces need to be requested asynchronously. This makes the time required to generate the content page depend on the number of data request interfaces and the request speed of each data request interface. It is heavily reliant on multiple data request interfaces. When a data request interface fails, it will greatly reduce the speed of content page generation and put pressure on the application server. Summary of the Invention
[0004] In view of the above problems, this application is made to provide a method, apparatus, device and storage medium for generating content pages, so as to optimize the way content data is requested and reduce the possibility of slow content page generation.
[0005] To achieve the above objectives, the following specific solutions are proposed:
[0006] A method for generating content pages, comprising:
[0007] Upon receiving a page request instruction sent by the client, the page request instruction is parsed to obtain multiple page content information IDs for the requested page content;
[0008] Based on the preset interface address concatenation rules, generate a content request interface address containing the IDs of the content information of each page;
[0009] Through the content request interface address, obtain content module data that matches the content information ID of each page and is pre-normalized by the normalized template of the content management system from the content component module system;
[0010] In accordance with the order in which the data of each content module is obtained, the data of each content module is rendered sequentially on the client page corresponding to the client, thereby obtaining several content pages composed of each content module, and returning the several content pages to the client.
[0011] Optionally, by using the content request interface address, content module data that matches the content information ID of each page and is pre-normalized by the normalized template of the content management system is obtained from the content component module system, including:
[0012] In the content component module system, identify the target static JSON interface that matches the content request interface address;
[0013] Based on the preset reading rules for each page content information ID, the content module data that matches the page content information ID and is pre-standardized by the standardized template of the content management system is read through the target static JSON interface.
[0014] Optionally, the publishing process of the target static JSON interface includes:
[0015] In the content component module system, a target component corresponding to each page content information ID is determined;
[0016] Construct a target module that includes all target components;
[0017] When the content module data of each target component in the target module is updated, the content module data is normalized using the normalization template of the content management system to obtain normalized content module data;
[0018] If the content module data of each target component is successfully normalized during the update, the target static JSON interface of the target module is generated and published.
[0019] Optionally, the assembly includes target modules of each target component, including:
[0020] In response to the user's dragging and dropping of various target components, a target module containing each target component is constructed according to the dragging order of the user, so that the content component module system can provide standardized content module data to the content management system according to the dragging order.
[0021] Optionally, the fields of each of the content module data are the same as the fields of the target static JSON interface.
[0022] Optionally, the data in each content module includes ordinary articles;
[0023] The rendering process for the aforementioned ordinary article includes:
[0024] In several of the aforementioned content pages, the rendering area of the ordinary article is determined;
[0025] In the rendering area, the image of the ordinary article and the text portion of the ordinary article are distributed horizontally.
[0026] or,
[0027] If the ordinary article contains only one image larger than a preset size, in the rendering area, the image of the ordinary article is placed below the text portion of the ordinary article.
[0028] or,
[0029] If the ordinary article contains only three images, in the rendering area, the images of the ordinary article are distributed above the text portion of the ordinary article.
[0030] An apparatus for generating content pages, used in a content management system, comprising:
[0031] The content information ID acquisition unit is used to receive a page request instruction sent by the client, parse the page request instruction to obtain multiple page content information IDs for the page content request;
[0032] The interface address generation unit is used to generate a content request interface address containing the content information IDs of each page according to a preset interface address concatenation rule.
[0033] The content module data acquisition unit is used to acquire, through the content request interface address, content module data that matches the content information ID of each page and is pre-normalized by the normalized template of the content management system from the content component module system;
[0034] The content data rendering unit is used to render the data of each content module sequentially in the client page corresponding to the client according to the order in which the data of each content module is obtained, so as to obtain a content page composed of each content module, and return the content page to the client.
[0035] Optionally, the content module data acquisition unit includes:
[0036] The target static interface determination unit is used to determine the target static JSON interface in the content component module system that matches the content request interface address.
[0037] The content data reading unit is used to read content module data that matches the content information ID of each page and is pre-normalized by the normalization template of the content management system through the target static JSON interface, according to the preset reading rules of the content information ID of each page.
[0038] Optionally, the device may also include:
[0039] The first static interface publishing unit is used to determine the target component corresponding to each page content information id in the content component module system.
[0040] The second unit of static interface publishing is used to build target modules containing various target components;
[0041] The third static interface publishing unit is used to normalize the content module data through the normalization template of the content management system when the content module data of each target component in the target module is updated, so as to obtain normalized content module data.
[0042] The fourth unit of static interface publishing is used to generate and publish the target static JSON interface of the target module if the content module data of each target component is successfully normalized during the update.
[0043] Optionally, the second unit for publishing the static interface includes:
[0044] The user interaction component unit is used to respond to the user's dragging and dropping of various target components. According to the dragging and dropping order of the target components by the user, it constructs a target module containing each target component, so that the content component module system can provide standardized content module data to the content management system according to the dragging and dropping order.
[0045] Optionally, the data in each content module includes ordinary articles;
[0046] The device also includes:
[0047] The rendering area determination unit is used to determine the rendering area of the ordinary article among the several content pages.
[0048] A regular text rendering unit is used to distribute the image of the regular article and the text portion of the regular article horizontally in the rendering area; or, if the regular article contains only one image larger than a preset size, distribute the image of the regular article below the text portion of the regular article in the rendering area; or, if the regular article contains only three images, distribute the images of the regular article above the text portion of the regular article in the rendering area.
[0049] A device for generating content pages, including a memory and a processor;
[0050] The memory is used to store programs;
[0051] The processor is used to execute the program to implement the various steps of the content page generation method described above.
[0052] A readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method for generating a content page as described above.
[0053] By employing the above technical solution, this application receives a page request instruction sent by a client, parses the instruction to obtain multiple page content information IDs for the requested content, generates a content request interface address containing each page content information ID according to a preset interface address concatenation rule, and retrieves content module data from the content component module system that matches each page content information ID and is pre-standardized by the standardized template of the content management system. Following the order in which the content module data is retrieved, each content module data is rendered sequentially on the client page corresponding to the client, resulting in several content pages composed of various content modules, which are then returned to the client. Therefore, it is evident that only the page content information IDs need to be transmitted to obtain the content request interface address for initiating the request, and the transmission of content module data can be achieved through a single interface corresponding to the content request interface address. This eliminates the dependence on multiple data interfaces, reduces the possibility of slow content page generation, and helps alleviate the pressure on the application server. Attached Figure Description
[0054] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this application. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:
[0055] Figure 1 A schematic diagram illustrating a process for generating a content page, provided as an embodiment of this application;
[0056] Figure 2 A schematic diagram of a component in the content component module system provided in the embodiments of this application;
[0057] Figure 3 A schematic diagram of a data segment with standardized data structure provided in an embodiment of this application;
[0058] Figure 4A schematic diagram of a device structure for generating content pages is provided in an embodiment of this application;
[0059] Figure 5 This is a schematic diagram of the structure of a content page generation device provided in an embodiment of this application. Detailed Implementation
[0060] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0061] The proposed solution can be implemented based on a terminal with data processing capabilities, which can be a content management system.
[0062] Next, combined Figure 1 The method for generating the content page of this application may include the following steps:
[0063] Step S110: Receive a page request instruction sent by the client, and parse the page request instruction to obtain multiple page content information IDs for the page content request.
[0064] Specifically, the client's page request instruction can be generated in response to a user clicking a control that requests a webpage. For example, if the control clicked by the user requests a page with images and text, then the parsed page content request's page content information ID will be the image information ID and the text information ID.
[0065] Understandably, the content management system has pre-configured the address templates for request interfaces. When the content management system generates the request interface address, only the id changes in the address format. Therefore, it is only necessary to obtain the ids of multiple page content information requested by the page content system.
[0066] Step S120: Generate a content request interface address containing the content information IDs of each page according to the preset interface address concatenation rules.
[0067] Specifically, the content request interface address requests only one interface, which can be a JSON interface. The JSON interface requested by the content request interface address can allow the transmission of data fields corresponding to the content information ID of each page.
[0068] Step S130: Obtain content module data that matches the content information ID of each page and is pre-normalized by the normalized template of the content management system from the content component module system through the content request interface address.
[0069] Specifically, the content component module system can include a variety of components, each component corresponding to an updatable content module data. The content component module system can also include multiple JSON interfaces, each of which can correspond to a module containing one or more components, and can allow the transmission of one or more content module data corresponding to the module.
[0070] For example Figure 2 The components in the content component module system may include header components for customized navigation, focus image components for reading column image news, banner image components for reading column image news, information flow components for reading column text lists, product library product display components for reading product library API interfaces, key headline news components for reading column headlines, comment module components for reading topic or text comment lists, special ad placement module components for inserting advertisements, e-commerce quotation module components for inserting product library or Juchaozhi e-commerce quotations and recording commissions via link redirection, and other module components for redirecting to third-party mini programs, etc.
[0071] It is understandable that the data structure of the content module data corresponding to these components can be pre-standardized according to the standardized modules of the content management system's standardized template.
[0072] For example Figure 3The data structure for the price component can be standardized to a "price" field; the data structure for the publication time component can be standardized to "pubTime"; the data structure for the comment count component can be standardized to "cmtCount"; the data structure for the link address component can be standardized to "link"; the data structure for the description component can be standardized to "summary"; the data structure for the score component can be standardized to "score"; the data structure for the video source component can be standardized to "videoSrc"; the data structure for the guide image type component can be standardized to "guideType"; and the data structure for other fields can be standardized to "othe". The data structure for the title content module can be standardized to "title", the data structure for the image URL content module can be standardized to "imgUrl", the data structure for the image array content module can be standardized to "imgUrls", the data structure for the article ID content module can be standardized to "id", the data structure for the data category content module can be standardized to "type", the data structure for the mini-program jump key content module can be standardized to "appkey", the data structure for the mini-program path content module can be standardized to "path", the data structure for the jump protocol content module can be standardized to "scheme", and the data structure for the e-commerce logo content module can be standardized to "mallLogo".
[0073] After the data structure of the standardized content module data is established, the component can be combined with other components to obtain a module, and then the module can transmit the data of each content module.
[0074] Step S140: According to the order in which the data of each content module is obtained, the data of each content module is rendered sequentially in the client page corresponding to the client to obtain several content pages composed of each content module, and the several content pages are returned to the client.
[0075] Specifically, after obtaining data from multiple content modules, the existing client components of the client application (such as mini-programs or H5) can be used to render them. The order in which the data of each content module is obtained can be the order in which the data of each content module is added when the module is created.
[0076] The content page generation method provided in this embodiment receives a page request instruction sent by a client, parses the instruction to obtain multiple page content information IDs for the requested content, generates a content request interface address containing these IDs according to a preset interface address concatenation rule, and retrieves content module data from the content component module system that matches each page content information ID and is pre-standardized by the content management system's standardized template using this content request interface address. Following the order in which the content module data is retrieved, each content module data is rendered sequentially on the client page corresponding to the client, resulting in several content pages composed of these content modules. These content pages are then returned to the client. Therefore, only the page content information IDs need to be transmitted to obtain the content request interface address for initiating the request, and the transmission of content module data can be achieved through a single interface corresponding to this address. This eliminates the dependency on multiple data interfaces, reduces the possibility of slow content page generation, and helps alleviate the pressure on the application server.
[0077] In some embodiments of this application, the process of obtaining, through the content request interface address, content module data that matches the content information ID of each page and is pre-normalized by the normalized template of the content management system from the content component module system in step S130 is described. This process may include:
[0078] S1. Determine the target static JSON interface in the content component module system that matches the content request interface address.
[0079] It is understood that the content component module system may include multiple static JSON interfaces, each of which is pre-configured. Different JSON interfaces can allow the transmission of several different content module data. Therefore, all content module data allowed to be transmitted by the target static JSON interface matching the content request interface address can correspond to all page content information IDs in the content request interface address.
[0080] S2. Based on the preset reading rules for each page content information ID, read the content module data that matches the page content information ID and has been pre-standardized by the standardized template of the content management system through the target static JSON interface.
[0081] It is understandable that the content component module system can update the content module data periodically and synchronize it to various static JSON interfaces. Therefore, the content management system can read the content module data that matches the content information ID of each page and is pre-standardized by the standardized template of the content management system through the target static JSON interface, according to the preset reading rules of the content information ID of each page.
[0082] In some embodiments of this application, the publishing process of the target static JSON interface mentioned in the above embodiments is described, and the process may include:
[0083] S1. In the content component module system, determine the target component corresponding to each page content information id.
[0084] It is understood that the target component corresponding to each page content information ID is the component that needs to request and obtain content module data.
[0085] S2. Construct a target module containing each target component.
[0086] Understandably, the target module is a module that retrieves all content module data for the required request.
[0087] Specifically, the target module can be assembled by responding to the user's drag-and-drop operation of each target component and in the order in which the user drags and drops each target component, so that the content component module system can provide the content management system with each standardized content module data in the order of dragging and dropping.
[0088] S3. When the content module data of each target component in the target module is updated, the content module data is normalized using the normalization template of the content management system to obtain normalized content module data.
[0089] Specifically, the fields of the content module data of each target component in the target module are the same as the fields of the target static JSON interface.
[0090] Understandably, standardizing the data structure of content modules can unify the data structure of the content management system, making multiple components compatible.
[0091] S4. If the content module data of each target component is successfully normalized during the update, generate and publish the target static JSON interface of the target module.
[0092] The content page generation method provided in this embodiment standardizes the data structure of the content module data when publishing the target static JSON interface, enabling a unified data structure for the content management system and allowing multiple components to be used interchangeably, thus reducing front-end development time. Simultaneously, the assembled target static JSON interface only needs to accept a single HTTP request to transmit data from different components, thereby rendering the entire page, significantly reducing waiting time and rendering speed.
[0093] In some embodiments of this application, the content module data mentioned in the above embodiments may include ordinary articles. Based on this, the rendering process of the ordinary articles may include:
[0094] S1. Determine the rendering area of the ordinary article in the several content pages.
[0095] S2. In the rendering area, the images of the ordinary article are distributed horizontally with the text portion of the ordinary article; or, if the ordinary article contains only one image larger than a preset size, the image of the ordinary article is distributed below the text portion of the ordinary article in the rendering area; or, if the ordinary article contains only three images, the images of the ordinary article are distributed above the text portion of the ordinary article in the rendering area.
[0096] In addition, the content module data can also include old articles. Based on this, the rendering process of the old articles can be specifically processed according to requirements.
[0097] The apparatus for generating content pages provided in the embodiments of this application is described below. The apparatus for generating content pages described below can be referred to in correspondence with the method for generating content pages described above.
[0098] See Figure 4 , Figure 4 This is a schematic diagram of a device structure for generating content pages, as disclosed in an embodiment of this application.
[0099] like Figure 4 As shown, the device may include:
[0100] The content information ID acquisition unit 11 is used to receive a page request instruction sent by the client, parse the page request instruction to obtain multiple page content information IDs of the page content request;
[0101] The interface address generation unit 12 is used to generate a content request interface address containing the content information IDs of each page according to a preset interface address concatenation rule.
[0102] The content module data acquisition unit 13 is used to acquire, through the content request interface address, content module data that matches the content information ID of each page and is pre-normalized by the normalized template of the content management system from the content component module system;
[0103] The content data rendering unit 14 is used to render the data of each content module in the client page corresponding to the client in the order of obtaining the data of each content module, so as to obtain a content page composed of each content module and return the content page to the client.
[0104] Optionally, the content module data acquisition unit includes:
[0105] The target static interface determination unit is used to determine the target static JSON interface in the content component module system that matches the content request interface address.
[0106] The content data reading unit is used to read content module data that matches the content information ID of each page and is pre-normalized by the normalization template of the content management system through the target static JSON interface, according to the preset reading rules of the content information ID of each page.
[0107] Optionally, the device may also include:
[0108] The first static interface publishing unit is used to determine the target component corresponding to each page content information id in the content component module system.
[0109] The second unit of static interface publishing is used to build target modules containing various target components;
[0110] The third static interface publishing unit is used to normalize the content module data through the normalization template of the content management system when the content module data of each target component in the target module is updated, so as to obtain normalized content module data.
[0111] The fourth unit of static interface publishing is used to generate and publish the target static JSON interface of the target module if the content module data of each target component is successfully normalized during the update.
[0112] Optionally, the second unit for publishing the static interface includes:
[0113] The user interaction component unit is used to respond to the user's dragging and dropping of various target components. According to the dragging and dropping order of the target components by the user, it constructs a target module containing each target component, so that the content component module system can provide standardized content module data to the content management system according to the dragging and dropping order.
[0114] Optionally, the data in each content module includes ordinary articles;
[0115] The device also includes:
[0116] The rendering area determination unit is used to determine the rendering area of the ordinary article among the several content pages.
[0117] A regular text rendering unit is used to distribute the image of the regular article and the text portion of the regular article horizontally in the rendering area; or, if the regular article contains only one image larger than a preset size, distribute the image of the regular article below the text portion of the regular article in the rendering area; or, if the regular article contains only three images, distribute the images of the regular article above the text portion of the regular article in the rendering area.
[0118] The content page generation apparatus provided in this application embodiment can be applied to devices for generating content pages, such as terminals: mobile phones, computers, etc. Optionally, Figure 5 The hardware structure block diagram of the content page generation device is shown below, with reference to... Figure 5 The hardware structure of the device that generates the content page may include: at least one processor 1, at least one communication interface 2, at least one memory 3, and at least one communication bus 4;
[0119] In this embodiment of the application, the number of processor 1, communication interface 2, memory 3, and communication bus 4 is at least one, and processor 1, communication interface 2, and memory 3 communicate with each other through communication bus 4;
[0120] Processor 1 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention.
[0121] Memory 3 may include high-speed RAM, and may also include non-volatile memory, such as at least one disk storage device;
[0122] The memory stores a program, which the processor can call. The program is used for:
[0123] Upon receiving a page request instruction sent by the client, the page request instruction is parsed to obtain multiple page content information IDs for the requested page content;
[0124] Based on the preset interface address concatenation rules, generate a content request interface address containing the IDs of the content information of each page;
[0125] Through the content request interface address, obtain content module data that matches the content information ID of each page and is pre-normalized by the normalized template of the content management system from the content component module system;
[0126] In accordance with the order in which the data of each content module is obtained, the data of each content module is rendered sequentially on the client page corresponding to the client, thereby obtaining several content pages composed of each content module, and returning the several content pages to the client.
[0127] Optionally, the refined and extended functions of the program can be found in the description above.
[0128] This application embodiment also provides a storage medium that can store a program suitable for execution by a processor, the program being used for:
[0129] Upon receiving a page request instruction sent by the client, the page request instruction is parsed to obtain multiple page content information IDs for the requested page content;
[0130] Based on the preset interface address concatenation rules, generate a content request interface address containing the IDs of the content information of each page;
[0131] Through the content request interface address, obtain content module data that matches the content information ID of each page and is pre-normalized by the normalized template of the content management system from the content component module system;
[0132] In accordance with the order in which the data of each content module is obtained, the data of each content module is rendered sequentially on the client page corresponding to the client, thereby obtaining several content pages composed of each content module, and returning the several content pages to the client.
[0133] Optionally, the refined and extended functions of the program can be found in the description above.
[0134] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.
[0135] The various embodiments in this specification are described in a progressive manner. Each embodiment focuses on the differences from other embodiments. The various embodiments can be combined as needed, and the same or similar parts can be referred to each other.
[0136] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A method for generating content pages, characterized in that, Applied to content management systems, including: Upon receiving a page request instruction sent by the client, the page request instruction is parsed to obtain multiple page content information IDs for the requested page content; Based on the preset interface address concatenation rules, generate a content request interface address containing the IDs of the content information of each page; Through the content request interface address, obtain content module data that matches the content information ID of each page and is pre-normalized by the normalized template of the content management system from the content component module system; According to the order in which the data of each content module is obtained, the data of each content module is rendered sequentially in the client page corresponding to the client to obtain several content pages composed of each content module, and the several content pages are returned to the client. Through the content request interface address, retrieve content module data from the content component module system that matches the content information ID of each page and is pre-normalized by the normalized template of the content management system, including: In the content component module system, identify the target static JSON interface that matches the content request interface address; Based on the preset reading rules for each page content information ID, the content module data that matches the page content information ID and is pre-standardized by the standardized template of the content management system is read through the target static JSON interface; The publishing process of the target static JSON interface includes: In the content component module system, a target component corresponding to each page content information ID is determined; Construct a target module that includes all target components; When the content module data of each target component in the target module is updated, the content module data is normalized using the normalization template of the content management system to obtain normalized content module data; If the content module data of each target component is successfully normalized during the update, the target static JSON interface of the target module is generated and published. The assembly comprises target modules of various target components, including: In response to the user's dragging and dropping of various target components, a target module containing each target component is constructed according to the dragging order of the user, so that the content component module system can provide standardized content module data to the content management system according to the dragging order.
2. The method according to claim 1, characterized in that, The fields of each of the content module data are the same as the fields of the target static JSON interface.
3. The method according to claim 1, characterized in that, The data for each content module includes ordinary articles; The rendering process for the aforementioned ordinary article includes: In several of the aforementioned content pages, the rendering area of the ordinary article is determined; In the rendering area, the image of the ordinary article and the text portion of the ordinary article are distributed horizontally. or, If the ordinary article contains only one image larger than a preset size, in the rendering area, the image of the ordinary article is placed below the text portion of the ordinary article. or, If the ordinary article contains only three images, in the rendering area, the images of the ordinary article are distributed above the text portion of the ordinary article.
4. An apparatus for generating content pages, characterized in that, The content management system applied to the content page generation method as described in claim 1 includes: The content information ID acquisition unit is used to receive a page request instruction sent by the client, parse the page request instruction to obtain multiple page content information IDs for the page content request; The interface address generation unit is used to generate a content request interface address containing the content information IDs of each page according to a preset interface address concatenation rule. The content module data acquisition unit is used to acquire, through the content request interface address, content module data that matches the content information ID of each page and is pre-normalized by the normalized template of the content management system from the content component module system; The content data rendering unit is used to render the data of each content module sequentially in the client page corresponding to the client according to the order in which the data of each content module is obtained, so as to obtain a content page composed of each content module, and return the content page to the client.
5. The apparatus according to claim 4, characterized in that, The content module data acquisition unit includes: The target static interface determination unit is used to determine the target static JSON interface in the content component module system that matches the content request interface address. The content data reading unit is used to read content module data that matches the content information ID of each page and is pre-normalized by the normalization template of the content management system through the target static JSON interface, according to the preset reading rules of the content information ID of each page.
6. A device for generating content pages, characterized in that, Including memory and processor; The memory is used to store programs; The processor is configured to execute the program to implement the various steps of the content page generation method as described in any one of claims 1-3.
7. A readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the content page generation method as described in any one of claims 1-3.