Page generation method and device, electronic equipment and storage medium

Abstract

The invention relates to a page generation method and device, electronic equipment and a storage medium, and the method comprises the steps: obtaining the configuration protocol information of at least one page in a resource promotion tool through a life cycle manager, and analyzing the configuration protocol information and supplementary configuration protocol information of the at least one page through the life cycle manager, blocks and block information contained in each page are obtained, the supplementary configuration protocol information is obtained through a preset file address contained in the configuration protocol information of at least one page, and the supplementary configuration protocol information is configured by a provider of the resource popularization tool according to a configuration requirement required by an application party of the resource popularization tool; and calling a renderer through the life cycle manager, and performing page rendering based on the blocks and the block information contained in each page to obtain at least one page in the resource promotion tool. According to the embodiment of the invention, page rendering is realized through the life cycle manager, and the dynamic configuration capability is achieved, so that the flexibility of service strategy adjustment is improved.

Description

Technical Field

[0001] The present disclosure relates to the field of Internet technology, and in particular to a page generation method, device, electronic device, and storage medium. Background Art

[0002] With the development of e-commerce, resource providers on e-commerce platforms often utilize various resource promotion tools provided by e-commerce platforms to attract and retain more users. These tools include flash sales, coupons, and discounts. These various resource promotion applications are developed and generated based on the requirements documents for each resource promotion application.

[0003] However, in the related art, each generation of a resource promotion tool requires source code development, and the generation of the resource promotion tool page requires manual execution by the user, which is a cumbersome process and has low generation efficiency. Summary of the Invention

[0004] The present disclosure provides a page generation method, device, electronic device, and storage medium. The technical solutions of the present disclosure are as follows:

[0005] According to a first aspect of an embodiment of the present disclosure, there is provided a page generation method, comprising:

[0006] Obtaining, through the lifecycle manager, configuration protocol information of at least one page in the resource promotion tool;

[0007] The lifecycle manager is used to parse the configuration protocol information and supplementary configuration protocol information of at least one page to obtain the blocks and block information contained in each page; the supplementary configuration protocol information is obtained through the preset file address contained in the configuration protocol information of at least one page; the supplementary configuration protocol information is configured by the provider of the resource promotion tool according to the configuration requirements of the user of the resource promotion tool;

[0008] The renderer is called through the lifecycle manager, and the page is rendered based on the blocks and block information contained in each page to obtain at least one page in the resource promotion tool.

[0009] In some possible embodiments, obtaining, by the lifecycle manager, configuration protocol information of at least one page in the resource promotion tool includes:

[0010] When the resource promotion tool is applied by the first application party, the configuration protocol information of the creation page, the configuration protocol information of the management page, and the configuration protocol information of the data page are obtained through the lifecycle manager; the first application party is the resource provider of the resources promoted by the resource promotion tool; the creation page is used to create activities, rules, or content in the resource promotion tool; the management page is used to manage activities, products, or objects in the resource promotion tool;

[0011] or;

[0012] When the application party of the resource promotion tool is the second application party, the configuration protocol information of the creation page and the configuration protocol information of the management page are obtained through the lifecycle manager; the second application party is the provider of the resource promotion tool.

[0013] In some possible embodiments, the configuration protocol information and supplementary configuration protocol information of at least one page are parsed using a lifecycle manager to obtain blocks and block information contained in each page, including:

[0014] The lifecycle manager is used to parse the configuration protocol information and supplementary configuration protocol information of at least one page, and the blocks and components in the blocks contained in each page are determined from the configuration protocol information of the created page; the components in the blocks include preset components and dynamic components; the preset components are built-in general basic components; the dynamic components are external components to meet the application scenarios of different resource promotion tools;

[0015] The method also includes:

[0016] Initialize the parameters of the components in the block according to the configuration protocol information of each page, and preload the components in the block.

[0017] In some possible embodiments, the lifecycle manager calls a renderer to perform page rendering based on the blocks and block information contained in each page to obtain at least one page in the resource promotion tool, including:

[0018] The renderer is called through the lifecycle manager, and the renderer is used to render based on the routing information and the block information of each page to obtain the components in the block contained in each page; the routing information is parsed and obtained from the configuration protocol information of the page creation;

[0019] During the rendering process, the functions corresponding to the reference access mechanism are injected into the blocks contained in each page through the lifecycle manager; the functions corresponding to the reference access mechanism are used for interaction between blocks.

[0020] In some possible embodiments, the method further includes:

[0021] When a change in routing information is detected, obtaining updated configuration protocol information of at least one page in the resource promotion tool through the lifecycle manager;

[0022] Parsing the updated configuration protocol information and the supplementary configuration protocol information of at least one page using a lifecycle manager to obtain blocks and block information contained in each page;

[0023] The lifecycle manager calls the renderer to perform page rendering based on the changed routing information, the blocks included in each page, and the block information, to obtain at least one page in the resource promotion tool.

[0024] In some possible embodiments, the method further includes:

[0025] The cache manager is called through the lifecycle manager, and the cache manager is used to cache the configuration protocol information and supplementary configuration protocol information of at least one page, dynamic components, and block information of blocks contained in each rendered page.

[0026] In some possible embodiments, the configuration protocol information and supplementary configuration protocol information of at least one page are parsed using a lifecycle manager to obtain blocks and block information contained in each page, including:

[0027] Obtaining a supplementary file from a preset file address using a lifecycle manager; the preset file address is obtained from configuration protocol information of a created page; the supplementary configuration protocol information in the supplementary file includes configuration protocol information of a custom page or configuration protocol information of a custom block in at least one page;

[0028] The configuration protocol information and the supplementary configuration protocol information of at least one page are parsed using a lifecycle manager to obtain blocks and block information contained in each page.

[0029] According to a second aspect of an embodiment of the present disclosure, there is provided a page generating apparatus, comprising:

[0030] a protocol acquisition module configured to acquire configuration protocol information of at least one page in the resource promotion tool through the lifecycle manager;

[0031] The protocol parsing module is configured to parse the configuration protocol information and supplementary configuration protocol information of at least one page using the lifecycle manager to obtain blocks and block information contained in each page; the supplementary configuration protocol information is obtained using a preset file address contained in the configuration protocol information of at least one page; the supplementary configuration protocol information is configured by the provider of the resource promotion tool according to the configuration requirements of the user of the resource promotion tool;

