Decoupling website service from presentation layer

Aspects of the present disclosure involve systems and methods for performing operations comprising: retrieving, from a content management system, website generation data; identifying a first type of object in the website generation data; obtaining, from a centralized storage of a plurality of website presentation layers, a first website presentation layer corresponding to the first type of object; and generating, for display on a webpage, a first display element corresponding to the first type of object according to a look and feel defined by the first website presentation layer and having first content defined by the website generation data.

TECHNICAL FIELD

The present disclosure relates generally to website generation and presentation.

BACKGROUND

The popularity of users interacting with other users online continues to grow. There are many ways for users to interact online with other users. Users can communicate with their friends using messaging applications and can play with other users online in multiplayer video games or perform other actions using various other applications. Oftentimes, the main way users communicate with each other and obtain content is via websites.

DETAILED DESCRIPTION

Typically, website developers generate websites by defining the content on the websites, behavior of elements on the websites and the how the content visually looks on the websites. Namely, website developers not only need to generate the content (such as pictures and text) that is on the website but also need to write code for how the content is presented. This process takes a great deal of time, adds expense and slows down the speed at which websites can be launched. Sometimes, entities may avoid updating or creating websites altogether to avoid this long process and expense.

In some cases, a new webpage may need to be added to a given website for a given entity. This new webpage may be generated by the given entity itself or a third-party, such as an advertiser, that would like to present content on the given entity's website. To generate the new webpage, certain elements, such as buttons on the webpage or other interactive or non-interactive components, need to adhere to predefined visual specifications that are specific to the given entity. These visual specifications ensure that a consistent look and feel is provided across various webpages of the same entity. That is, a button that appears on one webpage of the entity looks the same (e.g., has the same color scheme, font type and size, and is of a certain shape and size) as another button that appears on another webpage of the entity. Adhering to these specifications further introduces delays and development cost and resources as code segments that define the layout and presentation of the content on the webpage have to be re-written for each new webpage that is added to the website.

The disclosed embodiments improve the efficiency and speed at which websites are developed and launched using a website generation system. The website generation system decouples the presentation component of website or webpage creation from the content of the website or webpage. Specifically, the disclosed website generation system stores various website presentation layers that correspond to different object types on a centralized storage facility, such as a facility associated with a given entity. Website generation data, such as website generation data received from another entity, is obtained that defines only the content and the behavior of the website. A translator identifies a first type of object in the website generation data, such as a button that has certain content. The translator looks up, via a stored map or look-up table, a corresponding first website presentation layer associated with the first type of object. The disclosed website generation system then generates code for displaying on a webpage a first display element corresponding to the first type of object according to a look and feel defined by the first presentation layer and having first content defined by the website generation data. Namely, the website generation system generates code to present on a webpage the button with the specified content (e.g., a text or image or video) provided in the website generation data and which has the visual elements (e.g., has a color scheme, font type and size, and is of a certain shape and size) that meet specifications of the given entity.

In this way, a website developer need only define the content and behavior attributes of the website and does not need to define how the content is presented. By using a translator to look up a website presentation layer corresponding to certain object types in the website generation data provided by various entities, a consistent look and feel can be provided across different webpages of a website associated with a particular entity. The disclosed website generation system further expedites the website development process and reduces the number of resources needed to generate websites by decoupling the visual presentation element generation of the website development process from the content and behavior generation of the website development process. Namely, a new webpage can be created by only specifying the content of the webpage (e.g., the text, images and video) and behavior (e.g., buttons and interactive elements) of the webpage without having to define the look and feel of the content and behavior elements. According to the disclosed embodiments, the device resources (e.g., processor cycles, memory, and power usage) needed to accomplish a task with the device are thereby reduced.

Networked Computing Environment

FIG. 1is a block diagram showing an example messaging system100for exchanging data (e.g., messages and associated content) over a network. The messaging system100includes multiple instances of a client device102, each of which hosts a number of applications, including a messaging client104. Each messaging client104is communicatively coupled to other instances of the messaging client104and a messaging server system108via a network106(e.g., the Internet). Messaging server system108may include a content management system107, in which case, each messaging client104accesses a website from the content management system107via the messaging server system108. In some implementations, all or a portion of the distributed content management system107is implemented externally to the messaging server system108. In these circumstances, each messaging client104accesses a website from the content management system107directly via the network106.

In some embodiments, the messaging client104implements a web browser application that requests a website from the content management system107. In response, the messaging client104receives website generation data from the content management system107. The messaging client104processes the website generation data to identify an object of a given type. The messaging client104uses a translator that is locally stored or remotely stored on database120to identify a website presentation layer associated with the given type of object. The messaging client104retrieves the identified website presentation layer from the website presentation layers128and generates code for presenting the object with visual components having a certain look and feel (e.g., having certain font type, color, and size, and having certain graphical properties, such as element shape, size and color) using the retrieved website presentation layer. As an example, the website generation data may define content and behavior of the webpage according to an XML specification (or JSON file) and the website presentation layer provides JavaScript code segments for presenting the content and behavior with centralized and shared look and feel. The messaging client104then presents on the client device102, such as on the web browser application, a webpage with the content defined by the website generation data and having a look and feel defined by the website presentation layer of various types of objects in the website generation data.

