A cross-platform content implementation method and related equipment

Abstract

This application discloses a cross-platform content implementation method, including: setting domain-specific language configuration, developing a target page, and outputting a first domain-specific language statement and a second domain-specific language statement. Based on the above scheme, this application only requires developing the target page once during the page development process. It can then output the first and second domain-specific language statements respectively through pre-set corresponding rules applied to the mini-program environment and the webpage environment. The first domain-specific language statement can be used by users in the mini-program environment, i.e., to display the target page to users in the mini-program environment, while the second domain-specific language statement is used to display the target page to users in the webpage environment. This method avoids the large amount of manpower and resources consumed by repeated development and improves the convenience of the development process.

Description

Technical Field

[0001] This application belongs to the field of data processing, and in particular relates to a cross-platform content implementation method and related equipment. Background Technology

[0002] With social development, mobile terminals and their supporting applications have become increasingly powerful, gradually becoming an indispensable part of people's lives. Among them, the scope and proportion of use of mini-program platform applications and web platform applications are also gradually increasing. For an application or service, in order to cope with users' usage habits, there are often two implementation methods: web platform and mini-program platform.

[0003] Currently, the resources needed for use and display on web platforms and mini-program platforms all require separate manpower for development. However, the resources actually displayed to users are similar, meaning that users see mostly the same things on different applications. The development of multiple applications displaying the same content by different people has resulted in a significant waste of human and material resources. Summary of the Invention

[0004] The purpose of this invention is to provide a cross-platform content implementation method, aiming to solve the problem of excessive repetitive work in the existing development process, resulting in a waste of human and material resources.

[0005] The first aspect of this application provides a cross-platform content implementation method, including:

[0006] Configure domain-specific language settings, which include corresponding rules for the mini-program environment and corresponding rules for the webpage environment;

[0007] Develop the target page;

[0008] The first domain-specific language statement is output based on the target page, and the first domain-specific language statement is output based on the corresponding rules applied to the mini-program environment;

[0009] Output a second domain-specific language statement, which is based on the corresponding rules applied to the web page environment.

[0010] Based on the cross-platform content implementation method provided in the first aspect of the embodiments of this application, optionally, the output of second domain-specific language statements includes:

[0011] Pre-rendering is performed based on language statements specific to the first domain to obtain the target page for rendering;

[0012] Output a second domain-specific language statement based on the rendered target page.

[0013] The second aspect of this application provides a cross-platform content implementation method, including:

[0014] Receive access requests sent by users;

[0015] The user's platform category is determined based on the access request, and the platform category is either a mini-program platform or a web platform.

[0016] If the user's platform category is the mini-program platform, then read the first domain-specific language statement;

[0017] Parse the language statements specific to the first domain and display the target page on the mini-program platform;

[0018] If the user's platform category is the webpage platform, then read the second domain-specific language statement;

[0019] Parse the language statements specific to the second domain and display the target page on the web platform;

[0020] The first domain-specific language statement and the second domain-specific language statement are obtained according to the method described in claim 1.

[0021] Optionally, based on the cross-platform content implementation method provided in the second aspect of the embodiments of this application, the method further includes:

[0022] Authentication is performed based on the user's platform category.

[0023] A third aspect of this application provides a cross-platform content implementation device, including:

[0024] The setting unit is used to set domain-specific language configurations, which include corresponding rules applied to the mini-program environment and corresponding rules applied to the webpage environment.

[0025] Development unit, used to develop target pages;

[0026] The first domain-specific language statement output unit is used to output a first domain-specific language statement based on the target page. The first domain-specific language statement is output based on the corresponding rules applied to the mini-program environment.

[0027] The second domain-specific language statement output unit is used to output a second domain-specific language statement, which is output based on the corresponding rules applied to the web page environment.

[0028] A fourth aspect of this application provides a cross-platform content implementation device, including:

[0029] The receiving unit is used to receive access requests sent by users;

[0030] The determining unit is configured to determine the user's platform category based on the access request, wherein the platform category is either a web platform or a mini-program platform.

[0031] A webpage platform display unit is configured to read first domain-specific language statements if the user's platform category is the webpage platform.

[0032] Parse the language statements specific to the first domain and display the target page on the web platform;

