System and method for automatic suggestion and automatic selection of dynamic site compilation within a cloud-based content-centric environment

Abstract

Systems and methods for automatic selection and suggestion of dynamic site compilation in a cloud-based content hub environment are described herein. According to an embodiment, an embodiment provides an artificial intelligence / machine learning (AI / ML) engine that monitors and collects both content and consumption analytics associated with content items on a web page. Based on analysis of such metrics, automatic suggestions can be generated for content to be tagged, so that content items can be statically compiled with the website (optimized for viewing speed and user experience), or dynamically acquired / loaded when the website is loaded or refreshed.

Description

[0001] Copyright Notice

[0002] Portions of the disclosure of this patent document contain material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

[0003] Priority Claim and Cross-Reference to Related Applications

[0004] This application claims the benefit of priority to the following applications: U.S. Provisional Application No. 62 / 900,266, filed on September 13, 2019, and entitled “SYSTEM AND METHOD FOR DYNAMIC SITE COMPILATION WITHIN A CLOUD-BASED HUB ENVIRONMENT”; U.S. Patent Application No. 17 / 019,179, filed on September 11, 2020, and entitled “SYSTEM AND METHOD FOR PROVIDING A USER INTERFACE FOR DYNAMIC SITE COMPILATION WITHIN A CLOUD-BASED CONTENT HUB ENVIRONMENT”; U.S. Patent Application No. 17 / 019,180, filed on September 11, 2020, and entitled “SYSTEM AND METHOD FOR PROVIDING CUSTOM COMPONENT COMPILATION WITHIN A CLOUD-BASED CONTENT HUB ENVIRONMENT”; U.S. patent application No. 17 / 019,181, filed on September 11, 2020, and entitled “SYSTEM AND METHOD FOR AUTOMATIC SUGGESTION FOR DYNAMIC SITE COMPILATION WITHIN A CLOUD-BASED CONTENT HUB ENVIRONMENT”; and U.S. patent application No. 17 / 019,182, filed on September 11, 2020, and entitled “SYSTEM AND METHOD FOR AUTOMATIC SELECTION FOR DYNAMIC SITE COMPILATION WITHIN A CLOUD-BASED CONTENT HUB ENVIRONMENT”, all of which are incorporated herein by reference. Technical Field

[0005] The present disclosure relates generally to website development; more particularly, to systems and methods for dynamic site compilation for distributed website development in a cloud-based content-centric environment. Background Art

[0006] During the development of any given website, especially those driven by content, and during updates to that content, there are generally two approaches to ensuring that the website content is delivered to the website's viewers. These two approaches include dynamically fetching the content from a remote location, and statically caching the content at a local storage device.

[0007] According to an embodiment, static content can generally be considered as files that are stored on the server side of a website (e.g., in a local storage device) and are presented in the same manner each time the content is delivered to a viewer of the website. Examples of such static content include, but are not limited to, images, gifs, HTML, and other types of content that generally do not change between different loads of a given website. Static content can be thought of as similar to a printed publication - once the content is printed, it is generally not changed or updated. One of the advantages of static content is that it is generally loaded very quickly because it is stored in a local storage device.

[0008] According to an embodiment, in contrast, dynamic content is content that typically changes due to specific factors of the user at each visit, or content that changes due to updating or changing the content creation on the website. Typically, websites that rely heavily on dynamic content will change from one load of the website to another, for example, because a team of content creators updates and publishes updates to the website in real time. Although dynamic content provides the advantage of keeping the website up to date between subsequent loads (or push refreshes) of the website, such content is typically slower to load than cached content because such dynamic content is stored at a remote location relative to the website server.

[0009] Today's websites increasingly contain a mix of static and dynamic content, and website developers are generally not very technically oriented. Therefore, it is becoming increasingly important to provide a mechanism that can allow non-technical content developers to optimize their websites to provide the best and most up-to-date (in terms of content) experience to end users visiting such websites. Summary of the invention

[0010] According to an embodiment, the embodiments of the present disclosure allow non-technical users as well as technical users such as website developers to "tag" or mark various components of a website or page. One category of such tags or marks may indicate that such items tagged or marked with the category will be dynamically loaded when the website is visited (e.g., obtained from the source and then loaded into the website for viewing), while another category of tags or marks may indicate that the items so marked are fixed at compile time (e.g., static cache, i.e., the content is compiled within the published website).

[0011] According to an embodiment, the cost of running complex content management system (CMS) queries in a site can be reduced by choosing to compile certain components into the page (static caching). The CMS query is then executed during compilation and the results are inserted directly into the compiled page. This results in a better user experience and allows for very large scalability by offloading repeated calls to the CMS server.

[0012] According to an embodiment, this document further discloses an AI / ML engine (also referred to variously herein as an AI / ML analysis engine and an analysis engine) that can utilize both content analysis and consumption analysis when providing suggested tags to users and / or automatically tag certain components of a website and content items based on, for example, confidence scores.

[0013] According to an embodiment, the present disclosure relates to a system for automatic suggestion of dynamic site compilation in a cloud-based content center environment, which may include: a computer, including a microprocessor; a cloud-based content center, including an application interface suitable for receiving commands, a content management system including at least one database, a website development toolkit having a connection with at least the content management system, and a network server including a website database; and a content analysis engine, the content analysis engine being associated with a cache including a training set; wherein a command is received via the application interface to build a website, wherein the command targets at least one content item stored at the content management system; wherein the at least one content item is associated with at least one metadata tag after being targeted by the command, wherein the setting of the at least one metadata tag is used to indicate that the at least one content item associated with the at least one metadata tag will be statically compiled at the network server or will be dynamically loaded when the website is loaded or refreshed; wherein the content analysis engine performs optimization analysis on the at least one content item associated with the metadata tag; wherein, based on the result of the optimization analysis, the content analysis engine automatically generates a suggestion on the setting of the metadata tag; and wherein the website development toolkit compiles and publishes a website based at least on the received command, the compiled website includes the at least one content item, and the compiled website is publicly accessible.

[0014] According to an embodiment, the present disclosure also relates to a system for automatic selection of dynamic site compilation in a cloud-based content center environment, which may include: a computer, including a microprocessor; a cloud-based content center, including an application interface suitable for receiving commands, a content management system including at least one database, a website development toolkit having a connection with at least the content management system, and a network server including a website database; and a content analysis engine, the content analysis engine being associated with a cache including a training set; wherein a command is received via the application interface to build a website, wherein the command targets at least one content item stored at the content management system; wherein the at least one content item is associated with at least one metadata tag after being targeted by the command, wherein the setting of the at least one metadata tag is used to indicate that the at least one content item associated with the at least one metadata tag will be statically compiled at the network server or will be dynamically loaded when the website is loaded or refreshed; wherein the content analysis engine performs optimization analysis on the at least one content item associated with the metadata tag; wherein the metadata tag is automatically set based on the result of the optimization analysis; and wherein the website development toolkit compiles and publishes a website based at least on the received command, the compiled website includes the at least one content item, and the compiled website is publicly accessible. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 Illustrated is system or archive file check-in / check-out in an enterprise content management system according to an embodiment.

[0016] Figure 2 Illustrated is system or archive file check-in / check-out in an enterprise content management system according to an embodiment.

[0017] Figure 3 A system for dynamic site compilation in a cloud-based content-centric environment is shown according to an embodiment.

[0018] Figure 4 A system for dynamic site compilation in a cloud-based content-centric environment is shown according to an embodiment.

[0019] Figure 5 A system for dynamic site compilation in a cloud-based content-centric environment is shown according to an embodiment.

[0020] Figure 6 A flow diagram of a suggestion engine and an automatic tagging engine for use in dynamic site compilation in a cloud-based content-centric environment is shown according to an embodiment.

[0021] Figure 7A flow diagram of a suggestion engine and an automatic tagging engine for use in dynamic site compilation in a cloud-based content-centric environment is shown according to an embodiment.

[0022] Figure 8 A flow diagram of a suggestion engine and an automatic tagging engine for use in dynamic site compilation in a cloud-based content-centric environment is shown according to an embodiment.

[0023] Fig. 9 A flow chart of a method for a suggestion engine and an automatic tagging engine for use in dynamic site compilation in a cloud-based content-centric environment is shown according to an embodiment.

[0024] Fig.10 is a screenshot of an exemplary website design portal / toolkit as provided in a cloud-based content center, according to an embodiment.

[0025] Fig.11 is a screenshot of an exemplary website design portal / toolkit as provided in a cloud-based content center, according to an embodiment.

[0026] Fig.12 is a screenshot of an exemplary website design portal / toolkit as provided in a cloud-based content center, according to an embodiment.

[0027] Fig.13 is a screenshot of an exemplary website design portal / toolkit as provided in a cloud-based content center, according to an embodiment.

[0028] Fig.14 is a screenshot of an exemplary website design portal / toolkit as provided in a cloud-based content center, according to an embodiment.

[0029] Fig.15 is a screenshot of an exemplary website design portal / toolkit as provided in a cloud-based content center, according to an embodiment.

[0030] Fig.16A is a screenshot of an exemplary website design portal / toolkit as provided in a cloud-based content center, according to an embodiment.

[0031] Fig. 16B is a screenshot of an exemplary website design portal / toolkit as provided in a cloud-based content center, according to an embodiment.

[0032] Fig. 16C is a screenshot of an exemplary website design portal / toolkit as provided in a cloud-based content center, according to an embodiment.

[0033] Fig.17 A process for compilation of components according to an embodiment is shown.

[0034] Fig.18 is a flow chart of a method for providing a user interface for dynamic site compilation in a cloud-based content-centric environment according to an embodiment.

[0035] Fig.19 is a flow chart of a method for providing custom component compilation within a cloud-based content-centric environment, according to an embodiment.

[0036] Fig. 20 is a flow chart of a method for automatic selection of dynamic site compilation in a cloud-based content-centric environment, according to an embodiment.

[0037] Fig.21 is a flow chart of a method for automatic suggestions for dynamic site compilation in a cloud-based content-centric environment, according to an embodiment. DETAILED DESCRIPTION

[0038] The foregoing and other features will become apparent upon reference to the attached description, claims, and drawings. Specific details are set forth to provide an understanding of the various embodiments. However, it will be apparent that the various embodiments may be practiced without these specific details. The attached description and drawings are not intended to be limiting.

[0039] According to an embodiment, a content management system enables content to be created, uploaded, accessed, and modified by multiple users. For example, a content item such as a document can be created and uploaded by one user and subsequently accessed and modified by other users. In addition, a single document can be accessed (e.g., viewed) by multiple users simultaneously. A content management system can be useful for businesses where, for example, several people collaborate on a project by accessing the same document or set of documents.

[0040] However, when a user wishes to upload multiple content items, a complexity issue may arise. In such a case, the user may typically be presented with the option of creating an archive file (e.g., a zip file or other archive file type that combines / compresses multiple content files into a single file) so that all files are uploaded to the ECM application and a single check-in operation is performed to avoid the multiple check-in operations that would be required if each content item were uploaded separately. However, the ECM application does not break the uploaded archive file into an easily usable hierarchical structure, nor into content items represented outside of the archive file.

[0041] Figure 1 Illustrated is system or archive file check-in / check-out in an enterprise content management system according to an embodiment.

[0042] like Figure 1As shown, according to an embodiment, for each of multiple client devices 100, 102 and 104 having a user interface 101, 103, 105 and physical device hardware 106, 107, 108 (e.g., CPU, memory), a content access application 110, 111, 112 can be provided to the client device for execution thereon.

[0043] According to an embodiment, a client device may communicate 162 with an application server 130 , which includes physical computer hardware 131 (eg, CPU, memory) and an enterprise content management system 132 .

[0044] According to an embodiment, the content access application at the client device can communicate with the enterprise content management system via a network 160 (e.g., the Internet or a cloud environment). The content access application can be configured to enable users 150, 152, 154 to view, upload, modify, delete, or otherwise access content such as content items 120, 122, 124 at each client device. For example, new content can be added or uploaded to the enterprise content management system by the user interacting with the content access application on the relevant client device. The content can be transmitted to the enterprise content management system for storage.

[0045] According to an embodiment, the enterprise content management system can be or include a platform for merging content that can be managed by multiple users of an enterprise. According to an embodiment, the enterprise content management system can be configured to communicate with a content database 136 for storing content (or content items) 140, and can deliver the content to the user via the user's client device. According to an embodiment, the content database can be a relational database management system (RDBMS), a file system, or other data source accessible to the enterprise content management system. Content can include, for example, documents, files, emails, memos, images, videos, slide presentations, conversations, and user profiles.

[0046] According to an embodiment, an enterprise content management system can be configured to associate metadata with content. Metadata can include information about a content item, such as its title, author, publication date, historical data (such as who accessed the item and when, where the content is stored, etc.).

[0047] According to an embodiment, the metadata may be stored in a metadata database 138. According to an embodiment, the enterprise content management system may be configured to communicate with the metadata database to access metadata stored therein and to store metadata generated by the system in the metadata database.

[0048] According to an embodiment, the enterprise content management system may also be configured to communicate with a search index 139. The search index may be configured to provide indexing and searching of content and data stored in content databases and metadata databases. According to an embodiment, the search index may be a relational database management system (RDBMS) or a search tool such as Oracle Secure EnterpriseSearch (Oracle SES).

[0049] According to an embodiment, content stored within a content database may be checked out by a user at the user's client device for modification and may be checked back into the enterprise content management system.

[0050] According to an embodiment, a checked-out document may be locked while checked out to a particular user to prevent other users from modifying the checked-out document. However, the system may be configured to allow other users to view the document while it is checked out. According to an embodiment, a new version of the content may be created and stored in a content database of the enterprise content management system.

[0051] According to an embodiment, the enterprise content management system may further include a content management application 133, which includes a security component 142. The security component may include or store security data, which includes user permissions and rights regarding specific content items and / or specific actions. For example, the security data may indicate that certain users are allowed to access and / or modify certain documents. As another example, the security data may indicate that only certain users are allowed to create links between content items, modify certain content items, or delete content items.

[0052] Figure 2 Illustrated is system or archive file check-in / check-out in an enterprise content management system according to an embodiment.

[0053] According to an embodiment, generally, the enterprise content management 210 system includes a repository for storing content (e.g., database 215) and allowing access to these stored content items via ECM as needed and when needed. Operations frequently performed by users 201, 202 of the ECM system may include check-in and check-out operations, as well as operations that utilize content items stored in the database 215, such as using content items on a published website. Access permissions to content items may vary according to user permissions, including reading, writing, deleting, and managing.

[0054] According to an embodiment, a content management system such as the enterprise content management system described above may form part of a cloud-based content hub.

