Technical Field

The present invention relates to a content management system that allows new versions to be uploaded and published in a practical way without the need for uploading new versions (without redeployment) on web provider servers or mobile device operating system application stores as a result of content changes made on the website and mobile applications.

More specifically, the present invention relates to a content management system that allows the changes made to the digital content presented to the client devices of the end users, such as a website or a mobile application, to be published on the web, and to integrate the application without being sent to the application store of the mobile device operating system, allowing the updates to be displayed directly on the user mobile device screen.

State of the Art

Content management systems emerged in order to compile, present in an easy way, access and evaluate the increasing amount of information on the Internet. Currently, with the development of needs and technology, developments on these systems continue. There are varieties with different system structures according to the purposes of these systems. Companies which serve with both websites and mobile applications (E-commerce, Finance, News, and other similar sectors) need content updates for both environments of their ever-changing and increasing content.

Currently, changes to the website and mobile application must be updated separately for each environment. This causes repetition of the process and waste of time. For example, when an e- commerce platform makes an update to the web and mobile application content it is publishing, it has to upload new versions separately on both the web server and the mobile application servers.

Since mobile application platforms, which is widely used today have different software infrastructures according to the operating system of mobile devices, it is necessary to develop and compile appropriate mobile application software. For example, users can install and update their mobile applications on their devices via Google Play and App Store applications for Android and iOS operating systems, respectively. In this process, the updated application files are forwarded to the relevant operating system store management and await approval for the application to be updated. Considering the time difference between countries, if store management consists of individuals, it may take 24-48 hours to receive this update approval. In addition, revision requests may be encountered due to changing application store procedures and rules, which can prolong the approval process too much. In addition to these, all users must also update the updated mobile application on their mobile devices. This can make it impossible to make content changes that require frequent application updates.

On the side of the web page or web applications, although this issue is easier compared to mobile applications, presenting the updated content to the user on a comprehensive website requires the procedure of uploading the new version to the server. This means that even for a simple update, the entire web application is updated on the server, also causes a significant time loss, and increasing possibility of errors.

In the patent document US9448776B1 , a system and method for converting the website into a mobile application is disclosed. However, there is no mention of the content management system where changes and updates can be made and its simultaneous integration for every environment (web and mobile).

In the patent document US9146728B2, a system is disclosed to create mobile software applications that can be updated simultaneously without code changes, reloads and user updates. However, there is no mention of the website content management system and its integration for every environment.

The fact that the content management systems solutions in the prior art could not provide a solution that could be updated for all user devices (mobile devices, tablets, computers, etc.) through a single system and interface and compiled the content according to the device or system to which the request was made and to display it directly on the device screen without requiring any new version updating (re-deployment) and mobile store approvals, etc., made it necessary emergence of the solution according to the present invention.

Object and Summary of the Invention

The object of the present invention is to create an integrated system that reduces the workload that can take days to a few hours, with a web-based content management system, by converting the website and mobile application codes into changes and updates in a fast and standard way, without making changes separately for both environments. Another object of the present invention is to ensure that the mobile operating system is published without wasting time instead of waiting for the approval of the application store and to present a digital platform that allows it to be presented to the end user quickly.

The invention is a system that allows the content management system to publish the changes made to the contents of the website on the web and to integrate the application without sending it to the application store of the mobile device operating system, and comprises the following steps:

- sending a request to the cache server in order to access the content by the client via web browser or mobile application,

- presenting the data in the cache server to the client via a web browser or mobile application, if the requested content exists on the cache servers,

- sending the requests to the converter module on the main server if the requested content does not exist on the cache servers,

- calling the content requested by the client from the content management system of the converter module with the tags of the contents of the page,

- sending the contents requested by the client to the converter module by the content management system in a data package arranged in data exchange format,

- converting the incoming data in the said data exchange format into a structure that the web browser and mobile application can detect, by the converter module,

- sending the data in the said data exchange format obtained in the converter module to the html converter for the web browser client and to the resolver engine for the mobile application,

- presenting the data in the data exchange format coming to the html converter to the requested structure, by the converter module to the web browser, and the data exchange format coming to the resolver engine being converted to the local components of the mobile operating system to the mobile application user.

