WO2023123089A1

WO2023123089A1 - Content management system, static page management method and device, and storage medium

Info

Publication number: WO2023123089A1
Application number: PCT/CN2021/142611
Authority: WO
Inventors: 韩非; 雷焱森; 刘阳; 温书豪; 马健
Original assignee: 深圳晶泰科技有限公司
Priority date: 2021-12-29
Filing date: 2021-12-29
Publication date: 2023-07-06

Abstract

The present application discloses a content management system, a static page management method and device, and a storage medium. The system comprises: a page editor used for acquiring a source code file, for displaying a static page produced from the source code file and, in response to an editing operation on a target node in the static page, for modifying node content data associated with the target node so as to obtain an updated static page and an updated source code file; a version management system used for acquiring a source code file from a codebase and sending the source code file to the page editor and also used for acquiring an updated source code file from the page editor and sending the updated source code file to the codebase; a front-end development scaffolding tool used for producing a static page from a source code file acquired by the page editor; and a static resource server used for storing an updated static page. The present application resolves the problem in the prior art of over-dependence on data models during static page content management.

Description

Content management system, static page management method, device and storage medium

technical field

The present application relates to the technical field of page management, in particular, to a content management system, a static page management method, device and storage medium.

Background technique

The current mainstream CMS (Content Management System, content management system) is driven by data, that is, content management is realized through dynamic pages. Write, write the corresponding data model in the server-side program, and build a table in the database to store the corresponding data. When the visitor visits the corresponding website, the server-side reads the corresponding data from the database, dynamically renders the page and Return to the client.

CMS in related technologies include: Django-CMS, ThinkPhp, Strapi, and other content management system frameworks based on different languages. Database; page dynamic rendering, when a user visits, the server dynamically renders the page.

Therefore, the CMS in the related art has the following problems: Problem 1, when managing the content of the static page, it relies too much on the data model. For some or all of the content on the static page, the corresponding data model is established in the program in advance and a table is created in the database, and finally the template is replaced and reconstructed for the static page. It should be noted that, as static pages become more and more complex today, the previous page reconstruction, data model design and development will bring huge time investment in maintenance. Question 2, dynamic pages are not conducive to SEO (Search Engine Optimization, search engine optimization), dynamic links to SEO optimization is more convenient for page adjustment and management, dynamic page links have a greater pressure on server load, website access speed Slow, the path is not accurate and clear, the page exception rate is high, and there are false path files, which is not conducive to SEO optimization effect.

Aiming at the problem of excessive reliance on the data model when managing the content of the static page in the related art, no effective solution has been proposed yet.

Contents of the invention

The present application provides a content management system, static page management method, device and storage medium to solve the problem of excessive reliance on data models when managing the content of static pages in the related art.

According to one aspect of the present application, a content management system is provided. The system includes: a page editor, which is used to obtain source code files, display static pages generated by source code files, and respond to editing operations on target nodes in static pages, modify node content data associated with target nodes, and obtain updated static Pages and updated source code files, in which a static page is associated with a key-value pair dataset of node identifiers and node content; the version management system is used to obtain source code files from the code warehouse and send the source code files to the page for editing It is also used to obtain the updated source code file from the page editor and send the updated source code file to the code warehouse; the front-end development scaffolding tool is used to generate the source code file obtained by the page editor into a static page; static resources The server is configured to obtain the updated static page from the page editor, store the updated static page, and generate an access link corresponding to the updated static page.

Optionally, the static resource server is a cloud server, and the cloud server stores the updated static page and generates an access path corresponding to the updated static page.

Optionally, the front-end development scaffolding tool performs at least one of the following processes on the source code file to obtain a static page: packaging processing, compression processing, and page content injection processing; wherein, the packaging processing is used to detect the public code corresponding to the source code file and convert the public The visual data corresponding to the code is injected into the mark position of the static page; the compression processing is used to compress the space data and newline data in the source code file, and replace the variable larger than the preset length with the variable of the target length; the page content injection processing is used to convert the The data in the source code file is injected into the default page template.

According to another aspect of the present application, a static page management method is provided. The method includes: obtaining the source code file, generating the source code file as a static page through the front-end development scaffolding tool, and displaying the static page, wherein, the static page is associated with a node identifier and a node content key-value pair data set; responding to the static The editing operation of the target node in the page modifies the node content data associated with the target node to obtain an updated static page; the source code file is updated according to the updated static page to obtain an updated source code file.

Optionally, after updating the source code file according to the updated static page and obtaining the updated source code file, the method further includes: detecting whether a release instruction for the updated static page is received; to synchronize the updated static page to the static resource server.

Optionally, after receiving the release instruction, after synchronizing the updated static page to the static resource server, the method further includes: receiving feedback information corresponding to the release instruction, and judging whether the updated static page is The release is successful; if the release fails, obtain the source code file of the previous version of the updated static page through the version management system, and obtain the target source code file; generate the static page corresponding to the target source code file through the front-end development scaffolding tool, and obtain the target source code file to be detected in response to the editing operation of the static page to be detected, modify the content data associated with the static page to be detected, obtain the target static page, and update the target source code file according to the target static page.