[0055] According to an embodiment, a cloud-based content center can allow users to manage content and digital assets via a network 205 connection (e.g., regardless of location). In addition, such a content center allows users to store files in a cloud environment, allowing access to such files no matter where the user is.

[0056] According to an embodiment, to simplify the creation and delivery of content to improve customer and employee engagement, a cloud-based content hub may provide easy-to-use collaboration and workflow management.

[0057] According to an embodiment, current website development and media access are increasingly content-centric. Content is at the core of almost all marketing and sales efforts. Users within a cloud-based content center can easily and effectively share, collaborate, process, and manage content. Users can typically access such a center via any networked computer, tablet, or smartphone. Users can manage the content as if it resided on a local drive, and can add, delete, and move files within the center as needed. A cloud-based content center can also be a place for collaboration, where content creators can generate articles to be published, waiting for editorial approval. For example, if a picture needs to be approved before it is used on a website, an editor or other sufficiently qualified user can view it (again, on any device), approve it, and move it through the design and publishing process.

[0058] According to an embodiment, the cloud-based content center can also provide for sharing individual files or even entire folders with other users of the content center, provided that security and identity permissions have been managed. The content center can also provide permissioned sharing, where a user who uploads content to be shared can selectively share the content only with specified users. The cloud-based content center can also provide for sharing and joint development of websites and digital asset collections, so other users can access the content needed for a project.

[0059] According to an embodiment, a cloud-based content hub can synchronize content between a user's local computer and the cloud. Users can install applications on their local devices that automatically synchronize files across the cloud and optionally with other user devices. Such sharing also allows for sharing of document updates, such as user-generated content.

[0060] According to an embodiment, a user can utilize a cloud-based content center to communicate with other users about files, folders, content items, or assets used in an upcoming promotion, allowing users to post comments about them. Such files can also be modified via annotations, highlighting specific points, and commenting on them. Likewise, a cloud-based content center can be used to conduct user discussions, such as a project leader allowing team members to exchange views on projects and processes. Files (such as content) can then be added to such conversations, allowing all participants to view, revise, suggest revisions, and comment on the content.

[0061] According to an embodiment, a cloud-based content center can be used for workflow. Workflows can be set up to deliver content to the appropriate personnel for approval and revision, thereby eliminating bottlenecks in the process flow. Simplified process management and content sharing means higher efficiency and smaller gaps in shared knowledge.

[0062] According to an embodiment, a cloud-based content center can be used for website creation, updating, and maintenance. Websites can be created and reviewed using unconventional templates and themes as needed. Users can easily preview the appearance of the created site on devices with different screens. For the best mobile experience, page content is automatically rearranged on smaller screens. Sites can use the latest information and assets to produce materials that are always current.

[0063] According to an embodiment, a user can manage all assets required for a website in one place and set policies governing the use of these assets. This can allow website creators to use content and data from existing sources in an easy manner.

[0064] According to an embodiment, a cloud-based content center can be used to publish and update websites and make them immediately available. Users can process one or more updates, preview the updates in the site, and then publish the update with a single click.

[0065] According to an embodiment, users can create content items, such as articles or blog posts or lists, and publish them on a website or in a brochure or wherever they are needed. The different layouts mean that the content exists separately from the formatting, freeing the user to update the content as needed without having to worry about how the content looks or whether it fits on the page.

[0066] Dynamic site compilation

[0067] According to an embodiment, a cloud-based content center can provide knowledge workers (i.e., non-technical users) with visual website assembly tools to build sites by dragging and dropping components onto pages. The user's actions when building a website can use metadata to define pages, which are then dynamically rendered at runtime.

[0068] According to an embodiment, because runtime pages are dynamically rendered, such websites may suffer from several performance issues, including but not limited to:

[0069] ● Delay page startup to load the page’s metadata before knowing what to render on the page.

[0070] ● Flashes of unstyled content (FOUC) while waiting for all CSS to load before being able to render.

[0071] ●Page animation (jump) as a component is rendered at different speeds at different locations on the page.

[0072] ●The additional server load of each client querying unchanged resources will affect the overall page rendering speed.

[0073] According to an embodiment, one solution to this type of problem involves server-side component rendering (on a per-request basis). When a request is made, dynamic components have the opportunity to be "pre-rendered" into the page, so that the initial view of the page is mostly what is needed. Additional client-side hydration can then be applied to these pre-rendered components.

[0074] According to an embodiment, another solution to this type of problem is static site generation (developer-centric). The site is created by developers who can use tools to compile a static version of the site. Another example is static site generation (non-technical user-centric). Non-technical users use UI tools to build out the site. During website publishing, dynamic data is converted to runtime data and optimized for performance. In addition, there are JSP / PHP / ... page generation tools on request that can be used for this purpose.

[0075] However, according to embodiments, embodiments of the present disclosure allow non-technical users as well as technical users such as website developers to "tag" or mark various components of a website or page. Then, one category of such tags or marks can indicate that such items tagged or marked with that category can continue to be dynamic (i.e., dynamically rendered when the website is loaded or refreshed), while another category of tags or marks can indicate that the items so marked are fixed at compile time (e.g., static cache).

[0076] According to an embodiment, the cost of running complex content management system (CMS) queries in the site can be eliminated by choosing to compile components into the page (static caching). The CMS query is then executed during compilation and the results are inserted directly into the compiled page. This results in a much better user experience and allows for very large scalability by offloading repeated calls to the CMS server.

[0077] Component compilation

[0078] According to an embodiment, the system allows developers to use a variety of techniques and optimize pages or sites for runtime performance. For example, during website development, a framework such as VueJS can be used to render a client's component so that the component can be dynamically added to a page and updated. According to an embodiment, a developer can create a custom (component) compiler for use during compilation of a specific component to convert the component to HTML / CSS so that it can be injected into a page without using JavaScript.

[0079] According to an embodiment, the addition of offline site compilation can provide up to (sometimes even more than) 400% loading speed gains until the point where the page begins to render. This is achieved by reducing the initial page load to a single request rather than multiple requests to build up the page HTML before the page begins to render. This eliminates the problem of flash of unstyled content (FOUC) introduced by any product, allowing template developers to control how / when the page is displayed. This enhances the experience of users viewing the site as they navigate between pages in the site.

[0080] According to an embodiment, for content-heavy pages (where such content can be defined at compile time), page rendering is instant or near instant, without waiting for content queries to return and be available on the page. This not only provides a better experience for users viewing the page in a browser, but also offloads all queries from the content server. The load is paid once at compile time, rather than for each single page request, greatly improving scalability.

[0081] Figure 3 A system for dynamic site compilation in a cloud-based content-centric environment is shown according to an embodiment.

[0082] According to an embodiment, a cloud-based content center 320, which may run on multiple hardware and software resources 321 (e.g., microprocessors, memories, storage devices, operating systems, etc.), may include a client interface 325 (e.g., a graphical user interface, a command line interface, an application programming interface (API) . . . ), a content management system 322 (as described above), a server 330, and a dynamic cache 340. Although shown as part of the cloud-based content center, the server 330, the content management system 322, and the dynamic cache are accessible by the content center, rather than being considered to logically constitute first-level components of the content center.

[0083] According to an embodiment, for example, a client device or user machine 305 that can be accessed and used by a user 300 may include device hardware (processor, memory, etc.) and software 315, as well as an application as a content center application 310 that can be used to communicate with a cloud-based content center environment via a network (such as a wide area network (WAN), a local area network (LAN), or the Internet). The content center application may include a user interface that is not shown.

[0084] According to an embodiment, a user may utilize a content center application and, via client interface 325, for example, upload content (e.g., user-generated content such as articles, pictures, videos, etc.) to a content center, such as at a content management system. Such uploading and / or synchronization may be performed via a manual request, or via automatic processing as a signal emitted by the content center application, or by instructions received from client interface 325. A user may also utilize the content center application and / or client interface 325 to view, modify, edit, delete, or collaborate on content stored within the content management system, provided that the user has been appropriately authenticated via the content center (such authentication system may be in the Figure 3 not shown).

[0085] According to an embodiment, the user can also utilize the website development toolkit 326 of the client interface 325 to develop and publish a website via the server 330. (In other embodiments, the website development toolkit can be an independent service provided by the content center. For convenience, the toolkit 326 is shown as part of the client interface in the embodiment currently described).

[0086] According to an embodiment, as described above, the website development toolkit may provide a plurality of website templates, and the ability to drag and drop various items onto such templates, thereby making it easy for non-technical users 300 to use the provided tools. Examples of such development tools may be found at Figure 10 to Figure 1 Seen in 6.

[0087] According to an embodiment, the website development toolkit may provide a website pane where, based on received input, various pre-made templates and items may be placed (e.g., via drag and drop) onto a website template, which may then be previewed and / or published to the server 330, e.g., based on received commands.

[0088] According to an embodiment, since the website development toolkit can interact with the content management system, any content item in the content management system that a user can access can also be provided as an item that can be placed on a website template. For example, if one member of a team is working on an article in the content management system, another member of the team can use such content when developing a website by placing an item containing the content in a template provided by the website development toolkit.

[0089] According to an embodiment, the website development toolkit may additionally provide an item tagging component that may receive input from, for example, a user to tag certain items of a website as dynamic caches, while other items of a website placed under development may be tagged as static caches.

[0090] Then, according to an embodiment, the content items tagged as static can be stored at server 330 / compiled with the website at server 330 (e.g., stored in cache 335), so that when the website is loaded or refreshed, the server does not have to communicate with other entities to collect the tagged as static content to be displayed or rendered on the website.

[0091] According to an embodiment, items tagged to be statically cached may be stored 360 in a cache 335 at a server 330 that compiled the website when the website was compiled. Examples of items to be statically cached include items on a website that do not change often, since these items are only allowed to change when the website is recompiled or republished, and not just when a web page is refreshed by a viewer of the published website.

[0092] According to an embodiment, items tagged to be dynamically cached may be stored 361 at, for example, a dynamic cache / website content database 340, or may be stored at a content management system 322. Examples of items to be statically cached include items on a website that changes frequently, since such items will be allowed to change when a viewer of the published website refreshes the web page. For example, an article that is being revised and / or updated as a story develops. If such an article is processed in a content management system, a user can place the item in a theme website template corresponding to the story via a website development toolkit and tag the item as dynamic. Then, as the content is updated, the content on the published website is also updated 362 when the website is refreshed or pushed to refresh at the server 330.

[0093] According to an embodiment, items tagged as dynamic cache may be retrieved from content management system 322 or dynamic cache 340, for example, when server 330 loads or refreshes a website.

[0094] Figure 4 A system for dynamic site compilation in a cloud-based content-centric environment is shown according to an embodiment.

[0095] According to an embodiment, a cloud-based content center 420, which may run on multiple hardware and software resources 421 (e.g., microprocessors, memories, storage devices, operating systems, etc.), may include a client interface 425 (e.g., a graphical user interface, a command line interface, an application programming interface (API) . . . ), a content management system 422 (as described above), a server 430, a dynamic cache 440, and an artificial intelligence / machine learning (AI / ML) engine 450 and an associated storage device / cache 451, where a training database may be stored and updated. Although shown as part of the cloud-based content center, the server 430, the content management system 422, and the dynamic cache are accessible by the content center, rather than being considered to logically constitute first-level components of the content center.

[0096] According to an embodiment, for example, a client device or user machine 405 that can be accessed and used by a user 400 may include device hardware (processor, memory, etc.) and software 415, as well as an application as a content center application 410 that can be used to communicate with a cloud-based content center environment via a network (such as a wide area network (WAN), a local area network (LAN), or the Internet). The content center application may include a user interface that is not shown.

[0097] According to an embodiment, a user may utilize a content center application and, via client interface 425, for example, upload content (e.g., user-generated content such as articles, pictures, videos, etc.) to a content center, such as at a content management system. Such uploading and / or synchronization may be performed via a manual request, or via automatic processing as a signal emitted by the content center application, or by instructions received from client interface 425. A user may also utilize the content center application and / or client interface 425 to view, modify, edit, delete, or collaborate on content stored within the content management system, as long as the user has been properly authenticated via the content center.

[0098] According to an embodiment, the user can also utilize the website development toolkit 426 of the client interface 425 to develop and publish a website via the server 430. (In other embodiments, the website development toolkit can be an independent service provided by the content center. For convenience, the toolkit 426 is shown as part of the client interface in the embodiment currently described).

[0099] According to an embodiment, as described above, the website development toolkit may provide a plurality of website templates, and the ability to drag and drop various items onto such templates, thereby allowing non-technical users 400 to easily use the provided tools.

[0100] According to an embodiment, the website development toolkit may provide a website pane where, based on received input, various pre-made templates and items may be placed (e.g., via drag and drop) onto a website template, which may then be previewed and / or published to server 430, for example, based on received commands.

[0101] According to an embodiment, since the website development toolkit can interact with the content management system 422, any content item in the content management system that a user can access can also be provided as an item that can be placed (e.g., dragged and dropped) onto a website template. For example, if one member of a team is working on an article in the content management system, another member of the team can use such content when developing a website by placing an item containing the content into a template provided by the website development toolkit.

[0102] According to an embodiment, the website development toolkit may additionally provide an item tagging component that may receive input from, for example, a user to tag certain items of a website as dynamic caches, while other items of a website placed in development may be tagged as static caches. Such tags may include metadata attached to content items.

[0103] Then, according to an embodiment, the content items tagged as static can be stored at server 430 / compiled with the website at server 330 (e.g., stored in cache 435) so that when the website is loaded or refreshed, the server does not have to communicate with other entities to collect the tagged as static content to be displayed or rendered on the website. In this way, visitors to website 470 using visitor machine 471 can view and interact with the website. When the website is loaded or refreshed, the items tagged as static will load faster than items that are dynamically obtained when loading / refreshing.

[0104] According to an embodiment, items tagged to be dynamically cached may be stored 461 at, for example, a dynamic cache / website content database 440, or may be stored at a content management system 422. Examples of items to be statically cached include items on a website that changes frequently, since such items will be allowed to change upon a refresh of a web page by a viewer of the published website. For example, an article that is being revised and / or updated as a story develops. If such an article is processed in a content management system, a user may place the item within a theme website template corresponding to the story via a website development toolkit and tag the item as dynamic. Then, as the content is updated, the content on the published website is also updated 462 upon a website refresh or push refresh at the server 430.

[0105] According to an embodiment, when a website at, for example, server 430 is loaded or refreshed (e.g., a website compiled at server 430 is viewed or loaded from visitor 470 via visitor machine 471), items tagged as dynamic cache can be obtained from content management system 422 or dynamic cache 440.

[0106] According to an embodiment, items tagged to be statically cached may be stored 460 in a cache 435 at a server 430 that compiled the website when the website was compiled. Examples of items to be statically cached include items on a website that do not change often, since these items are only allowed to change when the website is recompiled or republished, and not just when a web page is refreshed by a viewer of the published website.