A messaging client104is able to communicate and exchange data with another messaging client104and with the messaging server system108via the network106. The data exchanged between messaging client104, and between a messaging client104and the messaging server system108, includes functions (e.g., commands to invoke functions) as well as payload data (e.g., text, audio, video or other multimedia data).

The messaging server system108provides server-side functionality via the network106to a particular messaging client104. While certain functions of the messaging system100are described herein as being performed by either a messaging client104or by the messaging server system108, the location of certain functionality either within the messaging client104or the messaging server system108may be a design choice. For example, it may be technically preferable to initially deploy certain technology and functionality within the messaging server system108but to later migrate this technology and functionality to the messaging client104where a client device102has sufficient processing capacity.

Turning now specifically to the messaging server system108, an Application Program Interface (API) server110is coupled to, and provides a programmatic interface to, application servers112. The application servers112are communicatively coupled to a database server118, which facilitates access to a database120that stores data associated with messages processed by the application servers112. Similarly, a web server124is coupled to the application servers112, and provides web-based interfaces to the application servers112. To this end, the web server124processes incoming network requests over the Hypertext Transfer Protocol (HTTP) and several other related protocols.

The Application Program Interface (API) server110receives and transmits message data (e.g., commands and message payloads) between the client device102and the application servers112. Specifically, the Application Program Interface (API) server110provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the messaging client104in order to invoke functionality of the application servers112. The Application Program Interface (API) server110exposes various functions supported by the application servers112, including account registration, login functionality, the sending of messages, via the application servers112, from a particular messaging client104to another messaging client104, the sending of media files (e.g., images or video) from a messaging client104to a messaging server114, and for possible access by another messaging client104, the settings of a collection of media data (e.g., story), the retrieval of a list of friends of a user of a client device102, the retrieval of such collections, the retrieval of messages and content, the addition and deletion of entities (e.g., friends) to an entity graph (e.g., a social graph), the location of friends within a social graph, and opening an application event (e.g., relating to the messaging client104).

The application servers112host a number of server applications and subsystems, including for example a messaging server114, an image processing server116, and a social network server122. The messaging server114implements a number of message processing technologies and functions, particularly related to the aggregation and other processing of content (e.g., textual and multimedia content) included in messages received from multiple instances of the messaging client104. As will be described in further detail, the text and media content from multiple sources may be aggregated into collections of content (e.g., called stories or galleries). These collections are then made available to the messaging client104. Other processor- and memory-intensive processing of data may also be performed server-side by the messaging server114, in view of the hardware requirements for such processing.

The application servers112also include an image processing server116that is dedicated to performing various image processing operations, typically with respect to images or video within the payload of a message sent from or received at the messaging server114.

The social network server122supports various social networking functions and services and makes these functions and services available to the messaging server114. To this end, the social network server122maintains and accesses an entity graph306(as shown inFIG. 3) within the database120. Examples of functions and services supported by the social network server122include the identification of other users of the messaging system100with which a particular user has relationships or is “following,” and also the identification of other entities and interests of a particular user.

The website presentation layers128store a plurality of website presentation layers. Each website presentation layer defines a specific look and feel for a specific type of object that is presented on a website. Each website presentation layer includes code segments that define the font size, font type, font color, graphical element shape, size, and color for different object types. For example, a first type of object, such as a button that is linked to another webpage, may be associated with a first website presentation layer that presents the button in a certain color and in a certain shape, such as an oval with a yellow background. A second type of object, such as a button that causes an application to be downloaded, may be associated with a second website presentation layer that presents the button in a different color and in a different shape, such as a square with a red background. A third type of object, such as a static title of the webpage, may be associated with a third website presentation layer that presents the title in a certain color and in a certain font type and size. In some cases, the website presentation layers also define the position and placement of the objects on the webpage, such as at the top, bottom, side, or as a pop-up on the webpage. In some cases, the website presentation layers128are stored as react components.

The content management system107stores website generation data for various entities. This content management system107may be a central repository of website data that is used to present websites. As new websites are created, their respective code (e.g., JSON or XML code) is uploaded and stored on the content management system107. In some cases, the content management system107also stores in a separate repository the translator that maps different object types to different website presentation layers128. In some cases, the website presentation layers128are stored on the content management system107. The content management system107provides specifications for how object types are defined in website generation data, which is used by developers to generate the content and behavior of websites. Different entities can develop and upload different website generation data that use the same scheme to define object types. The object types are associated with the same shared website presentation layers128for presenting the visual elements of the website generation data which creates a consistent look and feel for webpages that are developed by different entities.

