Content management system interface generation method and device, equipment and storage medium

Abstract

The application relates to a content management system interface generation method and device, computer equipment and a storage medium. The method comprises the following steps: receiving first trigger information sent by a code warehouse management platform, wherein the trigger information carries a first configuration file; parsing the first configuration file into a form of a first data transmission mode; mapping the form of the first data transmission mode into a browser input component, so that a user end displays a first form corresponding to the first configuration file according to the browser input component, and the first form is a visual interface of a content management system platform on the user end; wherein the first configuration file is generated by the user end and sent to the code warehouse management platform by the user end, and the first trigger information is generated after the code warehouse management platform receives the first configuration file. In the application, the form is directly generated in a mapping mode, so that the system generation efficiency is high.

Description

Technical Field

[0001] This application relates to the field of computers, and more particularly to a method, apparatus, device, and storage medium for generating an interface based on a content management system. Background Technology

[0002] A Content Management System (CMS) is a software system that sits between the web front-end (web server) and the back-end office system or process (content creation and editing).

[0003] Content creators, editors, and publishers use content management systems (CMS) to submit, modify, approve, and publish content. Most existing CMSs on the market configure pages through a single configuration page. This means a configuration page defines all field types, names, and attributes for a form page, and then the data is maintained within the form page. After data maintenance, the data is retrieved through one or more data transmission protocols.

[0004] Existing solutions often fail to guarantee data type security and have low generation and maintenance efficiency. Summary of the Invention

[0005] In order to solve the above-mentioned technical problems, or at least partially solve the above-mentioned technical problems, this application provides a method, apparatus, device and storage medium for generating a content management system interface.

[0006] Firstly, this application provides a method for generating a content management system interface, applied to a server, the method comprising: Receive first trigger information sent by the code repository management platform, wherein the trigger information carries a first configuration file; The first configuration file is parsed into a form for the first data transmission mode; The form of the first data transmission mode is mapped to a browser input component so that the user terminal displays the first form corresponding to the first configuration file according to the browser input component. The first form is the visual interface of the content management system platform on the user terminal. The first configuration file is generated by the user terminal and sent to the code repository management platform by the user terminal, and the first triggering information is generated by the code repository management platform after receiving the first configuration file.

[0007] This application also provides a content management system interface generation apparatus, the apparatus comprising: The receiving unit is used to receive first trigger information sent by the code repository management platform, wherein the trigger information carries a first configuration file; A parsing unit is used to parse the first configuration file into a form of the first data transmission mode; A mapping unit is used to map the form of the first data transmission mode to a browser input component, so that the user terminal displays the first form corresponding to the first configuration file according to the browser input component, and the first form is the visual interface of the content management system platform on the user terminal. The first configuration file is generated by the user terminal and sent to the code repository management platform by the user terminal, and the first triggering information is generated by the code repository management platform after receiving the first configuration file.

[0008] This application also provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of any of the methods described above.

[0009] This application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of any of the methods described above.

[0010] In the content management system interface generation method of this application embodiment, the first configuration file in the trigger information is parsed into a form of a first data transmission mode, and the form of the first data transmission mode is mapped to a browser input component, so that the user terminal displays the first form corresponding to the first configuration file according to the browser input component. The first form is the visual interface of the content management system platform on the user terminal. In this application, since the form is generated directly by mapping, the system generation efficiency is high. Attached Figure Description

[0011] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0012] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0013] Figure 1 This is a diagram illustrating the application environment of the content management system interface generation method in this application embodiment; Figure 2 This is a flowchart illustrating the content management system interface generation method in this application embodiment; Figure 3The image shown is a schematic diagram of a first configuration file including annotations, according to an embodiment of this application. Figure 4 As shown Figure 3 The diagram shows the corresponding display of the first configuration file on the user's device. Figure 5 The diagram shown is a schematic representation of second document data carrying version information according to an embodiment of this application; Figure 6 The diagram shown is a schematic diagram of a first configuration file according to an embodiment of this application; Figure 7 The image shown is of this application. Figure 6 A schematic diagram of the form corresponding to the first configuration file shown; Figure 8 The diagram shown is a schematic representation of the content management system according to an embodiment of this application; Figure 9 The diagram shown is a schematic diagram of a content management system interface generation device according to an embodiment of this application; Figure 10 This is a diagram showing the internal structure of a computer device in an embodiment of this application. Detailed Implementation