[0032] The page rendering module is configured to execute calling the renderer through the lifecycle manager, perform page rendering based on the blocks and block information contained in each page, and obtain at least one page in the resource promotion tool.

[0033] In some possible embodiments, the protocol acquisition module is configured to execute:

[0034] When the resource promotion tool is applied by the first application party, the configuration protocol information of the creation page, the configuration protocol information of the management page, and the configuration protocol information of the data page are obtained through the lifecycle manager; the first application party is the resource provider of the resources promoted by the resource promotion tool; the creation page is used to create activities, rules, or content in the resource promotion tool; the management page is used to manage activities, products, or objects in the resource promotion tool;

[0035] or;

[0036] When the application party of the resource promotion tool is the second application party, the configuration protocol information of the creation page and the configuration protocol information of the management page are obtained through the lifecycle manager; the second application party is the provider of the resource promotion tool.

[0037] In some possible embodiments, the protocol parsing module is configured to perform:

[0038] The lifecycle manager is used to parse the configuration protocol information and supplementary configuration protocol information of at least one page, and the blocks and components in the blocks contained in each page are determined from the configuration protocol information of the created page; the components in the blocks include preset components and dynamic components; the preset components are built-in general basic components; the dynamic components are external components to meet the application scenarios of different resource promotion tools;

[0039] The apparatus further includes an initialization module configured to execute:

[0040] Initialize the parameters of the components in the block according to the configuration protocol information of each page, and preload the components in the block.

[0041] In some possible embodiments, the page rendering module is configured to execute:

[0042] The renderer is called through the lifecycle manager, and the renderer is used to render based on the routing information and the block information of each page to obtain the components in the block contained in each page; the routing information is parsed and obtained from the configuration protocol information of the page creation;

[0043] During the rendering process, the functions corresponding to the reference access mechanism are injected into the blocks contained in each page through the lifecycle manager; the functions corresponding to the reference access mechanism are used for interaction between blocks.

[0044] In some possible embodiments,

[0045] The protocol acquisition module is configured to acquire updated configuration protocol information of at least one page in the resource promotion tool through the lifecycle manager when a change in routing information is detected;

[0046] The protocol parsing module is configured to parse the updated configuration protocol information and the supplementary configuration protocol information of at least one page using the lifecycle manager to obtain blocks and block information contained in each page;

[0047] The page rendering module is configured to execute page rendering based on the changed routing information, the blocks and block information contained in each page through the lifecycle manager call renderer to obtain at least one page in the resource promotion tool.

[0048] In some possible embodiments, the device further includes a cache module configured to execute

[0049] The cache manager is called through the lifecycle manager, and the cache manager is used to cache the configuration protocol information and supplementary configuration protocol information of at least one page, dynamic components, and block information of blocks contained in each rendered page.

[0050] In some possible embodiments, the protocol parsing module is configured to perform:

[0051] Obtaining a supplementary file from a preset file address using a lifecycle manager; the preset file address is obtained from configuration protocol information of a created page; the supplementary configuration protocol information in the supplementary file includes configuration protocol information of a custom page or configuration protocol information of a custom block in at least one page;

[0052] The configuration protocol information and the supplementary configuration protocol information of at least one page are parsed using a lifecycle manager to obtain blocks and block information contained in each page.

[0053] According to a third aspect of an embodiment of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing processor-executable instructions; wherein the processor is configured to execute instructions to implement a method as described in any one of the first aspects above.

[0054] According to a fourth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided. When instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute any one of the methods in the first aspect of the embodiment of the present disclosure.

[0055] According to a fifth aspect of an embodiment of the present disclosure, a computer program product is provided, which includes a computer program, the computer program is stored in a readable storage medium, and at least one processor of a computer device reads and executes the computer program from the readable storage medium, so that the computer device performs any one of the methods in the first aspect of the embodiment of the present disclosure.

[0056] The technical solutions provided by the embodiments of the present disclosure bring at least the following beneficial effects:

[0057] The configuration protocol information of at least one page in the resource promotion tool is obtained through the lifecycle manager, and the configuration protocol information and supplementary configuration protocol information of at least one page are parsed using the lifecycle manager to obtain the blocks and block information contained in each page. The supplementary configuration protocol information is obtained through the preset file address contained in the configuration protocol information of at least one page. The supplementary configuration protocol information is configured by the provider of the resource promotion tool according to the configuration requirements required by the user of the resource promotion tool. The renderer is called through the lifecycle manager to render the page based on the blocks and block information contained in each page to obtain at least one page in the resource promotion tool. In an embodiment of the present application, the lifecycle manager in the page rendering engine is responsible for managing each stage of the page rendering engine, from the entire process of obtaining the protocol to the final rendering of the page, which can improve the R&D efficiency of the resource promotion tool, and has dynamic and configurable capabilities, so that the page elements and information of the resource promotion tool can be quickly changed and adjusted, thereby improving the flexibility of business strategy adjustment.

[0058] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0060] Figure 1 is a schematic diagram of an application environment of a page generation method according to an exemplary embodiment;

[0061] Figure 2 is a flow chart showing a page generation method according to an exemplary embodiment;

[0062] Figure 3 is a schematic diagram showing a framework of a page rendering engine according to an exemplary embodiment;

[0063] Figure 4 This is a schematic diagram of a React component rendering process in front-end development according to an exemplary embodiment;

[0064] Figure 5 is a flow chart showing a page generation method according to an exemplary embodiment;

[0065] Figure 6 is a flow chart showing a page generation method according to an exemplary embodiment;

[0066] Figure 7 The figure is a block diagram of an electronic device for page generation according to an exemplary embodiment. DETAILED DESCRIPTION

[0067] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making any creative efforts shall fall within the scope of protection of the present invention.

[0068] It should be noted that the terms "first," "second," and the like in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar first objects and are not necessarily used to describe a specific order or precedence. It should be understood that the numbers used in this manner are interchangeable where appropriate so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with certain aspects of the present disclosure as detailed in the appended claims.

[0069] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for display, data for analysis, etc.) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties.

[0070] See also Figure 1 , Figure 1 is a schematic diagram showing an application environment of a page generation method according to an exemplary embodiment. Figure 1 As shown, the application environment may include a server (resource promotion tool providing platform) 011 and a client 012 .