For example, different entities can develop webpages for presentation on a website associated with a particular entity, and because the visual presentation of the website elements is controlled by the particular entity through the website presentation layers128, those webpages can be presented with a consistent look and feel associated with the particular entity without the different entities having to define the look and feel of the elements. Namely, the various entities only need to define the content and behavior aspects of the website and use consistent object type naming for the content and behavior aspects that are defined. The content management system107can use the website presentation layers128that are provided by a specific entity to control the look and feel of how the content and behavior aspects of the website are presented to a user.

System Architecture

FIG. 2is a block diagram illustrating further details regarding the messaging system100, according to some examples. Specifically, the messaging system100is shown to comprise the messaging client104and the application servers112. The messaging system100embodies a number of subsystems, which are supported on the client side by the messaging client104and on the sever side by the application servers112. These subsystems include, for example, an ephemeral timer system202, a collection management system204, an augmentation system206, a map system208, and a game system210.

The ephemeral timer system202is responsible for enforcing the temporary or time-limited access to content by the messaging client104and the messaging server114. The ephemeral timer system202incorporates a number of timers that, based on duration and display parameters associated with a message, or collection of messages (e.g., a story), selectively enable access (e.g., for presentation and display) to messages and associated content via the messaging client104. Further details regarding the operation of the ephemeral timer system202are provided below.

The collection management system204furthermore includes a curation interface212that allows a collection manager to manage and curate a particular collection of content. For example, the curation interface212enables an event organizer to curate a collection of content relating to a specific event (e.g., delete inappropriate content or redundant messages). Additionally, the collection management system204employs machine vision (or image recognition technology) and content rules to automatically curate a content collection. In certain examples, compensation may be paid to a user for the inclusion of user-generated content into a collection. In such cases, the collection management system204operates to automatically make payments to such users for the use of their content.

In some examples, the augmentation system206provides a user-based publication platform that enables users to select a geolocation on a map and upload content associated with the selected geolocation. The user may also specify circumstances under which a particular media overlay should be offered to other users. The augmentation system206generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geolocation.

In other examples, the augmentation system206provides a merchant-based publication platform that enables merchants to select a particular media overlay associated with a geolocation via a bidding process. For example, the augmentation system206associates the media overlay of the highest bidding merchant with a corresponding geolocation for a predefined amount of time.

The map system208provides various geographic location functions, and supports the presentation of map-based media content and messages by the messaging client104. For example, the map system208enables the display of user icons or avatars (e.g., stored in profile data308) on a map to indicate a current or past location of “friends” of a user, as well as media content (e.g., collections of messages including photographs and videos) generated by such friends, within the context of a map. For example, a message posted by a user to the messaging system100from a specific geographic location may be displayed within the context of a map at that particular location to “friends” of a specific user on a map interface of the messaging client104. A user can furthermore share his or her location and status information (e.g., using an appropriate status avatar) with other users of the messaging system100via the messaging client104, with this location and status information being similarly displayed within the context of a map interface of the messaging client104to selected users.

The game system210provides various gaming functions within the context of the messaging client104. The messaging client104provides a game interface providing a list of available games (e.g., web-based games or web-based applications) that can be launched by a user within the context of the messaging client104, and played with other users of the messaging system100. The messaging system100further enables a particular user to invite other users to participate in the play of a specific game, by issuing invitations to such other users from the messaging client104. The messaging client104also supports both voice and text messaging (e.g., chats) within the context of gameplay, provides a leaderboard for the games, and also supports the provision of in-game rewards (e.g., coins and items).

Data Architecture

FIG. 3is a schematic diagram illustrating data structures300, which may be stored in the database120of the messaging server system108, according to certain examples. While the content of the database120is shown to comprise a number of tables, it will be appreciated that the data could be stored in other types of data structures (e.g., as an object-oriented database).

The database120includes message data stored within a message table302. This message data includes, for any one particular message, at least message sender data, message recipient (or receiver) data, and a payload. Further details regarding information that may be included in a message, and included within the message data stored in the message table302, is described below with reference toFIG. 4.

An entity table304stores entity data, and is linked (e.g., referentially) to an entity graph306and profile data308. Entities for which records are maintained within the entity table304may include individuals, corporate entities, organizations, objects, places, events, and so forth. Regardless of entity type, any entity regarding which the messaging server system108stores data may be a recognized entity. Each entity is provided with a unique identifier, as well as an entity type identifier (not shown).

The entity graph306stores information regarding relationships and associations between entities. Such relationships may be social, professional (e.g., work at a common corporation or organization), interested-based, or activity-based, merely for example.

The profile data308stores multiple types of profile data about a particular entity. The profile data308may be selectively used and presented to other users of the messaging system100, based on privacy settings specified by a particular entity. Where the entity is an individual, the profile data308includes, for example, a user name, telephone number, address, settings (e.g., notification and privacy settings), as well as a user-selected avatar representation (or collection of such avatar representations). A particular user may then selectively include one or more of these avatar representations within the content of messages communicated via the messaging system100, and on map interfaces displayed by messaging clients104to other users. The collection of avatar representations may include “status avatars,” which present a graphical representation of a status or activity that the user may select to communicate at a particular time.