[0033] The mini-program platform display unit is used to read second domain-specific language statements if the user's platform category is the mini-program platform.

[0034] Parse the language statements specific to the second domain and display the target page on the mini-program platform.

[0035] The first domain-specific language statement and the second domain-specific language statement are obtained according to the method described in claim 1.

[0036] A fifth aspect of this application provides a cross-platform content implementation device, including:

[0037] Central processing unit, memory, input / output interfaces, wired or wireless network interfaces, and power supply;

[0038] The memory is either a short-term storage memory or a persistent storage memory;

[0039] The central processing unit is configured to communicate with the memory and execute instructions in the memory on the cross-platform content implementation device to perform the method as described in any one of claims 1 to 2.

[0040] A sixth aspect of this application provides a cross-platform content implementation device, including:

[0041] Central processing unit, memory, input / output interfaces, wired or wireless network interfaces, and power supply;

[0042] The memory is either a short-term storage memory or a persistent storage memory;

[0043] The central processing unit is configured to communicate with the memory and execute instructions in the memory on the cross-platform content implementation device to perform the method as described in any one of claims 3 to 4.

[0044] A seventh aspect of this application provides a computer-readable storage medium including instructions that, when executed on a computer, cause the computer to perform the method described in any one of the first and second aspects of this application.

[0045] The eighth aspect of this application provides a computer program product containing instructions that, when run on a computer, cause the computer to perform the method described in any one of the first and second aspects of this application.

[0046] As can be seen from the above technical solutions, the embodiments of this application have the following advantages: The embodiments of this application provide a cross-platform content implementation method, including: setting a domain-specific language configuration, wherein the domain-specific language configuration includes corresponding rules applied to a mini-program environment and corresponding rules applied to a webpage environment; developing a target page; outputting a first domain-specific language statement based on the target page, wherein the first domain-specific language statement is output based on the corresponding rules applied to the mini-program environment; and outputting a second domain-specific language statement, wherein the second domain-specific language statement is output based on the corresponding rules applied to the webpage environment. Based on the above solution, it can be seen that this application only needs to develop the target page once during the page development process. The first domain-specific language statement and the second domain-specific language statement can be output respectively through the pre-set corresponding rules applied to the mini-program environment and the corresponding rules applied to the webpage environment. The first domain-specific language statement can be used by users in the mini-program environment, i.e., to display the target page to users in the mini-program environment, while the second domain-specific language statement is used to display the target page to users in the webpage environment. This method avoids the large amount of manpower and resources consumed by repeated development and improves the convenience of the development process. Attached Figure Description

[0047] 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, the drawings described below are merely embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort. It is understood that the drawings provided in this section are only for better understanding of this solution and do not constitute a limitation on this application.

[0048] Figure 1 A flowchart illustrating an embodiment of the cross-platform content implementation method provided in this application;

[0049] Figure 2 Another flowchart illustrating an embodiment of the cross-platform content implementation method provided in this application;

[0050] Figure 3 Another flowchart illustrating an embodiment of the cross-platform content implementation method provided in this application;

[0051] Figure 4Another flowchart illustrating an embodiment of the cross-platform content implementation method provided in this application;

[0052] Figure 5 A schematic diagram of a cross-platform content implementation device embodiment provided in this application;

[0053] Figure 6 Another structural schematic diagram of an embodiment of the cross-platform content implementation device provided in this application;

[0054] Figure 7 Another structural schematic diagram of an embodiment of the cross-platform content implementation device provided in this application;

[0055] Figure 8 This is another structural schematic diagram of an embodiment of the cross-platform content implementation device provided in this application. Detailed Implementation

[0056] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application are clearly and completely described below. Obviously, the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application. At the same time, for the sake of clarity and conciseness, descriptions of well-known functions and structures are omitted in the following description.

[0057] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments described herein can be implemented in a sequence other than that illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0058] With social development, mobile terminals and their supporting applications have become increasingly powerful, gradually becoming an indispensable part of people's lives. Among them, the scope and proportion of use of mini-program applications and web applications are also gradually increasing. For an application or service, in order to cope with users' usage habits, there are often two usage methods: web application and mini-program application.