[0014] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0015] Figure 1 This is an application environment diagram of a content management system (CMS) interface generation method in one embodiment. (Refer to...) Figure 1 This content management system interface generation method is applied to a content management system. The content management system includes a client 110 and a server 120. The client 110 and server 120 are connected via a network. The client 110 can be a desktop client or a mobile client; a mobile client can be at least one of a mobile phone, tablet, or laptop. The client 110 can be configured with a display device, which can have a browser or a browser-like interface. The server 120 can be a standalone server or a server cluster consisting of multiple servers.

[0016] like Figure 2As shown, in one embodiment, a content management system generation method is provided. This embodiment mainly applies this method to the above-mentioned... Figure 1 Let's take client 110 (or server 120) as an example. (Refer to...) Figure 2 The content management system generation method specifically includes: Step 210: Receive the first trigger information sent by the code repository management platform (Gitlab), which carries the first configuration file; Step 220: Parse the first configuration file into a form for the first data transmission mode; Step 230: Map the form of the first data transmission mode to a browser input component so that the user terminal displays the first form corresponding to the first configuration file according to the browser input component. The first form is the visual interface of the content management system platform on the user terminal. The first configuration file is generated by the user and sent to the code repository management platform (Gitlab platform). The first trigger information is generated by the code repository management platform after receiving the first configuration file.

[0017] In this embodiment of the application, the first configuration file may be generated from data configured on the user's end, or it may be generated based on data configured by the user on the user's end.

[0018] In this embodiment, the first configuration file can be a Protobuf configuration file. ProtoBuf, short for Protocol Buffers, is a language-independent, platform-independent, and extensible method for serializing structured data; it can be used for data communication protocols, data storage, etc. In this embodiment, the form for the first data transmission mode can be a JSON form.

[0019] In this embodiment of the application, the user sends the first configuration file to the code repository management platform. The repository management platform listens to the first configuration file and generates trigger information, which includes the first configuration file.

[0020] In this embodiment, the triggering information can also be a webhook service provided by the GitLab platform, which is triggered when the content on the GitLab platform changes. The GitLab platform receives the first configuration file, and when the content changes, the webhook service is triggered, generating the first triggering information.

[0021] In this embodiment, the browser, i.e., the user terminal, can render a form based on the browser input component. This form serves as the visual interface of the content management system platform on the user terminal. In the content management system platform interface generation method of this embodiment, the first configuration file in the trigger information is parsed into a form of a first data transmission mode, and the form of the first data transmission mode is mapped to a browser input component. This allows the user terminal to display the first form corresponding to the first configuration file based on the browser input component. The first form is the visual interface of the content management system platform on the user terminal. Because this application directly generates the form using a mapping method, the system generation efficiency is high.

[0022] In one embodiment of this application, the first configuration file includes a form configuration file, the form configuration file includes comments, and the form includes form attributes. The form that parses the first configuration file into the first data transmission mode includes: The comments in the first configuration file are parsed into form attributes of the form in the first data transmission mode.

[0023] In one embodiment of this application, the form attributes can be specific requirements or special requirements of the form, such as attributes like "optional", "required", "unique data", "changeable", and "unchangeable".

[0024] In one embodiment of this application, the first configuration file further includes a system protocol file. The first configuration file is sent from the user's client to the code repository management platform, and includes: According to the system protocol document, the first configuration file is sent from the user terminal to the code repository management platform.

[0025] In this embodiment, the system protocol file can be a variety of data transmission protocols, such as RPC, HTTP, etc. The system protocol file can be a pre-defined protocol within the system.

[0026] In this embodiment, the system protocol file and configuration file use the same Proto file, which unifies the files and eliminates the protocol conversion step, thus ensuring data security.