Optionally, before updating the source code file according to the updated static page to obtain the updated source code file, the method further includes: judging whether a confirmation instruction for the updated static page is received, and if the confirmation instruction is received , executing the step of updating the source code file according to the updated static page to obtain the updated source code file.

According to another aspect of the present application, a device for managing static pages is provided. The device includes: a first acquisition unit for acquiring source code files, generating the source code files as static pages through front-end development scaffolding tools, and displaying the static pages, wherein the static pages are associated with a node identifier and a key value of the node content For the data set; the first response unit is used to respond to the editing operation of the target node in the static page, modify the node content data associated with the target node, and obtain an updated static page; the update unit is used to update the static page according to the updated static page Update the source code file to get the updated source code file.

Optionally, the device further includes: a detection unit, configured to detect whether a release instruction for the updated static page is received after the update unit updates the source code file according to the updated static page and obtains the updated source code file; A unit, configured to synchronize the updated static page to the static resource server when the detection unit detects that the publishing instruction is received.

Optionally, the device further includes: a receiving unit, configured to receive feedback information corresponding to the release instruction after the synchronization unit synchronizes the updated static page to the static resource server, and judge whether the updated static page is published according to the feedback information Success; the second acquisition unit is used to obtain the source code file of the previous version of the updated static page through the version management system in the case of failure of the release, and obtains the target source code file; the generation unit is used to generate through the front-end development scaffolding tool The static page corresponding to the target source code file obtains the static page to be detected; the second response unit is used to respond to the editing operation of the static page to be detected, modify the content data associated with the static page to be detected, obtain the target static page, and according to The target static page updates the target source code file.

Optionally, the device further includes: a judging unit, used for judging whether a confirmation instruction for the updated static page is received before the updating unit updates the source code file according to the updated static page and obtains the updated source code file; The unit is configured to execute the step of updating the source code file according to the updated static page to obtain the updated source code file when the confirmation instruction is received.

According to another aspect of the embodiments of the present invention, a non-volatile storage medium is also provided, and the non-volatile storage medium includes a stored program, wherein, when the program runs, the device where the non-volatile storage medium is located is controlled to execute a A method of managing static pages.

According to another aspect of the embodiments of the present invention, there is also provided an electronic device, including a processor and a memory; computer-readable instructions are stored in the memory, and the processor is used to run the computer-readable instructions, wherein, when the computer-readable instructions run A static page management method is implemented.

Through this application, the page editor is used to obtain the source code file, display the static page generated by the source code file, and respond to the editing operation of the target node in the static page, modify the node content data associated with the target node, and obtain the updated Static pages and updated source code files, where a static page is associated with a node identifier and a key-value pair data set of node content; a version management system is used to obtain source code files from the code warehouse and send the source code files to the page The editor is also used to obtain the updated source code file from the page editor and send the updated source code file to the code warehouse; the front-end development scaffolding tool is used to generate the source code file obtained by the page editor into a static page; static The resource server is used to obtain the updated static page from the page editor, store the updated static page, and generate an access link corresponding to the updated static page, which solves the problem of data loss when managing the content of the static page in related technologies. Model dependence is too high. Static resources are stored in the way of linking node content data with node identifiers, and the node content data associated with nodes in static pages can be modified to achieve the purpose of modifying static pages, thereby improving the flexibility of managing static pages and reducing the need for data models. The effect of dependence.

Description of drawings

The drawings constituting a part of the application are used to provide further understanding of the application, and the schematic embodiments and descriptions of the application are used to explain the application, and do not constitute an improper limitation to the application. In the attached picture:

FIG. 1 is a schematic diagram of a content management system provided according to an embodiment of the present application;

Fig. 2 is a schematic diagram of an optional content management system provided according to an embodiment of the present application;

FIG. 3 is a flowchart of a static page management method provided according to an embodiment of the present application;

Fig. 4 is a flow chart of the rollback operation of the page code in the static page management method provided according to the embodiment of the present application;

Fig. 5 is a schematic diagram of an apparatus for managing static pages provided according to an embodiment of the present application.

Detailed ways

It should be noted that, in the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and embodiments.

In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiment of the application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiment of the application. Obviously, the described embodiment is only It is an embodiment of a part of the application, but not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without creative efforts shall fall within the scope of protection of this application.

It should be noted that the terms "first" and "second" in the description and claims of the present application and the above drawings are used to distinguish similar objects, but not necessarily used to describe a specific sequence or sequence. It should be understood that the data so used may be interchanged under appropriate circumstances for the embodiments of the application described herein. Furthermore, the terms "comprising" and "having", as well as any variations thereof, are intended to cover a non-exclusive inclusion, for example, a process, method, system, product or device comprising a sequence of steps or elements is not necessarily limited to the expressly listed instead, may include other steps or elements not explicitly listed or inherent to the process, method, product or apparatus.

For ease of description, some nouns or terms involved in the embodiments of the present application are described below:

CMS (full name in English: content management system, Chinese: content management system) is a software that helps users create, manage and modify content on the website without professional technical knowledge. its different data. Static pages actually exist and are directly loaded into the pages displayed on the client's browser without compilation by the server.

SEO: (English full name: Search Engine Optimization, Chinese: Search Engine Optimization), search engine optimization is a way to adjust the website by understanding the operating rules of the search engine and improve the ranking of the target website in the relevant search engine.

According to an embodiment of the present application, a content management system is provided, as shown in Figure 1, the system includes:

The page editor 101 is used to obtain the source code file, display the static page generated by the source code file, and respond to the editing operation of the target node in the static page, modify the node content data associated with the target node, and obtain the updated static page and update The final source code file, in which the static page is associated with a key-value pair data set of node identifier and node content.

Specifically, the page editor 101 is a set of browser-side web applications for previewing static pages and editing static page content. It can pull locally packaged static pages, and can also obtain the submission records of the project warehouse through the version management system 102. Switch the project to a different submission version, obtain the source code file from the code warehouse, and package the source code file into a static page through the front-end development scaffolding tool 103, and generate node identifiers and node content data corresponding to multiple nodes of the static page, multiple pairs The node identifier and node content data constitute key-value pair data.

After the static page is generated, the user can edit the content of the static page, visually click the node in the page, and dynamically modify the node content of the key-value pair data. After the node content is modified, according to the current static page and the corresponding key value Generate a new static page for the data. When modifying and saving the preview page, reversely locate the path and location of the source code file of the modified node, update the source code file, and achieve the purpose of modifying the content of the source code file, achieving the realization of a static page out of the database for content management purposes.

In an optional embodiment, when the page editor 101 previews the page, it can import a packaged static page under the corresponding directory of the project, click on the corresponding page to jump to the URL, and load the corresponding page at the same time Data, update the content data when saving, the NodeGit third-party tool library can be used in the page editor 101, the tool library can realize the encapsulation of the underlying operation of the version management system 102, and provide the API interface of javascript objects.

The version management system 102 is used to obtain the source code file from the code warehouse, and send the source code file to the page editor 101, and is also used to obtain the updated source code file from the page editor 101, and send the updated source code file to the code storehouse.

It should be noted that the version management system 102 refers to the management tool of the code warehouse, which can be Git and SVN. In this example, the third-party tool library NodeGit is used to control Git to switch the code warehouse, code rollback, A series of operations such as code pull and submission.

Specifically, after clicking Save on the page editor 101, the page editor 101 will search for the file corresponding to the source code according to the currently updated node-node content mapping relationship, and after matching the corresponding file, the version management system 102 will update the source code file according to the latest node content.

The front-end development scaffolding tool 103 is used to generate the source code file obtained by the page editor 101 into a static page.

Specifically, the static resource server 104 may export the static resource files stored locally on the computer to a specified file directory of the static resource server, and the front-end development scaffolding tool 103 generates static pages according to the static resource files.

The static resource server 104 is configured to obtain an updated static page from the page editor 101, store the updated static page, and generate an access link corresponding to the updated static page.

Specifically, when storing a static page, you can use a scanning tool to scan the content nodes in the static page, and assign a unique identifier to each content node, and generate a flattened key-value pair data according to the scanning situation. The key-value pair data stores the node identifier and node content in one-to-one correspondence, thereby forming a static resource file, and storing the static resource file in the static resource server 104 .

Wherein, the scanning tool may be an analysis script tool of NodeJS, and may also be a tool for analyzing an html file and generating a DOM structure. This embodiment does not limit the type of the scanning tool.

In an optional embodiment, as shown in Figure 2, the page editor 101 in the content management system is a GUI editing tool, the version management system 102 is git, the front-end development scaffolding tool 103 is a webpack tool, and the static resource server 104 For the cloud server, use the webpack packaging tool to package the source code files to build a static page. The GUI editing tool can edit the static page and generate an updated static page. The GUI editing tool can also synchronize the updated static page to the cloud. The server, GUI editing tools and git can execute Git commands through NodeJ to update the source code corresponding to the static page.

The content management system provided by the embodiment of the present application adopts the page editor 101 to obtain the source code file, display the static page generated by the source code file, and modify the node associated with the target node in response to the editing operation of the target node in the static page content data, to obtain the updated static page and the updated source code file, wherein, the static page is associated with a key-value pair data set of node identifier and node content; the version management system 102 is used to obtain the source code file from the code warehouse , and send the source code file to the page editor 101, and also be used to obtain the updated source code file from the page editor 101, and send the updated source code file to the code warehouse; the front-end development scaffolding tool 103 is used to edit the page The source code file obtained by the editor 101 is generated as a static page; the static resource server 104 is used to obtain the updated static page from the page editor 101, store the updated static page, and generate an access link corresponding to the updated static page to solve The problem of over-reliance on the data model when managing the content of the static page in the related art is solved. Static resources are stored in the way of linking node content data with node identifiers, and the node content data associated with nodes in static pages can be modified to achieve the purpose of modifying static pages, thereby improving the flexibility of managing static pages and reducing the need for data models. The effect of dependence.