[0059] Currently, the resources needed for use and display in web applications and mini-programs all require separate development by different personnel. However, the resources actually displayed to users are similar; users see mostly the same content across different applications. Developing multiple applications displaying the same content by different personnel results in a significant waste of human and material resources. To address these issues, this application provides a cross-platform content implementation method. Please refer to [link to relevant documentation]. Figure 1 One embodiment of the cross-platform content implementation method provided in this application includes steps 101-104.

[0060] 101. Configure domain-specific language settings.

[0061] Specifically, the domain-specific language configuration includes corresponding rules applied to the mini-program environment and corresponding rules applied to the web page environment. A domain-specific language (DSL) refers to a computer language focused on a specific application domain. DSLs can improve development efficiency by abstracting and building models, extracting common code, and reducing repetitive work. Furthermore, DSLs can adapt to changes in the execution environment and compensate for the limitations of the host language.

[0062] During implementation, it is necessary to set corresponding rules for the mini-program environment and the webpage environment respectively. That is, it is necessary to design the interpretation rules of DSL statements for the mini-program environment and the interpretation rules for the webpage environment, so as to facilitate the development using domain-specific languages ​​and obtain program statements applicable to both environments.

[0063] 102. Develop the target page.

[0064] Specifically, develop the target page. The target page is the page you want to show to users. In the actual implementation process, a visual page building platform can be built in advance. Building is to assemble the page from the components, similar to building blocks. You can freely drag and drop, sort and adjust the position of the components, and configure the page and component description information. The components are the pre-set components used to display content, which can be text, images or buttons, etc.

[0065] 103. Output a first domain-specific language statement based on the target page.

[0066] Specifically, a first domain-specific language (DSL) statement is output based on the target page. This first DSL statement is output based on the corresponding rules applied to the mini-program environment. The developed target page is converted into the first DSL statement. In actual implementation, conversion rules for different components within the target page can be preset, and the first DSL statement is output. The first DSL statement is the statement describing the target page applied to the mini-program environment. In actual use, the target page can be displayed to users in the mini-program environment on the server side using the first DSL statement and its corresponding interpretation rules.

[0067] 104. Output the second domain-specific language statement.

[0068] Specifically, a second domain-specific language (DSL) statement is output, which is based on the corresponding rules applied to the webpage environment. In practice, after obtaining the first DSL statement, it can be converted to obtain the second DSL statement. During this process, rendering and other processing can be performed to ensure the effectiveness of the second DSL statement. Alternatively, the second DSL statement can be directly converted from the target page using preset rules. The specific output method of the second DSL statement can be determined according to the actual situation and is not limited here. In actual use, the target page can be displayed to users in the web environment on the server side using the second DSL statement and its corresponding interpretation rules.

[0069] As can be seen from the above technical solutions, the embodiments of this application have the following advantages: The embodiments of this application provide a cross-platform content implementation method, including: setting a domain-specific language configuration, wherein the domain-specific language configuration includes corresponding rules applied to a mini-program environment and corresponding rules applied to a webpage environment; developing a target page; outputting a first domain-specific language statement based on the target page, wherein the first domain-specific language statement is output based on the corresponding rules applied to the mini-program environment; and outputting a second domain-specific language statement, wherein the second domain-specific language statement is output based on the corresponding rules applied to the webpage environment. Based on the above solution, it can be seen that this application only needs to develop the target page once during the page development process. The first domain-specific language statement and the second domain-specific language statement can be output respectively through the pre-set corresponding rules applied to the mini-program environment and the corresponding rules applied to the webpage environment. The first domain-specific language statement can be used by users in the mini-program environment, i.e., to display the target page to users in the mini-program environment, while the second domain-specific language statement is used to display the target page to users in the webpage environment. This method avoids the large amount of manpower and resources consumed by repeated development and improves the convenience of the development process.

[0070] To facilitate the practical use of this method, this application also provides a more detailed embodiment that can be implemented optionally. Please refer to [link / reference]. Figure 2 Another embodiment of the cross-platform implementation method provided in this application includes steps 201-205.

[0071] 201. Configure domain-specific language settings.

[0072] 202. Develop the target page.

[0073] 203. Output a first domain-specific language statement based on the target page.