[0027] In embodiments of this application, parsing the first configuration file into a form of the first data transmission mode includes: The first configuration file is parsed into the original structure mapping through the database; The original structure is mapped to semantic reconstruction to generate a form for the first data transmission mode, and the comments of the first configuration file are reconstructed to generate form attributes of the form for the first data transmission mode.

[0028] In the embodiments of this application, the first configuration file is a Proto file, and the form of the first data transmission mode is a JSON form; The first configuration file is parsed into its original structure mapping via the database, including: The Proto file is parsed using the protobuf.js library to generate the original structure mapping; The original structure is semantically reconstructed to generate a form for the first data transmission mode. The comments in the first configuration file are reconstructed to generate form attributes for the form in the first data transmission mode, including: The original structure is semantically reconstructed to generate a key-value (KV) structure. The KV structure is then mapped to JSON data format. A JSON form is generated based on the JSON data format. The comments in the first configuration file are reconstructed to generate the form attributes of the JSON form.

[0029] In this embodiment, the original structure mapping is generated using the protobuf.js library. protobuf.js is an open-source database library that provides functions such as conversion between Proto and JSON, serialization, deserialization, and data format validation. In this embodiment of the application, the transformation from the first configuration file to the original structure mapping can be achieved using the protobuf.js library. Figure 6 The diagram shown is a schematic diagram of the first configuration file of this application embodiment, where the original structure is mapped to a specific data structure.

[0030] Semantic reconstruction refers to rewriting the original data structure into a data structure of a specific format. In this application, the original structure is mapped and rewritten into a KV structure.

[0031] In existing technologies, Proto files cannot be directly mapped to JSON because Proto is only a structure, while JSON contains both the structural information of the data and the content of the data.

[0032] The original structure in this application refers to the structural state before data is added and encoded during the conversion from Proto to JSON.

[0033] JSON forms are actually a key-value (KV) structured map data protocol. In the embodiments of this application, the client's browser obtains the browser input component to be rendered based on the KV structure, renders the browser input component into an actual form, and displays the actual form.

[0034] In this application, the first configuration file is a Proto file. Due to its inherent characteristics, the Proto file is a strongly typed configuration file. Furthermore, in this application, the first configuration file contains a form configuration file and a system protocol file. After defining the communication protocol (Proto file), the Proto file directly parses and maps the data structure described in the file. This allows users to maintain structured data in the generated form page (a visual representation of the data structure described in the Proto file), improving maintenance efficiency. It can be directly mapped to a data configuration page, saving the conversion steps required when using different transmission protocols and increasing development speed. Simultaneously, no protocol conversion is needed in systems with different transmission protocols, thus reducing system complexity and eliminating numerical or format distortions caused by protocol conversion, thereby ensuring data type security.

[0035] In one embodiment of this application, comments in a proto file can be written in YAML format. When parsing the proto file, the js-YAML library will parse the comments into attributes of the final generated form. For example, a comment can be `required`, with the corresponding form attribute being "required"; a comment can be `uniq`, with the corresponding form attribute being "unique data".

[0036] JS stands for JavaScript, a scripting language that runs in a browser. YAML is a language used to write configuration files. The js-yaml library is a database that connects scripting languages ​​and configuration files.

[0037] Figure 3 The diagram shown is a first configuration file containing comments according to an embodiment of this application. The comments are required and the corresponding form attributes are: required. Figure 4 As shown Figure 3 The diagram shows the corresponding display of the first configuration file on the user's device. Figure 4 In the text, "*" indicates that the field is required. Figure 3 , Figure 4 In the embodiment shown, the first configuration file includes the required comment. First, the first configuration file is parsed by the protobuf.js library to generate the original structure mapping. Then, the original structure mapping is reconstructed into a form of the first data transmission mode. The comment is reconstructed into form attributes. Finally, the form is mapped into a browser input component so that the browser displays the form. At this time, the required comment corresponds to the "*" in the form.

[0038] In this embodiment of the application, when configuring the configuration file on the user side, the first configuration file includes comments. In the generated form, the comments become form attributes, which simplifies the configuration process and improves efficiency.