[0071] In some possible embodiments, the server 011 may include an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. The operating system running on the server may include, but is not limited to, Android, iOS, Linux, Windows, Unix, etc.

[0072] In some possible embodiments, the client 012 may include, but is not limited to, smartphones, desktop computers, tablet computers, laptop computers, smart speakers, digital assistants, augmented reality (AR) / virtual reality (VR) devices, smart wearable devices, and other image-based clients. It may also be software running on the client, such as an application or applet. Optionally, the operating system running on the client may include, but is not limited to, Android, iOS, Linux, Windows, Unix, and the like.

[0073] In some possible embodiments, the client 012 obtains the configuration protocol information of at least one page in the resource promotion tool through the lifecycle manager, and uses the lifecycle manager to parse the configuration protocol information and supplementary configuration protocol information of at least one page to obtain the blocks and block information contained in each page. The supplementary configuration protocol information is obtained through the preset file address contained in the configuration protocol information of at least one page. The supplementary configuration protocol information is configured by the provider of the resource promotion tool according to the configuration requirements required by the user of the resource promotion tool. The renderer is called through the lifecycle manager to render the page based on the blocks and block information contained in each page to obtain at least one page in the resource promotion tool. In the embodiment of the present application, the lifecycle manager in the page rendering engine is responsible for managing each stage of the page rendering engine, from obtaining the protocol to the final rendering of the page, which can improve the research and development efficiency of the resource promotion tool, and has dynamic and configurable capabilities, so that the page elements and information of the resource promotion tool can be quickly changed and adjusted, thereby improving the flexibility of business strategy adjustment.

[0074] In one exemplary embodiment, the databases corresponding to the client and server can both be node devices in a blockchain system, capable of sharing acquired and generated information with other node devices in the blockchain system, enabling information sharing among multiple node devices. Multiple node devices in a blockchain system can be configured with the same blockchain, which is composed of multiple blocks, with adjacent blocks having an associated relationship. This allows any tampering of data in any block to be detected by the next block, thereby preventing tampering of the blockchain data and ensuring the security and reliability of the blockchain data.

[0075] Figure 2 It is a flowchart of a page generation method according to an exemplary embodiment. It should be noted that this specification provides method operation steps as described in the embodiment or flowchart, but may include more or fewer operation steps based on conventional or non-creative labor. The order of steps listed in the embodiment is only one way of executing the steps among many steps, and does not represent the only execution order. When the actual system or product is executed, it can be executed in sequence or in parallel (for example, in a parallel processor or multi-threaded processing environment) according to the method shown in the embodiment or the accompanying drawings. Specifically, Figure 2 As shown, the flow chart includes at least the following steps S201-S205:

[0076] In step S201, configuration protocol information of at least one page in a resource promotion tool is obtained through a lifecycle manager.

[0077] In the embodiment of the present application, the execution subject of steps S201-S205 and the technical solution expanded based on steps S201-S205 is a page rendering engine. Optionally, the page rendering engine can be integrated into a client located on a computer or mobile device.

[0078] Figure 3 FIG. 1 is a schematic diagram showing a framework of a page rendering engine according to an exemplary embodiment. Figure 3 As shown in the figure, the core of the page rendering engine mainly consists of a lifecycle manager, a renderer, and a cache manager.

[0079] In some possible embodiments, the lifecycle manager is responsible for managing various stages of the page rendering engine, from obtaining the protocol to the final rendering of the page. The renderer is responsible for generating the final page content based on the protocol content. The cache manager is used to store the protocol content, dynamic components, and rendered page block information to improve the performance and efficiency of the entire page rendering engine.

[0080] Optionally, the lifecycle manager can obtain the protocol from the R&D platform of the resource promotion tool and parse the obtained protocol to facilitate understanding and execution of the instructions therein. Then, the lifecycle manager calls the renderer to generate the final page content based on the parsed protocol content.

[0081] Optionally, a renderer is essentially a program module that converts data into visual output. In a renderer, protocol-driven refers to the use of specific protocols to control, coordinate, and standardize the communication and interaction between various parts of the rendering process, ensuring that the rendering work can proceed smoothly according to predetermined rules and processes. In other words, protocol-driven provides a set of standardized communication rules for the process of converting data into visual output. These rules specify how different components exchange data, pass instructions, and work together to achieve efficient and accurate rendering. In a renderer, block assembly is the process of combining various different elements, data, or instructions into a complete renderable block.

[0082] Optionally, a cache manager is used to store protocols, dynamic components, and pages to avoid repeated actions and improve rendering efficiency.

[0083] In an embodiment of the present application, the page rendering engine can obtain configuration protocol information of at least one page in the resource promotion tool through the lifecycle manager. Optionally, the at least one page includes at least one of a creation page, a management page, and a data page.

[0084] Optionally, the creation page in the resource promotion tool is used to create activities, rules, or content in the resource promotion tool. The creation page may have the following functions:

[0085] First, event creation: This includes providing a visual operation interface that allows users to easily create various resource promotion activities, such as full-reduction activities, limited-time discounts, giveaway activities, etc. Users can set basic information about the activity, such as the activity name, activity time, participating products, etc.

[0086] Second, rule setting: allows users to set detailed activity rules based on resource promotion goals and strategies. For example, in a full discount activity, set the amount threshold and amount of full discount; in a gift activity, set the type, quantity, and conditions for obtaining the gift, etc.

[0087] Third, content editing: Supports editing of promotional content for resource promotion activities, such as designing event posters and writing event copy. Users can upload images and add text to create attractive resource promotion materials to increase the appeal and participation of the event.

[0088] Optionally, the management page in the resource promotion tool is used to manage activities, products, or objects in the resource promotion tool. The management page may have the following functions:

[0089] First, activity management: Centrally manage the created resource promotion activities, including the start, pause, and end of activities. Operations personnel can flexibly control the status of activities based on the actual situation of the activities. For example, if a certain activity is found to be ineffective, it can be suspended in time for adjustment;

[0090] Second, product management: manage products participating in resource promotion activities. You can add, delete, and remove products from shelves to ensure accurate product information and sufficient inventory to avoid overselling and other problems.

[0091] Third, user management: manage users who participate in resource promotion activities, such as viewing user participation records, winning records, etc. At the same time, users can be grouped according to their behavior and characteristics to provide support for targeted resource promotion;