[0107] According to an embodiment, items tagged to be dynamically cached may be stored 461 at, for example, a dynamic cache / website content database 440, or may be stored at a content management system 422. Examples of items to be statically cached include items on a website that changes frequently, since such items will be allowed to change upon a refresh of a web page by a viewer of the published website. For example, an article that is being revised and / or updated as a story develops. If such an article is processed in a content management system, a user may place the item within a theme website template corresponding to the story via a website development toolkit and tag the item as dynamic. Then, as the content is updated, the content on the published website is also updated 462 upon a website refresh or push refresh at the server 430.

[0108] According to an embodiment, the AI / ML engine 450 can monitor and track the life cycle of content published at a website hosted at the server 430 via the AI / ML engine's content analysis engine (also referred to herein as an analysis engine), which utilizes a knowledge database at the cache 435. Metrics that can be tracked by the content analysis engine can include, for example, the frequency of publishing (i.e., the website loads or refreshes a page containing a content item). Metrics that can be tracked by the content analysis engine can also include, for example, the rate of change of each content item published on the website (whether the items are tagged as static or dynamic). This tracking can be performed by monitoring the website at the server at its associated cache 435, and can also include monitoring the content management system and dynamic cache for the update rate of content items at, for example, the content management system 422 and the dynamic cache 440. Additional metrics that can be tracked by the AI / ML engine's content analysis engine can include monitoring the use / viewing of the content (e.g., the prevalence of use) (both at the website (e.g., by viewers 470)), as well as the individual use of content items at the content management system 422, the dynamic cache 440, and the server's cache 435.

[0109] Depending on the embodiment, such an analysis engine may collect information about, for example, the published website's popular pages, popular content, pages where viewers spend the most time, and the like.

[0110] Automatic content suggestions based on analysis

[0111] According to an embodiment, based on monitored metrics associated with content items, the AI / ML engine may provide one or more recommendations 490 to the user 400, for example via the user machine 405, regarding which content items would be most effective if tagged as static and which content items would be most effective if tagged as dynamic.

[0112] Figure 5 A system for dynamic site compilation in a cloud-based content-centric environment is shown according to an embodiment.

[0113] According to an embodiment, a cloud-based content center 520, which may run on multiple hardware and software resources 521 (e.g., microprocessors, memories, storage devices, operating systems, etc.), may include a client interface 525 (e.g., a graphical user interface, a command line interface, an application programming interface (API) . . . ), a content management system 522 (as described above), a server 530, a dynamic cache 540, and an artificial intelligence / machine learning (AI / ML) engine 550 and an associated storage device / cache 551, where a training database may be stored and updated. Although shown as part of the cloud-based content center, the server 530, the content management system 522, and the dynamic cache are accessible by the content center, rather than being considered to logically constitute first-level components of the content center.

[0114] According to an embodiment, for example, a client device or user machine 505 that can be accessed and used by a user 500 may include device hardware (processor, memory, etc.) and software 515, as well as an application as a content center application 510 that can be used to communicate with a cloud-based content center environment via a network (such as a wide area network (WAN), a local area network (LAN), or the Internet). The content center application may include a user interface that is not shown.

[0115] According to an embodiment, a user may utilize a content center application and, via client interface 525, for example, upload content (e.g., user-generated content such as articles, pictures, videos, etc.) to a content center, such as at a content management system. Such uploading and / or synchronization may be performed via a manual request, or via automatic processing as a signal emitted by the content center application, or by instructions received from client interface 525. A user may also utilize the content center application and / or client interface 525 to view, modify, edit, delete, or collaborate on content stored within the content management system, as long as the user has been properly authenticated via the content center.

[0116] According to an embodiment, the user can also utilize the website development toolkit 526 of the client interface 525 to develop and publish a website via the server 530. (In other embodiments, the website development toolkit can be an independent service provided by the content center. For convenience, the toolkit 526 is shown as part of the client interface in the embodiment currently described).

[0117] According to an embodiment, as described above, the website development toolkit may provide a plurality of website templates, and the ability to drag and drop various items onto such templates, thereby allowing non-technical users 500 to easily use the provided tools.

[0118] According to an embodiment, the website development toolkit may provide a website pane where, based on received input, various pre-made templates and items may be placed (e.g., via drag and drop) onto a website template, which may then be previewed and / or published to the server 530, for example, based on received commands.

[0119] According to an embodiment, since the website development toolkit can interact with the content management system 522, any content item in the content management system that a user can access can also be provided as an item that can be placed (e.g., dragged and dropped) onto a website template. For example, if one member of a team is working on an article in the content management system, another member of the team can use such content when developing a website by placing an item containing the content into a template provided by the website development toolkit.

[0120] According to an embodiment, the website development toolkit may additionally provide an item tagging component that may receive input from, for example, a user to tag certain items of the website as dynamic caches, while other items of the website placed under development may be tagged as static caches. Such tags may include metadata attached to the content items.

[0121] Then, according to an embodiment, the content items tagged as static can be stored at server 530 / compiled with the website at server 330 (e.g., stored in cache 535) so that when the website is loaded or refreshed, the server does not have to communicate with other entities to collect the content tagged as static to be displayed or rendered on the website. In this way, visitors to website 570 using visitor machine 571 can view and interact with the website. When the website is loaded or refreshed, the items tagged as static will load faster than items that are dynamically obtained when loading / refreshing.

[0122] According to an embodiment, items tagged to be dynamically cached may be stored 561 at, for example, a dynamic cache / website content database 540, or may be stored at a content management system 522. Examples of items to be statically cached include items on a website that changes frequently, since such items will be allowed to change when a viewer of the published website performs a refresh of the web page. For example, an article that is being revised and / or updated as a story develops. If such an article is processed in a content management system, a user can place the item in a theme website template corresponding to the story via a website development toolkit and tag the item as dynamic. Then, as the content is updated, the content on the published website is also updated 562 when the website is refreshed or pushed to refresh at the server 530.

[0123] According to an embodiment, when a website at, for example, server 530 is loaded or refreshed (e.g., a website compiled at server 530 is viewed or loaded from visitor 570 via visitor machine 571), items tagged as dynamic cache can be obtained from content management system 522 or dynamic cache 540.

[0124] According to an embodiment, items tagged to be statically cached may be stored 560 in a cache 535 at a server 530 that compiled the website when the website was compiled. Examples of items to be statically cached include items on a website that do not change often, since these items are only allowed to change when the website is recompiled or republished, and not just when a web page is refreshed by a viewer of the published website.

[0125] According to an embodiment, items tagged to be dynamically cached may be stored 561 at, for example, a dynamic cache / website content database 540, or may be stored at a content management system 522. Examples of items to be statically cached include items on a website that changes frequently, since such items will be allowed to change upon a web page refresh by a viewer of the published website. For example, an article that is being revised and / or updated as a story develops. If such an article is processed in a content management system, a user may place the item within a theme website template corresponding to the story via a website development toolkit and tag the item as dynamic. Then, as the content is updated, the content on the published website is also updated 562 upon a website refresh or push refresh at the server 530.

[0126] According to an embodiment, the AI / ML engine 550 can monitor and track the life cycle of content published at a website hosted at the server 530 via the content analysis engine of the AI / ML engine, which utilizes the knowledge database at the cache 535. Metrics that can be tracked by the content analysis engine can include, for example, the frequency of publishing (i.e., the website loads or refreshes the page containing the content item). Metrics that can be tracked by the content analysis engine can also include, for example, the rate of change of each content item published on the website (whether these items are tagged as static or dynamic). This tracking can be performed by monitoring the website at the server at its associated cache 535, and can also include monitoring the content management system and dynamic cache for the update rate of content items at, for example, the content management system 522 and the dynamic cache 540. Additional metrics that can be tracked by the content analysis engine of the AI / ML engine can include monitoring the use / viewing of the content (e.g., the prevalence of use) (both at the website (e.g., by viewers 570)), as well as the individual use of content items at the content management system 522, the dynamic cache 540, and the server's cache 535.

[0127] Depending on the embodiment, such an analysis engine may collect information about, for example, the published website's popular pages, popular content, pages where viewers spend the most time, and the like.

[0128] According to an embodiment, based on monitored metrics associated with content items, the AI / ML engine may automatically tag certain content as static 590 (i.e., compiled with the website and stored in cache 535), and may automatically tag certain other content as dynamic 591 (i.e., to be stored in dynamic cache 540, or stored at content management system 522). This automatic tagging of content items as static or dynamic may be determined by a content analysis engine (of the AI / ML engine) as to which content items would be most effective to be tagged as dynamic and which content items would be most effective to be tagged as dynamic.

[0129] Figure 6 A flow diagram of a suggestion engine for use in dynamic site compilation in a cloud-based content-centric environment is shown, according to an embodiment.

[0130] According to an embodiment, as described above, the website development toolkit discussed above may work in conjunction with a suggestion and automatic tagging engine for tagging various website elements as dynamic or static.

[0131] According to an embodiment, content authors such as user 600 can manage content and publish content to a cloud-based content center via, for example, a client interface at step 650. Such content can be managed and published at content management and publishing system 605, which can include, for example, a content management system as described above.

[0132] According to an embodiment, at step 651, lifecycle analysis 610 of the published content may be tracked via a content analysis engine 640 (which may be based on, for example, artificial intelligence and machine learning via a knowledge database). Such tracking metrics may include publication frequency, content change rate, content classification, planned publication activity, and similarity to other eligible content (e.g., content that has previously undergone static complication).

[0133] According to an embodiment, at step 652, content authors such as user 600 may utilize a website authoring interface 615 such as a website development toolkit in order to place various items, including the content published from step 650, into the draft website via, for example, provided website templates and drag-and-drop functionality.

[0134] According to an embodiment, user 600 may build 620 (e.g., compile, package, and optimize) a website before publishing (before the website is available for public viewing or viewed internally by others with access permission) at step 653. For example, such a website may be previewed by the author, then revised, and previewed again.

[0135] According to an embodiment, at step 654, the website may be published (as compiled website 625) to, for example, a publicly accessible server that may be accessed 655 by website viewers 630. As described above, compiled website 625 may include content that is both tagged as static content (e.g., content items that are compiled with the website as static content and are not obtained from an alternate source when the website is loaded / refreshed) or dynamic content (e.g., content items that are not compiled with the website as static content, but are obtained from an alternate source such as content management system 605 or a dynamic cache when the website is loaded / refreshed).

[0136] According to an embodiment, the consumption analysis engine 635 may collect website visitor / website behavior about the website as the website viewer 640 interacts with the published website at step 656. Such an analysis engine may collect information about, for example, popular web pages, popular content on the web pages, engagement (time spent on the page / content, repeat views by the same user, bounce rate), direct access pages (e.g., direct access to the page from a search engine result), custom conversions.

[0137] According to an embodiment, at step 657, the artificial intelligence / machine learning tagging engine 640 may monitor the analysis collected from steps 651 and 656 in order to generate a recommendation 658 regarding a tagging (static or dynamic) decision. The engine 640 may be associated with a knowledge database (not shown), which may include a set of seed data and may be built based on the metrics of the analysis and the analysis of the accuracy of the output of the engine 640.

[0138] According to an embodiment, the engine 640 may present the optimized tagging suggestions / recommendations to the site author at step 658 (eg, via the website authoring interface 615 ).

[0139] According to an embodiment, the AI / ML engine constantly monitors content analytics as well as consumption analytics. Thus, the engine 640 is able to revise and change previous tag suggestions / decisions based on analysis of subsequent metrics (metrics generated after the initial tag suggestion / decision).

[0140] According to an embodiment, the AI / ML engine may perform analysis such as the following examples:

[0141] Content Qualification Metrics:

[0142] 1. Release frequency (CQw1)

[0143] 2. Content change rate (CQw2)

[0144] 3. Content Classification (CQw3)

[0145] 4. Arrange release activities (CQw4)

[0146] 5. Similarity to other eligible content (previously statically compiled content) (CQw5)

[0147] ==Content Qualification (CQ)=fn(CQw1,CQw2,CQw3,CQw4,CQw5)

[0148] Using the qualification metric:

[0149] 1. Popular Pages (UQw1)

[0150] 2. Popular content (UQw2)

[0151] 3. Engagement (time spent on page / content, repeat views by the same user, bounce rate) (UQw3)

[0152] 4. Direct access to the page (e.g., directly accessing the page from a search engine result)

[0153] (UQw4)

[0154] 5. Custom conversion (UQw5)

[0155] ==Qualification (UQ)=fn(UQw1,UQw2,UQw3,UQw4,UQw5)

[0156] Among them, the AI / ML engine processes:

[0157] 1. For each content item in the system:

[0158] a. Calculate CQ and UQ continuously.

[0159] 2. Periodically calculate:

[0160] a. Generate a list of best candidates (content items) for static compilation.

[0161] b. Make suggestions / auto-tags for static compilation based on the generated best candidate list.

[0162] Automatic selection based on analyzed content

[0163] Figure 7 A flow diagram of an automatic tagging engine for use in dynamic site compilation in a cloud-based content-centric environment is shown, according to an embodiment.

[0164] According to an embodiment, as described above, the website development toolkit discussed above may work in conjunction with a suggestion and automatic tagging engine for tagging various website elements as dynamic or static.

[0165] According to an embodiment, content authors such as user 700 can manage content and publish content to a cloud-based content center via, for example, a client interface at step 750. Such content can be managed and published at content management and publishing system 705, which can include, for example, a content management system as described above.

[0166] According to an embodiment, at step 751, lifecycle analysis 710 of published content may be tracked via content analysis engine 740 (which may be based on, for example, artificial intelligence and machine learning via a knowledge database). Such tracking metrics may include frequency of publication, rate of content change, and prevalence of content usage.

[0167] According to an embodiment, at step 752, a content author such as user 700 may utilize a website authoring interface 715 such as a website development toolkit in order to place various items, including the content published from step 750, into the draft website via, for example, provided website templates and drag-and-drop functionality.

[0168] According to an embodiment, user 700 may build 720 (e.g., compile, package, and optimize) a website before publishing (before the website is available for public viewing or internally viewed by others with access permission) at step 753. For example, such a website may be previewed by the author, then revised, and previewed again.

[0169] According to an embodiment, at step 754, the website may be published (as a compiled website 725) to, for example, a publicly accessible server that may be accessed 755 by website viewers 730. As described above, the compiled website 725 may include content that is both tagged as static content (e.g., content items that are compiled with the website as static content and are not obtained from an alternate source when the website is loaded / refreshed) or dynamic content (e.g., content items that are not compiled with the website as static content, but are obtained from an alternate source such as a content management system 705 or a dynamic cache when the website is loaded / refreshed).