[0039] In this embodiment of the application, before parsing the first configuration file into a form of the first data transmission mode, the method further includes: Retrieve the second configuration file nested within the first configuration file; The form that parses the first configuration file into the first data transmission mode includes: The first configuration file is parsed into a form in the first data transmission mode, and the second configuration file is parsed into a subform within the form in the first data transmission mode; Mapping the form in the first data transmission mode to a browser input component includes: Map the form of the first data transmission mode to a browser input component, and map the second configuration file to a child component in the browser input component.

[0040] The first configuration file can be a Proto file, and the second configuration file nested within it can be a Message file. When parsing the Proto file, the nested Message file is interpreted as a nested page structure within a form, i.e., a subform within a form. When mapping the Proto file to JSON format, the subform is mapped to a child component within a browser component. When displayed in the user's browser, the Message file will be displayed as a subform within the corresponding Proto form.

[0041] In this embodiment, the first configuration file and the second configuration file can be nested within each other. For example, a Message file may be nested within a Proto file, and another Proto file may be nested within the Message file. Correspondingly, the parsed key-value (KV) structures are also nested, for example, a first KV structure - a second KV structure - a first KV substructure. The first KV structure corresponds to the first configuration file, the second KV structure corresponds to the second configuration file, and the first KV substructure is a sub-configuration file nested within the second configuration file, whose attributes can be the same as those of the first configuration file.

[0042] Specifically, configuration file nesting can be: a Message nested in a Proto file, and another Proto file nested in the Message. The corresponding key-value structure can be: Proto corresponding key-value - Message corresponding key-value - another Proto corresponding key-value. When displayed, it will be shown as form - subform - subform of subform.

[0043] In this embodiment of the application, after mapping the form of the first data transmission mode to a browser input component so that the user terminal displays the first form corresponding to the first configuration file according to the browser input component, the method further includes: Receive update information from the user regarding the data in the first form; Retrieve the data of the first document corresponding to the first form; Update the data in the first document based on the updated information; An updated second document data is generated and stored, the updated second document data being identical to the updated first document data.

[0044] In this embodiment of the application, the second document data includes version information; After mapping the form of the first data transmission mode to a browser input component so that the client displays the first form corresponding to the first configuration file based on the browser input component, the method further includes: Receive rollback information from the user regarding the data in the first form. The rollback information includes the target version information. Retrieve data from multiple second documents corresponding to the first form; Based on the target version information, target second document data is obtained, wherein the version information of the target second document data corresponds to the target version information, and the target second document data is used to perform data rollback.

[0045] In this embodiment, each time the user saves changes to the form data, new version information is generated. In this embodiment, after a new version is added, it is published in an optional publishing environment via a publish event hook; each time a new version is published, new version information is generated.

[0046] In this application, after an update, the first document data is saved, and a second document data identical to the first document data is generated. Both the first and second document data are saved simultaneously. The next update modifies the first document data and also generates an updated second document data identical to the updated first document data. That is, in this application, each modification modifies the first document data, and each modification generates a second document data set. This second document data set carries version information, facilitating rollback during subsequent data rollback.

[0047] Version information can be a numerical identifier or a timestamp, etc., which will not be elaborated here.

[0048] Figure 5 The diagram shown is a schematic representation of second document data carrying version information according to an embodiment of this application. Figure 5 In the illustrated embodiment, the version information is a numerical number, and the operation on the second document data can be previewing or rolling back, etc.

[0049] In the method of this application embodiment, the first configuration file is a Proto file. Various data types and repeatable data types in the Proto file have browser-side component mappings. Table 1 shows the mapping relationship between the data types in the Proto file and the browser-side (JavaScript) data types and browser components in this application.

[0050] Table 1. Mapping relationship between data types in Proto files and data types and browser components on the user's browser.

[0051] Figure 6 The diagram shown is a schematic diagram of the first configuration file according to an embodiment of this application, as follows: Figure 6 As shown, 610 is the protocol file name, 620 indicates the overall form information, and 630 and 640 are the specific content of the form. The first configuration file described above, after being parsed and mapped by the method in this embodiment, can be obtained as follows: Figure 7 The diagram shows the form corresponding to the first configuration file. Specifically, this form is for "Retrieving Recommended Products for Insurance," and the productcode corresponds to the name in subsequent forms. From 630, we can obtain 710, and from 640, we can obtain 720.