The database120also stores augmentation data, such as overlays or filters, in an augmentation table310. The augmentation data is associated with and applied to videos (for which data is stored in a video table314) and images (for which data is stored in an image table316).

Another type of filter is a data filter, which may be selectively presented to a sending user by the messaging client104, based on other inputs or information gathered by the client device102during the message creation process. Examples of data filters include current temperature at a specific location, a current speed at which a sending user is traveling, battery life for a client device102, or the current time.

Other augmentation data that may be stored within the image table316includes augmented reality content items (e.g., corresponding to applying Lenses or augmented reality experiences). An augmented reality content item may be a real-time special effect and sound that may be added to an image or a video.

As described above, augmentation data includes augmented reality content items, overlays, image transformations, AR images, and similar terms that refer to modifications that may be applied to image data (e.g., videos or images). This includes real-time modifications, which modify an image as it is captured using device sensors (e.g., one or multiple cameras) of a client device102and then displayed on a screen of the client device102with the modifications. This also includes modifications to stored content, such as video clips in a gallery that may be modified. For example, in a client device102with access to multiple augmented reality content items, a user can use a single video clip with multiple augmented reality content items to see how the different augmented reality content items will modify the stored clip. For example, multiple augmented reality content items that apply different pseudorandom movement models can be applied to the same content by selecting different augmented reality content items for the content. Similarly, real-time video capture may be used with an illustrated modification to show how video images currently being captured by sensors of a client device102would modify the captured data. Such data may simply be displayed on the screen and not stored in memory, or the content captured by the device sensors may be recorded and stored in memory with or without the modifications (or both). In some systems, a preview feature can show how different augmented reality content items will look within different windows in a display at the same time. This can, for example, enable multiple windows with different pseudorandom animations to be viewed on a display at the same time.

As mentioned above, the video table314stores video data that, in one example, is associated with messages for which records are maintained within the message table302. Similarly, the image table316stores image data associated with messages for which message data is stored in the entity table304. The entity table304may associate various augmentations from the augmentation table310with various images and videos stored in the image table316and the video table314.

A map of object types to website presentation layers318stores a mapping that associates different object types defined in website generation data to corresponding website presentation layers128. The map of object types to website presentation layers318is used by a translator to identify and retrieve the corresponding website presentation layer318for a given object type that is identified and detected in website generation data retrieved from the content management system107. For example, the map of object types to website presentation layers318associates a first type of object, such as a button that is linked to another webpage, with a first website presentation layer that presents the button in a certain color and in a certain shape, such as an oval with a yellow background. The map of object types to website presentation layers318associates a second type of object, such as a button that causes an application to be downloaded with a second website presentation layer that presents the button in a different color and in a different shape, such as a square with a red background. The map of object types to website presentation layers318associates a third type of object, such as a static title of the webpage, with a third website presentation layer that presents the title in a certain color and in a certain font type and size.

Data Communications Architecture

FIG. 4is a schematic diagram illustrating a structure of a message400, according to some examples, generated by a messaging client104for communication to a further messaging client104or the messaging server114. The content of a particular message400is used to populate the message table302stored within the database120, accessible by the messaging server114. Similarly, the content of a message400is stored in memory as “in-transit” or “in-flight” data of the client device102or the application servers112. A message400is shown to include the following example components:message identifier402: a unique identifier that identifies the message400.message text payload404: text, to be generated by a user via a user interface of the client device102, and that is included in the message400.message image payload406: image data, captured by a camera component of a client device102or retrieved from a memory component of a client device102, and that is included in the message400. Image data for a sent or received message400may be stored in the image table316.message video payload408: video data, captured by a camera component or retrieved from a memory component of the client device102, and that is included in the message400. Video data for a sent or received message400may be stored in the video table314.message audio payload410: audio data, captured by a microphone or retrieved from a memory component of the client device102, and that is included in the message400.message augmentation data412: augmentation data (e.g., filters, stickers, or other annotations or enhancements) that represents augmentations to be applied to message image payload406, message video payload408, or message audio payload410of the message400. Augmentation data412for a sent or received message400may be stored in the augmentation table310.message duration parameter414: parameter value indicating, in seconds, the amount of time for which content of the message (e.g., the message image payload406, message video payload408, message audio payload410) is to be presented or made accessible to a user via the messaging client104.message geolocation parameter416: geolocation data (e.g., latitudinal and longitudinal coordinates) associated with the content payload of the message. Multiple message geolocation parameter416values may be included in the payload, each of these parameter values being associated with respect to content items included in the content (e.g., a specific image within the message image payload406, or a specific video in the message video payload408).message story identifier418: identifier values identifying one or more content collections (e.g., “stories” identified in the story table312) with which a particular content item in the message image payload406of the message400is associated. For example, multiple images within the message image payload406may each be associated with multiple content collections using identifier values.message tag420: each message400may be tagged with multiple tags, each of which is indicative of the subject matter of content included in the message payload. For example, where a particular image included in the message image payload406depicts an animal (e.g., a lion), a tag value may be included within the message tag420that is indicative of the relevant animal. Tag values may be generated manually, based on user input, or may be automatically generated using, for example, image recognition.message sender identifier422: an identifier (e.g., a messaging system identifier, email address, or device identifier) indicative of a user of the client device102on which the message400was generated and from which the message400was sent.message receiver identifier424: an identifier (e.g., a messaging system identifier, email address, or device identifier) indicative of a user of the client device102to which the message400is addressed.