[0092] Fourth, permission management: set the operating permissions of different users for resource promotion tools. For example, administrators have full permissions to create, modify, and delete activities, while ordinary operators only have permissions to view and start activities.

[0093] Optionally, the data page in the resource promotion tool is used to analyze and compare the data involved in the resource promotion tool. The data page may have the following functions:

[0094] First, resource promotion effectiveness analysis: This displays data indicators for various resource promotion activities, such as click-through rate, conversion rate, sales, average order value, etc., to help operations staff intuitively understand the effectiveness of resource promotion activities. For example, by analyzing the conversion rates of different promotional activities, it is possible to determine which type of activity is more popular with consumers.

[0095] Second, user behavior insights: This can present user behavior data, such as browsing time, browsing paths, and click hotspots, to optimize page design and layout. For example, if you find that users click a lot on a certain product recommendation area, you can consider increasing the display weight of that area.

[0096] Third, data comparison and trend analysis: This feature allows you to compare data across different time periods, resource promotion channels, and product categories, while displaying changing trends. This allows operators to identify strengths and weaknesses in resource promotion activities, predict future trends, and develop more effective resource promotion strategies.

[0097] In the embodiment of the present application, the pages included in the at least one page can be determined according to the identity of the user of the resource promotion tool.

[0098] In an optional embodiment, the at least one page includes a creation page, a management page, and a data page. Optionally, when the user of the resource promotion tool is the first user, the page rendering engine may obtain configuration protocol information for the creation page, the management page, and the data page through the lifecycle manager.

[0099] Optionally, the first application party may be a resource provider of the resources promoted by the resource promotion tool, such as an enterprise or a merchant, who mainly provides commodities.

[0100] Specifically, when the resource promotion tool is used by an enterprise or merchant, the first operation performed by the page rendering engine when it begins loading is to call the protocol acquisition lifecycle hook function. This function retrieves the configuration protocol information for the creation page, the management page, and the data page through the interface agreed upon with the backend. Optionally, the protocol acquisition lifecycle hook function can be the "onGetProtocal" function. This means that the protocol acquisition lifecycle hook function is triggered at the beginning of the entire rendering process and is the key entry point for acquiring the protocol.

[0101] In another optional embodiment, the at least one page includes a creation page and a management page. Optionally, when the application party of the resource promotion tool is the second application party, the page rendering engine can obtain the configuration protocol information of the creation page and the configuration protocol information of the management page through the lifecycle manager.

[0102] Optionally, the second application party may be a provider of the resource promotion tool, such as a platform that provides the resource promotion tool.

[0103] Specifically, when the resource promotion tool is applied by the platform providing the tool, the first action performed by the page rendering engine upon loading is to call the protocol acquisition lifecycle hook function. This function retrieves the configuration protocol information for page creation and management through the interface agreed upon with the backend. Optionally, the protocol acquisition lifecycle hook function can be the "onGetProtocal" function. This means that the protocol acquisition lifecycle hook function is triggered at the beginning of the entire rendering process and is the key entry point for acquiring the protocol.

[0104] In an embodiment of the present application, the lifecycle hook function may be a function in the lifecycle manager, which is a function used to execute specific code logic at a specific lifecycle stage in software programming, especially in the use of some frameworks and libraries.

[0105] In an embodiment of the present application, the configuration protocol information for creating a page may be the createInitConfig protocol, the configuration protocol information for managing a page may be the listPageInitConfig protocol, and the configuration protocol information for a data page may be the dataEffectInitConfig protocol.

[0106] The createInitConfig protocol optionally contains detailed information about all sections of the resource promotion tool, such as the layout and functionality of different areas on each page. It also includes some tool configuration information, such as initial settings and parameter adjustments. This is an important basis for building the tool page and determining its initial state.

[0107] Optionally, the listPageInitConfig protocol is mainly targeted at the tool's management page, including descriptive information about the management page, such as the page's functional description and display logic, as well as table rendering configuration, that is, how to display relevant data tables on the management page, including settings for the number of columns, column names, data sources, and other aspects of the table.

[0108] Optionally, the dataEffectInitConfig protocol is specifically used for the data effect page and also includes a description of the page and table rendering configuration. It is responsible for managing and displaying tool-related data effect data, such as the effect statistics and analysis results after the tool is used, and how they are presented in the table.

[0109] In this way, when forming a page in a resource promotion tool, the embodiment of the present application can form a personalized resource promotion tool that better meets the needs by considering the actual application of the resource promotion tool users, thereby achieving a balance between application needs and resource consumption.

[0110] In step S203, the lifecycle manager is used to parse the configuration protocol information and supplementary configuration protocol information of at least one page to obtain the blocks and block information contained in each page; the supplementary configuration protocol information is obtained through the preset file address contained in the configuration protocol information of at least one page; the supplementary configuration protocol information is configured by the provider of the resource promotion tool according to the configuration requirements required by the user of the resource promotion tool.

[0111] As mentioned above, the configuration protocol information for creating a page contains detailed information on all page blocks of the resource promotion tool, such as the layout, functions, and other related information of different areas on each page. Therefore, in some possible embodiments, the page rendering engine can use the lifecycle manager to parse the configuration protocol information and supplementary protocol configuration information of at least one page, and determine the blocks and components in the blocks contained in each page from the configuration protocol information for creating the page.

[0112] Specifically, after the page rendering engine obtains the configuration protocol information of at least one page, it can call the lifecycle hook function of the parsing protocol to parse the configuration protocol information and supplementary protocol configuration information of at least one page, determine the blocks contained in each page from the configuration protocol information of the creation page, that is, from the createInitConfig protocol, and extract the block information required for each page. The block information required for each page can be understood as the components that make up each block.

[0113] For example, in a resource promotion tool, different blocks may include product display area, promotion activity area, user evaluation area, etc. These different areas can be composed of different components.

[0114] In other possible embodiments, the page rendering engine can use the lifecycle manager to parse the configuration protocol information and supplementary protocol configuration information of at least one page, determine the blocks and components in the blocks contained in each page from the configuration protocol information of the created page, initialize the parameters of the components in the blocks according to the configuration protocol information of each page, and preload the components in the blocks.

[0115] Specifically, after the page rendering engine obtains the configuration protocol information and supplementary protocol configuration information of at least one page, it can call the lifecycle hook function of the parsing protocol to parse the configuration protocol information and supplementary protocol configuration information of at least one page, determine the blocks contained in each page from the configuration protocol information of the creation page, that is, from the createInitConfig protocol, and extract the block information required for each page. The block information required for each page can be understood as the components that make up each block.

