Page generation method and device and page template generation method and device

Abstract

The invention discloses a page generation method and device and a page template generation method and device, and relates to the technical field of software development. The method comprises the steps of obtaining at least one page template corresponding to scene features, determining a first page template from the at least one page template, and generating a page according to the first page template. In the page generation process, the page templates are obtained according to the scene features, and one page template is selected from the obtained page templates to generate a page. The page template is obtained according to the scene characteristics, so that the page template is related to the business scene corresponding to the scene characteristics. The user does not need to consider the business scene suitable for the page template in the template selection process, the page template can be directly selected from the page templates related to the business scene, and the template selection difficulty can be reduced.

Description

Page generation method, page template generation method, and device Technical Field

[0001] The present application relates to the field of software development technology, and in particular to a page generation method, a page template generation method, and a device. Background Art

[0002] Low-code development is a method of interactively developing applications through a graphical interface. This method allows users to complete application development in a more efficient way through graphical drag and drop, parameter configuration, etc.

[0003] During the application building process, multiple page models can be recommended to users. Users can select page templates that meet their needs from multiple page templates to generate pages in the application, thereby improving the efficiency of application building.

[0004] When selecting a page template, users need to choose a template that meets their needs from a large number of templates. This requires not only clarifying their needs but also determining the scenarios in which different page templates are suitable. However, during application development, users often lack a clear understanding of their needs and are unable to accurately determine the scenarios in which different page templates are suitable, making page template selection more difficult.

[0005] Application Contents

[0006] The purpose of the embodiments of the present application is to provide a page generation method, a page template generation method, and a device, including but not limited to solving the problem of difficulty in selecting page templates during low-code construction.

[0007] In a first aspect, a page generation method is provided, the method further comprising:

[0008] Obtain at least one page template corresponding to the scene feature;

[0009] determining a first page template from the at least one page template;

[0010] Generate a page according to the first page template.

[0011] In the embodiment of the present application, during the page generation process, page templates are obtained based on scenario characteristics, and a page template is selected from the obtained page templates to generate the page. Because the page templates are obtained based on scenario characteristics, the page templates are related to the business scenario corresponding to the scenario characteristics. During the template selection process, the user does not need to consider the business scenario to which the page template applies; they can directly select a page template from the page templates related to the business scenario, which can reduce the difficulty of template selection.

[0012] In one embodiment, before obtaining at least one page template corresponding to the scene feature, the method further includes:

[0013] Obtain scene feature sets based on user portraits;

[0014] The scene feature is determined from the scene feature set.

[0015] In an embodiment of the present application, a scene feature set is obtained based on the user portrait, and scene features in the scene feature set are recommended to the user. This allows the scene features recommended to the user to be relevant to the user, so that the page template recommended to the user based on the scene features can be closer to the user's needs, thereby reducing the difficulty for the user to select a template.

[0016] In one embodiment, the page template includes a plurality of first blocks. Before generating a page according to the first page template, the method further includes:

[0017] determining a component selected by a user for the first block;

[0018] The components selected by the user for the first block are arranged in the first block.

[0019] In an embodiment of the present application, blocks for placing components are arranged in the page template, and users can layout components in the page based on the blocks. Since multiple blocks in the page template are arranged in the page template according to a certain layout structure, there is no need to adjust the layout of the page after laying out the components, which can reduce the workload during page layout and improve the efficiency of application construction.

[0020] In one embodiment, determining the component selected by the user for the first block includes:

[0021] Acquire at least one candidate component according to the scene feature and / or the first block;

[0022] The component selected by the user for the first block is determined from the at least one candidate component.

[0023] In an embodiment of the present application, multiple alternative components are recommended to the user based on the block and / or scene characteristics. Since the components recommended to the user are related to the block and / or the business scenario corresponding to the scene characteristics, it is convenient for the user to select the components related to the block and / or business scenario and layout them in the block, thereby allowing the user to quickly and accurately select the component layout in the page template.

[0024] In one embodiment, the method further comprises:

[0025] determining at least one data set based on the component;

[0026] determining a target data set configured by a user for the component from the at least one data set;

[0027] Set the target dataset as the data source of the component.

[0028] In an embodiment of the present application, when a user configures a data set for a component, one or more data sets can be obtained based on the component, allowing the user to select a data set from at least one data set as the data source of the component, which can improve the editing efficiency of the component and thus improve the efficiency of application construction.

[0029] In one embodiment, determining at least one data set according to the component includes:

[0030] determining the at least one data set according to the component and the first block in which the component is located;

[0031] Alternatively, determining the at least one data set based on the scene characteristics and the component;

[0032] Alternatively, the at least one data set is determined according to the component, the scene feature, and the first block where the component is located.

[0033] In an embodiment of the present application, during the process of editing a component, the electronic device can recommend a data set to the user based on the component and the block in which the component is located, or recommend data to the user based on the scene characteristics corresponding to the component and the page template, or recommend a data set to the user based on the component, the scene characteristics and the block. This can make the data set not only related to the component, but also related to the business scenario and / or block, making the recommended data set more accurate, and can facilitate the user to quickly set an accurate data source for the component, thereby improving page layout efficiency.

[0034] In one embodiment, the method further comprises:

[0035] obtaining at least one component model according to the component;

[0036] determining a target component model selected by a user for the component from the at least one component model;

[0037] The properties of the component are configured according to the property parameters in the target component model.

[0038] In an embodiment of the present application, a component model is obtained based on the component, and the properties of the component are configured according to the property parameters in the component model. This can facilitate users to quickly set the properties of the component, thereby improving the editing efficiency of the component.

[0039] In one embodiment, obtaining at least one component model according to the component includes:

[0040] Acquire the at least one component model according to the scene feature and the component;

[0041] Alternatively, the at least one component model is obtained according to a data set configured by a user for the component and the component;

[0042] Alternatively, the at least one component model is obtained based on a data set configured by a user for the component, the component, and the scene feature.

[0043] In an embodiment of the present application, when obtaining a component model, the component model corresponding to the component is obtained based on the component, as well as the scenario characteristics and / or the data set. This allows the component model to be related to the business scenario corresponding to the scenario characteristics and / or to the data set that the component is frequently configured with. This allows the component model recommended to the user to be more in line with user needs, thereby facilitating the user to quickly adjust the component model to obtain component properties that meet their needs.

[0044] In one embodiment, before generating a page according to the first page template, the method further includes:

[0045] Acquire at least one page topic according to the scene feature;

[0046] Determining a target page theme selected by a user for the first page template from the at least one page theme;

[0047] The appearance of the first page template is configured according to the appearance parameters in the target page theme.

[0048] In an embodiment of the present application, page themes are recommended to users based on the scenario features corresponding to the page template, so that the page theme can be related to the business scenario corresponding to the scenario features, so that the page appearance set according to the page theme is suitable for the corresponding business scenario, thereby allowing users to quickly and accurately adjust the appearance of the page.

[0049] In one embodiment, before generating a page according to the first page template, the method further includes:

[0050] determining a second page template when the first page template does not match, wherein a plurality of second blocks are arranged in the second page template;

[0051] When the first block and the second block are the same block, the components arranged in the first block are arranged in the second block.

[0052] In an embodiment of the present application, during the process of replacing a page template, the electronic device can arrange the components in the block before the replacement in the same block after the replacement, which can reduce the workload after replacing the page template and thus improve the efficiency of application construction.

[0053] In one embodiment, before obtaining at least one page template corresponding to the scene feature, the method includes:

[0054] Get a pre-generated page;

[0055] Generating the page template according to the pre-set page;

[0056] The scene feature corresponding to the page template is obtained from the pre-generated page.

[0057] In one embodiment, a block corresponding to each component in the pre-generated page is arranged in the page template, and the position of the block in the page template is the same as the position of the corresponding component in the page.

[0058] In one embodiment, the method further comprises:

[0059] Setting a unique block identifier for the block in the page template;

[0060] A first component tag is set for the component corresponding to the block according to the block identifier of the block.

[0061] In one embodiment, the method further includes: setting a second component tag for the component in the pre-generated page according to the scenario feature.

[0062] In one embodiment, the method further includes: constructing a component model based on the attribute information of the component included in the pre-generated page; and generating a first model tag of the component model based on the component identifier of the component included in the pre-generated page.

[0063] In one embodiment, the method further includes: generating a second model tag for the component model according to the scene feature.

[0064] In one embodiment, the method further comprises: generating a third model tag of the component model according to a dataset identifier of the dataset, when the component included in the pre-generated page is configured with a dataset.

[0065] In one embodiment, the method further includes: generating a page theme according to the appearance parameters of the pre-generated page; and generating a theme tag of the page theme according to the scene characteristics.

[0066] In one embodiment, the method further includes: generating behavior information when the user configures a data set for the component, wherein the behavior information includes a component identifier of the component and a data set identifier of the data set.

[0067] In one embodiment, the behavior information further includes the scene feature and / or the block identifier of the first block where the component is located.

[0068] In a second aspect, a method for generating a page template is provided, the method comprising:

[0069] Get the page;

[0070] Generate a page template according to the page;

[0071] Acquire scene features of the page from the page;

[0072] A template tag of the page template is generated according to the scene feature.

[0073] In one embodiment, a block corresponding to each component in the page is arranged in the page template, and the position of the block in the page template is the same as the position of the corresponding component in the page.

[0074] In one embodiment, the method further includes: setting a unique block identifier for the block; and setting a first component tag for the component corresponding to the block according to the block identifier.

[0075] In one embodiment, the method further includes: setting a second component tag for the component according to the scene feature.

[0076] In one embodiment, the method further includes: constructing a component model according to the attribute parameters of the component; and generating a first model tag of the component model according to the component identifier of the component.

[0077] In one embodiment, the method further includes: generating a second model tag for the component model according to the scene feature.