[0074] Specifically, steps 201 to 203 above are the same as those described above. Figure 1 The corresponding embodiments are similar, and the details can be found in the foregoing content, which will not be repeated here.

[0075] 204. Pre-render based on the language-specific statements of the first domain to obtain the target page for rendering.

[0076] 205. Output a second domain-specific language statement based on the rendered target page.

[0077] Specifically, the rendering process may include:

[0078] Step 1: Pure rendering service development. The pure rendering service only performs rendering. By inputting the initial DSL (Domain-Specific Language Statement), component list, and data list, you can obtain the rendered HTML.

[0079] Step Two: Page Assembly Service Development. After obtaining the rendered HTML, the next step is to assemble the page. The core process involves filling the prototype with the pre-fetched header and footer, JS list, CSS, and rendered HTML. The prototype is essentially an HTML template. After assembly, a complete HTML page is created. Based on this complete HTML page, second-domain-specific language statements are generated for subsequent use.

[0080] The main difference between mini-program rendering and web rendering is that web rendering can perform server-side rendering. When previewing or publishing a page, a pre-render is performed on the server, and a new DSL is regenerated based on the initial DSL. When users access the page, the HTML is directly output, allowing them to see the page content more quickly.

[0081] As can be seen from the above technical solutions, the embodiments of this application have the following advantages: The embodiments of this application provide a cross-platform content implementation method, including: setting a domain-specific language configuration, wherein the domain-specific language configuration includes corresponding rules applied to a mini-program environment and corresponding rules applied to a webpage environment; developing a target page; outputting a first domain-specific language statement based on the target page, wherein the first domain-specific language statement is output based on the corresponding rules applied to the mini-program environment; and outputting a second domain-specific language statement, wherein the second domain-specific language statement is output based on the corresponding rules applied to the webpage environment. Based on the above solution, it can be seen that this application only needs to develop the target page once during the page development process. The first domain-specific language statement and the second domain-specific language statement can be output respectively through the pre-set corresponding rules applied to the mini-program environment and the corresponding rules applied to the webpage environment. The first domain-specific language statement can be used by users in the mini-program environment, i.e., to display the target page to users in the mini-program environment, while the second domain-specific language statement is used to display the target page to users in the webpage environment. This method avoids the large amount of manpower and resources consumed by repeated development and improves the convenience of the development process.

[0082] The above describes the methods for implementing cross-platform content during development. The following describes the methods for implementing cross-platform content on the user side; please refer to [link / reference]. Figure 3 An embodiment of the cross-platform content implementation method provided in this application includes:

[0083] 301. Receive access requests sent by users.

[0084] Specifically, it receives access requests sent by users, which indicate the specific page the user wishes to access. This page is pre-developed by the developers, and generally, this specific page is as described above. Figure 1 and Figure 2 The target page described in the corresponding embodiment. Users access the target page to browse its content and obtain its services.

[0085] 302. Determine the user's platform category based on the access request.

[0086] Specifically, the user's platform category is determined based on the access request. This platform category can be either a mini-program platform or a web platform. It is understood that in actual implementation, the mini-program platform category can be further subdivided, i.e., any one of WeChat mini-programs, Alipay mini-programs, or Douyin mini-programs. The access request should contain the user's identity identifier and access path, and this information can be used to determine the user's specific platform category. If the user's platform category is a mini-program platform, then step 303 is executed to read the first domain-specific language statement; if the user's platform category is a web platform, then step 305 is executed to read the second domain-specific language statement.

[0087] 303. Read first-domain-specific language statements.

[0088] 304. Parse the language statements specific to the first domain and display the target page on the mini-program platform.

[0089] Specifically, if the user's platform category is a mini-program platform category, then steps 303 and 304 are executed, namely, reading and parsing the first domain-specific language statement, and displaying the target page on the mini-program platform. The first domain-specific language statement is based on the above... Figure 1 or Figure 2 As described in the corresponding embodiment, the target page is obtained by converting it according to the corresponding rules applied to the mini-program environment in the domain-specific language configuration. Therefore, after processing the first domain-specific language statement, a target page that can be displayed in the mini-program platform environment can be obtained, thereby enabling users to browse the target page in the mini-program environment.