[0116] Optionally, after the page rendering engine determines the blocks and components within each page, it can initialize the block parameters. Specifically, since the configuration protocol information for each page not only contains the definition of the page blocks, but also specifies in detail the parameter settings required for each block during initialization, each block can be correctly initialized through this configuration protocol information to meet the requirements of the overall page design and business logic. For example, a block may require specific text content, image links, etc. as parameters.

[0117] Optionally, the page rendering engine can also perform block preloading. Specifically, block preloading refers to pre-fetching and storing the required preset or dynamic components within a block before the page is actually rendered. Block preloading can be performed via the "preloader" lifecycle hook function. For example, if a block contains a dynamic ad component, the preloading process will pre-fetch and store the images, videos, and other resources required for the ad component.

[0118] In an embodiment of the present application, before the page is actually rendered, these preset components or dynamic components can be prepared in advance through a preloading operation. When the page is rendered to this block, it can be presented quickly, avoiding the delay caused by real-time acquisition of components and improving the user experience.

[0119] In some possible embodiments, the initialization of block input parameters and the block preloading operation can be performed simultaneously, which can optimize the loading efficiency of the page, shorten the overall page loading time by processing different tasks in parallel, and thus shorten the overall page rendering generation time.

[0120] In the embodiment of the present application, the lifecycle hook function of the parsing protocol mentioned above can be the "onParse" function. This means that in the lifecycle management system of the page rendering engine, the parsing protocol stage is specifically responsible for handling protocol parsing related tasks.

[0121] In an embodiment of the present application, the components in the blocks included in each page include preset components and dynamic components. Optionally, the preset components are built-in general basic components, that is, the preset components represent a portion of the blocks in the page that are pre-set within the page rendering engine, that is, some general or basic page components built into the page rendering engine. Optionally, the dynamic components are taken from external components to meet the application scenarios of different resource promotion tools, that is, the dynamic components can be new page components provided by external umd files with dynamic life cycles or page components customized to meet the different requirements of different application scenarios.

[0122] In this way, some common or basic page components built into the page rendering engine can be used to quickly and easily build page areas and then build pages. New page components provided by external umd files with dynamic life cycles or page components customized to meet the different requirements of different application scenarios can make the page rendering engine flexible and able to meet the page construction requirements in different scenarios according to dynamically changing needs.

[0123] As described above, after the steps of protocol parsing, initialization input and block preloading operations, the embodiment of the present application can complete the preliminary preparations for page construction, and then further perform page rendering and display operations based on the prepared block information.

[0124] In addition, the blocks and block information contained in each page are concentrated in the configuration information of the created page, so as to facilitate initialization and preloading in advance after the blocks and block information are parsed.

[0125] In step S205 , the lifecycle manager calls the renderer, performs page rendering based on the blocks and block information contained in each page, and obtains at least one page in the resource promotion tool.

[0126] In an embodiment of the present application, the page rendering engine can invoke a renderer through a lifecycle manager and use the renderer to render components within each page's blocks based on routing information and block information for each page. The routing information can be parsed and retrieved from the configuration protocol information used to create the page. During the rendering process, the lifecycle manager injects functions corresponding to a reference access mechanism into each page's blocks; optionally, the functions corresponding to the reference access mechanism are used for interaction between blocks.

[0127] Optionally, the page rendering engine can call the renderer through the page rendering lifecycle hook function, and use the renderer to render based on the routing information and the block information of the blocks contained in each page, to generate components in the blocks contained in each page, that is, to generate elements on each page.

[0128] In the embodiment of the present application, the page rendering lifecycle hook function mentioned above can be the "onRender" function. In React, lifecycle hook functions are used to perform specific operations at different life stages of a component. Here, the page rendering engine calls the "onRender" function, which means that when the page rendering-related process starts, a series of rendering-related operations will begin to be executed.

[0129] In an embodiment of the present application, the configuration protocol information for creating a page may include routing information. Routing information is responsible for determining the content to be displayed based on the URL address requested by the user. In other words, routing information determines which page content should be displayed when the user accesses different paths. In this system, based on the current routing information, the page rendering engine can find the corresponding block information.

[0130] In some possible embodiments, block information may include the block's layout, style, data, and so on. This block information can then be used to generate a ReactElement. ReactElement is the foundation for React components and the DOM elements ultimately rendered on the page. By generating a ReactElement, React knows how to render the page block onto the page with the correct structure and style. ReactElement is an object that describes the UI in React.

[0131] In an embodiment of the present application, during the rendering process, a function corresponding to the reference access mechanism is injected into the blocks contained in each page through the lifecycle manager; the function corresponding to the reference access mechanism is used for interaction between blocks.

[0132] Optionally, reactRef (often referred to as ref in React) is a function corresponding to the reference access mechanism, which is a method used to access DOM elements or component instances in functional components or class components. Here, the page rendering engine can inject a reactRef into each page block, which means that each block has a unique reference identifier.

[0133] Optionally, embodiments of the present application can expose this reactRef to the global environment of the lifecycle, making it accessible to different blocks. This allows blocks to interact through this ref. For example, a block can obtain an instance of another block through a ref, and then call its methods, access its status, and so on, enabling data transfer and collaborative operations between blocks.

[0134] Figure 4 This is a schematic diagram of a React component rendering process in front-end development according to an exemplary embodiment. Figure 4 As shown in the figure, it shows that from a set of module blocks, including breadcrumb navigation breadcrumb, table table, custom form kcube_form, modal box form modal_kcube_form, etc., after the default configuration defaultconfig and protocol configuration information protocolconfig, it enters the page rendering stage.

[0135] During the page rendering phase, these modules are converted into React elements ReactElements by creating the React element createReactElement method, such as ReactElement <breadcrumb>、ReactElement

[0136]

[0137]

[0138]

[0139]

[0140] Figure 5 Figure 5

[0141]

[0142]

[0143]

[0144]

[0145]

[0146]

[0147]

[0148]

[0149]

[0150]

[0151]

[0152]

[0153]

[0154]

[0155]

[0156]

[0157] Figure 6

[0158] Figure 6

[0159]

[0160]

[0161]

[0162]

[0163]

[0164]

[0165]

[0166]

[0167]