[0170] According to an embodiment, the consumption analysis engine 735 may collect website visitor / website behavior about the website as the website viewer 740 interacts with the published website, at step 756. Such an analysis engine may collect information about, for example, the published website's popular pages, popular content, pages where viewers spend the most time, etc.

[0171] According to an embodiment, in step 757, the artificial intelligence / machine learning tagging engine 740 may monitor the analysis collected from steps 751 and 756 in order to automatically tag 758 certain content items as static or dynamic when building a website. In this way, instead of presenting options to the user 700 as to which content items should be tagged as static or dynamic, the engine 740 itself can make the decision, thereby simplifying the website design and building process for the user 700. The engine 740 may be associated with a knowledge database (not shown), which may include a set of seed data and may be built based on the metrics of the analysis and the analysis of the accuracy of the output of the engine 740.

[0172] According to an embodiment, at step 758, based on a determination of the benefits of tagging one, some, or all content items as static or dynamic, the engine 740 can make such tagging decisions and automatically select tags for various items on the website based on its analysis and compile components into the website.

[0173] According to an embodiment, the AI / ML engine constantly monitors content analytics as well as consumption analytics. Thus, the engine 740 is able to revise and change previous tag suggestions / decisions based on analysis of subsequent metrics (metrics generated after the initial tag suggestion / decision).

[0174] Figure 8 A flow diagram of an automatic tagging engine for use in dynamic site compilation in a cloud-based content-centric environment is shown, according to an embodiment.

[0175] According to an embodiment, as described above, the website development toolkit discussed above may work in conjunction with a suggestion and automatic tagging engine for tagging various website elements as dynamic or static.

[0176] According to an embodiment, content authors such as user 800 can manage content and publish content to a cloud-based content center via, for example, a client interface at step 850. Such content can be managed and published at a content management and publishing system 805, which can include, for example, a content management system as described above.

[0177] According to an embodiment, at step 851, lifecycle analysis 810 of published content may be tracked via content analysis engine 840 (which may be based on, for example, artificial intelligence and machine learning via a knowledge database). Such tracking metrics may include frequency of publication, rate of content change, and prevalence of content usage.

[0178] According to an embodiment, at step 852, content authors such as user 800 may utilize a website authoring interface 815 such as a website development toolkit in order to place various items, including the content published from step 850, into the draft website via, for example, provided website templates and drag-and-drop functionality.

[0179] According to an embodiment, user 800 may build 820 (e.g., compile, package, and optimize) a website before publishing (before the website is available for public viewing or internally viewed by others with access permission) at step 853. For example, such a website may be previewed by the author, then revised, and previewed again.

[0180] According to an embodiment, at step 854, the website may be published (as a compiled website 825) to, for example, a publicly accessible server that may be accessed 855 by website viewers 830. As described above, the compiled website 825 may include content that is both tagged as static content (e.g., content items that are compiled with the website as static content and are not obtained from an alternate source when the website is loaded / refreshed) or dynamic content (e.g., content items that are not compiled with the website as static content, but are obtained from an alternate source such as a content management system 805 or a dynamic cache when the website is loaded / refreshed).

[0181] According to an embodiment, the consumption analysis engine 835 may collect website visitor / website behavior about the website as the website viewer 840 interacts with the published website, at step 856. Such an analysis engine may collect information about, for example, the published website's popular pages, popular content, pages where viewers spend the most time, etc.

[0182] According to an embodiment, in step 857, the artificial intelligence / machine learning tagging engine 840 may monitor the analysis collected from steps 851 and 856 in order to automatically tag 858 certain content items as static or dynamic when building a website. In this way, as opposed to presenting options to the user 800 regarding which content items should be tagged as static or dynamic, the engine 840 itself can make the decision, thereby simplifying the website design and building process for the user 800. The engine 840 may be associated with a knowledge database (not shown), which may include a set of seed data and may be built based on metrics of the analysis and analysis of the accuracy of the output of the engine 840.

[0183] According to an embodiment, the user may set up the engine 840 with a variable confidence score index, wherein any tag suggestions below the set confidence score may be provided to the user at step 858 so as to make a static / dynamic content tagging decision when the confidence score is not met at 841. When the confidence score is met at 841, the engine 840 may automatically make a tagging decision 859, and such content may be automatically built into the website without user approval.

[0184] According to an embodiment, the AI / ML engine constantly monitors content analytics as well as consumption analytics. Thus, the engine 840 is able to revise and change previous tag suggestions / decisions based on analysis of subsequent metrics (metrics generated after the initial tag suggestion / decision).

[0185] Fig. 9 A flow chart of a method for an automatic tagging engine used in dynamic site compilation in a cloud-based content-centric environment is shown according to an embodiment.

[0186] According to an embodiment, a site may be created and published at 900. At 905, the site (or a page of the site) may be edited.

[0187] According to an embodiment, at 910, if the edit involves adding a component to the website, it can be checked at 915 whether the component references a piece of content, such as from a content management system of a cloud-based content center. If not, then at 920, the item can be tagged, or it is suggested that it be tagged as rendered during website compilation (static caching).

[0188] According to an embodiment, if the component does reference a content item, the method may check whether the content item is valid at 925. If not, the item may be tagged or suggested to be tagged to be rendered during website compilation (static caching) at 920. If yes, the item may be tagged or suggested to be tagged to be rendered at runtime (dynamic caching) at 930.

[0189] According to an embodiment, at 935, if the edit involves adding a content item or digital asset, the method may check whether the content item is valid at 925. If not, then at 920, the item may be tagged or suggested to be tagged to be rendered during website compilation (static caching). If so, then at 930, the item may be tagged or suggested to be tagged to be rendered at runtime (dynamic caching).

[0190] According to an embodiment, at 940, if the edit involves adding a content list to the website, it can be checked whether the result of the content list is valid at 945. If not, then at 920, the item can be tagged or suggested to be tagged as rendered during website compilation (static caching).

[0191] According to an embodiment, if the result of the content list is valid, then at 930, the item may be tagged or suggested to be tagged to render the item at runtime (dynamic caching).

[0192] user interface

[0193] Fig.10 is a screenshot of an exemplary website design portal / toolkit as provided in a cloud-based content center, according to an embodiment.

[0194] More specifically, Fig.10 Shown are screenshots showing multiple site template options of an exemplary website design portal / toolkit as provided in a cloud-based content center, according to an embodiment.

[0195] Fig.11is a screenshot of an exemplary website design portal / toolkit as provided in a cloud-based content center, according to an embodiment.

[0196] More specifically, Fig.11 1 is a screen shot showing a plurality of content assets that can be used in a designed website as provided in a cloud-based content center according to an embodiment of an exemplary website design portal / toolkit. For example, as described above, such content assets can be stored at a content management system.

[0197] Fig.12 is a screenshot of an exemplary website design portal / toolkit as provided in a cloud-based content center, according to an embodiment.

[0198] More specifically, Fig.12 1 is a screen shot showing a plurality of content assets that can be used in a designed website as provided in a cloud-based content center according to an embodiment of an exemplary website design portal / toolkit. For example, as described above, such content assets can be stored at a content management system.

[0199] Fig.13 is a screenshot of an exemplary website design portal / toolkit as provided in a cloud-based content center, according to an embodiment.

[0200] More specifically, Fig.13 1 is a screen shot showing multiple content assets that can be selectively loaded statically or dynamically into a website design as provided in a cloud-based content center according to an embodiment of an exemplary website design portal / toolkit. For example, as described above, such content assets can be stored at a content management system.

[0201] Fig.14 is a screenshot of an exemplary website design portal / toolkit as provided in a cloud-based content center, according to an embodiment.

[0202] More specifically, Fig.14 is a screenshot of an exemplary website design portal / toolkit as provided in a cloud-based content center according to an embodiment showing drag-and-drop functionality for selectively loading content assets in a website design statically or dynamically. For example, as described above, such content assets may be stored at a content management system.

[0203] Fig.15 is a screenshot of an exemplary website design portal / toolkit as provided in a cloud-based content center, according to an embodiment.

[0204] More specifically, Fig.15is a screenshot of an exemplary website design portal / toolkit as provided in a cloud-based content center showing content items that have been selected or tagged to be statically compiled into a published website or dynamically acquired when the website is loaded, according to an embodiment. Fig.15 In the screenshot shown, the content list "starter-blog-authors" can be specified as static and compiled into the published website, resulting in a reduced loading time for the website.

[0205] Fig.16A is a screenshot of an exemplary website design portal / toolkit as provided in a cloud-based content center, according to an embodiment.

[0206] More specifically, Fig.16A is a screen shot of a settings window for selected content items of an exemplary website design portal / toolkit as provided in a cloud-based content center. The settings window provides the user with flag options to selectively render content items when the website is published. In some embodiments, such options can be selected via user interaction. In other embodiments, as described above, the engine can provide suggested tags for such content items, or, again as described above, can even tag content items as dynamic without user interaction.

[0207] Fig. 16B is a screenshot of an exemplary website design portal / toolkit as provided in a cloud-based content center, according to an embodiment.

[0208] More specifically, Fig. 16B 16 is a screenshot of an exemplary website design portal / toolkit as provided in a cloud-based content center showing a settings window for a selected content item. The content item settings window can provide optimization tips 1610, for example, when a user or developer hovers over or selects an interactive icon within the user interface. For example, for a selected content item on a page, the optimization tips can include suggestions to render at publish time (static) or render at load time (dynamic). Such suggestions 1610 can be based on analysis of one or both of consumption or content analysis by the AI / ML engine.

[0209] In accordance with an embodiment, in this manner, the results of AI / ML analysis of consumption and content analysis are exposed to, for example, a user or developer via a user interface in a manner that provides recommendations to the user as to whether to select any given content on the site to be published statically (optimized) or to leave it to be dynamically loaded as described above.

[0210] Fig. 16C is a screenshot of an exemplary website design portal / toolkit as provided in a cloud-based content center, according to an embodiment.

[0211] More specifically, Fig. 16C 1620 is a screenshot of a settings window for a selected content item of an exemplary website design portal / toolkit as provided in a cloud-based content center. The content item settings window can display automatic / automated selections for optimizing content on the website, for example, when a user or developer hovers over or selects an interactive icon within the user interface. For example, for a selected content item on a page, the optimization tip can include an explanation of the AI / ML engine's decision to mark the selected content item as rendered on publish (static) or rendered on load (dynamic) based on analysis of consumption and content analysis. Such explanation 1620 can be based on the AI / ML engine's analysis of one or both of consumption or content analysis.

[0212] According to an embodiment, in this way, the results of AI / ML analysis of consumption and content analysis are exposed to, for example, a user or developer via a user interface in a manner that provides the user with an interpretation of the system's selection of content on the site as statically published (optimized) or leaving it to be dynamically loaded as described above.

[0213] Depending on the embodiment, users or site developers can override static / dynamic decisions made by the system based on AI / ML analysis of content and consumption analytics.

[0214] Automatic selection of dynamic or static data

[0215] According to an embodiment, the system does not provide suggestions, but rather makes a determination and selects multiple pieces of content to be statically compiled. Such a decision-making process can be based on, for example, a set of defined criteria (e.g., there must be an X level of certainty that the content changes from one page view to another). This can be useful, for example, when a content creator / marketer is overwhelmed by the large number of options presented by the above-described embodiments. In this case, an option can be selected to have the suggestion engine take over the decision-making process regarding the statically compiled content.

[0216] Custom Components

[0217] As described above, according to an embodiment, the system allows developers to use a variety of techniques and optimize pages or sites for runtime performance, including in some cases using a custom (component) compiler for use during compilation of a specific component to convert the component into HTML / CSS so that it can be injected into the page without using JavaScript.

[0218] Examples of component types that can be added to a page include paragraphs, headings, images, or separators; which can be defined by a local component file or a remote component file. Local component files are stored on a local server and can be set to render directly within the page, or they can be rendered in an iframe within the page. Remote component files are stored on a remote server and are always rendered in an iframe.

[0219] According to an embodiment, a component can be associated with a JavaScript JSON (render.js) file; and can also be associated with a template that describes how its content will be displayed, such as within a site theme. Once added to a site, developers can edit the component's property settings to meet requirements such as page content, fonts and font sizes, image borders and placement, and other styles. For example, a local component can be defined as:

[0220] / Components / component-name

[0221] appinfo.json

[0222] _folder_icon.jpg

[0223] assets

[0224] settings.html

[0225] render.js

[0226] As another example, a native component using an iframe might be defined as:

[0227] / Components / component-name

[0228] appinfo.json

[0229] folder_icon.jpg

[0230] assets

[0231] settings.html

[0232] render.js

[0233] js

[0234] sites.min.js

[0235] knockout.min.js

[0236] jquery.min.js

[0237] As another example, a remote component could be defined as:

[0238] / Components / component-name

[0239] appinfo.json

[0240] _folder_icon.jpg

[0241] keys.json

[0242] According to an embodiment, a developer can create component compilation specific instructions for a specific component, which are passed during compilation and operate as a custom (component) compiler to convert the specific component into HTML / CSS so that the component can then be injected into the page. Alternatively, if there is a custom compiler defined for a specific component, the component compilation specific instructions associated with the specific component will be used to modify the resulting HTML to be inserted into the page. If there is no custom compiler defined for a specific component, the component will be rendered according to the usual process, such as via the component's render.js file.

[0243] According to an embodiment, the custom compiler may also indicate that a component requires JavaScript "hydration" at runtime, in which case the component's hydrate() function within its render.js file will be called. Alternatively, if the component does not require hydration, the component's render.js file will not be loaded.

[0244] Fig.17 A process for compilation of components according to an embodiment is shown.

[0245] like Fig.17 As shown, according to an embodiment, at 1710, a request is received to compile a site. For example, this can be a manual request, or can be automatically triggered by editing the site in the user interface or by any of the various embodiments of the above-mentioned AI / ML suggestion or prediction processing.

[0246] At 1712, it is determined whether all pages have been compiled, and if so, then at 1714, the compiled site is provided.

[0247] Otherwise, at 1720, each page that makes up the site is compiled. During page compilation, at 1722, it is determined whether a page template compiler exists. If so, then at 1724, the page template is compiled. Otherwise, at 1726, an existing page template can be used.

[0248] At 1730, determine whether all components are compiled. If so, then at 1732, the page is compiled.

[0249] At 1740, each component instance that makes up the page is compiled. If the component is marked for compilation at 1742, and the component compiler exists at 1744, then at 1760, the component is compiled. Otherwise, at 1750, the component is rendered at runtime.

[0250] After all components in the page are compiled, the process continues at 1770 for each subsequent page until all pages in the site have been compiled.

[0251] Page Layout Compiler