[0090] 305. Read second-domain-specific language statements.

[0091] 306. Parse the language statements specific to the second domain and display the target page on the web platform.

[0092] Specifically, if the user's platform category is a web platform, then steps 305 and 306 are executed, namely, reading and parsing the second domain-specific language statement, and displaying the target page on the web platform. The second domain-specific language statement is based on the above... Figure 1 or Figure 2 As described in the corresponding embodiment, the target page is obtained by converting it according to the corresponding rules applied to the webpage environment in the domain-specific language configuration. Therefore, after processing the second domain-specific language statement, a target page that can be displayed in the webpage platform environment can be obtained, thereby enabling users to browse the target page in the webpage environment.

[0093] As can be seen from the above technical solutions, the embodiments of this application have the following advantages: The embodiments of this application provide a cross-platform content implementation method, which receives an access request sent by a user; determines the user's platform category based on the access request, wherein the platform category is either a mini-program platform or a web platform; if the user's platform category is the mini-program platform, then reads a first domain-specific language statement; parses the first domain-specific language statement, and displays the target page on the mini-program platform; if the user's platform category is the web platform, then reads a second domain-specific language statement; parses the second domain-specific language statement, and displays the target page on the web platform; the first domain-specific language statement and the second domain-specific language statement are based on the above... Figure 1 or Figure 2 The method described in the corresponding embodiment is used to obtain the result. Based on the above solution, it is clear that this application only requires developing the target page once during the page development process. It can then output first domain-specific language statements and second domain-specific language statements respectively through pre-set corresponding rules applied to the mini-program environment and the webpage environment. The first domain-specific language statement can be used by users in the mini-program environment, i.e., to display the target page to users in the mini-program environment, while the second domain-specific language statement is used to display the target page to users in the webpage environment. This method avoids the large amount of manpower and resources consumed by repeated development and improves the convenience of the development process.

[0094] To facilitate the practical use of this method, this application also provides a more detailed embodiment that can be implemented optionally. Please refer to [link / reference]. Figure 4 Another embodiment of the cross-platform implementation method provided in this application includes steps 401-408.

[0095] 401. Receive access requests sent by users.

[0096] 402. Determine the user's platform category based on the access request.

[0097] Specifically, steps 401 to 402 above are the same as those described above. Figure 1 Steps 301 to 302 in the corresponding embodiment are similar, and can be referred to the foregoing content for details, which will not be repeated here.

[0098] 403. Authentication is performed based on the platform category stated by the user.

[0099] Specifically, if the user's platform category is the aforementioned mini-program platform, then identity verification is performed based on the mini-program platform. The verification process includes verifying the user's identity and authenticating the page the user wants to access. Specifically, it may include: obtaining the main package tool library; if successful, obtaining the URL parameters and further calling the index interface to obtain page configuration data; if successful, calling the information interface to obtain interface data, thereby completing the verification of the user's identity and the page. If a deviation occurs during the verification process, a prompt can be sent to the user according to the settings, such as prompting "system busy" or "activity does not exist," or the customer can be redirected to a specified page. The specific form can be determined according to the actual situation and is not limited here.

[0100] 404. Read first-domain-specific language statements.

[0101] Specifically, read the first domain-specific language statement, which can be set in the interface data.

[0102] 405. Parse the language statements specific to the first domain and display the target page on the web platform.

[0103] Specifically, the domain-specific language statements are parsed, and the target page is displayed on a web platform. Taking WeChat Mini Programs as an example, a new Mini Program subpackage is created within an existing or new Mini Program. Subpackaging helps reduce the size of the main program package and provides relative independence, making it easy to reuse the subpackage in other Mini Programs. The required domain-specific language rules, i.e., Mini Program components (button components, image components, etc.), and the rendering logic of the page within the subpackage are developed within the subpackage. When a user accesses the Mini Program subpackage page, the subpackage prioritizes synchronously loading the common logic modules (network requests, Toast modules, etc.) from the main package; it then parses the page configuration information based on interface data, including Mini Program page configuration and component list information such as title, background, and share; it then iterates through the component list and dynamically renders the page content using pre-registered components. This completes the page display process on the Mini Program side.