Optionally, in the content management system provided in the embodiment of the present application, the static resource server 104 is a cloud server, and the cloud server stores updated static pages and generates an access path corresponding to the updated static pages.

Specifically, the static resource server 104 is a cloud server with a cloud storage function provided by the current cloud provider. In addition, developers can also develop server programs to process requests and responses, and deploy the programs on corresponding servers.

It should be noted that for the cloud storage function, static pages can be stored on the cloud server and access links can be generated, and the jump between pages can be realized according to the relative file path and the jump relationship in the page, and the corresponding static page can be displayed. There is no need to deal with the browser's response specifically, where the relative path before the page is similar to the relative path between the local, for example: a folder is placed on the cloud server, and there are 1.html and 2.html in the folder , 3.html three files, you can access this folder on the cloud through the website www.test.com, when you need to access 1.html, you only need to modify and access www.test.com/1.html, access 2. html, 2.html and 1.html are the same.

It should be noted that the use of the cloud storage function requires the installation of the COSCMD tool. In the file directory of the current computer user, configure the bucket (Bucket), region (Region), secret key, and secret key ID of the cloud server. After the configuration is complete, With the shell process of node, call the command line to upload local folders and files to the cloud server. The uploaded files refer to the static resources to be stored as mentioned above; the uploaded folder contains all the codes of a static resource management. The NodeJS part also has static resource pictures, video text and other parts. Among them, the command format for uploading files: coscmd upload<localpath><cospath>, the command format for uploading folders: coscmd upload-r<localpath><cospath>.

Optionally, in the content management system provided by the embodiment of the present application, the front-end development scaffolding tool 103 performs at least one of the following processes on the source code file to obtain a static page: packaging processing, compression processing, and page content injection processing; wherein, packaging processing It is used to detect the public code corresponding to the source code file, and inject the visual data corresponding to the public code into the mark position of the static page; the compression process is used to compress the space data and newline data in the source code file, and replace the variable larger than the preset length is the variable of the target length; the page content injection process is used to inject the data in the source code file into the preset page template.

Specifically, the front-end development scaffolding tool 103 integrates functions of source code file packaging, compression, obfuscation, hot update, and automatic page content injection.

It should be noted that in order to achieve code reuse in the source code development stage of static pages, the same parts in multiple pages will be extracted, such as the top menu bar, the bottom address bar, and some forms or sidebars will also be reused , so that only one code needs to be maintained during the source code development stage, without repeated changes.

Among them, the packaging and compression function of the front-end development scaffolding tool 103 is that it can detect the injected code fragments of the common part on different pages, and inject the corresponding public part into the corresponding target position according to this fragment. Specifically, many pages may There will be a public header or bottom, these public parts only need to maintain one copy, mark or import in other files in a special way, and finally inject these public parts into each marked place, and replace the original marked.

At the same time, the packaging function of the front-end development scaffolding tool 103 also has the ability to merge requests and merge multiple static resources into one. The compression and obfuscation functions of the front-end development scaffolding tool 103 are mainly aimed at js script files, compressing redundant spaces and line breaks, and replacing redundant variables in the code. For example, the variable named thisisatestname in some codes can be compressed by the scaffolding tool Replace it with an abbreviation such as a or b), so as to achieve storage space for smaller files and save transmission bandwidth.

The hot update of the front-end development scaffolding tool 103 is the ability to package and refresh pages in real time during static page development and debugging, thereby improving the efficiency of development and debugging.

The automatic injection of the page content of the front-end development scaffolding tool 103 refers to the ability of the scaffolding tool to match special strings in the page to perform template injection or template replacement. Will match <% and %> and the contents of them, and replace.

The template injection of the front-end development scaffolding tool 103 can be realized by the plug-in of webpack. The simplest method is to match a target string, then find the target content according to the information obtained by matching in this string, and then read the target content for replacement. The static pages packaged with functions will have special tags for identification and positioning at specific content, and the generated pages will cooperate with the GUI tool for page editing and preview to realize the positioning of edited content and the ability to reverse locate the corresponding content in the source code location.

In an optional embodiment, the front-end development scaffolding tool 103 is Webpack, the statically dependent third-party style and component library is Bootstrap, and html-loader is used to deal with the template reuse problem of repeated parts of multiple pages.