[0078] In one embodiment, the method further includes: generating a third model tag of the component model according to a dataset identifier of the dataset when the component is configured with a dataset.

[0079] In one embodiment, the method further includes: generating a page theme according to the appearance parameters of the page; and generating a theme tag of the page theme according to the scene characteristics.

[0080] In a third aspect, a page generation device is provided, the device comprising:

[0081] A first acquisition module is used to acquire at least one page template corresponding to the scene feature;

[0082] A first determining module, configured to determine a first page template from the at least one page template;

[0083] The first generating module is used to generate a page according to the first page template.

[0084] In a fourth aspect, a device for generating a page template is provided, the device comprising:

[0085] The first acquisition module is used to acquire the page;

[0086] A first generating module, configured to generate a page template according to the page;

[0087] A second acquisition module is used to acquire the scene feature of the page from the page;

[0088] The second generating module is used to generate a template tag of the page template according to the scene feature.

[0089] In a fifth aspect, an electronic device is provided, comprising the apparatus as described in the third aspect or the fourth aspect.

[0090] In a sixth aspect, a readable storage medium is provided, wherein the readable storage medium is used to store computer program code. When the computer program code is executed by an electronic device, the electronic device executes the method as described in the first aspect or the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0092] Figure 1 is a flowchart of a low-code application construction process provided in an embodiment of the present application.

[0093] FIG2 is a flowchart showing the steps of a method for generating a page template provided in an embodiment of the present application.

[0094] FIG3 is a schematic diagram of a generation principle of a page template provided in an embodiment of the present application.

[0095] FIG4 is a schematic diagram of the structure of a page template provided in an embodiment of the present application.

[0096] FIG5 is a schematic structural diagram of another page template provided in an embodiment of the present application.

[0097] FIG6 is a schematic structural diagram of another page template provided in an embodiment of the present application.

[0098] FIG7 is a schematic diagram of a step flow of a page generation method provided in an embodiment of the present application.

[0099] Figure 8 is a schematic diagram of the operating interface of a low-code platform provided in an embodiment of the present application.

[0100] Figure 9 is a schematic diagram of the operating interface of another low-code platform provided in an embodiment of the present application.

[0101] Figure 10 is a schematic diagram of the operating interface of another low-code platform provided in an embodiment of the present application.

[0102] Figure 11 is a schematic diagram of the operating interface of another low-code platform provided in an embodiment of the present application.

[0103] Figure 12 is a schematic diagram of the operating interface of another low-code platform provided in an embodiment of the present application.

[0104] Figure 13 is a schematic diagram of the operating interface of another low-code platform provided in an embodiment of the present application.

[0105] FIG14 is a flow chart of a page generation method provided in an embodiment of the present application.

[0106] FIG15 is a schematic structural diagram of a page generating device provided in an embodiment of the present application.

[0107] FIG16 is a schematic structural diagram of a device for generating a page template provided in an embodiment of the present application.

[0108] FIG17 is a schematic structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0109] In order to make the purpose, technical solutions and advantages of this application more clearly understood, the present application is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit this application.

[0110] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this application belongs; the terms used herein are for the purpose of describing specific embodiments only and are not intended to limit this application. The terms "including" and "having" and any variations thereof in the specification and claims of this application and the accompanying drawings are intended to cover non-exclusive inclusions.

[0111] In the description of the embodiments of this application, the terms "first," "second," etc. are used only to distinguish different objects and should not be understood to indicate or imply relative importance or to implicitly indicate the quantity, specific order, or primary and secondary relationship of the indicated technical features. In the description of the embodiments of this application, the meaning of "plurality" is more than two, unless otherwise specifically defined.

[0112] In the description of the embodiments of this application, the term "and / or" is simply a description of the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent the following three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally indicates that the associated objects are in an "or" relationship.

[0113] To facilitate understanding of this application, we first briefly introduce the process of building an application with low code.

[0114] FIG1 is a schematic diagram of a process for building a low-code application according to an embodiment of the present application. The method may include the following steps:

[0115] Step 101: Create a page in the application.

[0116] Among them, in the process of developing applications using low-code construction, the user first creates a page in the application. After creating the page, execute steps 102 to 104 in sequence, select the components that need to be laid out in the page, arrange the page, and edit the components in the page.

[0117] Components are elements on a page, such as titles, input boxes, buttons, forms, pie charts, and bar charts, but are not limited thereto.

[0118] Step 102: Select components that need to be laid out on the page.

[0119] In some embodiments, components of the same type are grouped together. In the process of selecting components, the user first determines the component type that needs to be placed on the page, then searches for and determines the component among multiple components of the corresponding component type, and finally places the component on the page.

[0120] Step 103: Layout the page.

[0121] During the page editing process, one task is to adjust the page layout. Since the page layout is related to each component in the page, the user needs to comprehensively consider the position of each component in the page and adjust the position of each component to make the page layout consistent with user needs.

[0122] During the page layout process, another task is to edit the page appearance, page events, and page behavior. When editing the page appearance, the user needs to edit the page's background color, background image, font, font color, font size, border color, border size, button size, button color, line spacing, and cascading style sheets (CSS), etc., so that the page's appearance meets user needs. When editing page behavior, the user needs to edit the page's closing, jumping, flipping, and displaying behaviors, but is not limited to these. When editing page events, it is necessary to edit the reasons that trigger each page behavior, such as setting the triggering event for the closing behavior to clicking the close button.

[0123] Step 104: Edit the component.

[0124] When editing a component on a page, you need to edit its appearance, events, and behavior. Component appearance includes, but is not limited to, its color, size, and shape. Component events include, but are not limited to, display, move, and input events. When editing component events, you need to edit the conditions that trigger each component's behavior, for example, setting the trigger for an input event to click an input button.

[0125] It should be noted that step 103 and step 104 may be performed simultaneously or in steps. When the application includes multiple pages, steps 101 to 104 are executed in a loop to create multiple pages in the application.

[0126] As shown in Figure 1, during the low-code construction process, it is necessary to create pages, adjust page layouts, edit the appearance, events, and behaviors of pages, and edit the appearance, events, and behaviors of components. The workload is relatively large and the time required is relatively long.

[0127] In related technologies, in order to improve the efficiency of low-code construction, multiple page models can be recommended to users. Users can select a page template that meets their needs from multiple page templates and generate a page based on the selected page template. In the page template selection process, users need to select a page template that meets their needs from a large number of page templates according to their own needs, so that users not only need to clarify their own needs, but also need to determine the scenarios for which different page templates are applicable. In the application construction process, users are usually not clear about their own needs, and users cannot accurately determine the scenarios for which different page templates are applicable. Therefore, the selection of page templates is more difficult.

[0128] To address the above technical issues, an embodiment of the present application provides a page generation method that, during the page generation process, recommends page templates to users based on scenario characteristics. The scenario characteristics correspond to the business scenarios to which the page templates are applicable, so that the page templates recommended to users are relevant to the business scenarios. During the template selection process, users do not need to consider the business scenarios to which the page templates are applicable; they can directly select a page template from page templates related to the business scenarios, thereby reducing the difficulty of selecting a page template.

[0129] FIG2 is a flow chart illustrating the steps of a method for generating a page template provided in an embodiment of the present application. The method is applicable to electronic devices, such as, but not limited to, personal computers (PCs), tablet computers, laptop computers, servers, and server clusters. The following embodiments describe the method for generating a page template using a server as an example; other electronic devices may refer to the server.

[0130] As shown in FIG2 , the method for generating a page template may include the following steps:

[0131] Step 21: Get the page.

[0132] Step 22: Generate a page template based on the page.

[0133] The page is a pre-generated, existing page with various components arranged therein. The server may obtain the existing page and generate a page template based on the obtained page.

[0134] In one embodiment, a server can use a web crawler to retrieve web pages (i.e., web pages) from a website from the internet, and after retrieval, generate a page template based on the pages. FIG3 is a schematic diagram of a page template generation principle provided by an embodiment of the present application. Taking website A and website B shown in FIG3 as an example, a server can use a web crawler to retrieve the web pages of website A from the internet, generate page template A based on the retrieved web pages, and retrieve the web pages of website B from the internet, and generate page template B based on the retrieved web pages.

[0135] For example, when generating a page template, the server can directly use the page of website A obtained as page template A and store page template A in the template library. Similarly, after obtaining the webpage of website B, the obtained webpage can be directly used as page template B.

[0136] The above are merely illustrative examples, and the method for an electronic device to obtain a page and generate a page template based on the page may include but is not limited to the above examples.

[0137] Step 23: Obtain scene features of the page from the page.

[0138] Step 24: Generate a template tag for the page template based on the scene characteristics.

[0139] In this embodiment, during the process of generating a page template, the electronic device may obtain scenario features describing the business scenario of the page from the page, so as to generate a template tag of the page template according to the scenario features.

[0140] In one embodiment, a scenario feature can be relevant information on a webpage, such as industry information, company information, product information, website type information, and keywords. This relevant information describes the business scenario for which the webpage applies. As shown in Figure 3, the electronic device can analyze the information included in the webpage of website A to extract relevant information about website A and use the extracted relevant information as scenario feature A for the business scenario for which the webpage on website A applies. The electronic device can set scenario feature A as a template tag for page template A, and store the template tag and page template A in the template library.

[0141] Similarly, relevant information can be extracted from the web page of website B, and the extracted relevant information can be used as scene feature B. Scene feature B is set as the template tag of page template B and stored in the template library corresponding to page template B.

[0142] The template tag is used to establish an association between a page template and the business scenario to which it applies, so as to recommend page templates corresponding to the business scenario to the user based on the template tag. For example, when page template A is recommended to the user based on its template tag, since the template tag is related to the business scenario to which page template A applies, the page template A recommended to the user can be related to the business scenario to which page template A applies.