The contents (e.g., values) of the various components of message400may be pointers to locations in tables within which content data values are stored. For example, an image value in the message image payload406may be a pointer to (or address of) a location within an image table316. Similarly, values within the message video payload408may point to data stored within a video table314, values stored within the message augmentation data412may point to data stored in an augmentation table310, values stored within the message story identifier418may point to data stored in a story table312, and values stored within the message sender identifier422and the message receiver identifier424may point to user records stored within an entity table304.

FIG. 5is a diagrammatic representation of a website generation system500, in accordance with some examples. Specifically, the website generation system500includes various storage repositories that may be associated with the same or different entities. Some of the storage repositories shown in website generation system500may be stored in content management system107and others may be stored in application servers112. In some implementations, all of the storage repositories shown in website generation system500may be stored in content management system107. In some implementations, all of the storage repositories shown in website generation system500may be stored in application servers112.

A second entity storage repository520may include various components for generating a website. The components include local react components526(also referred to herein as “website presentation layer”), translators527, references to react components522(also referred to herein as “website presentation layer”) stored in a first entity storage repository510and references to translators524stored in a common storage repository530. As an example, a third-party entity relative to the first entity (e.g., an entity that provides the messaging client104) may define the content and behavior of a given website and upload and store that data as website generation data in the second entity storage repository520. The content and behavior may utilize a data model that is common to generation of websites that is used by various entities to define various objects, such as buttons, text, and images that are presented on the website. The data model provides various data object types and specifies ways to define the different object types in website generation data.

The third-party entity may define the content and behavior of the given website without defining the presentation or visual aspects of the content. Namely, the third-party entity defines the content and behavior without specifying the look and feel of the content and behavior. In some cases, the third-party entity uses the data object types defined by the data model to cause a shared website presentation layer to be used to generate the look and feel of the data objects of the given website content. For example, the third-party entity may reference a first type of data object using the data model to cause a button to appear on the website with a look and feel defined by the first entity.

During rendering of the website on a client device102, the address of the common storage repository530is used by the website generation data stored in the second entity storage repository520to retrieve one or more translators524associated with the first entity. The translators524are then used to map the first type of data object to a corresponding website presentation layer. The website presentation layer522(e.g., a react component) is retrieved from the first entity storage repository510. The retrieved website presentation layer522generates code for providing the look and feel for the content of the first type of data object. For example, the website presentation layer522generates a portion of the webpage for rendering a button having a specified size, color, shape and font style and color for presenting text, image, or video of the content defined by the website generation data. Other types of data objects defined by the website generation data are similarly rendered for display on the webpage using the corresponding website presentation layer522identified by the translator524.

In some cases, the given entity may define some presentation layer, such as the look and feel, of some data objects that are not included in the website presentation layers522. For example, the given entity may define the look and feel for a specific type of button that is presented on the webpage. To do so, the given entity may define one or more translators527that map to a corresponding website presentation layer526that is also defined by the given entity. When the given website is rendered for display, the translators527detect an object type that is in the website generation data that is mapped to the website presentation layer526that was defined by the given entity. The website presentation layer526generates the code for displaying the object type with the look and feel defined by the given entity. In this way, some portions of the webpage that are displayed based on the website generation data provided by the given entity can be displayed according to the shared presentation layer defined by the first entity while other portions of the webpage are displayed according to the presentation layer defined by the given entity. By using the shared presentation layers provided by the first entity, the amount of time and resources needed to create and define a website are reduced as the look and feel of certain object types on the website need not be defined by the given entity. This also ensures that a webpage defined by the given entity for presentation on a website hosted by the first entity has a consistent look and feel as other webpages displayed on the website hosted by the first entity that may have been generated based on website generation data provided by other entities.

FIG. 6is another diagrammatic representation of a website generation system600, in accordance with some examples. Specifically, as shown inFIG. 6, website generation data610is retrieved from the content management system107. This website generation data610is processed, such as locally by a web browser implemented on the client device102or by the application servers112. For example, the web browser may access a particular website address. The website address may be hosted by application servers112and may instruct the application servers112to retrieve the website generation data corresponding to the address from the content management system107. The application servers112process the website generation data to detect and identify one or more object types defined by the website generation data. In some cases, the website generation data is provided by a third-party entity relative to the entity associated with the application servers112.