Wherein, the project directory generated by the front-end development scaffolding tool 103 includes a plurality of folders, specifically, includes a config folder, and the config folder is a configuration file for packaging and constructing static page files. These configuration files guide webpack to build and package. Including the injection of public templates, the merging and packaging of js and css resources, the encoding of multimedia resources such as pictures, and the template processing of html files; it also includes the dist folder. The contents of the dist folder are static resource files after packaging and construction. The content of the static resource file previewed and published on the static resource server 104 also includes a map folder, the json data stored in the map folder is consistent with the directory structure of the html folder under the static folder, and each html file is stored. The json data of the editable content in the page. The json data stores the unique identifier of the dom node and the key-value pair data of the content. This file is automatically generated and updated every time the html file is updated (the process used Cheerio performs dom analysis on the html file in the node environment), and when packaging, it will replace the content of the corresponding node in the html folder according to the mapping data in this folder; return the server folder, and the files in the server folder are used for processing The service logic of the page editing GUI includes the operation of the code warehouse, the resource synchronization operation of the static resource server 104, and the rewriting operation of the source code file; it also includes the static folder, which stores the source code of the static page in the development stage under the static folder. It is used to generate the initial source of the final build and packaged page; it also includes the webapp folder, where the source code of the GUI interactive interface is stored under the webapp folder. When the GUI interface starts, the code here will be compiled and executed, and combined with the server file Cooperate with the files under the folder, and perform a series of operations on the files.

According to an embodiment of the present application, a static page management method is provided.

Fig. 3 is a flowchart of a static page management method according to an embodiment of the present application. As shown in Figure 3, the method includes the following steps:

Step S302, obtain the source code file, generate the source code file as a static page through the front-end development scaffolding tool, and display the static page, wherein, the static page is associated with a data set of node identifier and node content key-value pair.

You can obtain source code files from the code warehouse through the version management system, and package the source code files into static pages through the front-end development scaffolding tool, and generate node identifiers and node content data corresponding to multiple nodes of the static page, and multiple pairs of node identifiers and node identifiers. Node content data constitutes key-value pair data.

It should be noted that after developing a set of static pages, the overall resources can be packaged, and the packaged static resource files will be exported to the corresponding folder of the project for calling by the GUI web application for editing and previewing. On the page, you can use the closed tag to wrap the place that needs to be edited and modified, and give the tag class="cms-editable", inject a special tag on the content node that needs to be edited, so as to facilitate the establishment of mapping data between nodes and node content , and it is also convenient to accurately locate the marked target node during editing.

Step S304, in response to the editing operation on the target node in the static page, modify the node content data associated with the target node, and obtain an updated static page.

Specifically, the static pages under the project folder can be displayed, and the main interface will switch and display after clicking the static page to be edited. Use the mouse movement event to obtain the target node that the mouse is hovering over in real time when the mouse is moving, double-click the mouse to obtain the focus of the target node, and edit the content of the corresponding node. The above operations have the characteristics of what you see is what you get, and you can preview the page effect after the copy or image resource is updated in real time.

Step S306, updating the source code file according to the updated static page to obtain the updated source code file.

Optionally, in the static page management method provided in the embodiment of the present application, before updating the source code file according to the updated static page to obtain the updated source code file, the method further includes: judging whether to receive the updated The confirmation instruction of the static page, in the case of receiving the confirmation instruction, executes the step of updating the source code file according to the updated static page to obtain the updated source code file.

It should be noted that the updated static page is only a temporary file, only after clicking the save button, according to the currently updated node-node content mapping relationship, to find the corresponding file of the source code, after matching the corresponding file , the source code data will be updated persistently according to the latest content. Specifically, after clicking the save button, the focused dom in the mouse movement event will be obtained. After obtaining the custom attribute map-id of the dom, it can be identified according to the value Keyword goes to the corresponding json file under the map folder, and the content update in the current dom node is synchronized to the content corresponding to the key.

The static page management method provided by the embodiment of the present application obtains the source code file, generates the source code file as a static page through the front-end development scaffolding tool, and displays the static page, wherein, the static page is associated with a node identifier and node content Key-value pair data set; respond to the editing operation of the target node in the static page, modify the node content data associated with the target node, and obtain the updated static page; update the source code file according to the updated static page, and obtain the updated source code file The invention solves the problem in the related art that the content of the static page is overly dependent on the data model. Static resources are stored in the way of linking node content data with node identifiers, and the node content data associated with nodes in static pages can be modified to achieve the purpose of modifying static pages, thereby improving the flexibility of managing static pages and reducing the need for data models. The effect of dependence.

Optionally, in the static page management method provided in the embodiment of the present application, after updating the source code file according to the updated static page and obtaining the updated source code file, the method further includes: detecting whether the updated Publishing instruction of the static page; upon receiving the publishing instruction, synchronizing the updated static page to the static resource server.

Specifically, after the source code file is updated, it will actively trigger a project packaging operation to generate a brand new project folder, which can be previewed in the GUI tool. This operation simulates the interface published to the static resource server. After confirming that it is correct, the user can click the release button to trigger the submission operation of the code warehouse, and store the modification record in the version management system of the code warehouse. After submitting the source code, the GUI tool will save the project folder in the project The static pages under the static resource server are synchronized to the folder specified by the static resource server through the interface of the static resource server to realize the publishing of the static pages.