[0252] According to an embodiment, a page layout compiler is provided as a JavaScript module that compiles a corresponding page layout. A page layout compiler for a particular page layout is defined by a name associated with a "-compile.js" extension:

[0253] src

[0254] themes

[0255] <yourtheme>

[0256] layouts

[0257] <yourpagelayout>.html

[0258] <yourpagelayout>-compile.js

[0259] If "-compile.js" does not exist for the page layout, custom compilation is not applied. The page layout compiler needs to implement the "compile()" interface, which returns a promise, for example: about-compile.js:

[0260] var AboutPageCompiler=function(){};

[0261] AboutPageCompiler.prototype.compile=function(args){

[0262] var self=this,

[0263] layoutMarkup=args.layoutMarkup;

[0264] self.SCSCompileAPI=args.SCSCompileAPI;

[0265] return new Promise(function(resolve,reject){

[0266] var compiledPage = ";

[0267] / / do some work to compile the page

[0268] compiledPage=doSomeWork(layoutMarkup);

[0269] / / return the compiled page

[0270] resolve(compiledPage);

[0271] });

[0272] };

[0273] module.exports=new AboutPageCompiler();

[0274] Custom Compiler

[0275] According to an embodiment, the custom compiler supports: page layout; section layout; custom components; and content layout. During compilation, the compile-template command will look for a "compile.js" file in the same location as the component's "render.js":

[0276] src

[0277] components

[0278] <yourcomponent>

[0279] assets

[0280] render.js

[0281] compile.js

[0282] If the file does not exist, the component will not be compiled and will be rendered at runtime. If the file does exist, it needs to implement a "compile()" interface that returns a promise, for example:

[0283] var fs = require('fs'),

[0284] path=require('path'),

[0285] mustache=require('mustache');

[0286] var UWContentHeader=function(){};

[0287] UWContentHeader.prototype.compile=function(args){

[0288] var compId = args.compId,

[0289] customSettingsData=args.customSettingsData;

[0290] return new Promise(function(resolve,reject){

[0291] try{

[0292] var dir=__dirname,

[0293] templateFile=path.join(dir,'compile.html'),

[0294] template=fs.readFileSync(templateFile,'utf8');

[0295] var model = {

[0296] title:customSettingsData.title||”,

[0297] body:customSettingsData.body||”

[0298] };

[0299] var markup = ";

[0300] markup=mustache.render(template,model);

[0301] return resolve({

[0302] hydrate:false,

[0303] content:markup

[0304] });

[0305] }catch(e){

[0306] console.log(type+':failed to expand template');

[0307] console.log(e);

[0308] }

[0309] return resolve({});

[0310] });

[0311] };

[0312] module.exports=new UWContentHeader();

[0313] Component hydration

[0314] As mentioned above, the component compiler inserts HTML into the page. If the component needs to execute additional JavaScript at runtime to add things like event handlers, one approach is to inline the JavaScript, that is, you can put <script>标签直接插入到返回的编译标记中，该标签将在页面执行时执行，例如：

[0315] <script src＝".. / _sitesclouddelivery / renderer / libs / scs-core / jssorslider / js / jssor.slider.min.js"type＝"text / javascript">< / script>

[0316] <div id="slider_container_c46b122d-978a-429d-aa25-9b5698428f6f"style="position:relative;top:0px;left:0px;height:400px;width:600px;

[0317] background-color:rgb(68,68,68);visibility:visible;"data-jssorslider="

[0318] 1"> ...

[0319]

[0320] <script>