The application servers112access translators620that may be locally stored or stored on a remote database, such as on database120. The translators620map or determine the website presentation layers associated with each object type defined by the website generation data. Namely, the translators620access the react components630to map the object type to the corresponding website presentation layers. One or more website presentation layers128are retrieved and used to process the content of the website generation data for the corresponding object types to generate webpage code for presenting the object types with a specific look and feel. For example, a first object type may be presented with one look and feel that differs from the look and feel of a second object type. The webpage code is then provided by the application servers112to the web browser on the client device102for rendering the display of the webpage on the client device102.

FIG. 7shows an illustrative conversion700of the website generation data to code that is used to render a display of the website generation data using the website presentation layer defined by the first entity. Specifically, the website generation data provided by the second entity may define one or more object types using an JSON file710, as shown inFIG. 7. Namely, the object types are defined to include certain text, images, or videos without defining the look and feel of those text, images or videos. The translator and the website presentation layer processes the JSON file710and generates a JavaScript file720that defines the look and feel for the object types defined in the JSON file710. A web browser application processes the JavaScript file720to render a display of the object types using the look and feel defined by the website presentation layers.

In some implementations, after the given entity (e.g., the third-party relative to the first entity that provides the messaging client104) generates the website generation data, the look and feel of certain or all of the object types included in the website generation data is controlled by the first entity. In this way, at one point in time, the webpage corresponding to the website generation data has a first look and feel for the object types. At a later point in time, the first entity may update or change some of the website presentation layers of the object types included in the webpage. In this case, at the later point in time, the same content and behavior of the webpage has a different second look and feel for certain object types without the given entity having to make any changes to the website generation data. Any webpage that uses the website presentation layers provided by the first entity similarly is automatically updated to have the updated or changed look and feel defined by the first entity.

As an example, a second entity may define the object and behavior of a given webpage that is presented on a website hosted by the first entity. The look and feel of the webpage is controlled by the first entity.FIG. 8shows an illustrative webpage800that is rendered for display based on processing the website generation data provided by the second entity and using the website presentation layers provided by the first entity. The webpage is accessed using a first address810and includes a first object type820(e.g., a title) and a second object type830(e.g., a button). The first object type820is presented with a first look and feel that is defined by the first entity and the second object type820is presented with a second look and feel defined by the first entity. Specifically, the text using a font size, style and color of the first object type820is shown on the webpage800. The second entity only includes the text for the first object type820in the website generation data, and the presentation layer provided by the first entity for the first object type820determines the look and feel for the text in the website generation data.

As another example, the text, image or video is presented in a button with a font size, style, and color; and shape type of a plurality of shapes; and background color and size of the second object type830as shown on the webpage800. The second entity only includes the text, image or video for the second object type830in the website generation data, and the behavior (e.g., the link or address that is accessed if the second object type830is selected by the user), and the presentation layer provided by the first entity for the second object type830determines the look and feel for the text, image or video in the website generation data.

Another webpage900that is defined by a third entity or the first or second entity is shown inFIG. 9. The look and feel of the webpage900is controlled by the first entity. The webpage900is accessed using a second address910and includes a button920that corresponds to the second object type830shown inFIG. 8. Namely, both webpages800and900include a common object type (e.g., a button) for which the look and feel is determined by the presentation layer defined by the first entity. The third entity only includes the text, image or video for the second object type830in the website generation data, and the presentation layer provided by the first entity for the second object type830determines the look and feel for the button920in the website generation data. As shown, the look and feel for the button920presented on the second webpage900is the same as the look and feel of the button corresponding to the second object type830presented on the first webpage800. This is because both buttons are rendered using the shared presentation layer provided by the first entity. Neither the second nor the third entity needs to define the look and feel for the buttons presented on the webpages800and900. Namely, the button920on the second webpage900has the same shape, font style, size, and background color as the button corresponding to the second object type830presented on the first webpage800.

FIG. 10is a flowchart illustrating example operations of the website generation system in performing a process1000, according to example embodiments. The process1000may be embodied in computer-readable instructions for execution by one or more processors such that the operations of the process1000may be performed in part or in whole by the functional components of the content management system107; accordingly, the process1000is described below by way of example with reference thereto. However, in other embodiments at least some of the operations of the process1000may be deployed on various other hardware configurations, such as on application servers112. The operations in the process1000can be performed in any order, in parallel, or may be entirely skipped and omitted

At operation1001, a client device102retrieves from a content management system, website generation data. For example, a web browser application, implemented on the client device102, may specify an address from which a webpage is to be loaded. The address may instruct application servers112to retrieve website generation data from the content management system107.

At operation1002, the client device102or servers112identify a first type of object in the website generation data. For example, the servers112process the retrieved website generation data to identify a first type of object (e.g., a button) that is defined by the content and behavior of the website generation data.

At operation1003, the client device102or servers112obtains, from a centralized storage of a plurality of website presentation layers, a first website presentation layer corresponding to the first type of object. For example, the servers112obtain a translator from the content management system107or from a database120. The translator identifies the storage location or address of one or more website presentation layers128. The translator maps the first type of object to one of the website presentation layers128. The servers112obtain the website presentation layer128corresponding to the first type of object.