Brief Description of the Figures

In Figure 1 a, a principle interaction diagram regarding the content update interaction on request from a web browser in the content management system of the invention is presented.

In Figure 1 b, a principle interaction diagram of the content update interaction on request from a mobile in the content management system of the invention is presented.

In Figure 2, a representative block diagram of the content management system, converter and similar basic modules and the basic interaction between them is given. Reference Numbers

10. Client

11 . Mobile device

12. Computer

20. Application routing layer

25. Web browser

30. Mobile application

35. Resolver engine

40. Cache server

50. Converter

60. Database

70. Content Management System (CMS)

100. Code (LayoutCode) request for page layout from mobile device application (GET request)

110. The presence of current data is checked on the cache server for the mobile application page

120. Current data is sent to the mobile device (Return Json data)

130. In CMS converter, it is converted from the page data to the data format to be transmitted to the mobile device (Convert Json from layout)

140. The data (Json data) for the relevant mobile device page layout on the CMS is queried in the database

150. The data (Json data) created for the relevant mobile device page layout from the CMS is sent to the database

200. Request for LayoutCode from web browser (GET request)

210. The existence of data is checked on the cache server for the web browser page

220. Ready data is sent to the web browser (html data)

230. In the CMS converter, html conversion that can work in the web browser is made from the page data (Convert Json to React Html)

240. The data (Json data) for the relevant web browser page layout on the CMS is queried in the database

250. The data (Json data) created for the relevant web browser page layout from CMS is sent to the database

Detailed Description of the Invention

The present invention is the system of updating the web page or mobile application by converting the planned content changes and updates for both the web and mobile application environment without the need to reinstall the new version (re-deployment) on both the web provider server and the mobile device operating system application store with a common web-based content management system (CMS) (70) on users' client devices (10) (apps on their mobile devices (11 ), web browsers (25) on their computer (12) or mobile devices (1 1 ). Instead of making changes for each environment separately, updates and changes are made through a single system. Thanks to the present invention, mobile device (11 ) users, on the other hand, can download and update the mobile application (30) as soon as they run their applications, without the need to perform any special update processes thanks to the system inside the application (a resolver engine (35)) installed on their mobile device (i

Content created or changed in the content management system (70) panel is dynamically managed. By means of the interface (operator panel) presented by the content management system (70), any operator can practically change all the features of the content without writing a programming code, and it is possible to create the content by making additions. These features are; adding/removing images, changing the position of lines, font, size, position, colors and similar features of the texts used. It can be viewed without being published in the web environment with the preview feature in the content management system (70) panel. The web page consists of many templates and is placed in rows and columns. These templates consist of images, buttons, sliders, texts, and similar content. Each template is tagged and invoked with a unique name, such as an ID. In addition, all data belonging to the web page, including these changes and updates made with the content management system (70), are converted in accordance with a data exchange format and output as a data block. The data exchange format contains each feature of the templates as parameters and is used to integrate it into other environments. The data exchange format preferably used in the present invention is Json, which is a data format that provides the advantages of taking up little space in today's web-based data interaction and being able to be converted in a practical way.

The system components and interaction are seen in Figure 1 a for a request from a web browser (25), and in Figure 1 b for a request from a mobile application (30). In the present invention, primarily; the client (10) device sends a request to a cache server (40) to access a content (desired) via internet using a web browser (25) or mobile application (30). If requested contents of the client (10) exist on the cache servers (40), the data on the cache server (40) -as depicted in figure 2- is presented to the client (10) via web browser (25) or mobile application (30). If the requested contents do not exist on the cache server (40), requests are sent to the main server to access the requested content and the requested content from the main server is stored in the cache servers (40) to be kept for a certain period . These requests come to a converter (50) module in the main server. The converter (50) calls the page (content) requested by the client (10) device from the content management system (70) with the modified content tags of the page. The content management system (70), on the other hand, sends the data regarding the requested web page by the client (10) to the converter (50) module with a data exchange format. The data exchange format includes every feature of the templates as parameters. The converter (50) module converts the incoming data into another common data exchange format to complete the preparation for display on web or mobile platforms. In this way, unnecessary areas are deleted, and a suitable structure is obtained for both environments. The obtained new structured data in data exchange format is sent to an html converter module for web browser (25) client devices. Said html converter converts the data that comes to it in data exchange format into html codes to be displayed in a web browser (25). The converted html codes are sent to the client (10) device and presented to the screen of the client (10) to be viewed in the web browser (25) of the end user, and the current content from the main server is stored in the cache servers (40) to be kept for a certain period of time for future requests.