[0143] The above are merely illustrative examples. The method for an electronic device to obtain scene features and generate template tags based on the scene features may include but is not limited to the above examples.

[0144] Optionally, a block corresponding to each component in the page is arranged in the page template, and the position of the block in the page template is the same as the position of the corresponding component in the page.

[0145] In one embodiment, during the process of generating a page template, the server may generate the page template based on the layout of components on the page, wherein the page template includes a block corresponding to each component on the page, where the block is used to place the component. For example, the server may first determine the location of each component on the page and generate a blank page template having the same size as the page. The server may then determine a position in the blank page template corresponding to the location of the component and place the block corresponding to the component in the determined position, thereby obtaining a page template having a plurality of blocks arranged therein.

[0146] Figure 4 is a schematic diagram of the structure of a page template provided in an embodiment of the present application. As shown in Figure 4, blocks are indicated in the form of solid-line frames in page template 4. Page template 4 has a left-right bottom structure, with block 41 set on the left side of page template 4, block 42 set on the bottom, and block 43 set on the upper right side. The area within the dotted frame is the lower right side, and multiple blocks 44 are set in sequence from top to bottom in the lower right side.

[0147] As shown in Figure 3, in the process of generating a page template 4 based on a page, the server can determine the components such as pictures, forms, buttons and titles laid out in the page through the document object model (DOM) and / or image recognition, and determine the position of the components in the page, and the position can be determined by the coordinates of the components in the page. For example, if it is determined that a title component is set at the upper position of the page, the upper position is such as the position of block 43 in the page template. After determining the position of the title component in the page, the corresponding upper position is determined in the blank page template 4 according to the coordinates of the title component, and then block 41 is set at this position. Similarly, each block in the page template 4 can be generated.

[0148] Figure 5 is a schematic diagram of the structure of another page template provided in an embodiment of the present application. Page template 5 has a top-center-bottom structure. The top portion of page template 5 is marked with block 51; the area within the dotted box is the center portion of page template 5, with block 52 marked on the left side of the center, block 53 marked in the middle of the center, and block 54 marked on the right side of the center; and block 55 marked on the bottom portion of page template 5.

[0149] Figure 6 is a schematic diagram of another page template provided by an embodiment of the present application. The page template 6 is a left-center-right structure, with a block 61 marked on the left side of the page template 6, a block 62 marked on the right side, and multiple blocks 63 marked in sequence from top to bottom in the middle.

[0150] Among them, since the position of each block in the page template has been determined and arranged in the page template according to predetermined rules, when building an application based on the page template, the user only needs to place components in the group block, and does not need to adjust the position of the components in the page, which can improve the efficiency of component layout.

[0151] The above examples are merely illustrative, and specific methods for generating page templates may include, but are not limited to, the above examples. Blocks in a page template may also be marked in other ways, such as by different colors. This embodiment does not limit the specific marking method of blocks in a page template.

[0152] Optionally, the method may further include:

[0153] Set a unique block identifier for the block;

[0154] A first component tag is set for a component corresponding to the block according to the block identifier.

[0155] In one embodiment, the server may assign a unique block identifier to each block to identify the block, and may also assign the block identifier to the first component tag of the component corresponding to the block. For example, a different block identifier may be assigned to each block in page template 4. If the component on the page corresponding to block 43 is a title component, the title component may be identified from the component library, and the block identifier of block 43 may be assigned to the first component tag of the title component, which is then stored in the component library.

[0156] The first component tag is used to recommend components corresponding to the block to the user. For example, if a user selects page template 4 to build an application, when laying out components in block 43, the title component can be obtained from the component library based on the block identifier of block 43 (the block identifier is the first component tag) and recommended to the user.

[0157] The above are merely illustrative examples, and specific methods for setting the first component label for a component based on the block identifier may include but are not limited to the above examples.

[0158] Optionally, the method may further include:

[0159] A second component tag is set for the component according to the scenario characteristics.

[0160] In one embodiment, the server may set a second component tag for a component in the page based on the acquired scene feature. For example, if page template 4 is page template A shown in FIG3 , in the process of generating page template 4, after acquiring scene feature A, the electronic device may search and determine the title component (the title component is located in the page) from the component library, set scene feature A as the second component tag for the title component, and store the second component tag in correspondence with the title component in the component library.

[0161] The second component tag is used to recommend components related to the business scenario to the user. For example, when a user selects page template 4 to build an application, the title component can be retrieved from the component library based on scenario feature A (scenario feature A is the second component tag) and recommended to the user. Because the title component is used in the business scenario corresponding to scenario feature A, the title component recommended to the user is relevant to the business scenario described by scenario feature A.

[0162] The above are merely illustrative examples, and the specific method of setting the second component label for the component according to the scene characteristics may include but is not limited to the above examples.

[0163] Optionally, the method may further include:

[0164] Construct component models based on component attribute parameters;

[0165] A first model tag of the component model is generated according to the component identifier of the component.

[0166] In one embodiment, the server may obtain attribute parameters of the component from the page, construct a component model based on the attribute parameters of the component, and generate a first model tag of the component model according to the component identifier.

[0167] For example, when generating page template 4, the server can obtain attribute parameters of the title component from the page and generate a component model based on the obtained attribute parameters. The server can then obtain the component identifier of the title component from the component library and set the component identifier as the first model tag of the component model. The server can also store the component model in the model library and the corresponding first model tag.

[0168] The component model may include, but is not limited to, attribute parameters such as component size, color, font, and behavior.

[0169] In this embodiment, the first model tag is used to obtain a component model, and then recommend the component model to the user based on the first model tag. For example, if the component selected by the user when building an application is a title component, the component model can be obtained from the model library based on the component identifier of the title component (the component identifier is the first model tag), and then the component model is recommended to the user. The user can quickly set the properties of the title component based on the attribute parameters in the component model.

[0170] Optionally, the method may further include:

[0171] A second model label of the component model is generated according to the scene feature.

[0172] In one embodiment, the electronic device can set a second model tag for the component based on the acquired scene feature. For example, when generating page template A, if the component model is generated based on the attribute parameters of the title component, the acquired scene feature A can be used as the second model tag of the component model, and the component model and the second model tag are stored in the model library accordingly.

[0173] Among them, the second model tag is used to obtain the component model to recommend the component model to the user based on the second model tag. For example, if the component selected by the user when building the application is the title component and the corresponding scenario feature A is determined, the component model with both the first model tag and the second model tag can be obtained from the model library based on the component identifier of the title component (the component identifier is the first model tag) and the scenario feature A (the scenario feature A is the second model tag), and the component model is recommended to the user. Since the title component is used in a business scenario related to the scenario feature A, the recommended component model is related to the business scenario corresponding to the scenario feature A.

[0174] The above are merely illustrative examples, and the specific method of setting the second component label for the component according to the scene characteristics may include but is not limited to the above examples.

[0175] Optionally, the method may further include:

[0176] In the case that the component is configured with a dataset, a third model tag of the component model is generated according to the dataset identifier of the dataset.

[0177] In one embodiment, during the page template generation process, the server can detect from the page whether a component is configured with a dataset. If the component is configured with a dataset, the dataset identifier of the dataset can be set as the third model tag of the component model. For example, if the page includes a form component, and the dataset configured for the form component is a cold drink product dataset, the dataset identifier of the cold drink product dataset can be set as the third model tag of the component model.

[0178] The third model tag is used to obtain component models and recommend component models to users based on the third model tag. For example, if the component selected by the user when building an application is a form component and a cold drink product dataset is configured for the form component, then based on the component identifier of the form component (the first model tag) and the dataset identifier of the cold drink product dataset (the third model tag), component models with both the first model tag and the third model tag can be obtained from the model library and recommended to the user.

[0179] Alternatively, a component model having the first model label, the second model label, and the third model label may be obtained from the model library based on the first model label, the second model label, and the third model label, and the component model may be recommended to the user.

[0180] Optionally, the method may further include:

[0181] Generate page theme based on page appearance parameters;

[0182] Generate topic tags for page topics based on scene characteristics.

[0183] In one embodiment, when generating a page template, the electronic device may also use image recognition technology to detect and determine appearance parameters such as the background color, background image, font, font color, font size, and border color of the page, and generate a page theme based on the appearance parameters.

[0184] As shown in Figure 3, the electronic device can detect and determine the appearance parameters of a page on website A, such as the background color, background image, font, font color, font size, and border color. Based on the appearance parameters, the electronic device generates page theme A and stores page theme A in a theme library. Similarly, page theme B can be generated and stored in the theme library.

[0185] The electronic device may also generate a theme tag for the page theme based on the scene feature. For example, in the process of generating page template A, after generating page theme A, the electronic device may set scene feature A as the theme tag for page theme A.

[0186] Among them, the theme tags are used to recommend page themes corresponding to scene features to users. During the application construction process, different page themes can be recommended to users based on the theme tags, so that users can modify the theme appearance of the page according to the theme parameters in the page theme.

[0187] For example, when a user selects page template A to build an application, page theme A can be obtained from the theme library based on scenario feature A (scenario feature A is a theme tag) and recommended to the user. Since page theme A is applied to the business scenario corresponding to scenario feature A, the page theme A recommended to the user is related to the business scenario corresponding to scenario feature A.

[0188] The above are merely illustrative examples. The method of generating topic tags based on scene features may include but is not limited to the above examples, and this embodiment does not impose any limitation on this.

[0189] FIG7 is a schematic flow chart of the steps of a page generation method provided in an embodiment of the present application, which is applied to electronic devices, which may be mobile phones, personal computers (PCs), tablet computers, laptop computers, etc., but are not limited thereto. The electronic device can execute the page generation method provided in this embodiment through a low-code platform, which may be an online application building platform or an offline application building platform. This embodiment does not limit the implementation form of the low-code platform.

[0190] As shown in FIG7 , the page generation method may include the following steps:

[0191] Step 71: Obtain at least one page template corresponding to the scene feature.

[0192] In this embodiment, during the application construction process, the low-code platform can first determine the scenario characteristics and then obtain one or more corresponding page templates based on the scenario characteristics. For example, the low-code platform can recommend to the user a set of pre-acquired scenario characteristics including multiple scenario characteristics, then determine the scenario characteristics selected by the user from the multiple scenario characteristics, and obtain one or more page templates from the server based on the scenario characteristics selected by the user.

[0193] Figure 8 is a schematic diagram of an operating interface of a low-code platform provided in an embodiment of the present application. The operating interface of the low-code platform includes a title bar 81, a menu bar 82 and an operating area 83. The title bar 81 is used to display information related to the page (such as the application name and the page name), and to display some controls in the low-code platform; the menu bar 82 is used to display another part of the controls in the low-code platform; the operating area 83 is used to display page templates and pages, as well as various windows in the low-code platform. The above is only an illustrative example and does not constitute a limitation on the operating interface.

[0194] When creating a page, the user first clicks the new control 811 displayed in the title bar 81 or clicks the scene selection control 821 in the menu bar 82. In response to the user's click operation, the low-code platform displays a scene selection window 84. The scene selection window 84 displays multiple scene features in the scene feature set.

[0195] As shown in FIG8 , the scenario feature "battery" indicates that the page template is applicable to business scenarios related to the field of battery technology, the scenario feature "detection" indicates that the page template is applicable to business scenarios related to detection, and the scenario feature "quality management" indicates that the page template is applicable to business scenarios related to quality management. Scenario features may include but are not limited to the above examples.

[0196] After the scenario selection window 84 is displayed, the user can select one or more scenario features from the scenario selection window 84 based on the business scenario to which the page to be created is applicable. For example, if the page created by the user needs to be applied to battery quality inspection, the user can click on the scenario features "Battery", "Inspection", and "Quality Management" respectively. In response to the user's click operation, the low-code platform determines that the scenario features clicked by the user, "Battery", "Inspection", and "Quality Management", are the scenario features selected by the user.

[0197] After determining the scenario features "battery," "detection," and "quality management" selected by the user, the low-code platform can send the scenario features "battery," "detection," and "quality management" to the server. The server can then retrieve one or more page templates with template tags "battery," "detection," and "quality management" from the template library based on the scenario features "battery," "detection," and "quality management," and send the page templates to the low-code platform.

[0198] For example, if the scene feature "battery" is scene feature A shown in Figure 3, the server can obtain page template A from the template library based on scene feature A (scene feature A is a template tag) and send page template A to the electronic device. Similarly, one or more page templates corresponding to each scene feature can be obtained, and the page templates obtained from the template library can be sent to the low-code platform.

[0199] Correspondingly, after the low-code platform obtains at least one page template from the server, it can display a template selection window 85 in the operation area 83, and display at least one obtained page template in the form of a thumbnail in the template selection window 85, such as page template 4, page template 5 and page template 6 in the above example.

[0200] In one embodiment, page templates may be pre-stored in the low-code platform. After generating a page template, the server may send the page templates and their template tags stored in the template library to the low-code platform for storage. After determining the characteristics of the scenario selected by the user, the low-code platform may retrieve at least one corresponding page template from a plurality of pre-stored page templates based on the scenario characteristics.

[0201] The above are merely illustrative examples. The method by which the low-code platform determines scene features and obtains page templates based on scene features may include but is not limited to the above examples.

[0202] Step 72: Determine a first page template from at least one page template.

[0203] In this embodiment, after obtaining at least one page template based on the scenario characteristics, the low-code platform can determine a page template selected by the user from the at least one page template, and the page template can be called the first page template.

[0204] As shown in Figure 8, after obtaining page templates 4, 5, and 6, the low-code platform can display page templates 4, 5, and 6. At this time, if the user determines that page template 5 matches the requirements, the user can click or double-click the page template 5 displayed as a thumbnail. The low-code platform can respond to the user's click operation and determine that the page template 5 clicked by the user is the first page template.

[0205] The above examples are merely illustrative, and the method for determining the first page template from multiple first page templates may include but is not limited to the above examples.

[0206] Step 73: Generate a page according to the first page template.

[0207] In this embodiment, after determining the first page template, the low-code platform can generate a page based on the first page template. For example, when the page template obtained based on the scenario characteristics already has multiple components laid out, the user can click the save control 814 displayed in the title bar 81. In response to the user's click operation, the low-code platform directly generates a page based on the page template with the components laid out.

[0208] In one embodiment, the page template may be the page template shown in Figures 4 and 5. For example, if the first page template is page template 5, the user may select a component for each block in page template 5, and the low-code platform may layout the components selected by the user for the block in the block. After selecting components for each block in the first page template, the user may click the save control 814, and the low-code platform generates a page based on the page template with the components in response to the user's click.

[0209] In summary, in the embodiments of the present application, during the page generation process, page templates are obtained based on scenario characteristics, and a page template is selected from the obtained page templates to generate the page. Because the page templates are obtained based on scenario characteristics, the page templates are related to the business scenario corresponding to the scenario characteristics. During the template selection process, the user does not need to consider the business scenario to which the page template applies; they can directly select a page template from the page templates related to the business scenario, which can reduce the difficulty of template selection.

[0210] Optionally, in the process of acquiring scene features, the electronic device may acquire a scene feature set based on the user portrait and determine the scene features from the scene feature set.

[0211] For example, when a user registers an account on a low-code platform, he or she can simultaneously register the user's industry information, company information, position information, department information, age information, gender information, regional information, hobby information and other information. This information constitutes part of the user's user tag.

[0212] At the same time, low-code platforms can record user behavior information when building applications multiple times, using this behavior information as another part of the user's user tag. Behavioral information can include, but is not limited to, the page template used by the user when building the application, the scenario characteristics selected by the user, and the component types used by the user. For example, if a user sets the text content in the title component to "Detect" when building an application, "Detect" can be stored as a user's behavioral information.

[0213] Among them, user tags can be stored in the server, and all user tags of the user constitute the user's user profile, which can describe the user's business needs when building an application.

[0214] As shown in Figure 8, before a user begins building an application on the low-code platform, they can log in to a pre-registered account. The server can then retrieve a pre-stored user profile based on the account, and then retrieve a recommended scenario feature set based on the user profile and send the scenario feature set to the low-code platform. After receiving the scenario feature set sent by the server, the low-code platform can display multiple scenario features in the scenario feature set in a scenario selection window 84.

[0215] In some embodiments, the server can obtain the template tag of each template from the template library, calculate the matching degree between the user portrait and the scene feature, and send a scene feature set composed of multiple scene features with a matching degree greater than a preset threshold to the low-code platform.

[0216] In some embodiments, the server can record the scenario features selected by users during the application construction process, and record behavioral information such as the number of selections, deletions, and modifications of the scenario features. In the process of obtaining scenario features, the server can calculate the weight of each scenario feature based on the behavioral information such as the number of selections, deletions, and modifications. When sending the scenario features to the low-code platform, the weight of each scenario feature can also be sent.

[0217] Correspondingly, when displaying scene features, the low-code platform can sort multiple scene features by weight. The scene features with greater weights will be positioned closer to the front in the scene selection window, making it easier for users to select scene features that are more closely related to user behavior.

[0218] The above are merely illustrative examples. The specific method of recommending scene features to users based on user portraits can be set according to needs, and this embodiment does not impose any restrictions on this.

[0219] In an embodiment of the present application, a scene feature set is obtained based on the user portrait, and scene features in the scene feature set are recommended to the user. This allows the scene features recommended to the user to be relevant to the user, so that the page template recommended to the user based on the scene features can be closer to the user's needs, thereby reducing the difficulty for the user to select a template.

[0220] Optionally, a plurality of first blocks are arranged in the page template. Before generating a page according to the first page template, the method further includes:

[0221] determining a component selected by a user for the first block;

[0222] The components selected by the user for the first block are arranged in the first block.

[0223] The first block is a block in the first page template selected by the user. When multiple first blocks are arranged in the first page template, the user can select components for the first block, and the low-code platform can arrange the components selected by the user for the first block in the first block.

[0224] FIG9 is a schematic diagram of an operation interface of another low-code platform provided in an embodiment of the present application. After the user clicks a page template 5 from the template selection window 85, the low-code platform can close the template selection window 85 and display the page template 5 in the operation area 83. After the page template 5 is displayed, the user can select a component for each block in each page template 5.

[0225] As shown in FIG9 , after the user clicks the component selection control 822, the low-code platform may display a component selection window 86 in response to the user's click operation, wherein the component selection window 86 displays multiple components and a sliding control 861. When the user drags the sliding control 861, the component selection window 86 may display different components.

[0226] For example, when the user needs to place a title component in block 51, the user can drag the title component in the component selection window 86 to the top of block 51. When the title component hovers above block 51 for longer than a preset time, the low-code platform determines that the title component is the component selected by the user for block 51 and places the title component in block 51.

[0227] For another example, when the user needs to place a title component in block 51, the user can first click block 51 to select block 51, and then the user can double-click the title component in the component selection window 86. In response to the user's double-click operation, the low-code platform determines that the title component is the component selected by the user for block 51, and places the title component in block 51.

[0228] The above examples are merely illustrative, and the user may also select components for the block in other ways, which is not limited in this embodiment.

[0229] In an embodiment of the present application, blocks for placing components are arranged in the page template, and users can layout components in the page based on the blocks. Since multiple blocks in the page template are arranged in the page template according to a certain layout structure, there is no need to adjust the layout of the page after laying out the components, which can reduce the workload during page layout and improve the efficiency of application construction.

[0230] Optionally, the step of determining the component selected by the user for the first block may include:

[0231] Acquire at least one candidate component according to the scene feature and / or the first block;