Due to the occurrence of network exceptions from time to time, when there is a static page publishing failure, optionally, in the static page management method provided in the embodiment of the present application, when the release instruction is received, the updated static page After the page is synchronized to the static resource server, the method further includes: receiving feedback information corresponding to the publishing instruction, and judging whether the updated static page is successfully published according to the feedback information; if the publishing fails, obtaining the updated static page through the version management system Obtain the target source code file from the source code file of the previous version of the static page; generate the static page corresponding to the target source code file through the front-end development scaffolding tool, and obtain the static page to be detected; respond to the editing operation of the static page to be detected, and modify the static page to be detected The content data associated with the static page is obtained to obtain the target static page, and the target source code file is updated according to the target static page.

Specifically, after the static page is released, you can move to the officially released website to check the update status of the page content again. When an unexpected situation occurs, the publishing website can also send a notification message to the GUI tool. The GUI tool uses the function of version switching Perform the rollback operation of the page code, specifically, obtain the source code file corresponding to the static page through the version management system, generate the static page to be detected, modify the content data associated with the static page to be detected, and obtain the modified static page, thereby according to The modified static page updates the source code file to realize the rollback of the source code file.

According to the embodiment of the present application, another static page management method is also provided.

Step 1: Use the scaffolding tool to generate the file directory of the project according to the preset file content and file structure.

Step 2: Install all third-party plug-ins that the project depends on: webpack, nodeGit, bootstrap, coscmd, cheerio, etc.

Step 3: Develop a static page. In the process of developing a static page, use a closed tag to wrap the place that needs to be edited and modified, and assign the tag class="cms-editable". The purpose of this is to be able to edit when needed A special mark is injected into the content node of the content node, which is convenient for establishing the mapping data of the node and the node content, and at the same time, it is convenient for accurately locating the marked target node when editing.

Step 4: Edit and preview. After developing a set of static pages, you can package the overall resources. The packaged static resource files will be exported to the project folder, and run the script at the same time to open the GUI web application for editing and previewing.

After the GUI web application is started, the static pages under the project folder will be displayed. After clicking the static page to be edited, the main interface will be switched and displayed. Use the mouseover event of the mouse to obtain the target node that the mouse is hovering over in real time when the mouse is moving, double-click the mouse to obtain the focus of the target node, and edit the content of the corresponding node. This operation has the characteristics of what you see is what you get, and you can preview the page effect after the copy or image resource is updated in real time. But these are only temporary files, and the source code data will be permanently updated only after clicking the save button.

Step 5: Update the source code and trigger the packaging operation. After clicking Save on the GUI tool, the GUI will search for the file corresponding to the source code according to the currently updated node-node content mapping relationship. After matching the corresponding file, it will update the source code file according to the latest content.

It should be noted that after the source code file is updated, it will actively trigger a project packaging operation to generate a brand new project folder. At this time, the preview operation can be performed in the GUI tool. This operation simulates publishing to a static resource server on the interface. After confirming that it is correct, the user can click the publish button. This button will trigger the commit operation of the code warehouse, and the modification record of this time will be stored in the version management system of the code warehouse. After the submission is complete, the GUI tool will synchronize the static resources under the project folder in the project to the folder specified by the static resource server through the interface of the static resource server.

Step 6: Move to the officially released website to check the update status of the page content again. In case of an unexpected situation, use the version switching function of the GUI tool to perform the rollback operation of the page code.

Specifically, FIG. 4 is a flow chart of the rollback operation of the page code in the static page management method according to the embodiment of the present application. As shown in FIG. 4 , the rollback operation of the page code includes the following steps:

Node Git obtains the log submitted by git, switches the version, and judges whether to perform the detection operation. If so, pulls the source code of the target version, and triggers the packaging and reconstruction work of the scaffolding tool to package the static resources. Furthermore, the GUI defines the local node service, and the page is automatically refreshed to the latest version. The user can edit the content of the case on the GUI interface, display the edited page, and save the edited page. After saving, update the warehouse source code according to the node key-value pair data corresponding to the page, and trigger the packaging and building operation of the scaffolding tool. At the same time, start the preview server, preview the static files in the project directory, and publish the page. After the page is published, Node Git commits the changes to the current version, and COSCMD uploads the project files and folders.

Through this embodiment, on the one hand, by integrating GIT, webpack, nodeJS and other technologies and tools, the front-end and lightweight of static page content management can be realized, and the data content management system can get rid of the dependence on server programs and databases; Any editable node can be visually edited to realize visual real-time editing and preview of static page resources, which improves the efficiency of maintenance. In addition, developers do not need to refactor secondary development of static pages, and they can be used after one development. Static page resources are released , the path entity is clear, which is conducive to search engine optimization.

It should be noted that the steps shown in the flowcharts of the accompanying drawings may be performed in a computer system, such as a set of computer-executable instructions, and that although a logical order is shown in the flowcharts, in some cases, The steps shown or described may be performed in an order different than here.

The embodiment of the present application also provides a static page management device. It should be noted that the static page management device in the embodiment of the present application can be used to execute the static page management method provided in the embodiment of the present application. The static page management apparatus provided by the embodiment of the present application is introduced below.