[0104] 406. Authentication is performed based on the platform category stated by the user.

[0105] Specifically, if the user's platform category is a web platform, then the user's identity, i.e., the webpage, also needs to be verified. This includes: obtaining URL parameters, reading the index interface to obtain page configuration; if reading the index interface is successful, determining whether the page's eva parameter is correct; if reading the index interface fails, displaying an error page; if the page's eva parameter is incorrect, redirecting to the page with the correct eva parameter; if the page's eva parameter is correct, determining whether the current page supports opening a mini-program; if it does, redirecting to the mini-program page to open it, i.e., executing the aforementioned steps 403 to 405; if it does not support opening in the mini-program environment, continuing to call user information and parse the index interface, logging in related data through the information interface, determining whether login is required; if so, redirecting to the login page, and continuing subsequent steps after completing login, determining whether the user's identity matches; if it matches, continuing subsequent steps; if it does not match, redirecting to the correct page, thus completing the verification process for both the user and the page the user wishes to access.

[0106] 407. Read second-domain specific language statements.

[0107] 408. Parse the language statements specific to the second domain and display the target page on the mini-program platform.

[0108] Specifically, this includes: parsing the index interface to obtain the DSL link, parsing the component HTML code from the DSL, parsing the index interface to set the page title, background color, etc., parsing the user information interface to set the entry event for employees, etc., and generating the final HTML. This process utilizes isomorphic rendering services that match the webpage, including:

[0109] (1) Pure rendering service development: Pure rendering service only performs rendering. By inputting the initial DSL (Domain Specific Language), component list and data list, you can get the rendered HTML.

[0110] (2) Develop the splicing service, obtain the rendered HTML, and then splice the page. The core is to fill the prototype with the pre-fetched header and footer, js list, css and rendered HTML. The prototype is essentially an html-template. After splicing, it is a complete HTML page.

[0111] (3) Upper-layer service development: In reality, the content returned by the splicing service could be directly returned to the user. However, for performance, stability, and scalability considerations, we abstracted this layer. This service currently provides fallback and caching. If the lower-layer splicing service or pure rendering service goes down, a pre-processed fallback page will be returned to the user; for some businesses that do not have real-time requirements, different caching strategies can be configured for the page. In addition to fallback and caching, this layer can also be extended with other functions, such as page A / B testing and page offline testing.

[0112] The main difference between mini-program rendering and web rendering is that web rendering can perform server-side rendering. When previewing or publishing a page, a pre-render is performed on the server. A new DSL (i.e., second domain-specific language) is regenerated based on the initial DSL (i.e., first domain-specific language). When users access the page, HTML can be directly output, allowing them to see the page content more quickly.

[0113] As can be seen from the above technical solutions, the embodiments of this application have the following advantages: The embodiments of this application provide a cross-platform content implementation method, which receives an access request sent by a user; determines the user's platform category based on the access request, wherein the platform category is either a mini-program platform or a web platform; if the user's platform category is the mini-program platform, then reads a first domain-specific language statement; parses the first domain-specific language statement, and displays the target page on the mini-program platform; if the user's platform category is the web platform, then reads a second domain-specific language statement; parses the second domain-specific language statement, and displays the target page on the web platform; the first domain-specific language statement and the second domain-specific language statement are based on the above... Figure 1 or Figure 2 The method described in the corresponding embodiment is used to obtain the result. Based on the above solution, it is clear that this application only requires developing the target page once during the page development process. It can then output first domain-specific language statements and second domain-specific language statements respectively through pre-set corresponding rules applied to the mini-program environment and the webpage environment. The first domain-specific language statement can be used by users in the mini-program environment, i.e., to display the target page to users in the mini-program environment, while the second domain-specific language statement is used to display the target page to users in the webpage environment. This method avoids the large amount of manpower and resources consumed by repeated development and improves the convenience of the development process.

[0114] The foregoing describes the cross-platform content implementation method provided in this application. Optionally, this application also provides a cross-platform content implementation device. Please refer to [link to relevant documentation]. Figure 5 One embodiment of the cross-platform content implementation device provided in this application includes:

[0115] Setting unit 501 is used to set domain-specific language configuration, wherein the domain-specific language configuration includes corresponding rules applied to the mini-program environment and corresponding rules applied to the web page environment;