At operation1004, the client device102generates, for display on a webpage, a first display element corresponding to the first type of object according to a look and feel defined by the first presentation layer and having first content defined by the website generation data. For example, the servers112convert or generate code for displaying the webpage by processing the first type of object content (e.g., the text, image or video defined by the website generation data) using the obtained website presentation layer128. The code is provided to the web browser on the client device102(such as in response to receiving the request from the client device102for the webpage at the address specified by the client device102). The web browser presents the webpage in which various content types (defined by the content and behavior) defined by the website generation data stored on the content management system107are presented with a look and feel defined by the website presentation layers128corresponding to the content types.

Machine Architecture

FIG. 11is a diagrammatic representation of the machine1100within which instructions1108(e.g., software, a program, an application, an applet, an app, or other executable code) for causing the machine1100to perform any one or more of the methodologies discussed herein may be executed. For example, the instructions1108may cause the machine1100to execute any one or more of the methods described herein. The instructions1108transform the general, non-programmed machine1100into a particular machine1100programmed to carry out the described and illustrated functions in the manner described. The machine1100may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine1100may operate in the capacity of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine1100may comprise, but not be limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular telephone, a smartphone, a mobile device, a wearable device (e.g., a smartwatch), a smart home device (e.g., a smart appliance), other smart devices, a web appliance, a network router, a network switch, a network bridge, or any machine capable of executing the instructions1108, sequentially or otherwise, that specify actions to be taken by the machine1100. Further, while only a single machine1100is illustrated, the term “machine” shall also be taken to include a collection of machines that individually or jointly execute the instructions1108to perform any one or more of the methodologies discussed herein. The machine1100, for example, may comprise the client device102or any one of a number of server devices forming part of the messaging server system108. In some examples, the machine1100may also comprise both client and server systems, with certain operations of a particular method or algorithm being performed on the server-side and with certain operations of the particular method or algorithm being performed on the client-side.

The machine1100may include processors1102, memory1104, and input/output (I/O) components1138, which may be configured to communicate with each other via a bus1140. In an example, the processors1102(e.g., a Central Processing Unit (CPU), a Reduced Instruction Set Computing (RISC) Processor, a Complex Instruction Set Computing (CISC) Processor, a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Radio-Frequency Integrated Circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor1106and a processor1110that execute the instructions1108. The term “processor” is intended to include multi-core processors that may comprise two or more independent processors (sometimes referred to as “cores”) that may execute instructions contemporaneously. AlthoughFIG. 11shows multiple processors1102, the machine1100may include a single processor with a single-core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiples cores, or any combination thereof.

The memory1104includes a main memory1112, a static memory1114, and a storage unit1116, all accessible to the processors1102via the bus1140. The main memory1104, the static memory1114, and the storage unit1116store the instructions1108embodying any one or more of the methodologies or functions described herein. The instructions1108may also reside, completely or partially, within the main memory1112, within the static memory1114, within machine-readable medium1118within the storage unit1116, within at least one of the processors1102(e.g., within the processor's cache memory), or any suitable combination thereof, during execution thereof by the machine1100.

In further examples, the I/O components1138may include biometric components1128, motion components1130, environmental components1132, or position components1134, among a wide array of other components. For example, the biometric components1128include components to detect expressions (e.g., hand expressions, facial expressions, vocal expressions, body gestures, or eye-tracking), measure biosignals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identify a person (e.g., voice identification, retinal identification, facial identification, fingerprint identification, or electroencephalogram-based identification), and the like. The motion components1130include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope).

With respect to cameras, the client device102may have a camera system comprising, for example, front cameras on a front surface of the client device102and rear cameras on a rear surface of the client device102. The front cameras may, for example, be used to capture still images and video of a user of the client device102(e.g., “selfies”), which may then be augmented with augmentation data (e.g., filters) described above. The rear cameras may, for example, be used to capture still images and videos in a more traditional camera mode, with these images similarly being augmented with augmentation data. In addition to front and rear cameras, the client device102may also include a 360° camera for capturing 360° photographs and videos.

Communication may be implemented using a wide variety of technologies. The I/O components1138further include communication components1136operable to couple the machine1100to a network1120or devices1122via respective coupling or connections. For example, the communication components1136may include a network interface component or another suitable device to interface with the network1120. In further examples, the communication components1136may include wired communication components, wireless communication components, cellular communication components, Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components to provide communication via other modalities. The devices1122may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a USB).

The various memories (e.g., main memory1112, static memory1114, and memory of the processors1102) and storage unit1116may store one or more sets of instructions and data structures (e.g., software) embodying or used by any one or more of the methodologies or functions described herein. These instructions (e.g., the instructions1108), when executed by processors1102, cause various operations to implement the disclosed examples.