[0232] A component selected by the user for the first block is determined from at least one candidate component.

[0233] In one embodiment, the low-code platform can obtain at least one alternative component based on the scenario characteristics corresponding to the page template and / or the block identifier of the first block, and then determine the component selected by the user for the first block from the at least one alternative component.

[0234] Figure 10 is a schematic diagram of an operating interface of another low-code platform provided in an embodiment of the present application. As shown in Figure 10, when a user selects a component for block 53, they can click block 53. In response to the user's click operation, the low-code platform can determine the block identifier of block 53 and then send a data request including the block identifier to the server.

[0235] After receiving the data request, the server uses the block identifier in the data request as the component label (i.e., the first component label), determines one or more components with the first component label from the component library based on the first component label, obtains at least one alternative component, and then sends the alternative component to the low-code platform.

[0236] Correspondingly, after receiving at least one alternative component, the low-code platform can display a component recommendation window 87, and display alternative components such as the curve chart component, pie chart component, and bar chart component sent by the server in the component recommendation window 87.

[0237] At this point, the user can select a component for the first block from at least one candidate component displayed in the component recommendation window 87 according to their needs. For example, if the user needs to place a curve chart component in block 53, the user can click the curve chart component displayed in the component recommendation window 87. In response to the user's click operation, the low-code platform determines that the curve chart component is the component selected by the user for block 53, and then places the curve chart component in block 53.

[0238] In another embodiment, the low-code platform can obtain alternative components based on scenario features. For example, after the user clicks block 53, the low-code platform can send a data request including the scenario feature corresponding to the page template 5 (the scenario feature is the template tag of the page template 5) to the server. The server can use the scenario feature in the data request as a component tag (i.e., a second component tag), determine one or more components with the second component tag from the component library, obtain at least one alternative component, and then send the alternative component to the low-code platform.

[0239] In another embodiment, the low-code platform can obtain candidate components based on the block identifier and scenario characteristics of the first block. For example, the electronic device can send a data request to the server including the scenario characteristics corresponding to the page template 5 and the block identifier of block 53. The server can use the block identifier and scenario characteristics in the data request as component tags, determine one or more components with both component tags from the component library, obtain at least one candidate component, and then send the candidate component to the low-code platform.

[0240] In some embodiments, the server may pre-send all components in the component library to the low-code platform for storage. After determining candidate components based on the block identifier and / or scenario characteristics in the data request, the server may send the component identifier of each candidate component to the low-code platform. Correspondingly, after receiving the component identifier, the low-code platform may determine the corresponding candidate component from all pre-stored components based on the component identifier.

[0241] Alternatively, after determining that the user clicks a block, the low-code platform can directly determine one or more components from pre-stored components as alternative components based on the block identifier and / or scenario characteristics.

[0242] The above are merely illustrative examples, and specific methods for obtaining candidate components based on scene features and / or the first block may include but are not limited to the above examples.

[0243] In an embodiment of the present application, multiple alternative components are recommended to the user based on the block and / or scene characteristics. Since the components recommended to the user are related to the block and / or the business scenario corresponding to the scene characteristics, it is convenient for the user to select the components related to the block and / or business scenario and layout them in the block, thereby allowing the user to quickly and accurately select the component layout in the page template.

[0244] In some embodiments, when the components recommended by the low-code platform to the user do not meet the user's needs, the user can input scenario features to the low-code platform again. The low-code platform can determine other components from the server based on the scenario features input by the user and display other components.

[0245] As shown in FIG10 , the component recommendation window 87 may also display the scene features “icon”, “battery”, “safety diagnosis”, etc. determined by the user when selecting the page template. At the same time, the component recommendation window 87 may also display a feature input control 871 .

[0246] When the user determines that the component currently displayed in the component recommendation window 87 does not meet the user's needs, the user can click the feature input control 871. When the low-code platform receives the user's click operation on the feature input control 871, it can display the scenario selection window 86 again. At this time, the user can select other scenario features from the scenario selection window 86 (the scenario features are different from the pre-determined scenario features and can be called supplementary scenario features), and the low-code platform can send the supplementary scenario features to the server.

[0247] In some embodiments, after receiving the supplementary scenario features sent by the low-code platform, the server can re-determine the alternative components recommended to the user based on the supplementary scenario features or based on the scenario features and block identifiers, and send the alternative components to the low-code platform.

[0248] Optionally, the method may further include:

[0249] Obtain at least one component model according to the component;

[0250] determining a target component model selected by a user for a component from the at least one component model;

[0251] Configures the properties of a component based on the property parameters in the target component model.

[0252] In one embodiment, after determining the component selected by the user for the first block, the low-code platform can obtain at least one component model based on the component, and then determine the target component model selected by the user for the component from the at least one component model, and configure the properties of the component according to the property parameters in the target component model.

[0253] For example, after determining the component selected by the user for the first block, the low-code platform can send a data request including a component identifier to the server. After receiving the data request, the server uses the component identifier in the data request as a model tag (i.e., a first model tag), obtains one or more component models with the first model tag from the model library, and then sends the component model to the low-code platform. Correspondingly, after receiving the component model, the low-code platform can display the received component model.

[0254] Figure 11 is a schematic diagram of an operating interface for another low-code platform provided in an embodiment of the present application. As shown in Figure 11, the component selected by the user for block 53 is the product details component. After selecting the product details component for block 53, the user can click the product details component. In response to the user's click, the low-code platform sends a data request including the component identifier of the product details component to the server.

[0255] After receiving the data request, the server uses the data request as the first model tag, obtains one or more component models with the first model tag from the model library, and then sends the obtained component models to the low-code platform. After receiving the component models sent by the server, the low-code platform displays a model selection window 88 and displays the component models sent by the server in the model selection window 88, such as component model 1 and component model 2 shown in Figure 11.

[0256] At this point, the user can select a component model from component model 1 and component model 2 as needed. For example, if the user selects component model 1, they can click component model 1. In response to the user's click operation, the low-code platform determines that the component model 1 clicked by the user is the component model selected by the user for the product details component, and configures the properties of the product details component according to the property parameters in component model 1.

[0257] In an embodiment of the present application, a component model is obtained based on the component, and the properties of the component are configured according to the property parameters in the component model. This can facilitate users to quickly set the properties of the component, thereby improving the editing efficiency of the component.

[0258] Optionally, the step of acquiring at least one component model according to the component includes: acquiring at least one component model according to scene features and / or components.

[0259] In some embodiments, in the process of obtaining a component model, the component model can be obtained based on the component and scenario features. For example, after laying out the product details component for block 53, the low-code platform can send a data request to the server including the scenario features corresponding to the page template 5 and the component identifier of the product details component. After receiving the data request, the server uses the component identifier in the data request as the model tag (i.e., the first model tag) and the scenario features as the model tag (i.e., the second model tag), obtains the component model with both the first model tag and the second model tag from the model library, and then sends the component model to the low-code platform.

[0260] In other embodiments, in the process of obtaining the component model, the component model can be obtained based on the component and the dataset. For example, after laying out the product details component for block 53, if the user also configures a dataset for the product details component, the low-code platform can send a data request including the component identifier of the product details component and the dataset identifier of the dataset to the server. After receiving the data request, the server uses the component identifier in the data request as the model label (i.e., the first model label) and the dataset identifier as the model label (i.e., the third model label) to obtain the component model with both the first model label and the third model label from the model library, and then sends the component model to the low-code platform.

[0261] In other embodiments, in the process of obtaining the component model, the component model can be obtained based on the component, data set and scenario characteristics. For example, after laying out the product details component for block 53, if the user also configures a data set for the product details component, the low-code platform can send a data request to the server including the component identifier of the product details component, the data set identifier of the data set and the scenario characteristics. After receiving the data request, the server uses the component identifier in the data request as the model label (first model label), the scenario characteristics in the data request as the model label (second model label), and the data set identifier as the model label (third model label), and obtains the component model with the first model label, the second model label and the third model label from the model library, and then sends the component model to the low-code platform.

[0262] The above are merely illustrative examples, and specific methods for obtaining component models based on components may include but are not limited to the above examples.

[0263] In an embodiment of the present application, when obtaining a component model, the component model corresponding to the component is obtained based on the component, as well as the scenario characteristics and / or the data set. This allows the component model to be related to the business scenario corresponding to the scenario characteristics and / or to the data set that the component is frequently configured with. This allows the component model recommended to the user to be more in line with user needs, thereby facilitating the user to quickly adjust the component model to obtain component properties that meet their needs.

[0264] Optionally, before generating the page, the method may further include:

[0265] Obtain at least one page topic based on scene characteristics;

[0266] determining a target page theme selected by the user for the first page template from the at least one page theme;

[0267] Configure the appearance of the first page template according to the appearance parameters in the target page theme.

[0268] In one embodiment, before generating a page, the low-code platform can obtain and recommend at least one page theme to the user based on scenario characteristics, and configure the appearance of the first page template based on the appearance parameters in the page theme selected by the user.

[0269] Figure 12 is a schematic diagram of an operating interface of another low-code platform provided in an embodiment of the present application. A theme selection control 813 is displayed in the title bar 81. When the user needs to set the appearance of the first page template, the user can click the theme selection control 813. The low-code platform can send a data request including the scene features corresponding to the page template 5 to the server in response to the user's click operation. After receiving the data request, the server uses the scene features in the data request as a theme tag, obtains one or more page themes with the theme tag from the theme library, and sends the page themes to the low-code platform.

[0270] As shown in FIG12 , after receiving the page theme sent by the server, the low-code platform can display a theme selection window 89. The theme selection window 89 displays the theme identifiers of multiple page themes sent by the server, such as “Theme 1”, “Theme 2”, and “Theme 3” as shown in FIG12 .