[0116] Development unit 502 is used to develop the target page;

[0117] The first domain-specific language statement output unit 503 is used to output a first domain-specific language statement based on the target page. The first domain-specific language statement is output based on the corresponding rules applied to the mini-program environment.

[0118] The second domain-specific language statement output unit 504 is used to output a second domain-specific language statement, which is output based on the corresponding rules applied to the web page environment.

[0119] Optionally, the second domain-specific language statement output unit is specifically used to: pre-render based on the first domain-specific language statement to obtain the target page for rendering;

[0120] Output a second domain-specific language statement based on the rendered target page.

[0121] In this embodiment, the working methods and processes of each unit in the cross-platform content implementation device are the same as those described above. Figure 1 and Figure 2 The corresponding embodiments are similar in content, and will not be repeated here.

[0122] Please see Figure 6 Another embodiment of the cross-platform content implementation device provided in this application includes:

[0123] The receiving unit 601 is used to receive access requests sent by users;

[0124] The determining unit 602 is used to determine the user's platform category based on the access request, wherein the platform category is either a mini-program platform or a web platform.

[0125] The mini-program platform display unit 603 is used to read first domain-specific language statements if the user's platform category is the mini-program platform.

[0126] Parse the language statements specific to the first domain and display the target page on the mini-program platform;

[0127] The web platform display unit 604 is used to read second domain-specific language statements if the user's platform category is the web platform.

[0128] Parse the language statements specific to the second domain and display the target page on the web platform;

[0129] Based on the first domain-specific language statement and the second domain-specific language statement as described above Figure 1 or Figure 2 The corresponding embodiment was obtained.

[0130] Optionally, the mini-program platform display unit and the webpage platform display unit are also used to perform identity verification based on the user's platform category.

[0131] In this embodiment, the working methods and processes of each unit in the cross-platform content implementation device are the same as those described above. Figure 3 and Figure 4 The corresponding embodiments are similar in content, and will not be repeated here.

[0132] Figure 7 This is a schematic diagram of the structure of a cross-platform content implementation device provided in an embodiment of this application. The server 700 may include one or more central processing units (CPUs) 701 and a memory 705, in which one or more applications or data are stored.

[0133] In this embodiment, the specific functional module division in the central processing unit 701 can be the same as described above. Figure 7 The functional module division of each unit described in the text is similar, so it will not be repeated here.

[0134] The memory 705 can be volatile or persistent storage. The program stored in the memory 705 can include one or more modules, each module including a series of instruction operations on the server. Furthermore, the central processing unit 701 can be configured to communicate with the memory 705 and execute the series of instruction operations stored in the memory 705 on the server 700.

[0135] Server 700 may also include one or more power supplies 702, one or more wired or wireless network interfaces 703, one or more input / output interfaces 704, and / or one or more operating systems, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, etc.

[0136] The central processing unit 701 can perform the aforementioned... Figure 1 or Figure 2 The operations performed by the cross-platform content implementation device in the illustrated embodiment will not be described in detail here.

[0137] Figure 8This is a schematic diagram of the structure of a cross-platform content implementation device provided in an embodiment of this application. The server 800 may include one or more central processing units (CPUs) 801 and a memory 805, in which one or more applications or data are stored.

[0138] In this embodiment, the specific functional module division in the central processing unit 801 can be the same as described above. Figure 8 The functional module division of each unit described in the text is similar, so it will not be repeated here.

[0139] The memory 805 can be volatile or persistent storage. The program stored in the memory 805 can include one or more modules, each module including a series of instruction operations on the server. Furthermore, the central processing unit 801 can be configured to communicate with the memory 805 and execute the series of instruction operations stored in the memory 805 on the server 800.

[0140] Server 800 may also include one or more power supplies 802, one or more wired or wireless network interfaces 803, one or more input / output interfaces 804, and / or one or more operating systems, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, etc.

[0141] The central processing unit 801 can perform the aforementioned... Figure 1 or Figure 2 The specific operations performed by the cross-platform content implementation method in the illustrated embodiment will not be described in detail here.