[0052] In 630, the name, which is the form name, is "Product Code", and the comment "required: true" indicates that the attribute in 710 is "required".

[0053] Similarly, in 640, name, which is the form name, is "Solution Jump Link", and the comment "required: true" indicates that the attribute in 720 is "required".

[0054] The form's content is displayed on the user's browser as follows: Figure 7 As shown.

[0055] Figure 8 The diagram shown is a schematic representation of a content management system according to an embodiment of this application. Figure 8 As shown, this includes both the client and server. The GitLab platform can be configured on the client side.

[0056] Users configure the proto file on the client side.

[0057] Start a NodeJS service on the server. The NodeJS service proxies the SPA and serves as the entry point for the browser-side page (config.oa.com) to access this platform. The server listens for webhook messages from the GitLab platform (gitlab.oa.com). When it hears a push message for a Proto file, it parses the changed Proto file into a JSON data structure and further maps it to a browser component. For example, ... Figure 6 The file shown is parsed and mapped into a browser component.

[0058] The user's browser renders browser components as follows: Figure 7 The actual form shown.

[0059] After the user enters data into the generated form, the entered data is written to ConfigDB (MongoDB) by the NodeJS service. When synchronization is required, the user clicks the synchronization button, and the data in ConfigDB is written to other synchronization target databases by NodeJS.

[0060] In this embodiment of the application, entering data into the form is also a modification of the data in the form.

[0061] Modifying form data will modify the first document data. After modification, a second document, identical to the modified first document, will be generated and stored. Both the first and second document data will be written to the Config DB (MongoDB) by the NodeJS service. When synchronization is required, the data in the Config DB will be written to other synchronization target databases by NodeJS.

[0062] Data synchronization and saving can prevent data loss, ensure data synchronization, and reduce the occurrence of errors.

[0063] Other backend / frontend services retrieve the entered data through the Config Service (custom service). The Config Service provides RPC and HTTP protocol calling methods.

[0064] Corresponding to the above methods, this application provides a content management system generation apparatus, such as... Figure 9 As shown, the device includes: Receiving unit 910 is used to receive first trigger information sent by the code repository management platform, wherein the trigger information carries a first configuration file; The parsing unit 920 is used to parse the first configuration file into a form of the first data transmission mode; The mapping unit 930 is used to map the form of the first data transmission mode to a browser input component, so that the user terminal displays the first form corresponding to the first configuration file according to the browser input component. The first configuration file is generated by the user terminal and sent to the code repository management platform by the user terminal, and the first triggering information is generated by the code repository management platform after receiving the first configuration file.

[0065] In this embodiment of the application, the first configuration file includes a form configuration file, and the form configuration file includes comments. The parsing unit 920 parses the first configuration file into a form of the first data transmission mode, including: The comments in the first configuration file are parsed into form attributes of the form in the first data transmission mode.

[0066] In this embodiment of the application, the first configuration file further includes a system protocol file. The first configuration file is sent from the user terminal to the code repository management platform, including: According to the system protocol file, the first configuration file is sent from the user terminal to the code repository management platform.

[0067] In this embodiment of the application, the receiving unit 910 is further configured to obtain a second configuration file nested in the first configuration file before the parsing unit 920 parses the first configuration file into a form of the first data transmission mode; The parsing unit 920 is also used to parse the first configuration file into a form of the first data transmission mode, including: The parsing unit 920 is further configured to parse the first configuration file into a form of the first data transmission mode, and parse the second configuration file into a sub-form of the form of the first data transmission mode; The mapping unit 930 maps the form of the first data transmission mode to a browser input component, including: The form of the first data transmission mode is mapped to a browser input component, and the second configuration file is mapped to a sub-component in the browser input component.

[0068] In this embodiment of the application, the parsing unit 920 parses the first configuration file into a form of the first data transmission mode, including: The first configuration file is parsed into its original structure mapping using the database; The original structure is mapped and semantically reconstructed to generate a form for the first data transmission mode.