[0271] Among them, different page themes can be distinguished by different color system identifiers 891. The color system identifier 891 is filled with the color corresponding to the page theme, so that the user can distinguish multiple page themes according to the color system identifier 891.

[0272] For example, the user can select a theme identifier from multiple theme identifiers displayed in the theme selection window 89 according to the color scheme identifier 891 and click on the theme identifier. In response to the user's click operation, the low-code platform determines that the page theme to which the theme identifier clicked by the user belongs is the target page theme selected by the user for the first page template, and then configures the appearance of the first page template according to the appearance parameters in the target page theme. Configuring the appearance of the first page template is to configure the appearance of the page.

[0273] The above are merely illustrative examples. The method of obtaining the page theme based on scene features may include but is not limited to the above examples, and this embodiment does not impose any restrictions on this.

[0274] In an embodiment of the present application, page themes are recommended to users based on the scenario features corresponding to the page template, so that the page theme can be related to the business scenario corresponding to the scenario features, so that the page appearance set according to the page theme is suitable for the corresponding business scenario, thereby allowing users to quickly and accurately adjust the appearance of the page.

[0275] Optionally, before generating the page, the method may further include:

[0276] determining a second page template when the first page template does not match, wherein a plurality of second blocks are arranged in the second page template;

[0277] When the first block and the second block are the same block, the components arranged in the first block are arranged in the second block.

[0278] In one embodiment, when the first page template does not match the requirements, the user can replace the predetermined first page template with a second page template. As shown in Figure 8, a template selection control 812 is displayed in the title bar 81. When the user determines that the currently displayed first page template does not match the requirements, the user can click the template selection control 812. The low-code platform can display a template selection window 85 in response to the user's click operation. After displaying the template selection window 85, the low-code platform can display multiple alternative page templates pre-obtained from the server in the template selection window 85 in the form of thumbnails. Alternatively, multiple alternative page templates can be directly displayed in the operation area 83.

[0279] For example, the user can determine the desired page template 4 from the template selection window 85, the page template 4 is the second page template, and then click the thumbnail of the page template 4. In response to the user's click operation, the low-code platform determines that the page template 4 clicked by the user is the second page template.

[0280] Then, the low-code platform refreshes the operation area 83, first deleting the first page template displayed in the operation area, and then displaying the second page template in the same way as the first page template.

[0281] Among them, the block in the second page template is the second block. After displaying the second page template, the low-code platform searches for the second block with the same block identifier from the second page template based on the block identifier of the first block. When the second page template includes the second block that is the same as the first block, the components pre-arranged in the first block can be arranged in the second block.

[0282] As shown in Figure 8, block 55 in page template 5 and block 42 in page template 4 are both located at the bottom of the page template, and block 55 and block 42 have the same block identifier. After replacing page template 5 with page template 4, the low-code platform can layout the pre-layout components in block 55 in block 42.

[0283] It is understandable that after the second page template is displayed, the first page template in the operation area is deleted. At this time, the second page template is the first page template displayed in the operation area, and the second block in the second page template is the first block.

[0284] The above is merely an illustrative example. Methods for determining whether blocks are identical may include, but are not limited to, block identification, and this embodiment does not impose any limitation thereto.

[0285] In an embodiment of the present application, during the process of replacing a page template, the electronic device can arrange the components in the block before the replacement in the same block after the replacement, which can reduce the workload after replacing the page template and thus improve the efficiency of application construction.

[0286] Optionally, the method may further include:

[0287] When a user configures a data set for a component, behavior information is generated. The behavior information includes a component identifier of the component and a data set identifier of the data set.

[0288] In some embodiments, the server can establish a personal database for the user, which can store the user's behavior information during the application building process. For example, if a user places a product details component in one of the blocks during application building and sets the data source of the product details component to the cold drink product dataset, the low-code platform can generate a piece of behavior information, which includes the component identifier of the product details component and the dataset identifier of the cold drink product dataset.

[0289] The low-code platform can directly store this behavior information and / or send it to a server. The server then creates a personal database corresponding to the user's account and stores the behavior information in the personal database. After a user builds applications multiple times on the low-code platform, the low-code platform generates multiple pieces of behavior information. Consequently, multiple pieces of behavior information are stored in the personal database.

[0290] In one embodiment, the behavior information may further include a scene feature corresponding to the currently used first page template and / or a block identifier of the first block where the product details component is currently located.

[0291] The above are merely illustrative examples. The specific generation and storage process of behavior information can be set according to needs, and this embodiment does not limit this.

[0292] Optionally, the method may further include:

[0293] determining at least one data set based on the component;

[0294] determining a target data set configured by a user for a component from at least one data set;

[0295] Set the target dataset as the component's data source.

[0296] In some embodiments, after laying out the components in the first block, the low-code platform can determine at least one data set based on the component, and then determine the target data set configured by the user for the component from the at least one data set, and set the target data set as the data source of the component.

[0297] Figure 13 is a schematic diagram of an operating interface of another low-code platform provided in an embodiment of the present application. As shown in Figure 13, a user has arranged a product details component in block 53. While editing the product details component, the user can click on the product details component. In response to the click on the product details component, the low-code platform sends a data request to the server, which includes the component identifier of the product details component.

[0298] After receiving the data request, the server determines one or more pieces of behavior information, including the component identifier of the product details component, from the personal database based on the component identifier in the data request. The server then obtains the dataset identifier included in the behavior information, such as the dataset identifiers for the cold drink product dataset and the automobile product dataset shown in Figure 13. After obtaining the dataset identifiers, the server sends them to the low-code platform.

[0299] Correspondingly, after receiving the dataset identifier sent by the server, the low-code platform displays the dataset selection window 810, and displays the cold drink product dataset and the automobile product dataset in the dataset selection window 810 according to the dataset identifier.

[0300] At this point, the user can select and click the desired dataset from one or more datasets displayed in the dataset selection window 810. In response to the user's click operation, the low-code platform determines the dataset clicked by the user as the target dataset configured by the user for the component and sets the target dataset as the data source of the component.

[0301] The above examples are merely illustrative. Methods for determining a data set according to a component and determining a target data set configured by a user for a component from at least one data set may include but are not limited to the above examples.

[0302] In an embodiment of the present application, when a user configures a data set for a component, one or more data sets can be obtained based on the component, allowing the user to select a data set from at least one data set as the data source of the component, which can improve the editing efficiency of the component and thus improve the efficiency of application construction.

[0303] Optionally, the step of determining at least one data set according to the component may include:

[0304] determining at least one data set based on the component and the first block in which the component is located;

[0305] Alternatively, determining at least one data set based on scene characteristics and components;

[0306] Alternatively, at least one data set is determined according to the component, the scene feature, and the first block where the component is located.

[0307] In some embodiments, after a user clicks on a product details component, the low-code server may send a data request to the server that includes the component identifier of the product details component and the block identifier of the first block. After receiving the data request, the server obtains behavior information including both the component identifier and the block identifier from the personal database based on the component identifier and the block identifier included in the data request, obtains the dataset identifier in the behavior information, and then sends the obtained dataset identifier to the low-code platform.

[0308] In other embodiments, after a user clicks a product details component, the low-code platform may send a data request to the server, including the component identifier and scenario characteristics of the product details component. Upon receiving the data request, the server retrieves behavioral information including both the component identifier and scenario characteristics from a personal database based on the component identifier and scenario characteristics included in the data request, obtains a dataset identifier from the behavioral information, and then sends the obtained dataset identifier to the low-code platform.

[0309] In other embodiments, after a user clicks on a product details component, the low-code platform may send a data request to a server that includes the component identifier of the product details component, the block identifier of the first block, and the scene characteristics. After receiving the data request, the server retrieves behavior information including the component identifier, block identifier, and scene characteristics from a personal database based on the component identifier, block identifier, and scene characteristics included in the data request, obtains a dataset identifier from the behavior information, and then sends the obtained dataset identifier to the electronic device.

[0310] The above are merely illustrative examples. The manner of determining the data set according to the components and blocks, the manner of displaying the data set, and the specific form of the second selection instruction can be set as required, and this embodiment does not impose any restrictions on this.

[0311] In an embodiment of the present application, during the process of editing a component, the electronic device can recommend a data set to the user based on the component and the block in which the component is located, or recommend data to the user based on the scene characteristics corresponding to the component and the page template, or recommend a data set to the user based on the component, the scene characteristics and the block. This can make the data set not only related to the component, but also related to the business scenario and / or block, making the recommended data set more accurate, and can facilitate the user to quickly set an accurate data source for the component, thereby improving page layout efficiency.

[0312] FIG14 is a flow chart of a page generation method provided in an embodiment of the present application. The method may include the following steps:

[0313] Step 141: Obtain user portrait.

[0314] Among them, the user logs in to the server through the account before creating the page, and the server can obtain the pre-stored user portrait based on the account.

[0315] Step 142: Obtain scene features based on the user portrait.

[0316] As shown in Figure 8, after obtaining the user profile, the server determines the scenario features recommended to the user based on the user profile and sends the scenario features to the low-code platform. After receiving the scenario features, the low-code platform displays multiple scenario features recommended to the user in the scenario selection window 84.

[0317] Step 143: Recommend a page template based on the scene features selected by the user.

[0318] As shown in FIG7 , after the user selects a scenario feature from the scenario selection window 84, the low-code platform can send the scenario feature selected by the user to the server. The server determines a page template recommended to the user based on the scenario feature selected by the user and sends the page template to the low-code platform. After receiving the page template, the low-code platform displays a template selection window 85 and displays the recommended page template in the template selection window 85.

[0319] Step 144: Determine a first page template from the recommended page templates.

[0320] As shown in FIG. 7 , the user can click on one of the page templates displayed in the template selection window 85 . The page template clicked by the user is the first page template.

[0321] Step 145: Display the first page template.

[0322] As shown in Figure 3, after determining the first page template, the low-code platform can display the first page template in the operation area 83.