The mobile application (30) receives the data exchange format which the converter module (50) converted by receiving from the content management system (70) for client (10) devices, and the parameters in the data arranged in the data exchange format thanks to the resolver engine (35) module in the mobile application (30) and the content is presented to the end user by converting it into its own local components of the operating system of the mobile device (1 1 ). In this way, current content is presented to the end user without being sent to the application store of the mobile operating system (without requiring an additional mobile application update).

Figure 2 shows a representative diagram of how the content update process is managed for both mobile application (30) and web browsers (25), and the operating principle of the system for each interface is explained below with sample application scenarios.

If the user accesses a web page from a web browser (25) on his computer (12) or mobile device (1 1 ) (i.e., invoking (calling) the relevant website address in the web browser (25)), the following interaction is used in the content management system (70) and interaction managed by its units. In case the user enters the relevant website address from the web browser (25) or calls another page of the website from the interface on the screen (switches to a different page by clicking on the objects on the screen), a unique key data (a word, etc.) used to call the page to be accessed is queried by a web application routing layer (20) whether the content is in the cache. If there is a current content in the cache, the relevant page is sent back as a response to the request directly on the client (10) device requested by the user. In case the content is not in the cache, the current (updated) content is requested by being directed to the content management system (70) by the web application routing layer (20) with said unique key data. As a result of the request (GET request), the content management system (70) transmits data in a special format (e.g., Json) regarding the content changed by the operator (content management operator) to said converter (50). The converter (50) produces a data exchange format (a new Json output) in a suitable format so that the content can be viewed in the web browser (25) running on the mobile device (1 1 ) or computer (12) and transmits it back to the content management system (70). Said data exchange format output is sent to an html converter via the content management system (70). The resulting html output is sent to the content management system (70) and then to the converter (50). It is sent to the requesting client (10) via the converter (50) and the current content is displayed in the web browser (25) of the user's device.

In case of an updated content, this content is directly (without updating from codes on web provider servers) transmitted to the user's device (computer (12), mobile device (1 1 ) etc. client (10) on which the web browser (25) is running) provided by the content management system (70) and converter (50). In case the content update has been done before, that is, before a GET Request, it can be transmitted directly from the said cache server (40) to the user client (10). In any case, the updated content is returned in response to a GET Request from the user's client (10).

Content update; It consists of making changes in the content management interface presented to an administrator in the form desired to be displayed on the relevant web page. Thanks to the interface, the administrator can change the web page to the desired display on the user's screen (make changes in the rows and columns of the web page, pictures, text, and their formats), then it is possible to start the update by interacting (for example, a mouse click operation) with a command (publish or show, etc.) which presented in the interface. At this point, thanks to the update command received from the interface, the conversion process works and the html codes for the updated content are provided.

For example, the html codes of the web page with the changed content are converted into html codes by the said html converter. For this conversion, Json outputs from the content management system (70) are used and these files are converted into html files with up-to-date content by the html converter. The html data obtained after this conversion process is sent back directly to the user's web browser (25) by the converter (50) of the content management system (Get Request is responded to). At this stage, all content updates can be quickly shared with the user without the need for an update or re-deployment on the server of the web service provider.

In another application scenario, the user wishes to access the relevant content via a mobile application (30) pre-installed on a mobile device (1 1 ) (phone, tablet, etc.) as a client (10). Unlike the web browser (25), the mobile application (30) interacts with the content (for example, a Json file) to be returned to it from the internet environment and can reflect the same image (screen) on the user's mobile device (11 ).

In other words, in order to eliminate the need for approval, re-update or new version installation of the current content provided by the content management system (70) in the mobile application (30) store, the mobile device (1 1 ) is the one who compiles and interprets the content information received in the first downloaded application and a module is added that displays this directly on the mobile application page requested by the user.