[0069] In this embodiment of the application, after mapping the form of the first data transmission mode to a browser input component so that the user terminal displays the first form corresponding to the first configuration file according to the browser input component, the receiving unit 910 is further configured to: Receive update information from the user terminal regarding the data in the first form; Retrieve the first document data corresponding to the first form; The first document data is updated according to the update information; Generate and store updated second document data that is identical to the updated first document data.

[0070] In this embodiment of the application, the second document data includes version information; After mapping the form of the first data transmission mode to a browser input component, so that the user terminal displays the first form corresponding to the first configuration file according to the browser input component, the receiving unit 910 is further configured to: Receive rollback information from the user terminal regarding the data in the first form, wherein the rollback information includes the target version; Retrieve multiple second document data corresponding to the first form; Based on the target version in the rollback information, obtain second document data corresponding to the version information of the target version from multiple second document data; Data rollback is performed using the second document data corresponding to the version information and the target version.

[0071] In this embodiment of the application, the first configuration file is a Proto file, and the form of the first data transmission mode is a JSON form; The parsing unit 910 is also used for: The Proto file is parsed using the protobuf.js library to generate the original structure mapping; The step of generating a form for the first data transmission mode by reconstructing the semantic mapping of the original structure includes: The original structure is mapped and semantically reconstructed to generate a key-value (KV) structure, which is then used as the JSON form.

[0072] Figure 10 An internal structural diagram of a computer device in one embodiment is shown. Specifically, this computer device may be... Figure 1 The client is 110 (or the server is 120). For example... Figure 10As shown, the computer device includes a processor, memory, network interface, input device, and display screen connected via a system bus. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores an operating system and may also store computer programs. When executed by the processor, these computer programs enable the processor to implement a content management system generation method. The internal memory may also store computer programs, which, when executed by the processor, enable the processor to execute the content management system generation method. The display screen can be an LCD screen or an e-ink screen. The input device can be a touch layer covering the display screen, buttons, a trackball, or a touchpad mounted on the computer device's casing, or an external keyboard, touchpad, or mouse.

[0073] Those skilled in the art will understand that Figure 10 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0074] In one embodiment, the content management system generation apparatus provided in this application can be implemented as a computer program, and the computer program can be implemented as follows: Figure 10 It runs on the computer device shown. The computer device's memory can store the various program modules that make up the content management system generation device.

[0075] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it performs the following steps: receiving first trigger information sent by a code repository management platform, the trigger information carrying a first configuration file; parsing the first configuration file into a form of a first data transmission mode; mapping the form of the first data transmission mode to a browser input component, so that the user terminal displays a first form corresponding to the first configuration file according to the browser input component; wherein the first configuration file is generated by the user terminal and sent to the code repository management platform by the user terminal, and the first trigger information is generated by the code repository management platform after receiving the first configuration file.

[0076] In one embodiment, the processor also implements the steps of the above method when executing the computer program, which will not be repeated here.

[0077] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When executed by a processor, the computer program performs the following steps: receiving first trigger information sent by a code repository management platform, the trigger information carrying a first configuration file; parsing the first configuration file into a form of a first data transmission mode; mapping the form of the first data transmission mode into a browser input component, so that the user terminal displays a first form corresponding to the first configuration file according to the browser input component; wherein the first configuration file is generated by the user terminal and sent to the code repository management platform by the user terminal, and the first trigger information is generated by the code repository management platform after receiving the first configuration file.

[0078] In one embodiment, the computer program, when executed by a processor, also implements the steps of the above method, which will not be repeated here.

[0079] According to one aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the following steps: receiving first trigger information sent by a code repository management platform, the trigger information carrying a first configuration file; parsing the first configuration file into a form of a first data transmission mode; mapping the form of the first data transmission mode to a browser input component, so that a user terminal displays a first form corresponding to the first configuration file according to the browser input component; wherein the first configuration file is generated by the user terminal and sent to the code repository management platform by the user terminal, and the first trigger information is generated by the code repository management platform after receiving the first configuration file.