[0323] Step 146: Recommend block-related components to the user.

[0324] As shown in Figure 10, when the user needs to layout components in block 53, he can click block 53. The low-code platform determines the components associated with block 53 from the server and displays the components associated with block 53 in the component recommendation window 87.

[0325] Step 147: Select a component from the recommended components.

[0326] Step 148: Place the selected components in the blocks.

[0327] As shown in Figure 10, the user can determine the components that need to be placed in block 53 from the recommended components and click them. The low-code platform can layout the components clicked by the user in block 53.

[0328] Step 149: Determine whether the page template needs to be changed.

[0329] As shown in FIG8 , when a user needs to change a template, they can click on the template selection control 812. In response to the user's click, the low-code platform returns to step 143 and displays the template selection window 85 again, displaying multiple page templates recommended to the user. Alternatively, multiple page templates can be displayed directly in the operation area 83.

[0330] Step 150: Determine whether the component needs to be replaced.

[0331] As shown in FIG9 , when the user needs to replace a component in a block, the user can click on block 53. The low-code platform can respond to the user's click operation and display the component recommendation window 87 again. The user can again select a component from the component recommendation window 87 and place it in block 53.

[0332] Step 151: Determine whether component properties need to be edited.

[0333] Step 152: Modify component properties.

[0334] When a component property needs to be modified, the user can manually modify the property of the component. Alternatively, the user can click on the component, and the low-code platform will respond to the user's click operation by displaying a model selection window 88 and displaying component models recommended to the user in the model selection window 88. The user can select a component model from the recommended component models, and the electronic device will configure the component properties according to the component model selected by the user.

[0335] Step 153: Save the page template as a page.

[0336] Among them, after the component editing is completed, the low-code platform can save the page template as a page. At this time, you can enter the application publishing stage and publish the application.

[0337] FIG15 is a schematic diagram of the structure of a page generation device provided in an embodiment of the present application. The page generation device 15 includes:

[0338] A first acquisition module 151 is configured to acquire at least one page template corresponding to a scene feature;

[0339] A first determining module 152, configured to determine a first page template from at least one page template;

[0340] The first generating module 153 is configured to generate a page according to the first page template.

[0341] In one embodiment, the first acquisition module is further configured to acquire a scene feature set based on the user portrait;

[0342] The first determining module is further configured to determine a scene feature from the scene feature set.

[0343] In one embodiment, the apparatus further comprises:

[0344] a second determining module, configured to determine a component selected by the user for the first block;

[0345] The layout module is configured to layout the components selected by the user for the first block in the first block.

[0346] In one embodiment, the second determination module is specifically configured to obtain at least one candidate component based on the scene feature and / or the first block; and determine the component selected by the user for the first block from the at least one candidate component.

[0347] In one embodiment, the apparatus further comprises:

[0348] a third determining module, configured to determine at least one data set according to the component;

[0349] A fourth determining module, configured to determine a target data set configured by a user for a component from at least one data set;

[0350] The first setting module is used to set the target data set as the data source of the component.

[0351] In one embodiment, the third determination module is specifically used to determine at least one data set based on the component and the first block where the component is located; or, to determine at least one data set based on the scene characteristics and the component; or, to determine at least one data set based on the component, the scene characteristics and the first block where the component is located.

[0352] In one embodiment, the apparatus further comprises:

[0353] A second acquisition module is used to acquire at least one component model according to the component;

[0354] a fifth determining module, configured to determine a target component model selected by a user for a component from at least one component model;

[0355] The first configuration module is used to configure the properties of the component according to the property parameters in the target component model.

[0356] In one embodiment, the second acquisition module is specifically used to acquire at least one component model based on scene characteristics and components; or, to acquire at least one component model based on a data set and a component configured by a user for the component; or, to acquire at least one component model based on a data set, a component, and scene characteristics configured by a user for the component.

[0357] In one embodiment, the apparatus further comprises:

[0358] A third acquisition module is used to acquire at least one page theme according to the scene characteristics;

[0359] a sixth determining module, configured to determine a target page theme selected by the user for the first page template from at least one page theme;

[0360] The second configuration module is used to configure the appearance of the first page template according to the appearance parameters in the target page theme.

[0361] In one embodiment, the second determining module is further configured to determine a second page template if the first page template does not match, wherein the second page template has a plurality of second blocks arranged therein;

[0362] The layout module is further configured to place the components arranged in the first block in the second block when the first block and the second block are the same block.

[0363] In one embodiment, the first acquisition module is further configured to acquire a pre-generated page;

[0364] The first generating module is further used to generate a page template according to a pre-set page;

[0365] The first acquisition module is further configured to acquire scene features corresponding to the page template from a pre-generated page.

[0366] In one embodiment, a block corresponding to each component in the pre-generated page is arranged in the page template, and the position of the block in the page template is the same as the position of the corresponding component in the page.

[0367] In one embodiment, the apparatus further comprises:

[0368] The second setting module is used to set a unique block identifier for the block in the page template;

[0369] The third setting module is configured to set a first component tag for a component corresponding to the block according to the block identifier of the block.

[0370] In one embodiment, the apparatus further comprises:

[0371] The fourth setting module is used to set a second component tag for the component in the pre-generated page according to the scene characteristics.

[0372] In one embodiment, the apparatus further comprises:

[0373] A construction module, configured to construct a component model according to attribute information of components included in a pre-generated page;

[0374] The second generating module is configured to generate a first model tag of the component model according to the component identifier of the component included in the pre-generated page.

[0375] In one embodiment, the second generating module is further configured to generate a second model label of the component model according to the scene feature.

[0376] In one embodiment, the second generating module is further configured to generate a third model tag of the component model according to a dataset identifier of the dataset when the component included in the pre-generated page is configured with a dataset.

[0377] In one embodiment, the first generating module is further configured to generate a page theme according to the appearance parameters of the pre-generated page; and generate a theme tag of the page theme according to the scene characteristics.

[0378] In one embodiment, the first generating module is further configured to generate behavior information when the user configures a data set for a component, where the behavior information includes a component identifier of the component and a data set identifier of the data set.

[0379] In one embodiment, the behavior information further includes scene features and / or a block identifier of the first block where the component is located.

[0380] FIG16 is a schematic diagram of the structure of a device for generating a page template according to an embodiment of the present application. The page generating device 16 includes:

[0381] A first acquisition module 161 is used to acquire a page;

[0382] A first generating module 162 is used to generate a page template according to the page;

[0383] The second acquisition module 163 is used to acquire the scene characteristics of the page from the page;

[0384] The second generating module 164 is configured to generate a template tag of a page template according to scene features.

[0385] In one embodiment, a block corresponding to each component in the page is arranged in the page template, and the position of the block in the page template is the same as the position of the corresponding component in the page.

[0386] In one embodiment, the apparatus further comprises:

[0387] The first setting module is used to set a unique block identifier for the block; and set a first component tag for the component corresponding to the block according to the block identifier.

[0388] In one embodiment, the apparatus further comprises:

[0389] The second setting module is used to set a second component label for the component according to the scene characteristics.

[0390] In one embodiment, the apparatus further comprises:

[0391] A construction module, used to construct a component model according to the attribute parameters of the component;

[0392] The third generating module is configured to generate a first model tag of the component model according to the component identifier of the component.

[0393] In one embodiment, the third generating module is further configured to generate a second model label of the component model according to the scene feature.

[0394] In one embodiment, the third generating module is further configured to generate a third model tag of the component model according to a dataset identifier of the dataset when the component is configured with a dataset.

[0395] In one embodiment, the apparatus further comprises:

[0396] The fourth generating module is used to generate a page theme according to the appearance parameters of the page; and generate a theme tag of the page theme according to the scene characteristics.

[0397] Figure 17 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. The electronic device 17, such as the mobile phone, tablet computer, and computer mentioned above, includes the device shown in Figure 16 or Figure 17, including: a processor 171 and a memory 172, a communication interface 173, and a bus 174. Among them, the memory 172 is used to store instructions, and the processor 171 is used to execute the instructions stored in the memory 172. The processor 171, the memory 172, and the communication interface 173 are connected to each other through the bus 174.

[0398] An embodiment of the present application further provides a readable storage medium, which is used to store a computer program. When the computer program code is executed by an electronic device, the electronic device executes the above page generation method.

[0399] The above are merely optional embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included within the scope of the claims of the present application.

Claims

1. A page generation method, wherein: The method comprises: Obtain at least one page template corresponding to the scene feature; determining a first page template from the at least one page template; Generate a page according to the first page template.

2. The method according to claim 1, wherein: Before acquiring at least one page template corresponding to the scene feature, the method further includes: Obtain scene feature set based on user portrait; The scene feature is determined from the scene feature set.

3. The method according to claim 1 or 2, wherein: The page template includes a plurality of first blocks arranged therein. Before generating a page according to the first page template, the method further includes: determining a component selected by a user for the first block; The components selected by a user for the first block are arranged in the first block.

4. The method according to claim 3, wherein: The determining a component selected by a user for the first block includes: Acquire at least one candidate component according to the scene feature and / or the first block; The component selected by a user for the first block is determined from the at least one candidate component.

5. The method according to claim 3 or 4, wherein: The method further comprises: determining at least one data set according to the component; Determining a target data set configured by a user for the component from the at least one data set; Set the target dataset as the data source of the component.

6. The method according to claim 5, wherein: The determining at least one data set according to the component comprises: Determine the at least one data set according to the component and the first block where the component is located; Alternatively, determining the at least one data set according to the scene feature and the component; Alternatively, the at least one data set is determined according to the component, the scene feature, and the first block where the component is located.

7. The method according to any one of claims 3 to 6, wherein: The method further comprises: Acquire at least one component model according to the component; determining a target component model selected by a user for the component from the at least one component model; The properties of the component are configured according to the properties in the target component model.