The instructions1108may be transmitted or received over the network1120, using a transmission medium, via a network interface device (e.g., a network interface component included in the communication components1136) and using any one of several well-known transfer protocols (e.g., hypertext transfer protocol (HTTP)). Similarly, the instructions1108may be transmitted or received using a transmission medium via a coupling (e.g., a peer-to-peer coupling) to the devices1122.

Software Architecture

FIG. 12is a block diagram1200illustrating a software architecture1204, which can be installed on any one or more of the devices described herein. The software architecture1204is supported by hardware such as a machine1202that includes processors1220, memory1226, and I/O components1238. In this example, the software architecture1204can be conceptualized as a stack of layers, where each layer provides a particular functionality. The software architecture1204includes layers such as an operating system1212, libraries1210, frameworks1208, and applications1206. Operationally, the applications1206invoke API calls1250through the software stack and receive messages1252in response to the API calls1250.

The operating system1212manages hardware resources and provides common services. The operating system1212includes, for example, a kernel1214, services1216, and drivers1222. The kernel1214acts as an abstraction layer between the hardware and the other software layers. For example, the kernel1214provides memory management, processor management (e.g., scheduling), component management, networking, and security settings, among other functionality. The services1216can provide other common services for the other software layers. The drivers1222are responsible for controlling or interfacing with the underlying hardware. For instance, the drivers1222can include display drivers, camera drivers, BLUETOOTH® or BLUETOOTH® Low Energy drivers, flash memory drivers, serial communication drivers (e.g., USB drivers), WI-FI® drivers, audio drivers, power management drivers, and so forth.

The libraries1210provide a common low-level infrastructure used by the applications1206. The libraries1210can include system libraries1218(e.g., C standard library) that provide functions such as memory allocation functions, string manipulation functions, mathematic functions, and the like. In addition, the libraries1210can include API libraries1224such as media libraries (e.g., libraries to support presentation and manipulation of various media formats such as Moving Picture Experts Group-4 (MPEG4), Advanced Video Coding (H.264 or AVC), Moving Picture Experts Group Layer-3 (MP3), Advanced Audio Coding (AAC), Adaptive Multi-Rate (AMR) audio codec, Joint Photographic Experts Group (JPEG or JPG), or Portable Network Graphics (PNG)), graphics libraries (e.g., an OpenGL framework used to render in two dimensions (2D) and three dimensions (3D) in a graphic content on a display), database libraries (e.g., SQLite to provide various relational database functions), web libraries (e.g., WebKit to provide web browsing functionality), and the like. The libraries1210can also include a wide variety of other libraries1228to provide many other APIs to the applications1206.

The frameworks1208provide a common high-level infrastructure that is used by the applications1206. For example, the frameworks1208provide various graphical user interface (GUI) functions, high-level resource management, and high-level location services. The frameworks1208can provide a broad spectrum of other APIs that can be used by the applications1206, some of which may be specific to a particular operating system or platform.

In an example, the applications1206may include a home application1236, a contacts application1230, a browser application1232, a book reader application1234, a location application1242, a media application1244, a messaging application1246, a game application1248, and a broad assortment of other applications such as a third-party application1240. The applications1206are programs that execute functions defined in the programs. Various programming languages can be employed to create one or more of the applications1206, structured in a variety of manners, such as object-oriented programming languages (e.g., Objective-C, Java, or C++) or procedural programming languages (e.g., C or assembly language). In a specific example, the third-party application1240(e.g., an application developed using the ANDROID™ or IOS™ software development kit (SDK) by an entity other than the vendor of the particular platform) may be mobile software running on a mobile operating system such as IOS™, ANDROID™, WINDOWS® Phone, or another mobile operating system. In this example, the third-party application1240can invoke the API calls1250provided by the operating system1212to facilitate functionality described herein.

Glossary

“Component” refers to a device, physical entity, or logic having boundaries defined by function or subroutine calls, branch points, APIs, or other technologies that provide for the partitioning or modularization of particular processing or control functions. Components may be combined via their interfaces with other components to carry out a machine process. A component may be a packaged functional hardware unit designed for use with other components and a part of a program that usually performs a particular function of related functions.

Components may constitute either software components (e.g., code embodied on a machine-readable medium) or hardware components. A “hardware component” is a tangible unit capable of performing certain operations and may be configured or arranged in a certain physical manner. In various example embodiments, one or more computer systems (e.g., a standalone computer system, a client computer system, or a server computer system) or one or more hardware components of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or application portion) as a hardware component that operates to perform certain operations as described herein.

Considering embodiments in which hardware components are temporarily configured (e.g., programmed), each of the hardware components need not be configured or instantiated at any one instance in time. For example, where a hardware component comprises a general-purpose processor configured by software to become a special-purpose processor, the general-purpose processor may be configured as respectively different special-purpose processors (e.g., comprising different hardware components) at different times. Software accordingly configures a particular processor or processors, for example, to constitute a particular hardware component at one instance of time and to constitute a different hardware component at a different instance of time.