[0080] In one embodiment, the computer program product or computer program, when executed, also implements the steps of the above method, which will not be repeated here.

[0081] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0082] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0083] The above description is merely a specific embodiment of this application, enabling those skilled in the art to understand or implement this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A method for generating an interface based on a content management system, characterized in that, Applied to a server, the method includes: Receive first trigger information sent by the code repository management platform, wherein the trigger information carries a first configuration file; The first configuration file is parsed into a form for the first data transmission mode; The form of the first data transmission mode is mapped to a browser input component so that the user terminal displays the first form corresponding to the first configuration file according to the browser input component. The first form is the visual interface of the content management system platform on the user terminal. Wherein, the first configuration file is generated by the user terminal and sent by the user terminal to the code repository management platform, and the first triggering information is generated by the code repository management platform after receiving the first configuration file; The first configuration file is a Proto file, which includes a form configuration file, and the form configuration file includes comments and form attributes. The form that parses the first configuration file into the first data transmission mode includes: The Proto file is parsed using the protobuf.js library to generate the original structure mapping; The original structure is semantically reconstructed to generate a key-value (KV) structure. The KV structure is then mapped to JSON data format to generate a JSON form. The comments in the first configuration file are reconstructed to generate form attributes of the JSON form. The JSON form is a form of the first data transmission mode.

2. The method according to claim 1, characterized in that, The first configuration file also includes a system protocol file. The first configuration file is sent from the user terminal to the code repository management platform, including: According to the system protocol file, the first configuration file is sent from the user terminal to the code repository management platform.

3. The method according to claim 1, characterized in that, Before parsing the first configuration file into a form of the first data transmission mode, the method further includes: Retrieve the second configuration file nested within the first configuration file; The form that parses the first configuration file into the first data transmission mode includes: The first configuration file is parsed into a form of the first data transmission mode, and the second configuration file is parsed into a sub-form of the form of the first data transmission mode; The step of mapping the form of the first data transmission mode to a browser input component includes: The form of the first data transmission mode is mapped to a browser input component, and the second configuration file is mapped to a sub-component in the browser input component.

4. The method according to claim 1, characterized in that, After mapping the form of the first data transmission mode to a browser input component so that the user terminal displays the first form corresponding to the first configuration file according to the browser input component, the method further includes: Receive update information from the user terminal regarding the data in the first form; Retrieve the first document data corresponding to the first form; The first document data is updated according to the update information; An updated second document data is generated and stored, the updated second document data being identical to the updated first document data.

5. The method according to claim 4, characterized in that, The second document data includes version information; After mapping the form of the first data transmission mode to a browser input component so that the user terminal displays the first form corresponding to the first configuration file according to the browser input component, the method further includes: Receive rollback information from the user terminal regarding the data in the first form, wherein the rollback information includes target version information; Retrieve multiple second document data corresponding to the first form; Based on the target version information, target second document data is obtained, wherein the version information of the target second document data corresponds to the target version information, and the target second document data is used to perform data rollback.

6. A content management system interface generation device, characterized in that, The device includes: The receiving unit is used to receive first trigger information sent by the code repository management platform, wherein the trigger information carries a first configuration file; A parsing unit is used to parse the first configuration file into a form of the first data transmission mode; The mapping unit is used to map the form of the first data transmission mode to a browser input component, so that the user terminal displays the first form corresponding to the first configuration file according to the browser input component, and the first form is the visual interface of the content management system platform on the user terminal. Wherein, the first configuration file is generated by the user terminal and sent by the user terminal to the code repository management platform, and the first triggering information is generated by the code repository management platform after receiving the first configuration file; The first configuration file is a Proto file, which includes a form configuration file, and the form configuration file includes comments and form attributes. The form that parses the first configuration file into the first data transmission mode includes: The Proto file is parsed using the protobuf.js library to generate the original structure mapping; The original structure is semantically reconstructed to generate a key-value (KV) structure. The KV structure is then mapped to JSON data format to generate a JSON form. The comments in the first configuration file are reconstructed to generate form attributes of the JSON form. The JSON form is a form of the first data transmission mode.

7. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 5.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 5.

Images