[0168]

[0169]

[0170]

[0171]

[0172]

[0173]

[0174]

[0175]

[0176]

[0177]

[0178]

[0179]

[0180]

[0181]

[0182]

[0183] Figure 7

[0184] Figure 7

[0185]

[0186]

[0187]

[0188]

[0189]

[0190]

[0191]

[0192]

[0193]

[0194]

[0195]

[0196]

[0197]

[0198]

[0199]

[0200]

[0201] These React elements are connected to the lifecycle manager (lifecycleManager) via the corresponding function (reactRefs) of the access mechanism. The lifecycle manager is responsible for managing the lifecycle of these React components, including operations such as creation, update, and destruction. This entire process demonstrates how modular content can be rendered into an interactive front-end interface through configuration and React mechanisms. In this embodiment of the present application, when the renderer in the page rendering engine detects the completion of the rendering engine's "onRender" function, it means that the page rendering engine has completed the task of generating ReactElements from block information. At this point, the renderer extracts these generated ReactElements and places them into the page's JSX file, completing the page rendering process, essentially "assembling" the ReactElements into the visual page presented to the user. In this embodiment of the present application, the page rendering engine can use a cache manager to cache the configuration protocol information and supplementary configuration protocol information of at least one page, dynamic components, and block information for each block contained in each rendered page. In this embodiment of the present application, when a change in routing information is detected, the system re-executes the entire rendering lifecycle. This is a flowchart illustrating a page generation method according to an exemplary embodiment. As shown, the process includes: in step S207, upon detecting a change in routing information, obtaining updated configuration protocol information for at least one page in the resource promotion tool through the lifecycle manager. In step S209, the updated configuration protocol information and supplementary configuration protocol information for the at least one page are parsed using the lifecycle manager to obtain the blocks and block information contained in each page. In step S211, the lifecycle manager invokes the renderer to render the page based on the changed routing information, the blocks and block information contained in each page, thereby obtaining at least one page in the resource promotion tool. In other words, once routing information changes, it's like the user has switched their "navigation destination." The page rendering engine can re-execute the entire rendering lifecycle, including the steps of obtaining the protocol, parsing the protocol, and rendering the page, in order to redetermine and display the corresponding page content based on the new routing information. In this embodiment of the present application, although the rendering lifecycle must be re-executed, the steps of obtaining the protocol and rendering the page can directly obtain relevant data from the cache manager, eliminating the need for repeated execution. Because these steps may involve some data acquisition and processing operations, which are relatively time-consuming, using cache can reduce unnecessary repeated calculations, improve the efficiency of page re-rendering, and allow users to see the page content corresponding to the new routing information more quickly.In an embodiment of the present application, after step S201, that is, after obtaining the configuration protocol information of at least one page in the resource promotion tool through the lifecycle manager, the page rendering engine can use the lifecycle manager to obtain a supplementary file from a preset file address. The preset file address is obtained from the configuration protocol information of the created page. The supplementary configuration protocol information in the supplementary file may include the configuration protocol information of the custom page or the configuration protocol information of the custom block in at least one page. Optionally, the supplementary configuration protocol information can be configured by the provider of the resource promotion tool according to the configuration requirements required by the user of the resource promotion tool. Then, the page rendering engine can use the lifecycle manager to parse the configuration protocol information and the supplementary configuration protocol information of at least one page, obtain the blocks and block information contained in each page, and call the renderer through the lifecycle manager to perform page rendering based on the blocks and block information contained in each page, thereby obtaining at least one page in the resource promotion tool. Specifically, to meet certain tool customization requirements, including the customization of new pages or new components within a page, the page rendering engine, after obtaining the protocol, can call the injectLifecycle lifecycle hook function based on the page creation configuration protocol information (i.e., the default file address for the dynamic lifecycle, such as the umd file address, provided in the createInitConfig protocol). This function then requests this supplementary file, or umd file. Subsequently, the supplementary configuration protocol information defined in this file, namely the custom lifecycle, can be injected into and overwrite the page rendering engine's built-in lifecycles, injecting all lifecycles into the execution context. Of course, this does not overwrite its own lifecycles or any onGetProtocols that were executed before it. In this embodiment of the present application, the page rendering engine can be configured with a general stability detection scheme that reports real-time page views, unique views, jserrors, API call success rates, page performance, and more for the resource promotion tool page. Furthermore, tracking data is recorded throughout the page rendering engine's entire lifecycle, allowing statistics to be collected on the creation success rate, creation failure reasons, and creation efficiency of each resource promotion tool for data analysis. In summary, the lifecycle manager in the page rendering engine is responsible for managing each stage of the page rendering engine, from obtaining the agreement to the final rendering of the page, which can have the following beneficial effects: (1) It can improve the R&D efficiency, delivery quality and R&D stability of the R&D resource promotion tool; (2) It can be quickly iterated with zero code through configuration, without the need for source code development from scratch; (3) It has dynamic and configurable capabilities, so that the page elements and information of the resource promotion tool can be quickly changed and adjusted, improving the flexibility of business strategy adjustment; (4) It provides a unified tracking and detection solution, so that the resource promotion tool can run stably, safely and efficiently. This is a block diagram of a page generation device according to an exemplary embodiment.The device has the function of implementing the data processing method in the above-mentioned method embodiment, and the function can be implemented by hardware or by hardware executing corresponding software. Referring to the embodiment, the device includes a protocol acquisition module 601, a protocol parsing module 602 and a page rendering module 603: the protocol acquisition module 601 is configured to execute the acquisition of configuration protocol information of at least one page in the resource promotion tool through the lifecycle manager; the protocol parsing module 602 is configured to execute the parsing of the configuration protocol information and supplementary configuration protocol information of at least one page using the lifecycle manager to obtain the blocks and block information contained in each page; the supplementary configuration protocol information is obtained through the preset file address contained in the configuration protocol information of at least one page; the supplementary configuration protocol information is configured by the provider of the resource promotion tool according to the configuration requirements required by the user of the resource promotion tool; the page rendering module 603 is configured to execute the call of the renderer through the lifecycle manager, and perform page rendering based on the blocks and block information contained in each page to obtain at least one page in the resource promotion tool. In some possible embodiments, the protocol acquisition module is configured to execute: when the application party of the resource promotion tool is the first application party, obtaining the configuration protocol information of the creation page, the configuration protocol information of the management page and the configuration protocol information of the data page through the lifecycle manager; the first application party is the resource provider of the resources promoted by the resource promotion tool; the creation page is used for creating activities, rules or content in the resource promotion tool; the management page is used for managing activities, products or objects in the resource promotion tool; or; when the application party of the resource promotion tool is the second application party, obtaining the configuration protocol information of the creation page and the configuration protocol information of the management page through the lifecycle manager; the second application party is the provider of the resource promotion tool. In some possible embodiments, the protocol parsing module is configured to: parse the configuration protocol information and supplementary configuration protocol information of at least one page using a lifecycle manager, and determine the blocks and components within each block contained in each page from the configuration protocol information of the created page; the components within the block include preset components and dynamic components; the preset components are built-in general basic components; the dynamic components are external components taken to meet the application scenarios of different resource promotion tools; the device also includes an initialization module configured to: initialize the parameters of the components within the block according to the configuration protocol information of each page, and preload the components within the block. In some possible embodiments, the page rendering module is configured to: call a renderer via the lifecycle manager, and use the renderer to render based on routing information and block information of the blocks contained in each page to obtain the components within the blocks contained in each page; the routing information is parsed and obtained from the configuration protocol information of the created page; during the rendering process, inject functions corresponding to the reference access mechanism into the blocks contained in each page via the lifecycle manager; the functions corresponding to the reference access mechanism are used for interaction between blocks.In some possible embodiments, the protocol acquisition module is configured to, upon detecting a change in routing information, acquire updated configuration protocol information for at least one page in the resource promotion tool through the lifecycle manager. The protocol parsing module is configured to utilize the lifecycle manager to parse the updated configuration protocol information and supplementary configuration protocol information for at least one page, obtaining the blocks and block information contained in each page. The page rendering module is configured to, through the lifecycle manager, invoke a renderer to render the page based on the changed routing information, the blocks and block information contained in each page, thereby obtaining at least one page in the resource promotion tool. In some possible embodiments, the apparatus further includes a cache module configured to, through the lifecycle manager, invoke a cache manager, utilizing the cache manager to cache the configuration protocol information and supplementary configuration protocol information for at least one page, dynamic components, and block information for blocks contained in each rendered page. In some possible embodiments, the protocol parsing module is configured to: utilize a lifecycle manager to obtain a supplementary file from a preset file address; the preset file address is obtained from the configuration protocol information of the created page; the supplementary configuration protocol information in the supplementary file includes configuration protocol information for a custom page or configuration protocol information for a custom block within at least one page; and utilize the lifecycle manager to parse the configuration protocol information and supplementary configuration protocol information of at least one page to obtain the blocks and block information contained in each page. It should be noted that the apparatus provided in the above embodiments, when implementing its functions, is only illustrated by the division of the above functional modules. In actual applications, the above functions can be assigned to different functional modules as needed, i.e., the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. Furthermore, the apparatus and method embodiments provided in the above embodiments are based on the same concept. The specific implementation process is detailed in the method embodiment and will not be further described here. FIG. is a block diagram of an apparatus 3000 for page generation according to an exemplary embodiment. For example, apparatus 3000 can be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc. 3000 may include one or more of the following components: a processing component 3002, a memory 3004, a power component 3006, a multimedia component 3008, an audio component 3010, an input / output (I / O) interface 3012, a sensor component 3014, and a communication component 3016. The processing component 3002 generally controls the overall operation of the device 3000, such as operations associated with display, phone calls, data communications, camera operation, and recording operations. The processing component 3002 may include one or more processors 3020 to execute instructions to perform all or part of the steps of the above-described method.Furthermore, processing component 3002 may include one or more modules to facilitate interaction between processing component 3002 and other components. For example, processing component 3002 may include a multimedia module to facilitate interaction between multimedia component 3008 and processing component 3002. Memory 3004 is configured to store various types of data to support operations on device 3000. Examples of such data include instructions for any application or method operating on device 3000, contact data, phone book data, messages, images, videos, and the like. Memory 3004 may be implemented using any type of volatile or non-volatile memory device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk, or optical disk. Power supply component 3006 provides power to the various components of device 3000. The power component 3006 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 3000. The multimedia component 3008 includes a screen that provides an output interface between the device 3000 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, it may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. The touch sensors may not only sense the boundaries of a touch or slide action, but also the duration and pressure associated with the touch or slide action. In some embodiments, the multimedia component 3008 includes a front-facing camera and / or a rear-facing camera. When the device 3000 is in an operating mode, such as a capture mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each of the front-facing and rear-facing cameras may include a fixed optical lens system or have focal length and optical zoom capabilities. The audio component 3010 is configured to output and / or input audio signals. For example, the audio component 3010 includes a microphone (MIC), which is configured to receive external audio signals when the device 3000 is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal can be further stored in the memory 3004 or sent via the communication component 3016. In some embodiments, the audio component 3010 also includes a speaker for outputting audio signals. The I / O interface 3012 provides an interface between the processing component 3002 and the peripheral interface module, which can be a keyboard, a click wheel, a button, etc. These buttons may include but are not limited to: a home button, a volume button, a start button, and a lock button.Sensor assembly 3014 includes one or more sensors for providing various status assessments of device 3000. For example, sensor assembly 3014 can detect the open / closed state of device 3000, the relative positioning of components, such as the display and keypad of device 3000. Sensor assembly 3014 can also detect changes in the position of device 3000 or a component thereof, the presence or absence of user contact with device 3000, the orientation or acceleration / deceleration of device 3000, and changes in the temperature of device 3000. Sensor assembly 3014 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 3014 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 3014 may also include an accelerometer, a gyroscope, a magnetic sensor, a pressure sensor, or a temperature sensor. Communication assembly 3016 is configured to facilitate wired or wireless communication between device 3000 and other devices. The device 3000 can access a wireless network based on a communication standard, such as WiFi, an operator network (such as 2G, 3G, 4G or 5G), or a combination thereof. In an exemplary embodiment, the communication component 3016 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 3016 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies. In an exemplary embodiment, the device 3000 can be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components to perform the above method. An embodiment of the present invention further provides a computer-readable storage medium, which can be provided in an electronic device to store at least one instruction or at least one program for implementing a page generation method. The at least one instruction or the at least one program is loaded and executed by the processor to implement the page generation method provided in the above method embodiment. In an exemplary embodiment, a storage medium including instructions is also provided, such as a memory 3004 including instructions. The instructions can be executed by the processor 3020 of the device 3000 to complete the above method. Optionally, the storage medium can be a non-transitory computer-readable storage medium, for example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.Embodiments of the present invention further provide a computer-readable storage medium. When the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to perform any of the methods of the first aspect of the embodiments of the present disclosure. Embodiments of the present invention further provide a computer program product, comprising a computer program stored in a readable storage medium. At least one processor of a computer device reads and executes the computer program from the readable storage medium, causing the computer device to perform any of the methods of the first aspect of the embodiments of the present disclosure. It should be noted that the order of the embodiments of the present invention described above is for descriptive purposes only and does not represent the superiority or inferiority of the embodiments. Furthermore, the above descriptions of specific embodiments of this specification are provided. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the figures do not necessarily require the specific or sequential order shown to achieve the desired results. In certain embodiments, page generation and parallel processing are also possible or may be advantageous. The various embodiments in this specification are described in a progressive manner. Similar parts between the various embodiments can be referenced. Each embodiment focuses on the differences from other embodiments. In particular, for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment. A person of ordinary skill in the art can understand that all or part of the steps of the above embodiment can be completed by hardware, or can be completed by a program to instruct the relevant hardware, and the program can be stored in a computer-readable storage medium, and the above-mentioned storage medium can be a read-only memory, a magnetic disk or an optical disk, etc. The above is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention. < / breadcrumb>