[0142] This application also provides a computer storage medium for storing computer software instructions used for the above-described cross-platform content implementation method, including programs designed for executing the cross-platform content implementation method.

[0143] The cross-platform content implementation method can be as described above. Figures 1 to 4 The cross-platform content implementation method described in the corresponding embodiment.

[0144] This application also provides a computer program product, which includes computer software instructions that can be loaded by a processor to implement the above-described functionality. Figures 1 to 4 The flow of the cross-platform content implementation method described in the corresponding embodiment.

[0145] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, equivalent circuit transformations and unit divisions are only logical functional divisions. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connections shown or discussed may be through some interfaces, or indirect coupling or communication connections between apparatuses or units, and may be electrical, mechanical, or other forms.

[0146] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0147] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0148] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions or improvements made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A cross-platform content implementation method, characterized in that, include: Configure domain-specific language settings, which include corresponding rules for the mini-program environment and corresponding rules for the webpage environment; Develop the target page; The first domain-specific language statement is output based on the target page, and the first domain-specific language statement is output based on the corresponding rules applied to the mini-program environment; Output a second domain-specific language statement, which is output based on the corresponding rules applied to the web page environment; The output of the second domain-specific language statement includes: Pre-rendering is performed based on language statements specific to the first domain to obtain the target page for rendering; Output a second domain-specific language statement based on the rendered target page.

2. A cross-platform content implementation method, characterized in that, include: Receive access requests sent by users; The user's platform category is determined based on the access request, and the platform category is either a mini-program platform or a web platform. If the user's platform category is the mini-program platform, then read the first domain-specific language statement; Parse the language statements specific to the first domain and display the target page on the mini-program platform; If the user's platform category is the webpage platform, then read the second domain-specific language statement; Parse the language statements specific to the second domain and display the target page on the web platform; The first domain-specific language statement and the second domain-specific language statement are obtained according to the method described in claim 1.

3. The cross-platform content implementation method according to claim 2, characterized in that, The method further includes: Authentication is performed based on the user's platform category.

4. A cross-platform content implementation device, characterized in that, include: The setting unit is used to set domain-specific language configurations, which include corresponding rules applied to the mini-program environment and corresponding rules applied to the webpage environment. Development unit, used to develop target pages; The first domain-specific language statement output unit is used to output a first domain-specific language statement based on the target page. The first domain-specific language statement is output based on the corresponding rules applied to the mini-program environment. The second domain-specific language statement output unit is used to output a second domain-specific language statement, which is output based on the corresponding rules applied to the web page environment; The output of the second domain-specific language statement includes: Pre-rendering is performed based on language statements specific to the first domain to obtain the target page for rendering; Output a second domain-specific language statement based on the rendered target page.

5. A cross-platform content implementation device, characterized in that, include: The receiving unit is used to receive access requests sent by users; The determining unit is configured to determine the user's platform category based on the access request, wherein the platform category is either a mini-program platform or a web platform. The mini-program platform display unit is used to read first domain-specific language statements if the user's platform category is the mini-program platform. Parse the language statements specific to the first domain and display the target page on the mini-program platform; A webpage platform display unit is used to read second domain-specific language statements if the user's platform category is the webpage platform. Parse the language statements specific to the second domain and display the target page on the web platform; The first domain-specific language statement and the second domain-specific language statement are obtained according to the method described in claim 1.

6. A cross-platform content implementation device, characterized in that, include: Central processing unit, memory, input / output interfaces, wired or wireless network interfaces, and power supply; The memory is either a short-term storage memory or a persistent storage memory; The central processing unit is configured to communicate with the memory and execute instructions in the memory on the cross-platform content implementation device to perform the method as described in claim 1.

7. A cross-platform content implementation device, characterized in that, include: Central processing unit, memory, input / output interfaces, wired or wireless network interfaces, and power supply; The memory is either a short-term storage memory or a persistent storage memory; The central processing unit is configured to communicate with the memory and execute instructions in the memory on the cross-platform content implementation device to perform the method as described in any one of claims 2 to 3.

8. A computer-readable storage medium, characterized in that, Includes instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1 to 3.

9. A computer program product containing instructions, characterized in that, When it is run on a computer, it causes the computer to perform the method as described in any one of claims 1 to 3.

Images