Fig. 5 is a schematic diagram of an apparatus for managing static pages according to an embodiment of the present application. As shown in FIG. 5 , the device includes: a first acquiring unit 501 , a first responding unit 502 and an updating unit 503 .

Specifically, the first obtaining unit 501 is used to obtain the source code file, generate the source code file as a static page through the front-end development scaffolding tool, and display the static page, wherein the static page is associated with a node identifier and a key value of the node content to the dataset;

The first response unit 502 is configured to respond to an editing operation on the target node in the static page, modify the node content data associated with the target node, and obtain an updated static page;

The updating unit 503 is configured to update the source code file according to the updated static page to obtain the updated source code file.

Optionally, in the static page management device provided in the embodiment of the present application, the device further includes: a detection unit, configured to update the source code file according to the updated static page by the updating unit 503 and obtain the updated source code file, Detect whether a posting instruction for the updated static page is received; a synchronization unit is configured to synchronize the updated static page to the static resource server when the detection unit detects that the posting instruction is received.

Optionally, in the static page management device provided in the embodiment of the present application, the device further includes: a receiving unit, configured to receive the feedback corresponding to the release instruction after the synchronization unit synchronizes the updated static page to the static resource server information, and judge whether the updated static page is released successfully according to the feedback information; the second acquisition unit is used to obtain the source code file of the previous version of the updated static page through the version management system to obtain the target The source code file; the generation unit is used to generate the static page corresponding to the target source code file through the front-end development scaffolding tool to obtain the static page to be detected; the second response unit is used to respond to the editing operation of the static page to be detected and modify the static page to be detected The content data associated with the static page is obtained to obtain the target static page, and the target source code file is updated according to the target static page.

Optionally, in the static page management device provided in the embodiment of the present application, the device further includes: a judging unit, configured to update the source code file according to the updated static page before the updating unit 503 obtains the updated source code file, Judging whether a confirmation instruction for the updated static page is received; the execution unit is configured to execute the step of updating the source code file according to the updated static page to obtain the updated source code file when the confirmation instruction is received.

The static page management device provided by the embodiment of the present application obtains the source code file through the first acquisition unit 501, generates the source code file as a static page through the front-end development scaffolding tool, and displays the static page, wherein the static page is associated with a node symbol The key-value pair data set of symbols and node content; the first response unit 502 responds to the edit operation of the target node in the static page, modifies the node content data associated with the target node, and obtains the updated static page; the update unit 503 according to the updated The source code file of the static page is updated to obtain the updated source code file. It solves the problem of high reliance on the data model when managing the content of static pages in related technologies, stores static resources through node identifiers associated with node content data, and can modify the node content data associated with nodes in static pages The purpose of modifying the static page is achieved, thereby achieving the effect of improving the flexibility of managing the static page and reducing the dependence on the data model.

The static page management device includes a processor and a memory, and the above-mentioned first acquisition unit 501, first response unit 502, and update unit 503 are all stored in the memory as program units, and the processor executes the above-mentioned program units stored in the memory to achieve the corresponding functions.

The processor includes a kernel, and the kernel fetches corresponding program units from the memory. One or more kernels can be set, and the problem of excessive dependence on the data model in the management of static page content in related technologies can be solved by adjusting kernel parameters.

Memory may include non-permanent memory in computer-readable media, in the form of random access memory (RAM) and/or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM), memory including at least one memory chip.

The embodiment of the present application also provides a non-volatile storage medium, the non-volatile storage medium includes a stored program, wherein, when the program is running, the device where the non-volatile storage medium is located is controlled to execute a static page management method .

The embodiment of the present application also provides an electronic device, including a processor and a memory; computer-readable instructions are stored in the memory, and the processor is used to run the computer-readable instructions, wherein, when the computer-readable instructions are running, a static page Management method. The electronic device herein may be a server, a PC, a PAD, a mobile phone, and the like.

Those skilled in the art should understand that the embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present application is described with reference to flowcharts and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present application. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing equipment produce a An apparatus for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions The device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby The instructions provide steps for implementing the functions specified in the flow chart or blocks of the flowchart and/or the block or blocks of the block diagrams.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

Memory may include non-permanent storage in computer readable media, in the form of random access memory (RAM) and/or nonvolatile memory such as read only memory (ROM) or flash RAM. The memory is an example of a computer readable medium.

Computer-readable media, including both permanent and non-permanent, removable and non-removable media, can be implemented by any method or technology for storage of information. Information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Flash memory or other memory technology, Compact Disc Read-Only Memory (CD-ROM), Digital Versatile Disc (DVD) or other optical storage, Magnetic tape cartridge, tape magnetic disk storage or other magnetic storage device or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media excludes transitory computer-readable media, such as modulated data signals and carrier waves.

It should also be noted that the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus comprising a set of elements includes not only those elements, but also includes Other elements not expressly listed, or elements inherent in the process, method, commodity, or apparatus are also included. Without further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

The above are only examples of the present application, and are not intended to limit the present application. For those skilled in the art, various modifications and changes may occur in this application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included within the scope of the claims of the present application.

Claims

A content management system, characterized by comprising:

The page editor is used to obtain the source code file, display the static page generated by the source code file, and respond to the editing operation on the target node in the static page, modify the node content data associated with the target node, and obtain the updated The static page and the updated source code file, wherein the static page is associated with a node identifier and a key-value pair data set of node content;

The version management system is used to obtain the source code file from the code repository, and send the source code file to the page editor, and is also used to obtain the updated source code file from the page editor, and send the source code file to the page editor. Send the updated source code files to the code warehouse;

A front-end development scaffolding tool for generating the source code file obtained by the page editor as the static page;

The static resource server is configured to obtain the updated static page from the page editor, store the updated static page, and generate an access link corresponding to the updated static page.
The content management system according to claim 1, wherein:

The static resource server is a cloud server, and the cloud server stores the updated static page and generates an access path corresponding to the updated static page.
The content management system according to claim 1, wherein:

The front-end development scaffolding tool performs at least one of the following processes on the source code file to obtain the static page: packaging processing, compression processing, and page content injection processing;

Wherein, the packaging process is used to detect the public code corresponding to the source code file, and inject the visualization data corresponding to the public code into the marked position of the static page;

The compression process is used to compress space data and newline data in the source code file, and replace variables larger than a preset length with variables of a target length;

The page content injection process is used to inject the data in the source code file into the preset page template.
A method for managing static pages, characterized by comprising:

Obtaining the source code file, generating the source code file as a static page through a front-end development scaffolding tool, and displaying the static page, wherein the static page is associated with a node identifier and a key-value pair data set of node content;

Responding to an editing operation on the target node in the static page, modifying node content data associated with the target node to obtain an updated static page;

The source code file is updated according to the updated static page to obtain the updated source code file.
The method according to claim 4, characterized in that, after updating the source code file according to the updated static page and obtaining the updated source code file, the method further comprises:

Detecting whether a release instruction for the updated static page is received;

When the publishing instruction is received, the updated static page is synchronized to the static resource server.
The method according to claim 5, characterized in that, after receiving the release instruction, after synchronizing the updated static page to the static resource server, the method further comprises:

receiving feedback information corresponding to the release instruction, and judging whether the updated static page is successfully released according to the feedback information;

In the case of publishing failure, obtain the source code file of the previous version of the updated static page through the version management system to obtain the target source code file;

Generate the static page corresponding to the target source code file through the front-end development scaffolding tool to obtain the static page to be detected;

Responding to an editing operation on the static page to be detected, modifying content data associated with the static page to be detected to obtain a target static page, and updating the target source code file according to the target static page.
The method according to claim 4, wherein, before updating the source code file according to the updated static page and obtaining the updated source code file, the method further comprises:

judging whether a confirmation instruction for the updated static page is received;

When the confirming instruction is received, execute the step of updating the source code file according to the updated static page to obtain an updated source code file.
A management device for static pages, characterized by comprising:

The first obtaining unit is used to obtain the source code file, generate the source code file as a static page through the front-end development scaffolding tool, and display the static page, wherein the static page is associated with a node identifier and a node content key-value pair dataset;

The first response unit is configured to respond to an editing operation on the target node in the static page, modify the node content data associated with the target node, and obtain an updated static page;

An updating unit, configured to update the source code file according to the updated static page to obtain the updated source code file.
The device according to claim 8, wherein the device further comprises:

The detection unit is configured to detect whether a release instruction for the updated static page is received after the update unit updates the source code file according to the updated static page and obtains the updated source code file;

A synchronization unit, configured to synchronize the updated static page to a static resource server when the detection unit detects that the publishing instruction is received.
The device according to claim 9, wherein the device further comprises:

a receiving unit, configured to receive feedback information corresponding to the release instruction after the synchronization unit synchronizes the updated static page to the static resource server, and judge the updated static page according to the feedback information Whether the page is published successfully;

The second obtaining unit is used to obtain the source code file of the previous version of the updated static page through the version management system to obtain the target source code file when the release fails;

A generating unit, configured to generate a static page corresponding to the target source code file through the front-end development scaffolding tool, to obtain a static page to be detected;

The second response unit is configured to respond to an editing operation on the static page to be detected, modify the content data associated with the static page to be detected, obtain a target static page, and update the target source code according to the target static page document.
The device according to claim 8, wherein the device further comprises:

A judging unit, configured to judge whether a confirmation instruction for the updated static page is received before the updating unit updates the source code file according to the updated static page to obtain the updated source code file;

The execution unit is configured to execute the step of updating the source code file according to the updated static page to obtain an updated source code file when the confirmation instruction is received.
A non-volatile storage medium, characterized in that the non-volatile storage medium is used to store a program, wherein, when the program runs, the device where the non-volatile storage medium is located is controlled to execute claims 4 to 7 The management method of the static page described in any item.
An electronic device, characterized in that it includes a processor and a memory, the memory stores computer-readable instructions, and the processor is used to execute the computer-readable instructions, wherein the computer-readable instructions are executed when running The static page management method described in any one of claims 4 to 7.