8. The method according to claim 7, wherein: The acquiring at least one component model according to the component comprises: Acquire the at least one component model according to the scene feature and the component; Alternatively, the at least one component model is acquired according to a data set configured by a user for the component and the component; Alternatively, the at least one component model is acquired based on a data set configured by a user for the component, the component and the scene feature.

9. The method according to any one of claims 1 to 8, wherein: The method further comprises: Acquire at least one page theme according to the scene feature and / or the first page template; Determine a target page theme selected by a user for the first page template from the at least one page theme; The appearance of the first page template is configured according to the appearance parameters in the target page theme.

10. The method according to any one of claims 3 to 9, wherein: The method further comprises: determining a second page template when the first page template does not match, wherein a plurality of second blocks are arranged in the second page template; When the first block and the second block are the same block, the components arranged in the first block are arranged in the second block.

11. The method according to any one of claims 1 to 10, wherein: Before acquiring at least one page template corresponding to the scene feature, the method includes: Get a pre-generated page; Generating the page template according to the pre-set page; The scene feature corresponding to the page template is obtained from the pre-generated page.

12. The method of claim 11, wherein: The page template is arranged with a block corresponding to each component in the pre-generated page, and the position of the block in the page template is the same as the position of the corresponding component in the page.

13. The method according to claim 11 or 12, wherein: The method further comprises: Setting a unique block identifier for the block in the page template; A first component tag is set for the component corresponding to the block according to the block identifier of the block.

14. The method according to any one of claims 11 to 13, wherein: The method further comprises: A second component tag is set for the component in the pre-generated page according to the scenario feature.

15. The method according to any one of claims 11 to 14, wherein: The method further comprises: constructing a component model according to the attribute information of the component included in the pre-generated page; A first model tag of the component model is generated according to the component identifier of the component included in the pre-generated page.

16. The method according to claim 15, wherein: The method further comprises: A second model tag of the component model is generated according to the scene feature.

17. The method according to any one of claims 11 to 16, wherein: The method further comprises: In a case where the component included in the pre-generated page is configured with a data set, a third model tag of the component model is generated according to a data set identifier of the data set.

18. The method according to any one of claims 11 to 17, wherein: The method further comprises: Establishing a page theme according to the appearance parameters of the pre-generated page; Generate a topic tag for the page topic according to the scene feature.

19. The method according to any one of claims 1 to 18, wherein: The method further comprises: When the user configures a data set for the component, behavior information is generated, and the behavior information includes a component identifier of the component and a data set identifier of the data set.

20. The method according to claim 19, wherein: The behavior information also includes the scene feature and / or the block identifier of the first block where the component is located.

21. A method for generating a page template, wherein: The method comprises: Get the page; Building a page template according to the page; Acquire scene features of the page from the page; A template tag of the page template is generated according to the scene feature.

22. The method of claim 21, wherein: The page template is arranged with a block corresponding to each component in the page, and the position of the block in the page template is the same as the position of the corresponding component in the page.

23. The method according to claim 22, wherein: The method further comprises: Setting a unique block identifier for the block; A first component tag is set for the component corresponding to the block according to the block identifier.

24. The method according to claim 22 or 23, wherein: The method further comprises: A second component tag is set for the component according to the scene feature.

25. The method according to any one of claims 23-24, wherein: The method further comprises: Building a component model according to the attribute parameters of the component; A first model tag of the component model is generated according to the component identifier of the component.

26. The method according to claim 25, wherein: The method further comprises: A second model tag of the component model is generated according to the scene feature.

27. The method according to claim 25 or 26, wherein: The method further comprises: In the case that the component is configured with a data set, a third model tag of the component model is generated according to a data set identifier of the data set.

28. The method according to any one of claims 20 to 27, wherein: The method further comprises: Generate a page theme according to the appearance parameters of the page; Generate a topic tag for the page topic according to the scene feature.

29. A page generating device, wherein: The device comprises: A first acquisition module, used to acquire at least one page template corresponding to the scene feature; A first determining module, configured to determine a first page template from the at least one page template; The first generating module is used to generate a page according to the first page template.

30. The device according to claim 29, wherein: The first acquisition module is also used to acquire a scene feature set according to the user portrait; The first determining module is further configured to determine the scene feature from the scene feature set.

31. The device according to claim 29 or 30, wherein: The device also includes: A second determination module, used to determine the component selected by the user for the first block; A layout module is used to layout the components selected by the user for the first block in the first block.

32. The device according to claim 31, wherein The second determination module is specifically configured to obtain at least one candidate component according to the scene feature and / or the first block; and determine the component selected by the user for the first block from the at least one candidate component.

33. The device according to claim 31 or 32, wherein: The device also includes: A third determination module, configured to determine at least one data set according to the component; A fourth determination module, configured to determine a target data set configured by a user for the component from the at least one data set; The first setting module is used to set the target data set as the data source of the component.

34. The device according to claim 33, wherein The third determination module is specifically used to determine the at least one data set based on the component and the first block where the component is located; or, to determine the at least one data set based on the scene characteristics and the component; or, to determine the at least one data set based on the component, the scene characteristics and the first block where the component is located.

35. The device according to any one of claims 31 to 34, wherein: The device also includes: A second acquisition module, used for acquiring at least one component model according to the component; A fifth determining module, configured to determine a target component model selected by a user for the component from the at least one component model; The first configuration module is used to configure the properties of the component according to the property parameters in the target component model.

36. The device according to claim 35, wherein The second acquisition module is specifically used to acquire the at least one component model based on the scene characteristics and the component; or, to acquire the at least one component model based on the data set configured by the user for the component and the component; or, to acquire the at least one component model based on the data set configured by the user for the component, the component and the scene characteristics.

37. The device according to any one of claims 29 to 36, wherein: The device also includes: A third acquisition module, used to acquire at least one page theme according to the scene feature; A sixth determination module, configured to determine a target page theme selected by a user for the first page template from the at least one page theme; The second configuration module is used to configure the appearance of the first page template according to the appearance parameters in the target page theme.

38. The device according to any one of claims 31 to 37, wherein: The second determination module is further used to determine a second page template when the first page template does not match, wherein a plurality of second blocks are arranged in the second page template; The layout module is further configured to place the components placed in the first block in the second block when the first block and the second block are the same block.

39. The device of any one of claims 29 to 38, wherein: The first acquisition module is also used to acquire a pre-generated page; The first generating module is also used to generate the page template according to the pre-set page; The first acquisition module is further used to acquire the scene feature corresponding to the page template from the pre-generated page.

40. The apparatus of claim 39, wherein: The page template is arranged with a block corresponding to each component in the pre-generated page, and the position of the block in the page template is the same as the position of the corresponding component in the page.

41. The device according to claim 39 or 40, wherein: The device also includes: A second setting module, used for setting a unique block identifier for the block in the page template; The third setting module is used to set a first component tag for the component corresponding to the block according to the block identifier of the block.

42. The device according to any one of claims 39 to 41, wherein: The device also includes: The fourth setting module is used to set a second component tag for the component in the pre-generated page according to the scene feature.

43. The device according to any one of claims 39 to 42, wherein: The device also includes: A construction module, used to construct a component model according to the attribute information of the component included in the pre-generated page; The second generating module is used to generate a first model tag of the component model according to the component identifier of the component included in the pre-generated page.

44. The device according to claim 43, wherein The second generating module is further used to generate a second model label of the component model according to the scene feature.

45. The device according to claim 43 or 44, wherein The second generating module is further configured to generate a third model tag of the component model according to a data set identifier of the data set when the component included in the pre-generated page is configured with a data set.

46. ​​The device according to any one of claims 39 to 45, wherein: The first generating module is further used to generate a page theme according to the appearance parameters of the pre-generated page; and to generate a theme tag of the page theme according to the scene features.

47. The device according to any one of claims 29 to 46, wherein: The first generating module is further configured to generate behavior information when a user configures a data set for the component, wherein the behavior information includes a component identifier of the component and a data set identifier of the data set.

48. The apparatus of claim 47, wherein: The behavior information also includes the scene feature and / or the block identifier of the first block where the component is located.

49. A device for generating a page template, wherein: The device comprises: The first acquisition module is used to acquire a page; A first generating module, used to generate a page template according to the page; A second acquisition module, used for acquiring scene features of the page from the page; The second generating module is used to generate a template tag of the page template according to the scene feature.

50. The apparatus of claim 49, wherein: The page template is arranged with a block corresponding to each component in the page, and the position of the block in the page template is the same as the position of the corresponding component in the page.

51. The apparatus of claim 50, wherein: The device also includes: The first setting module is used to set a unique block identifier for the block; and set a first component tag for the component corresponding to the block according to the block identifier.

52. The device according to claim 50 or 51, wherein: The device also includes: The second setting module is used to set a second component tag for the component according to the scene feature.

53. The device according to any one of claims 51-52, wherein: The device also includes: A construction module, used for constructing a component model according to attribute parameters of the component; The third generating module is used to generate a first model label of the component model according to the component identifier of the component.

54. The apparatus of claim 53, wherein: The third generating module is further used to generate a second model label of the component model according to the scene feature.

55. The apparatus of claim 53 or 54, wherein: The third generating module is further configured to generate a third model tag of the component model according to a data set identifier of the data set when the component is configured with a data set.

56. The device according to any one of claims 49 to 55, wherein: The device also includes: The fourth generating module is used to generate a page theme according to the appearance parameters of the page; and to generate a theme tag of the page theme according to the scene characteristics.

57. An electronic device, wherein: The electronic device includes the page generating device as claimed in claim 29 or 49.

58. A readable storage medium, wherein: The readable storage medium is used to store computer program code, and when the computer program code is executed by an electronic device, the electronic device executes the method according to any one of claims 1 to 28.

Images