Thanks to the aforementioned module, it is sufficient for the user to download the mobile application (30) from the relevant operating system store once, and there is no need to take action again from the store and the operating system mobile application provider for updates.

When this special mobile application (30) content data obtained from the converter is sent back to the user mobile device (11 ), as mentioned, it is compiled and updated on the device screen by compiling it with the help of a resolver engine (35) that was previously placed in the mobile application (30) installed on the mobile device (11 ) content can be viewed. Thanks to the mentioned module, it is sufficient for the user to download the mobile application from the relevant operating system store once, and there is no need to take action from the store or the operating system mobile application provider again for updates. The module in question contains different codes for Android and iOS, which have different software infrastructures. However, the data compiled in the data exchange format arranged for the mobile application is used jointly and works in different mobile operating system applications. A drawing engine module detects the parameters in the data output in the data exchange format, converts them into its own local components of the mobile application and is reflected on the mobile device screen. The drawing engine module is developed separately for different mobile operating systems.

Similarly, as the process starts from the web browser (25), the GET request is transmitted to the content management system converter (50) in the internet environment, and it is ensured whether there has been a change in the page.

The whole process is managed similarly for both the mobile application (30) and the web browser (25), and the function of the content management system converter (50) is to determine where the request (GET Request) comes from (i.e. from a web browser (25) or mobile application (30) whether it comes from the content management system (70) after the current content data (preferably with a Json output) is transmitted to it, then whether it will compile it according to the web browser (25) with the help of an html converter or decides that it will be converted to an output that the mobile application (30) expects (for example, a Json output for mobile devices).

For content that can be updated simultaneously or at predetermined periods (for example, every 5 minutes), the content management system (70) converts the version desired to be displayed on user screens (web browser or mobile application) to an html (web browser (25)) codes or mobile applications (30) by means of the converter (50) to a Json output that can be parsed and ready for user demands. The converter (50) for the web browser (25) converts the current content data it receives from the content management system (70) to html codes via an html converter module (for example, React html code converter), and for the mobile application (30), the relevant mobile operating system (for example, iOS or Android) converts it to an output (Json file) to be parsed by the mobile application (30) and this output can be displayed on the screen of the mobile device (1 1 ) by making transformations in accordance with the operating system of the mobile device (1 1 ) with a built-in drawing engine in the said mobile application (30). In both cases, the converter (50) meets the requests (GET Request) created by the user-generated web browser (25) or the mobile application (30) and is at the center of the interactions in the content management system (70).

The flow in figure 2 for the mobile application (30) running on a mobile device (11 ) can be summarized as follows:

From a mobile device (11 ) screen for the page layout from the user's mobile application (30), a code (Layout Code) request (GET request) (100) is made (100). Subsequently, the presence of current (requested) data is checked (110) in the cache server (40) for the mobile application (30) page. If the data is available in the cache server (40), appropriate requested current data is sent to the mobile device (11 ) (Return Json data) (120). Otherwise, the data to be transmitted from the page data to the mobile device (1 1 ) in the converter (50) of the request content management system (70) is converted to the data exchange format (Convert Json from layout) (130). On the content management system (70), the data (Json data) for the page layout of the relevant mobile device (1 1 ) is queried in the database (60) (140). The data (Json data) created for the page layout of the content management system (70) related mobile device (11 ) from the content management system is sent to the database (60) (150). For the web browser (25) running on a computer (12), the flow in figure 2 can be summarized as follows:

The code (LayoutCode) request (200) is performed from the web browser on the computer (12) screen. The existence of data is checked (210) in the cache server (40) for the web browser (25) page. If the data is available in the cache server (40), appropriate ready data (html data) (220) is sent to the web browser (25). Otherwise, the content management system CMS (70) converts the page data to html that can work in the web browser (25) (Convert Json to React Html) (230). The data (Json data) for the related web browser (25) page layout on the content management system CMS (70) is queried in the database (240). The data (Json data) generated for the related web browser

(25) page layout from the content management system (70) is sent to the database (60) (250).

As a result, the content requested to be accessed is updated directly on the client (10) device (computer (12) or mobile device (1 1 )) by the user, by updating them in a more practical and fast manner without the need for updating on web service servers or mobile application stores that involve laborious procedures.