[0321] (function(){

[0322] / / get the required optionsvar options＝

[0323] {"$FillMode":2,"$AutoPlay":false,"$AutoPlayInterval":3000,"$SlideDuration":50

[0324] 0,"$ArrowKeyNavigation":true,"$HWA":false,"$BulletNavigatorOp tions":{"$Chance

[0325] ToShow":1,"$AutoCenter":1,"$SpacingX":5},"$ArrowNavigatorOpt ions":{"$ChanceTo

[0326] Show":1,"$AutoCenter":2,"$Steps":1},"$ThumbnailNavigatorOptio ns":{"$ChanceToShow":0,"$DisplayPieces":7,"$SpacingX":8,"$ParkingPosition":240}}； / / select the JSSOR value optionsoptions.$BulletNavigatorOptions.$Class＝

[0327] $JssorBulletNavigator$；

[0328] options.$ArrowNavigatorOptions.$Class＝

[0329] $JssorArrowNavigator$；

[0330] options.$ThumbnailNavigatorOptions.$Class＝

[0331] $JssorThumbnailNavigator$；

[0332] / / create the slider

[0333] var slider＝new

[0334] $JssorSlider$("slider_container_c46b122d-978a-429d-aa25-9b5698428f6f",

[0335] options)；

[0336] / / resize,maintaining aspect ratiovar container＝slider.$Elmt.parentElement；

[0337] if(container){

[0338] slider.$ScaleWidth(container.getBoundingClientRect().width)；

[0339] }

[0340] })()；

[0341] 水合函数

[0342] 根据实施例，另一种方法是在render.js文件中包含水合函数，并且请注意，当你返回编译的标记时，该组件要求在运行时水合。这避免了重复的<script>标签，并且使你能够利用现有的JavaScript代码来管理事件，例如：

[0343] return resolve({

[0344] hydrate:true,

[0345] content:markup

[0346] })；

[0347] 如果一个组件标注其需要水合，则在运行时，组件的render.js文件将被加载，并且hydrate()函数被调用以传入包含编译的标记的容器，例如：render.hydra()：

[0348] this.hydrate＝$.proxy(function(container){

[0349] var self＝this,

[0350] $container＝$(container),

[0351] $img＝$container.find('scs-image'),

[0352] $parentDiv＝$img.parent()；

[0353] / / hydrate the trigger events

[0354] $parentDiv.click(function(event){

[0355] self.viewModel.imageClicked($parentDiv[0],

[0356] event)；

[0357] })；

[0358] / / hydrate the action handlers

[0359] self.viewModel.imageWidth.subscribe(function

[0360] (newImageWidth){

[0361] / / calculate the new image style

[0362] var style；

[0363] if(self.viewModel.showTopLayout()){

[0364] style＝”；

[0365] }else{

[0366] style＝'flex-shrink:0；width:'+

[0367] newImageWidth+'；'；

[0368] }

[0369] / / update the sizing style

[0370] $parentDiv.attr('style',style)；

[0371] })；

[0372] 编译模板命令

[0373] 根据实施例，系统还支持编译模板命令(例如作为运行时命令，或由上述任何AI / ML处理触发的)的使用，这允许开发人员(或系统)编译模板内的所有站点页面，然后可以将这些页面部署到站点。编译模板命令具有以下选项：

[0374] cec compile-template<source>

[0375] 上述命令编译模板站点内的所有页面，并将编译的页面置于站点assets(资产)文件夹下。例如，命令行选项包括用于内容URL的通道访问令牌，例如：

[0376] cec compile-template Temp1

[0377] 编译模板Temp1中的站点，同时：

[0378] cec compile-template Temp1-c channelToken

[0379] 这会导致系统使用针对任何内容URL给定的channelToken来编译模板Temp1中的站点，包括：

[0380] 对于站点中的每个页面：读入站点和页面元数据；读入页面布局并应用任何页面布局编译器。

[0381] 对于页面上的每个插槽(slot)：使用page.json文件中定义的网格扩展插槽。

[0382] 对于插槽内的每个组件：应用任何组件编译器；并将生成的组件标记插入插槽内的对应位置。

[0383] 扩展编译标记中的任何宏，并在运行时插入由系统渲染器使用的"SCS”JavaScript对象。

[0384] 将编译的页面标记保存在src / templates / <template> / asset / pages文件夹下。

[0385] 图18是根据实施例的用于在基于云的内容中心环境中为动态站点编译提供用户界面的方法的流程图。

[0386] 根据实施例，在步骤1810，该方法可以在包括微处理器的计算机处提供；基于云的内容中心，基于云的内容中心包括适于接收命令的应用接口、包括至少一个数据库的内容管理系统、具有与至少该内容管理系统的连接和用户界面的网站开发工具包，以及包括网站数据库的网络服务器。

[0387] 根据实施例，在步骤1820，该方法可以提供内容分析引擎，该内容分析引擎与包括训练集的缓存相关联。

[0388] 根据实施例，在步骤1830，该方法可以经由用户界面的图形用户界面显示多个内容项的表示，每个内容项都存储在内容管理系统处。

[0389] 根据实施例，在步骤1840，该方法可以通过内容分析引擎对该多个内容项的内容项进行优化分析。

[0390] 根据实施例，在步骤1850，该方法可以经由图形用户界面显示该多个内容项的内容项的优化分析的结果。

[0391] 图19是根据实施例的用于在基于云的内容中心环境内提供自定义组件编译的方法的流程图。

[0392] 根据实施例，在步骤1910，该方法可以在包括微处理器的计算机处提供基于云的内容中心，该基于云的内容中心包括适于接收命令的应用接口、包括至少一个数据库的内容管理系统、具有与至少该内容管理系统的连接和用户界面的网站开发工具包、包括网站数据库的网络服务器，以及编译器，该编译器可以访问编译器指令的储存库。

[0393] 根据实施例，在步骤1920，该方法可以接收编译网站的指令，该指令包括内容管理数据库处的至少一个内容项。

[0394] 根据实施例，在步骤1930，该方法可以针对指示静态或动态编译内容项的指示的元数据检查内容项的实例。

[0395] 根据实施例，在步骤1940，在元数据指示静态编译内容项的实例时，并且在编译器指令存在于储存库中时(该编译器指令与该内容项的类型相关联)，该方法可以静态编译内容项的实例。

[0396] 图20是根据实施例的用于在基于云的内容中心环境中的动态站点编译的自动选择的方法的流程图。

[0397] 根据实施例，在步骤2010，该方法可以在包括微处理器的计算机处提供基于云的内容中心，该基于云的内容中心包括适于接收命令的应用接口、包括至少一个数据库的内容管理系统、具有与至少该内容管理系统的连接的网站开发工具包，以及包括网站数据库的网络服务器。

[0398] 根据实施例，在步骤2020，该方法可以提供内容分析引擎，该内容分析引擎与包括训练集的缓存相关联。

[0399] 根据实施例，在步骤2030，该方法可以经由应用接口接收命令以构建网站，其中该命令以存储在内容管理系统中的至少一个内容项为目标。

[0400] 根据实施例，在步骤2040，该方法可以将至少一个内容项在被命令作为目标之后与至少一个元数据标签相关联。

[0401] 根据实施例，在步骤2050，该方法可以通过内容分析引擎对与该元数据标签相关联的至少一个内容项进行优化分析。

[0402] 根据实施例，在步骤2060，该方法可以基于优化分析的结果自动设置元数据标签。

[0403] 根据实施例，在步骤2070，该方法可以通过网站开发工具包至少基于接收到的命令来编译和发布网站，所编译的网站包括至少一个内容项，所编译的网站是能够公开访问的。

[0404] 图21是根据实施例的用于在基于云的内容中心环境中的动态站点编译的自动建议的方法的流程图。

[0405] 根据实施例，在步骤2110，该方法可以在包括微处理器的计算机处提供基于云的内容中心，该基于云的内容中心包括适于接收命令的应用接口、包括至少一个数据库的内容管理系统、具有与至少该内容管理系统的连接的网站开发工具包，以及包括网站数据库的网络服务器。

[0406] 根据实施例，在步骤2120，该方法可以提供内容分析引擎，该内容分析引擎与包括训练集的缓存相关联。

[0407] 根据实施例，在步骤2130，该方法可以经由应用接口接收命令以构建网站，其中该命令以存储在内容管理系统中的至少一个内容项为目标。

[0408] 根据实施例，在步骤2140，该方法可以将至少一个内容项在被命令作为目标之后与至少一个元数据标签相关联。

[0409] 根据实施例，在步骤2150，该方法可以通过内容分析引擎对与该元数据标签相关联的至少一个内容项进行优化分析。

[0410] 根据实施例，在步骤2160，该方法可以基于优化分析的结果自动生成关于元数据标签的设置的建议。

[0411] 根据实施例，在步骤2170，该方法可以通过网站开发工具包至少基于接收到的命令来编译和发布网站，所编译的网站包括至少一个内容项，所编译的网站是能够公开访问的。

[0412] 尽管上面已经描述了本发明的各种实施例，但是应当理解，它们以示例而非限制的方式呈现。选择和描述实施例是为了解释本发明的特征和原理及其实际应用。这些实施例示出了这样的系统和方法，其中，利用本发明的各种特征通过提供新的和 / 或改进的功能和 / 或提供包括但不限于减少资源使用、增加容量、增加吞吐量、提高效率、减少到达时间、增强安全性和 / 或改善易用性的性能优势。

[0413] 在本文中参照示出架构、功能、处理和 / 或操作的方法、装置(系统)和计算机程序产品的流程图和 / 或框图来描述本发明的一些实施例。流程图或框图中的每个框表示元素、功能、处理、模块、段或部分指令(包括用于实现指定功能的一个或多个可执行指令)。在一些可替换实施例中，在框图或流程图中标注的功能不符合附图所示的顺序。例如，根据涉及的功能，连续地示出的两个框可以基本上同时地执行，或者按照相反的顺序执行。流程图和 / 或框图的每个块框，以及流程图和 / 或框图中的框的组合，可以通过执行指定功能的计算机程序指令和 / 或专用硬件、和 / 或硬件和计算机程序指令的组合来实现。

[0414] 在一些实施例中，本发明的特征在包括处理器、计算机可读存储介质和用于与其他计算机通信的网卡 / 网络接口的计算机中实现。在一些实施例中，本发明的特征在包括计算系统的网络计算环境中实现，该计算系统包括各种类型的计算机配置，包括经由网络互连的个人计算机、手持设备、多处理器系统、基于微处理器的或可编程的消费电子产品、网络PC、小型计算机、大型计算机等。该网络可以是局域网(LAN)、交换结构网络(例如InfiniBand)、广域网(WAN)和 / 或互联网。该网络可以包括铜传输电缆、光传输光纤、无线传输、路由器、防火墙、交换机、网关计算机和 / 或边缘服务器。

[0415] 在一些实施例中，本发明的特征在包括后端组件(例如，作为数据服务器)、或者包括中间件组件(例如，应用服务器)、或者包括前端组件(例如，具有图形用户界面或Web浏览器的客户端计算机，用户可以通过其与在本文中描述的主题的实现进行交互)的计算系统、或者通过网络互连的此类后端、中间件或前端组件的任何组合中实现。该计算系统可以包括彼此具有客户端-服务器关系的客户端和服务器。在一些实施例中，本发明的特征在包括分布式计算环境的计算系统中实现，在该分布式计算环境中，一个或多个计算机集群经由网络连接。该分布式计算环境可以使所有计算机位于一个位置，或者可以使位于不同远程地理位置的计算机的集群通过网络连接。

[0416] 在一些实施例中，本发明的特征在作为云计算系统的一部分或作为云计算系统的服务的云中实现，该云计算系统基于使用Web技术以自服务、计量方式交付给用户的共享弹性资源。云的特性可以包括例如：按需自服务；广泛的网络访问；资源池；快速弹性；和可计量的服务。云部署模型包括：公共、私有和混合。云服务模型包括软件即服务(SaaS)、平台即服务(PaaS)、数据库即服务(DBaaS)和基础设施即服务(IaaS)。云通常是指为用户提供共享的弹性资源的硬件、软件、网络和网络技术的结合。如在本文中所用，云可以包括公共云、私有云和 / 或混合云实施例，并且可以包括云SaaS、云DBaaS、云PaaS和 / 或云IaaS部署模型。

[0417] 在一些实施例中，使用或借助硬件、软件、固件或它们的组合来实现本发明的特征。在一些实施例中，本发明的特征是使用被配置或编程为执行本发明的一个或多个功能的处理器来实现的。在一些实施例中，处理器是设计用来进行在本文中描述的功能的单芯片或多芯片处理器、数字信号处理器(DSP)、片上系统(SOC)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或其他可编程逻辑器件、状态机、分立门或晶体管逻辑、分立硬件组件或其任何组合。在一些实现中，本发明的特征由针对给定功能的电路实现。在其他实现中，特征在被配置为使用存储在例如计算机可读存储介质上的指令来进行特定功能的计算机、计算系统、处理器和 / 或网络中实现。

[0418] 在一些实施例中，本发明的特征被并入软件和 / 或固件中，用于控制处理和 / 或网络系统的硬件，并用于使处理器和 / 或网络能够与利用本发明特征的其他系统交互。此类软件或固件可以包括但不限于应用程序代码、设备驱动程序、操作系统、虚拟机、管理程序、应用编程接口、编程语言和执行环境 / 容器。基于本公开的教导，熟练的程序员可以容易地准备适当的软件编码。

[0419] 在一些实施例中，本发明包括计算机程序产品，该计算机程序产品是具有指令的机器可读或计算机可读存储介质(多个介质)，其包括存储在其上 / 其中的软件和 / 或固件，这些指令可用于编程或以其他方式配置诸如计算机之类的系统执行进行本发明的任何处理或功能。存储介质或计算机可读介质可以包括适合于存储指令和 / 或数据的任何类型的介质或设备，包括但不限于软盘、硬盘驱动器、固态驱动器、光盘、DVD、CD-ROM、微驱动器以及磁光盘、ROM、RAM、EPROM、EEPROM、DRAM、VRAM、闪存设备、磁卡或光卡、分子存储器、纳米系统或它们的变体和组合。在特定实施例中，存储介质或计算机可读介质是非暂态机器可读存储介质或非暂态计算机可读存储介质。

[0420] 前面的描述并非旨在穷举或将本发明限制于所公开的精确形式。另外，在本发明的实施例已经使用特定系列的事务和步骤进行了描述的情况下，对于本领域技术人员来说应该显而易见的是，除非另有说明，否则该实施例不排除进行额外的事务和步骤。此外，虽然各种实施例描述了本发明的特征的特定组合，但应当理解，在本发明的范围内，这些特征的不同组合对于相关领域的技术人员来说将是显而易见的。特别地，在给定实施例、变体中列举或在附图中示出的特征(类似设备或类似方法)在不背离本发明的范围的情况下可以与另一实施例、变体或附图中的另一个特征组合或替换其。此外，在不脱离本发明的精神和范围的情况下，对相关领域的技术人员显而易见的是，在其中可以进行各种增加、减少、删除、变体、用等同物替换以及其他形式、细节、实施和应用的修改和变化。本发明的更广泛的精神和范围旨在由以下权利要求及其等同物来定义。

[0421] 本公开的各方面在以下的编号的条款中阐述：

[0422] 1.一种用于在基于云的内容中心环境中的动态站点编译的自动建议的系统，包括：

[0423] 计算机，包括微处理器；

[0424] 基于云的内容中心，包括

[0425] 适于接收命令的应用接口；

[0426] 内容管理系统，包括至少一个数据库；

[0427] 网站开发工具包，具有与至少内容管理系统的连接；以及

[0428] 网络服务器，包括网站数据库；以及

[0429] 内容分析引擎，所述内容分析引擎与包括训练集的缓存相关联；

[0430] 其中，经由应用接口接收命令以构建网站，其中所述命令以存储在内容管理系统处的至少一个内容项为目标；

[0431] 其中，所述至少一个内容项在被所述命令作为目标之后与至少一个元数据标签相关联；

[0432] 其中，内容分析引擎对与元数据标签相关联的所述至少一个内容项执行优化分析；

[0433] 其中，基于优化分析的结果，内容分析引擎自动生成关于元数据标签的设置的建议；并且

[0434] 其中，网站开发工具包至少基于接收到的命令来编译和发布网站，所编译的网站包括所述至少一个内容项，所编译的网站是能够公开访问的。

[0435] 2.条款1所述的系统，

[0436] 其中，网站在网络服务器处被编译和发布。

[0437] 3.条款2的系统，

[0438] 其中，内容分析引擎监视并记录与存储在内容管理系统处的所述至少一个内容项相关联的内容分析；并且

[0439] 其中，内容分析引擎监视并记录与在网络服务器处发布的所述至少一个内容项相关联的消费分析。

[0440] 4.条款3所述的系统，

[0441] 其中，内容分析引擎在包括训练集的缓存处记录与存储在内容管理系统处的所述至少一个内容项相关联的内容分析；并且

[0442] 其中，内容分析引擎在包括训练集的缓存处记录与在网络服务器处发布的所述至少一个内容项相关联的消费分析。

[0443] 5.条款4的系统，

[0444] 其中，至少基于所记录的内容分析和所记录的消费分析，对关于元数据标签的设置的建议的自动生成指示该内容项将在网络服务器处被静态编译。

[0445] 6.条款4的系统，

[0446] 其中，至少基于所记录的内容分析和所记录的消费分析，对关于元数据标签的设置的建议的自动生成指示该内容项将在网站的加载或刷新时被动态加载。

[0447] 7.条款4的系统，

[0448] 其中，由内容分析引擎对与所述至少一个内容项相关联的内容分析的监视和记录和对与所述至少一个内容项相关联的消费分析的监视和记录被连续执行。

[0449] 8.一种用于在基于云的内容中心环境中的动态站点编译的自动建议的方法，包括：

[0450] 在包括微处理器的计算机处提供基于云的内容中心，该基于云的内容中心包括

[0451] 适于接收命令的应用接口；

[0452] 内容管理系统，包括至少一个数据库；

[0453] 网站开发工具包，具有与至少内容管理系统的连接；以及

[0454] 网络服务器，包括网站数据库；

[0455] 提供内容分析引擎，所述内容分析引擎与包括训练集的缓存相关联；

[0456] 经由应用接口接收命令以构建网站，其中所述命令以存储在内容管理系统处的至少一个内容项为目标；

[0457] 将所述至少一个内容项在被所述命令作为目标之后与至少一个元数据标签相关联；

[0458] 由内容分析引擎对与元数据标签相关联的所述至少一个内容项执行优化分析；

[0459] 基于优化分析的结果，自动生成关于元数据标签的设置的建议；以及

[0460] 通过网站开发工具包至少基于接收到的命令来编译和发布网站，所编译的网站包括所述至少一个内容项，所编译的网站是能够公开访问的。

[0461] 9.条款8所述的方法，

[0462] 其中，网站在网络服务器处被编译和发布。

[0463] 10.条款9的方法，

[0464] 其中，内容分析引擎监视并记录与存储在内容管理系统处的所述至少一个内容项相关联的内容分析；并且

[0465] 其中，内容分析引擎监视并记录与在网络服务器处发布的所述至少一个内容项相关联的消费分析。

[0466] 11.条款10的方法，

[0467] 其中，内容分析引擎在包括训练集的缓存处记录与存储在内容管理系统处的所述至少一个内容项相关联的内容分析；并且

[0468] 其中，内容分析引擎在包括训练集的缓存处记录与在网络服务器处发布的所述至少一个内容项相关联的消费分析。

[0469] 12.条款11的方法，

[0470] 其中，至少基于所记录的内容分析和所记录的消费分析，对关于元数据标签的设置的建议的自动生成指示该内容项将在网络服务器处被静态编译。

[0471] 13.条款11的方法，

[0472] 其中，至少基于所记录的内容分析和所记录的消费分析，对关于元数据标签的设置的建议的自动生成指示该内容项将在网站的加载或刷新时被动态加载。

[0473] 14.条款11所述的方法，

[0474] 其中，由内容分析引擎对与所述至少一个内容项相关联的内容分析的监视和记录和对与所述至少一个内容项相关联的消费分析的监视和记录被连续执行。

[0475] 15.一种非暂态计算机可读存储介质，其上具有用于在基于云的内容中心环境中的动态站点编译的自动建议的指令，所述指令在由计算机读取和执行时使计算机执行包括如下的步骤：

[0476] 在包括微处理器的计算机处提供基于云的内容中心，该基于云的内容中心包括

[0477] 适于接收命令的应用接口；

[0478] 内容管理系统，包括至少一个数据库；

[0479] 网站开发工具包，具有至少与内容管理系统的连接；以及

[0480] 网络服务器，包括网站数据库；

[0481] 提供内容分析引擎，所述内容分析引擎与包括训练集的缓存相关联；

[0482] 经由应用接口接收命令以构建网站，其中所述命令以存储在内容管理系统处的所述至少一个内容项为目标；

[0483] 将所述至少一个内容项在被所述命令作为目标之后与至少一个元数据标签相关联；

[0484] 由内容分析引擎对与元数据标签相关联的所述至少一个内容项执行优化分析；

[0485] 基于优化分析的结果，自动生成关于元数据标签的设置的建议；以及

[0486] 通过网站开发工具包至少基于接收到的命令来编译和发布网站，所编译的网站包括所述至少一个内容项，所编译的网站是可公开访问的。

[0487] 16.条款15所述的非暂态计算机可读存储介质，

[0488] 其中，网站在网络服务器处被编译和发布。

[0489] 17.条款16所述的非暂态计算机可读存储介质，

[0490] 其中，内容分析引擎监视并记录与存储在内容管理系统处的所述至少一个内容项相关联的内容分析；并且

[0491] 其中，内容分析引擎监视并记录与在网络服务器处发布的所述至少一个内容项相关联的消费分析。

[0492] 18.条款17所述的非暂态计算机可读存储介质，

[0493] 其中，内容分析引擎在包括训练集的缓存处记录与存储在内容管理系统处的所述至少一个内容项相关联的内容分析；并且

[0494] 其中，内容分析引擎在包括训练集的缓存处记录与在网络服务器处发布的所述至少一个内容项相关联的消费分析。

[0495] 19.条款18所述的非暂态计算机可读存储介质，

[0496] 其中，至少基于所记录的内容分析和所记录的消费分析，对关于元数据标签的设置的建议的自动生成指示该内容项将在网络服务器处被静态编译。

[0497] 20.条款18所述的非暂态计算机可读存储介质，

[0498] 其中，至少基于所记录的内容分析和所记录的消费分析，对关于元数据标签的设置的建议的自动生成指示该内容项将在网站的加载或刷新时被动态加载。

[0499] 21.一种用于在基于云的内容中心环境中的动态站点编译的自动选择的系统，包括：

[0500] 计算机，包括微处理器；

[0501] 基于云的内容中心，包括

[0502] 适于接收命令的应用接口；

[0503] 内容管理系统，包括至少一个数据库；

[0504] 网站开发工具包，具有与至少内容管理系统的连接；以及

[0505] 网络服务器，包括网站数据库；以及

[0506] 内容分析引擎，所述内容分析引擎与包括训练集的缓存相关联；

[0507] 其中，经由应用接口接收命令以构建网站，其中所述命令以存储在内容管理系统处的至少一个内容项为目标；

[0508] 其中，所述至少一个内容项在被所述命令作为目标之后与至少一个元数据标签相关联；

[0509] 其中，内容分析引擎对与元数据标签相关联的所述至少一个内容项执行优化分析；

[0510] 其中，基于优化分析的结果，自动设置元数据标签；并且

[0511] 其中，网站开发工具包至少基于接收到的命令来编译和发布网站，所编译的网站包括所述至少一个内容项，所编译的网站是能够公开访问的。

[0512] 22.条款21所述的系统，

[0513] 其中，网站在网络服务器处被编译和发布。

[0514] 23.条款22所述的系统，

[0515] 其中，内容分析引擎监视并记录与存储在内容管理系统处的所述至少一个内容项相关联的内容分析；并且

[0516] 其中，内容分析引擎监视并记录与在网络服务器处发布的所述至少一个内容项相关联的消费分析。

[0517] 24.条款23所述的系统，

[0518] 其中，内容分析引擎在包括训练集的缓存处记录与存储在内容管理系统处的所述至少一个内容项相关联的内容分析；并且

[0519] 其中，内容分析引擎在包括训练集的缓存处记录与在网络服务器处发布的所述至少一个内容项相关联的消费分析。

[0520] 25.条款24所述的系统，

[0521] 其中，至少基于所记录的内容分析和所记录的消费分析，对元数据标签的自动设置指示该内容项将在网络服务器处被静态编译。

[0522] 26.条款24所述的系统，

[0523] 其中，至少基于所记录的内容分析和所记录的消费分析，对元数据标签的自动设置指示该内容项将在网站的加载或刷新时被动态加载。

[0524] 27.条款24所述的系统，

[0525] 其中，由内容分析引擎对与所述至少一个内容项相关联的内容分析的监视和记录和对与所述至少一个内容项相关联的消费分析的监视和记录被连续执行。

[0526] 28.一种用于在基于云的内容中心环境中的动态站点编译的自动选择的方法，包括：

[0527] 在包括微处理器的计算机处提供基于云的内容中心，该基于云的内容中心包括

[0528] 适于接收命令的应用接口；

[0529] 内容管理系统，包括至少一个数据库；

[0530] 网站开发工具包，具有与至少内容管理系统的连接；以及

[0531] 网络服务器，包括网站数据库；

[0532] 提供内容分析引擎，所述内容分析引擎与包括训练集的缓存相关联；

[0533] 经由应用接口接收命令以构建网站，其中所述命令以存储在内容管理系统处的至少一个内容项为目标；

[0534] 将所述至少一个内容项在被所述命令作为目标之后与至少一个元数据标签相关联；

[0535] 由内容分析引擎对与元数据标签相关联的所述至少一个内容项执行优化分析；

[0536] 基于优化分析的结果自动设置元数据标签；以及

[0537] 通过网站开发工具包至少基于接收到的命令来编译和发布网站，所编译的网站包括所述至少一个内容项，所编译的网站是能够公开访问的。

[0538] 29.条款28所述的方法，

[0539] 其中，网站在网络服务器处被编译和发布。

[0540] 30.条款29所述的方法，

[0541] 其中，内容分析引擎监视并记录与存储在内容管理系统处的所述至少一个内容项相关联的内容分析；并且

[0542] 其中，内容分析引擎监视并记录与在网络服务器处发布的所述至少一个内容项相关联的消费分析。

[0543] 31.条款30所述的方法，

[0544] 其中，内容分析引擎在包括训练集的缓存处记录与存储在内容管理系统处的所述至少一个内容项相关联的内容分析；并且

[0545] 其中，内容分析引擎在包括训练集的缓存处记录与在网络服务器处发布的所述至少一个内容项相关联的消费分析。

[0546] 32.条款31所述的方法，

[0547] 其中，至少基于所记录的内容分析和所记录的消费分析，对元数据标签的自动设置指示该内容项将在网络服务器处被静态编译。

[0548] 33.条款31所述的方法，

[0549] 其中，至少基于所记录的内容分析和所记录的消费分析，对元数据标签的自动设置指示该内容项将在网站的加载或刷新时被动态加载。

[0550] 34.条款31所述的方法，

[0551] 其中，由内容分析引擎对与所述至少一个内容项相关联的内容分析的监视和记录和对与所述至少一个内容项相关联的消费分析的监视和记录被连续执行。

[0552] 35.一种非暂态计算机可读存储介质，其上具有用于在基于云的内容中心环境中的动态站点编译的自动选择的指令，所述指令在由计算机读取和执行时使计算机执行包括如下的步骤：

[0553] 在包括微处理器的计算机处提供基于云的内容中心，该基于云的内容中心包括

[0554] 适于接收命令的应用接口；

[0555] 内容管理系统，包括至少一个数据库；

[0556] 网站开发工具包，具有与至少内容管理系统的连接；以及

[0557] 网络服务器，包括网站数据库；

[0558] 提供内容分析引擎，所述内容分析引擎与包括训练集的缓存相关联；

[0559] 经由应用接口接收命令以构建网站，其中所述命令以存储在内容管理系统处的至少一个内容项为目标；

[0560] 将所述至少一个内容项在被所述命令作为目标之后与至少一个元数据标签相关联；

[0561] 由内容分析引擎对与元数据标签相关联的所述至少一个内容项进行优化分析；

[0562] 基于优化分析的结果自动设置元数据标签；以及

[0563] 通过网站开发工具包至少基于接收到的命令来编译和发布网站，所编译的网站包括所述至少一个内容项，所编译的网站是能够公开访问的。

[0564] 36.条款35所述的非暂态计算机可读存储介质，

[0565] 其中，网站在网络服务器处被编译和发布。

[0566] 37.条款36所述的非暂态计算机可读存储介质，

[0567] 其中，内容分析引擎监视并记录与存储在内容管理系统处的所述至少一个内容项相关联的内容分析；并且

[0568] 其中，内容分析引擎监视并记录与在网络服务器处发布的所述至少一个内容项相关联的消费分析。

[0569] 38.条款37所述的非暂态计算机可读存储介质，

[0570] 其中，内容分析引擎在包括训练集的缓存处记录与存储在内容管理系统处的所述至少一个内容项相关联的内容分析；并且

[0571] 其中，内容分析引擎在包括训练集的缓存处记录与在网络服务器处发布的所述至少一个内容项相关联的消费分析。

[0572] 39.条款38所述的非暂态计算机可读存储介质，

[0573] 其中，至少基于所记录的内容分析和所记录的消费分析，对元数据标签的自动设置指示该内容项将在网络服务器处被静态编译。

[0574] 40.条款38所述的非暂态计算机可读存储介质，

[0575] 其中，至少基于所记录的内容分析和所记录的消费分析，对元数据标签的自动设置指示该内容项将在网站的加载或刷新时被动态加载。

[0576] 41.一种用于在基于云的内容中心环境中为动态站点编译提供用户界面的系统，包括：

[0577] 计算机，包括微处理器；

[0578] 基于云的内容中心，包括

[0579] 适于接收命令的应用接口；

[0580] 内容管理系统，包括至少一个数据库；

[0581] 网站开发工具包，具有与至少内容管理系统的连接和用户界面；以及

[0582] 网络服务器，包括网站数据库；以及

[0583] 内容分析引擎，该内容分析引擎与包括训练集的缓存相关联；

[0584] 其中，用户界面经由图形用户界面显示多个内容项的表示，每个内容项都存储在内容管理系统处；

[0585] 其中，内容分析引擎对所述多个内容项中的内容项进行优化分析；

[0586] 其中，经由图形用户界面显示所述多个内容项中的内容项的优化分析的结果。

[0587] 42.条款41所述的系统，

[0588] 其中，内容分析引擎监视并记录与所述多个内容项中的内容项相关联的内容分析；并且

[0589] 其中，内容分析引擎监视并记录与在网络服务器处发布的所述至少一个内容项相关联的消费分析。

[0590] 43.条款42所述的系统，

[0591] 其中，与内容项相关联的内容分析和与内容项相关联的消费分析被记录在与内容分析引擎相关联的缓存中。

[0592] 44.条款43所述的系统，

[0593] 其中，所述多个内容项中的内容项的优化分析包括：

[0594] 计算所述多个内容项中的内容项的内容资格得分；以及

[0595] 计算所述多个内容项中的内容项的使用资格得分。

[0596] 45.条款44所述的系统，

[0597] 其中，所述多个内容项中的内容项的优化分析还包括：

[0598] 基于计算的内容资格得分和使用资格得分，确定所述多个内容项中的内容项将被优化为静态发布的内容。

[0599] 46.条款45所述的系统，

[0600] 其中，经由图形用户界面显示的结果包括对静态发布所述多个内容项中的内容项的建议的表示。

[0601] 47.条款45所述的系统，

[0602] 其中，经由图形用户界面显示的结果包括对静态发布所述多个内容项中的内容项的决定的表示。

[0603] 48.一种用于在基于云的内容中心环境中为动态站点编译提供用户界面的方法，包括：

[0604] 在包括微处理器的计算机处提供基于云的内容中心，该基于云的内容中心包括：

[0605] 适于接收命令的应用接口；

[0606] 内容管理系统，包括至少一个数据库；

[0607] 网站开发工具包，具有与至少内容管理系统的连接和用户界面；以及

[0608] 网络服务器，包括网站数据库；

[0609] 提供内容分析引擎，该内容分析引擎与包括训练集的缓存相关联；

[0610] 经由用户界面的图形用户界面显示多个内容项的表示，每个内容项都存储在内容管理系统处；

[0611] 由内容分析引擎对所述多个内容项中的内容项进行优化分析；以及

[0612] 经由图形用户界面显示所述多个内容项中的内容项的优化分析的结果。

[0613] 49.条款48所述的方法，还包括：

[0614] 由内容分析引擎监视并记录与所述多个内容项中的内容项相关联的内容分析；以及

[0615] 由内容分析引擎监视并记录与在网络服务器处发布的所述至少一个内容项相关联的消费分析。

[0616] 50.条款49所述的方法，

[0617] 其中，与内容项相关联的内容分析和与内容项相关联的消费分析被记录在与内容分析引擎相关联的缓存中。

[0618] 51.条款50所述的方法，

[0619] 其中，所述多个内容项中的内容项的优化分析包括：

[0620] 计算所述多个内容项中的内容项的内容资格得分；以及

[0621] 计算所述多个内容项中的内容项的使用资格得分。

[0622] 52.条款51所述的方法，

[0623] 其中，所述多个内容项中的内容项的优化分析还包括：

[0624] 基于计算的内容资格得分和使用资格得分，确定所述多个内容项中的内容项将被优化为静态发布的内容。

[0625] 53.条款52所述的方法，

[0626] 其中，经由图形用户界面显示的结果包括对静态发布所述多个内容项中的内容项的建议的表示。

[0627] 54.条款52所述的方法，

[0628] 其中，经由图形用户界面显示的结果包括对静态发布所述多个内容项中的内容项的决定的表示。

[0629] 55.一种非暂态计算机可读存储介质，其上具有用于在基于云的内容中心环境中为动态站点编译提供用户界面的指令，所述指令在由计算机读取和执行时使计算机执行包括如下的步骤：

[0630] 在计算机处提供基于云的内容中心，该计算机包括微处理器，该基于云的内容中心包括：

[0631] 适于接收命令的应用接口；

[0632] 内容管理系统，包括至少一个数据库；

[0633] 网站开发工具包，具有与至少内容管理系统的连接和用户界面；以及

[0634] 网络服务器，包括网站数据库；

[0635] 提供内容分析引擎，该内容分析引擎与包括训练集的缓存相关联；

[0636] 经由用户界面的图形用户界面显示所述多个内容项的表示，每个内容项都存储在内容管理系统处；

[0637] 由内容分析引擎对所述多个内容项中的内容项进行优化分析；以及

[0638] 经由图形用户界面显示所述多个内容项中的内容项的优化分析的结果。

[0639] 56.条款55所述的非暂态计算机可读存储介质，所述步骤还包括：

[0640] 由内容分析引擎监视并记录与所述多个内容项中的内容项相关联的内容分析；以及

[0641] 由内容分析引擎监视并记录与在网络服务器处发布的所述至少一个内容项相关联的消费分析。

[0642] 57.条款56所述的非暂态计算机可读存储介质，

[0643] 其中，与内容项相关联的内容分析和与内容项相关联的消费分析被记录在与内容分析引擎相关联的缓存中。

[0644] 58.条款57所述的非暂态计算机可读存储介质，

[0645] 其中，所述多个内容项中的内容项的优化分析包括：

[0646] 计算所述多个内容项中的内容项的内容资格得分；以及

[0647] 计算所述多个内容项中的内容项的使用资格得分。

[0648] 59.条款58所述的非暂态计算机可读存储介质，

[0649] 其中，所述多个内容项中的内容项的优化分析还包括：

[0650] 基于计算的内容资格得分和使用资格得分，确定所述多个内容项中的内容项将被优化为静态发布的内容。

[0651] 60.条款59所述的非暂态计算机可读存储介质，

[0652] 其中，经由图形用户界面显示的结果包括对静态发布所述多个内容项中的内容项的建议的表示。

[0653] 61.一种用于在基于云的内容中心环境内提供自定义组件编译的系统，包括：

[0654] 计算机，包括微处理器；

[0655] 基于云的内容中心，包括

[0656] 适于接收命令的应用接口；

[0657] 内容管理系统，包括至少一个数据库；

[0658] 网站开发工具包，具有与至少内容管理系统的连接和用户界面；

[0659] 网络服务器，包括网站数据库；以及

[0660] 编译器，该编译器能够访问编译器指令的储存库；

[0661] 其中，接收编译网站的指令，该指令包括内容管理数据库处的至少一个内容项；

[0662] 其中，针对指示静态或动态编译内容项的指示的元数据来检查内容项的实例；以及

[0663] 其中，在元数据指示静态编译内容项的实例时，并且在编译器指令存在于储存库中时，所述编译器指令与该内容项的类型相关联，该内容项的实例被静态编译。

[0664] 62.条款61所述的系统，

[0665] 其中，当元数据指示动态编译内容项的实例时，该内容项的实例在网站的运行时被渲染。

[0666] 63.条款62所述的系统，

[0667] 其中，在元数据指示静态编译内容项的实例时，并且在编译器指令不存在于储存库中时，所述编译器指令与该内容项的类型相关联，该内容项的实例在网站的运行时被渲染。

[0668] 64.条款63所述的系统，

[0669] 其中，经由用户界面接收编译网站的指令，该指令包括指示静态或动态编译内容项的实例的指示的元数据。

[0670] 65.条款63所述的系统，还包括：

[0671] 内容分析引擎，该内容分析引擎与包括训练集的缓存相关联。

[0672] 66.条款65所述的系统，

[0673] 其中，经由内容分析引擎接收编译网站的指令，该指令包括指示静态或动态编译内容项的实例的指示的元数据。

[0674] 67.条款66所述的系统，

[0675] 其中，包括元数据的指令是由内容分析引擎对内容项进行的优化分析的结果，该优化分析基于该内容项的内容分析和消费分析。

[0676] 68.一种用于在基于云的内容中心环境内提供自定义组件编译的方法，包括：

[0677] 在包括微处理器的计算机处提供基于云的内容中心，该基于云的内容中心包括

[0678] 适于接收命令的应用接口；

[0679] 内容管理系统，包括至少一个数据库；

[0680] 网站开发工具包，具有与至少内容管理系统的连接和用户界面；

[0681] 网络服务器，包括网站数据库；以及

[0682] 编译器，该编译器能够访问编译器指令的储存库；

[0683] 接收编译网站的指令，该指令包括内容管理数据库处的所述至少一个内容项；

[0684] 针对指示静态或动态编译内容项的指示的元数据来检查内容项的实例；以及

[0685] 在元数据指示静态编译内容项的实例时，并且在编译器指令存在于储存库中时，静态编译该内容项的实例，所述编译器指令与该内容项的类型相关联。

[0686] 69.条款68所述的系统，

[0687] 其中，当元数据指示动态编译内容项的实例时，该内容项在网站的运行时被渲染。

[0688] 70.条款69所述的系统，

[0689] 其中，在元数据指示静态编译内容项的实例时，并且在编译器指令不存在于储存库中时，所述编译器指令与该内容项的类型相关联，该内容项的实例在网站的运行时被渲染。

[0690] 71.条款70所述的系统，

[0691] 其中，经由用户界面接收编译网站的指令，该指令包括指示静态或动态编译内容项的实例的指示的元数据。

[0692] 72.条款70所述的系统，还包括：

[0693] 提供内容分析引擎，该内容分析引擎与包括训练集的缓存相关联。

[0694] 73.条款72所述的系统，

[0695] 其中，经由内容分析引擎接收编译网站的指令，该指令包括指示静态或动态编译内容项的实例的指示的元数据。

[0696] 74.条款73所述的系统，

[0697] 其中，包括元数据的指令是由内容分析引擎对内容项的实例进行的优化分析的结果，该优化分析基于该内容项的实例的内容分析和消费分析。

[0698] 75.一种非暂态计算机可读存储介质，其上具有用于在基于云的内容中心环境内提供自定义组件编译的指令，所述指令在由计算机读取和执行时使计算机执行包括如下的步骤：

[0699] 在包括微处理器的计算机处提供基于云的内容中心，该基于云的内容中心包括

[0700] 适于接收命令的应用接口；

[0701] 内容管理系统，包括至少一个数据库；

[0702] 网站开发工具包，具有与至少内容管理系统的连接和用户界面；

[0703] 网络服务器，包括网站数据库；以及

[0704] 编译器，该编译器能够访问编译器指令的储存库；

[0705] 接收编译网站的指令，该指令包括内容管理数据库处的所述至少一个内容项；

[0706] 针对指示静态或动态编译内容项的指示的元数据来检查内容项的实例；以及

[0707] 在元数据指示静态编译内容项的实例时，并且在编译器指令存在于储存库中时，静态编译该内容项的实例，所述编译器指令与该内容项的类型相关联。

[0708] 76.条款75所述的非暂态计算机可读存储介质，

[0709] 其中，当元数据指示动态编译内容项的实例时，该内容项在网站的运行时被渲染。

[0710] 77.条款76所述的非暂态计算机可读存储介质，

[0711] 其中，在元数据指示静态编译内容项的实例时，并且在编译器指令不存在于储存库中时，所述编译器指令与该内容项的类型相关联，该内容项的实例在网站的运行时被渲染。

[0712] 78.条款77所述的非暂态计算机可读存储介质，

[0713] 其中，经由用户界面接收编译网站的指令，该指令包括指示静态或动态编译内容项的实例的指示的元数据。

[0714] 79.条款77所述的非暂态计算机可读存储介质，所述步骤还包括：

[0715] 提供内容分析引擎，该内容分析引擎与包括训练集的缓存相关联。

[0716] 80.条款79所述的非暂态计算机可读存储介质，

[0717] 其中，经由内容分析引擎接收编译网站的指令，该指令包括指示静态或动态编译内容项的实例的元数据；并且

[0718] 其中，包括元数据的指令是由内容分析引擎对内容项的实例进行的优化分析的结果，该优化分析基于该内容项的实例的内容分析和消费分析。< / script> < / yourcomponent> < / yourpagelayout> < / yourpagelayout> < / yourtheme>

Claims

1. A system for automatic suggestions for dynamic site compilation in a cloud-based content-centric environment, comprising: Computers, including microprocessors; Cloud-based content hub including: An application interface suitable for receiving commands; a content management system including at least one database; a website development kit with connectivity to at least a content management system; and Web servers, including the website's databases; and a content analysis engine associated with a cache comprising a training set; wherein a command is received via an application interface to construct a website, wherein the command targets at least one content item stored at a content management system; wherein the at least one content item is associated with at least one metadata tag after being targeted by the command, wherein the at least one metadata tag is configured to indicate that the at least one content item associated with the at least one metadata tag is to be statically compiled at the network server or is to be dynamically loaded upon loading or refreshing of the website; wherein the content analysis engine performs an optimization analysis on the at least one content item associated with the metadata tag; wherein, based on the results of the optimization analysis, the content analysis engine automatically generates suggestions on the settings of the metadata tags; and The website development toolkit compiles and publishes a website based at least on the received command, the compiled website includes the at least one content item, and the compiled website is publicly accessible.

2. The system according to claim 1, in, Websites are compiled and published at web servers.

3. The system according to claim 2, in, a content analysis engine monitoring and recording content analysis associated with the at least one content item stored at the content management system; and Therein, a content analysis engine monitors and records consumption analysis associated with the at least one content item published at the network server.

4. The system according to claim 3, in, The content analysis engine records, at a cache comprising a training set, content analysis associated with the at least one content item stored at the content management system; and Therein, the content analysis engine records consumption analysis associated with the at least one content item published at the network server at a cache including a training set.

5. The system according to claim 4, in, Based at least on the recorded content analysis and the recorded consumption analysis, a recommendation regarding settings of a metadata tag is automatically generated to indicate that the content item is to be statically compiled at the network server.

6. The system according to claim 4, in, Based at least on the recorded content analysis and the recorded consumption analysis, a suggestion regarding the setting of a metadata tag is automatically generated to indicate that the content item is to be dynamically loaded upon loading or refreshing of the website.

7. The system according to claim 4, in, Monitoring and recording of content analysis associated with the at least one content item and monitoring and recording of consumption analysis associated with the at least one content item by the content analysis engine are performed continuously.

8. A method for automatic suggestion of dynamic site compilation in a cloud-based content-centric environment, comprising: A cloud-based content center is provided at a computer including a microprocessor, the cloud-based content center including: An application interface suitable for receiving commands; a content management system including at least one database; a website development kit with connectivity to at least a content management system; and Web servers, including the website database; providing a content analysis engine associated with a cache including a training set; receiving, via the application interface, a command to construct a website, wherein the command targets at least one content item stored at a content management system; associating the at least one content item with at least one metadata tag after being targeted by the command, wherein the at least one metadata tag is set to indicate that the at least one content item associated with the at least one metadata tag is to be statically compiled at the network server or is to be dynamically loaded upon loading or refreshing of the website; performing, by a content analysis engine, an optimization analysis on the at least one content item associated with the metadata tag; Based on the results of the optimization analysis, automatically generating a recommendation regarding the settings of the metadata tags; and The website is compiled and published by the website development toolkit based at least on the received command, the compiled website includes the at least one content item, and the compiled website is publicly accessible.

9. The method according to claim 8, in, Websites are compiled and published at web servers.

10. The method according to claim 9, in, a content analysis engine monitoring and recording content analysis associated with the at least one content item stored at the content management system; and Therein, a content analysis engine monitors and records consumption analysis associated with the at least one content item published at the network server.

11. The method according to claim 10, in, The content analysis engine records, at a cache comprising a training set, content analysis associated with the at least one content item stored at the content management system; and Therein, the content analysis engine records consumption analysis associated with the at least one content item published at the network server at a cache including a training set.

12. The method according to claim 11, in, Based at least on the recorded content analysis and the recorded consumption analysis, a recommendation regarding settings of a metadata tag is automatically generated to indicate that the content item is to be statically compiled at the network server.

13. The method according to claim 11, in, Based at least on the recorded content analysis and the recorded consumption analysis, a suggestion regarding the setting of a metadata tag is automatically generated to indicate that the content item is to be dynamically loaded upon loading or refreshing of the website.

14. The method according to claim 11, in, Monitoring and recording of content analysis associated with the at least one content item and monitoring and recording of consumption analysis associated with the at least one content item by the content analysis engine are performed continuously.

15. A non-transitory computer-readable storage medium having instructions thereon for automatic suggestions for dynamic site compilation in a cloud-based content-centric environment, the instructions, when read and executed by a computer, causing the computer to perform the steps comprising: A cloud-based content center is provided at a computer including a microprocessor, the cloud-based content center including: An application interface suitable for receiving commands; a content management system including at least one database; A website development kit with a connection to at least a content management system; as well as Web servers, including the website database; providing a content analysis engine associated with a cache including a training set; receiving, via the application interface, a command to construct a website, wherein the command targets at least one content item stored at a content management system; associating the at least one content item with at least one metadata tag after being targeted by the command, wherein the at least one metadata tag is set to indicate that the at least one content item associated with the at least one metadata tag is to be statically compiled at the network server or is to be dynamically loaded upon loading or refreshing of the website; performing, by a content analysis engine, an optimization analysis on the at least one content item associated with the metadata tag; Based on the results of the optimization analysis, automatically generating recommendations regarding said settings of the metadata tags; as well as The website is compiled and published by the website development toolkit based at least on the received command, the compiled website includes the at least one content item, and the compiled website is publicly accessible.

16. The non-transitory computer readable storage medium of claim 15, in, Websites are compiled and published at web servers.

17. The non-transitory computer readable storage medium of claim 16, in, a content analysis engine monitoring and recording content analysis associated with the at least one content item stored at the content management system; and Therein, a content analysis engine monitors and records consumption analysis associated with the at least one content item published at the network server.

18. The non-transitory computer readable storage medium of claim 17, in, The content analysis engine records, at a cache comprising a training set, content analysis associated with the at least one content item stored at the content management system; and Therein, the content analysis engine records consumption analysis associated with the at least one content item published at the network server at a cache including a training set.

19. The non-transitory computer readable storage medium of claim 18, in, Based at least on the recorded content analysis and the recorded consumption analysis, a recommendation regarding settings of a metadata tag is automatically generated to indicate that the content item is to be statically compiled at the network server.

20. The non-transitory computer readable storage medium of claim 18, in, Based at least on the recorded content analysis and the recorded consumption analysis, a suggestion regarding the setting of a metadata tag is automatically generated to indicate that the content item is to be dynamically loaded upon loading or refreshing of the website.

21. A system for automatic selection of dynamic site compilations in a cloud-based content-centric environment, comprising: Computers, including microprocessors; Cloud-based content hub including: An application interface suitable for receiving commands; a content management system including at least one database; a website development kit with connectivity to at least a content management system; and Web servers, including the website's databases; and a content analysis engine associated with a cache comprising a training set; wherein a command is received via an application interface to construct a website, wherein the command targets at least one content item stored at a content management system; wherein the at least one content item is associated with at least one metadata tag after being targeted by the command, wherein the at least one metadata tag is configured to indicate that the at least one content item associated with the at least one metadata tag is to be statically compiled at the network server or is to be dynamically loaded upon loading or refreshing of the website; wherein the content analysis engine performs an optimization analysis on the at least one content item associated with the metadata tag; wherein metadata tags are automatically set based on the results of the optimization analysis; and The website development toolkit compiles and publishes a website based at least on the received command, the compiled website includes the at least one content item, and the compiled website is publicly accessible.

22. The system according to claim 21, in, Websites are compiled and published at web servers.

23. The system according to claim 22, in, a content analysis engine monitoring and recording content analysis associated with the at least one content item stored at the content management system; and Therein, a content analysis engine monitors and records consumption analysis associated with the at least one content item published at the network server.

24. The system according to claim 23, in, The content analysis engine records, at a cache comprising a training set, content analysis associated with the at least one content item stored at the content management system; and Therein, the content analysis engine records consumption analysis associated with the at least one content item published at the network server at a cache including a training set.

25. The system according to claim 24, in, Based at least on the recorded content analysis and the recorded consumption analysis, a metadata tag is automatically set to indicate that the content item is to be statically compiled at the network server.

26. The system according to claim 24, in, Based at least on the recorded content analytics and the recorded consumption analytics, a metadata tag is automatically set to indicate that the content item is to be dynamically loaded upon a load or refresh of the website.

27. The system according to claim 24, in, Monitoring and recording of content analysis associated with the at least one content item and monitoring and recording of consumption analysis associated with the at least one content item by the content analysis engine are performed continuously.

28. A method for automatic selection of dynamic site compilation in a cloud-based content-centric environment, comprising: A cloud-based content center is provided at a computer including a microprocessor, the cloud-based content center including: An application interface suitable for receiving commands; a content management system including at least one database; a website development kit with connectivity to at least a content management system; and Web servers, including the website database; providing a content analysis engine associated with a cache including a training set; receiving, via the application interface, a command to construct a website, wherein the command targets at least one content item stored at a content management system; associating the at least one content item with at least one metadata tag after being targeted by the command, wherein the at least one metadata tag is set to indicate that the at least one content item associated with the at least one metadata tag is to be statically compiled at the network server or is to be dynamically loaded upon loading or refreshing of the website; performing, by a content analysis engine, an optimization analysis on the at least one content item associated with the metadata tag; Automatically set metadata tags based on the results of the optimization analysis; and The website is compiled and published by the website development toolkit based at least on the received command, the compiled website includes the at least one content item, and the compiled website is publicly accessible.

29. The method according to claim 28, in, Websites are compiled and published at web servers.

30. The method according to claim 29, in, a content analysis engine monitoring and recording content analysis associated with the at least one content item stored at the content management system; and Therein, a content analysis engine monitors and records consumption analysis associated with the at least one content item published at the network server.

31. The method according to claim 30, in, The content analysis engine records, at a cache comprising a training set, content analysis associated with the at least one content item stored at the content management system; and Therein, the content analysis engine records consumption analysis associated with the at least one content item published at the network server at a cache including a training set.

32. The method according to claim 31, in, Based at least on the recorded content analysis and the recorded consumption analysis, a metadata tag is automatically set to indicate that the content item is to be statically compiled at the network server.

33. The method according to claim 31, in, Based at least on the recorded content analytics and the recorded consumption analytics, a metadata tag is automatically set to indicate that the content item is to be dynamically loaded upon a load or refresh of the website.

34. The method according to claim 31, in, Monitoring and recording of content analysis associated with the at least one content item and monitoring and recording of consumption analysis associated with the at least one content item by the content analysis engine are performed continuously.

35. A non-transitory computer-readable storage medium having instructions thereon for automatic selection of dynamic site compilation in a cloud-based content-centric environment, the instructions, when read and executed by a computer, causing the computer to perform the steps comprising: A cloud-based content center is provided at a computer including a microprocessor, the cloud-based content center including: An application interface suitable for receiving commands; a content management system including at least one database; A website development kit with a connection to at least a content management system; as well as Web servers, including the website database; providing a content analysis engine associated with a cache including a training set; receiving, via the application interface, a command to construct a website, wherein the command targets at least one content item stored at a content management system; associating the at least one content item with at least one metadata tag after being targeted by the command, wherein the at least one metadata tag is set to indicate that the at least one content item associated with the at least one metadata tag is to be statically compiled at the network server or is to be dynamically loaded upon loading or refreshing of the website; performing, by a content analysis engine, an optimization analysis on the at least one content item associated with the metadata tag; Automatically set metadata tags based on the results of optimization analysis; as well as The website is compiled and published by the website development toolkit based at least on the received command, the compiled website includes the at least one content item, and the compiled website is publicly accessible.

36. The non-transitory computer readable storage medium of claim 35, in, Websites are compiled and published at web servers.

37. The non-transitory computer readable storage medium of claim 36, in, a content analysis engine monitoring and recording content analysis associated with the at least one content item stored at the content management system; and Therein, a content analysis engine monitors and records consumption analysis associated with the at least one content item published at the network server.

38. The non-transitory computer readable storage medium of claim 37, in, The content analysis engine records, at a cache comprising a training set, content analysis associated with the at least one content item stored at the content management system; and Therein, the content analysis engine records consumption analysis associated with the at least one content item published at the network server at a cache including a training set.

39. The non-transitory computer readable storage medium of claim 38, in, Based at least on the recorded content analysis and the recorded consumption analysis, a metadata tag is automatically set to indicate that the content item is to be statically compiled at the network server.

40. The non-transitory computer readable storage medium of claim 38, in, Based at least on the recorded content analytics and the recorded consumption analytics, a metadata tag is automatically set to indicate that the content item is to be dynamically loaded upon a load or refresh of the website.

Images