Claims

1. A page generation method, characterized in that: include: Obtaining, through the lifecycle manager, configuration protocol information of at least one page in the resource promotion tool; Parsing the configuration protocol information and the supplementary configuration protocol information of the at least one page using the lifecycle manager to obtain blocks and block information included in each page; The supplementary configuration protocol information is obtained through the preset file address included in the configuration protocol information of the at least one page; the supplementary configuration protocol information is configured by the provider of the resource promotion tool according to the configuration requirements required by the user of the resource promotion tool; The lifecycle manager calls a renderer, and page rendering is performed based on the blocks and block information contained in each page to obtain at least one page in the resource promotion tool.

2. The page generation method according to claim 1, characterized in that: The acquiring, through the lifecycle manager, configuration protocol information of at least one page in the resource promotion tool includes: When the resource promotion tool is applied by a first application party, configuration protocol information of a creation page, configuration protocol information of a management page, and configuration protocol information of a data page are obtained through the lifecycle manager; the first application party is the resource provider of the resources promoted by the resource promotion tool; the creation page is used to create activities, rules, or content in the resource promotion tool; and the management page is used to manage activities, products, or objects in the resource promotion tool; or; When the application party of the resource promotion tool is a second application party, the configuration protocol information of the creation page and the configuration protocol information of the management page are obtained through the lifecycle manager; the second application party is the provider of the resource promotion tool.

3. The page generation method according to claim 2, characterized in that: The utilizing the lifecycle manager to parse the configuration protocol information and the supplementary configuration protocol information of the at least one page to obtain the blocks and block information contained in each page includes: The lifecycle manager is used to parse the configuration protocol information and supplementary configuration protocol information of the at least one page, and determine the blocks and components in the blocks contained in each page from the configuration protocol information of the created page; the components in the blocks include preset components and dynamic components; the preset components are built-in general basic components; the dynamic components are external components to meet the application scenarios of different resource promotion tools; The method further comprises: Initialize parameters of the components in the block according to the configuration protocol information of each page, and preload the components in the block.

4. The page generation method according to claim 3, characterized in that: The step of calling the renderer by the lifecycle manager to render the page based on the blocks and block information contained in each page to obtain at least one page in the resource promotion tool includes: The lifecycle manager calls the renderer, and the renderer is used to render based on routing information and block information of the blocks included in each page, to obtain components in the blocks included in each page; the routing information is parsed and obtained from the configuration protocol information of the created page; During the rendering process, the functions corresponding to the reference access mechanism are injected into the blocks contained in each page through the lifecycle manager; the functions corresponding to the reference access mechanism are used for interaction between blocks.

5. The page generation method according to any one of claims 1 to 4, characterized in that: The method further comprises: When a change in routing information is detected, obtaining updated configuration protocol information of at least one page in the resource promotion tool through the lifecycle manager; Parsing the updated configuration protocol information and the supplementary configuration protocol information of the at least one page using the lifecycle manager to obtain blocks and block information included in each page; The lifecycle manager calls a renderer to perform page rendering based on the changed routing information, the blocks contained in each page, and the block information, to obtain at least one page in the resource promotion tool.

6. The page generation method according to claim 4, characterized in that: The method further comprises: The cache manager is called by the lifecycle manager, and the cache manager is used to cache the configuration protocol information and the supplementary configuration protocol information of the at least one page, the dynamic component, and the block information of the blocks included in each rendered page.

7. The page generation method according to any one of claims 1 to 4, characterized in that: The utilizing the lifecycle manager to parse the configuration protocol information and the supplementary configuration protocol information of the at least one page to obtain the blocks and block information contained in each page includes: Obtaining a supplementary file from the preset file address using the lifecycle manager; the preset file address is obtained from the configuration protocol information of the created page; the supplementary configuration protocol information in the supplementary file includes the configuration protocol information of the custom page or the configuration protocol information of the custom block in the at least one page; The configuration protocol information of the at least one page and the supplementary configuration protocol information are parsed using the lifecycle manager to obtain blocks and block information contained in each page.

8. A page generating device, characterized in that: include: a protocol acquisition module configured to acquire configuration protocol information of at least one page in the resource promotion tool through the lifecycle manager; a protocol parsing module configured to parse the configuration protocol information and the supplementary configuration protocol information of the at least one page using the lifecycle manager to obtain blocks and block information contained in each page; The supplementary configuration protocol information is obtained through the preset file address included in the configuration protocol information of the at least one page; the supplementary configuration protocol information is configured by the provider of the resource promotion tool according to the configuration requirements required by the user of the resource promotion tool; The page rendering module is configured to execute calling the renderer through the lifecycle manager, perform page rendering based on the blocks and block information contained in each page, and obtain at least one page in the resource promotion tool.

9. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the page generation method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that When the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the page generating method according to any one of claims 1 to 7.

11. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the page generation method according to any one of claims 1 to 7 is implemented.

Images