Systems and methods for content creation based on audience preferences and context factors
The system addresses the challenge of creating content that aligns with audience preferences and contextual factors by generating content templates based on received audience and context parameters, resulting in efficient and effective content creation.
Patent Information
- Application Number
- JP2024566616
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-01-19
- Filing Date
- 2023-05-09
- Publication Date
- 2025-05-30
AI Technical Summary
Business experts face challenges in creating content that aligns with audience preferences and contextual factors, leading to cumbersome and time-consuming presentation construction, lack of standardization, and mismatch between presenter preferences and audience needs.
A method and system for creating content templates that involve receiving audience and context parameters, determining a content storyline, and generating a template based on these parameters, ensuring the content is tailored to the target audience's preferences and the context of the content.
The solution enables efficient creation of content templates that resonate with the target audience, reducing the time and effort required for content creation while ensuring consistency and alignment with audience preferences and contextual factors.
Smart Images

Figure 2025516652000001_ABST
Abstract
Description
Technical Field
[0001] (Cross - Reference to Related Applications) This application claims the priority and benefit of U.S. Patent Application No. 18 / 156,649, filed on January 19, 2023, and U.S. Provisional Patent Application No. 63 / 339,827, filed on May 9, 2022, both entitled "SYSTEMS AND METHODS FOR CONTENT CREATION BASED ON AUDIENCE PREFERENCE AND CONTEXTUAL FACTORS", the entire contents of each of which are incorporated herein by reference.
[0002] This specification relates to content creation, and more particularly, to content creation based on audience preference and contextual factors.
Background Art
[0003] Business experts often create content to communicate with a target audience. For example, such experts may give presentations to an audience to pitch ideas, report research findings, or provide knowledge about a particular topic. However, these presentations can take hours to construct and refine, and can be cumbersome to put together manually. In many cases, experts and their teams find it difficult to standardize content, distribute presentations, and establish a common language. Additionally, presentations or content are often developed based on the presenter's preferences rather than the audience's preferences.
Summary of the Invention
Means for Solving the Problems
[0004] At least one aspect of the present disclosure is directed to a method for creating a template for content. The method includes receiving at least one audience parameter representing at least one preference of a target audience when receiving content, receiving at least one context parameter representing the context of the content, determining a content storyline based on the at least one audience parameter and the at least one context parameter, and generating a content template based on the content storyline.
[0005] In one embodiment, the target audience is a single individual. In some embodiments, the target audience is two or more individuals. In various embodiments, the at least one audience parameter represents one or more of the target audience's image preferences, color preferences, illustration preferences, presentation preferences regarding logical discourse, presentation preferences regarding data, and preferences regarding visualizing data. In one embodiment, the method includes presenting at least one preference inquiry to the target audience, deriving at least one preference of the target audience when receiving content based on the response to the at least one preference inquiry, and generating at least one preference fingerprint regarding the target audience based on the at least one preference of the target audience.
[0006] In some embodiments, the at least one preference fingerprint includes the at least one audience parameter. In one embodiment, the at least one context parameter corresponds to one or more of the type, purpose, and goal of the content. In one embodiment, the content storyline corresponds to one or more of the sequence, order, and flow of the content. In various embodiments, the method includes selecting a style profile based on the at least one audience parameter and the at least one context parameter.
[0007] In one embodiment, the step of generating a content template includes generating a content template based on a content storyline and a style profile. In some embodiments, the style profile corresponds to one or more of a content theme, a font theme, a color theme, and an arrangement theme of the content. In various embodiments, the content is a presentation and the content template corresponds to a slide deck for the presentation. In one embodiment, the method includes exporting the content template to at least one content editing application.
[0008] Another aspect of the present disclosure is directed to a system for creating a template for content. The system includes at least one memory for storing computer-executable instructions and at least one processor for executing the instructions stored on the memory. Execution of the instructions programs at least one processor to perform operations including receiving at least one audience parameter representing at least one preference of a target audience when receiving content, receiving at least one context parameter representing a context of the content, determining a content storyline based on the at least one audience parameter and the at least one context parameter, and generating a content template based on the content storyline.
[0009] In one embodiment, the target audience is a single individual. In some embodiments, the target audience is two or more individuals. In various embodiments, at least one audience parameter represents one or more of the target audience's image preferences, color preferences, illustration preferences, presentation preferences regarding logical discourse, presentation preferences regarding data, and preferences regarding visualizing data. In one embodiment, executing the instructions includes presenting at least one preference query to the target audience, deriving at least one preference of the target audience when receiving content based on responses to the at least one preference query, and generating at least one preference fingerprint regarding the target audience based on the at least one preference of the target audience, and programming at least one processor to perform operations including these steps.
[0010] In some embodiments, at least one preference fingerprint includes at least one audience parameter. In one embodiment, at least one context parameter corresponds to one or more of the type, purpose, and goal of the content. In one embodiment, a content storyline corresponds to one or more of the sequence, order, and flow of the content. In various embodiments, executing the instructions includes programming at least one processor to perform operations including selecting a style profile based on at least one audience parameter and at least one context parameter.
[0011] In one embodiment, the step of generating a content template includes generating a content template based on a content storyline and a style profile. In some embodiments, the style profile corresponds to one or more of a content theme, a font theme, a color theme, and an arrangement theme of the content. In various embodiments, the content is a presentation, and the content template corresponds to a slide deck for the presentation. In one embodiment, executing the instructions programs at least one processor to perform operations including exporting the content template to at least one content editing application.
Brief Description of the Drawings
[0012]
Figure 1
Figure 2
Figure 3A
Figure 3B
Figure 3C
Figure 3D
Figure 3E
Figure 3F
Figure 4
Figure 5
Figure 6
Figure 7
Figure 8
Figure 9
Figure 10
Figure 11
DETAILED DESCRIPTION OF THE INVENTION
[0013] Detailed Description As described above, business experts often create content to communicate with a target audience. For example, such experts may present to an audience to pitch an idea, report research findings, or provide knowledge about a particular topic. However, these presentations can take hours to build and refine, and it can be tedious to compile them manually. In many cases, experts and their teams find it difficult to standardize content, distribute presentations, and establish a common language. Additionally, presentations or content are often developed based on the preferences of the presenter rather than the preferences of the audience.
[0014] Accordingly, a system and method for creating content templates based on audience preferences and context factors are provided herein. In at least one embodiment, a content storyline is generated based on parameters of a target audience and the context of the content. In one example, the parameters of the target audience correspond to the preference fingerprints of audience members. In some embodiments, a style profile is selected or created for a content template based on parameters of the target audience, the context of the content, and the storyline.
[0015] FIG. 1 is a block diagram of a system 100 for creating a content template according to aspects described herein. In one embodiment, system 100 is implemented by an application server 102. Application server 102 provides functionality for creating and providing one or more content templates. Application server 102 may be deployed, for example, in one or more data centers (not shown) at one or more geographical locations and includes software components and a database. The software components of application server 102 may include a fingerprint engine 106, a context engine 107, an outline engine 108, a style engine 109, and a user interface (UI) engine 110. The software components may include sub-components that may be executed on the same or different individual data processing devices. The database of application server 102 may include an application database 112a and a user database 112b. The database may reside within one or more physical storage systems. Exemplary features of the software components and data processing devices will be further described below.
[0016] Application server 102 is configured to transmit and receive data to and from a user's client device (e.g., user device 116) through one or more data communication networks 104 such as the Internet. The user can access the user interface of client application 118. In some embodiments, client application 118 is configured to be launched in a web browser or a special purpose software application running on user device 116.
[0017] Although this application will describe many functions as being performed by application server 102, in various implementations, some or all of the functions performed by application server 102 may be performed locally by a client application (e.g., client application 118). Client application 118 can communicate with application server 102 via network 104 using, for example, the Hypertext Transfer Protocol (HTTP), another standard protocol, or a proprietary protocol. User device 116 can be a mobile phone, smartwatch, tablet computer, personal computer, or game console. Other types of user devices are also possible.
[0018] In various implementations, system 100 can enable the creation of content templates associated with different types of content. In one embodiment, fingerprint engine 106 of application server 102 is configured to generate a fingerprint for each user. The fingerprint of each user represents the user's preferences when receiving or viewing content. In other words, the fingerprint represents the user's preferences when the user is the target audience (or within the target audience) for the content. In some embodiments, fingerprint engine 106 is configured to collect data from the user (e.g., via client application 118) and generate a fingerprint. Fingerprint engine 106 may store the fingerprint of each user in user database 112b.
[0019] The context engine 107 is configured to manage the context of content templates and corresponding content. In one embodiment, the context engine 107 collects information from a user who creates a content template (e.g., via the client application 118) and determines the context of the content. In some embodiments, the context includes the type, purpose, and / or goal of the content. For example, if the content is a presentation, the context may represent the type or tone of the presentation. In some embodiments, the application database 112a includes a library of context information accessed by the context engine 107. The context engine 107 may be configured to store context information regarding the content template within the application database 112a.
[0020] The outline engine 108 is configured to generate an outline (or story line) regarding the content template. The outline may correspond to the sequence, order, and / or flow of the content template. For example, if the content is a presentation, the outline may represent the type, number, and / or order of the slides in the slide show. In some embodiments, the application database 112a includes an outline library (e.g., a slide library) accessed by the outline engine 108. The outline engine 108 may be configured to store an outline (or story line) regarding the content template within the application database 112a.
[0021] The style engine 109 is configured to generate a style profile for a content template. In one embodiment, the style profile includes one or more stylistic attributes of the content template and / or the content. For example, the style profile may include one or more of a template theme, a font theme, a color theme, and an arrangement theme. In some embodiments, the template theme represents the stylistic preferences (e.g., graphics, logo, etc.) of a company or organization associated with the target audience of the content. The font theme may represent one or more font attributes (e.g., type, size, color, etc.) included within the content template and / or to be used for the generation of the content in a content editing tool. The color theme may represent one or more colors (or color schemes) included within the content template and / or to be used for the generation of the content. The arrangement theme may represent one or more approaches or techniques for presenting information (e.g., data, ideas, concepts, plans, etc.) included within the content template and / or to be used for the generation of the content.
[0022] In one embodiment, the style profile selected or created by the style engine 109 includes a working area for the content template. The working area may correspond to the area or region of a presentation slide where the content is located. In some embodiments, the location and / or size of the working area may be determined by the style profile. The style profile may also include a node count used to create various diagrams included within the content template (or the content). For example, the node count may define the number of nodes (e.g., boxes) included within a flowchart or flow diagram.
[0023] In some embodiments, the application database 112a includes a library of stylistic resources (e.g., fonts, colors, graphics, charts, tables, etc.) that are accessed by the style engine 109 to generate style profiles. In some embodiments, the style engine 109 may receive an uploaded presentation and extract various stylistic attributes. For example, a presentation associated with a particular company or organization may be provided to the style engine 109 to generate a corresponding style profile. In some embodiments, the style engine 109 may analyze an uploaded presentation and create (or find) a style profile that matches the stylistic attributes of the company or organization. In some embodiments, the style engine 109 may analyze XML data associated with an uploaded presentation and identify corresponding stylistic attributes. The style engine 109 may be configured to store each style profile within the application database 112a.
[0024] In one embodiment, the UI engine 110 is configured to manage the UI of the client application 118. For example, the UI engine 110 may collect or gather information from a user (e.g., a content template creator) via the client application 118. In some embodiments, the UI engine 110 provides the collected information to the engines 106 - 109 and / or stores the collected information in the databases 112a, 112b. Similarly, the UI engine 110 may provide and present information from the engines 106 - 109 or the databases 112a, 112b to the user via the client application 118. In some embodiments, the UI engine 110 provides an export service that enables content templates to be exported in various formats (e.g., PDF, Microsoft Word, Microsoft PowerPoint, etc.). In some embodiments, the UI engine 102 is configured to provide additional services such as user login, user account settings, user account management, etc.
[0025] FIG. 2 is an exemplary view 200 of the client application 118 according to aspects described herein. In one embodiment, the view 200 corresponds to the home screen of the client application 118. FIG. 2 and other figures presenting the user interface in this application include icons and labels and refer to various features (e.g., search, account, notifications, etc.) displayed by the user interface. Such icons and labels will be used to reference and describe such features in this application, but the features may be presented similarly using different icons and labels.
[0026] As shown, the client application 118 includes a new presentation button 202 that enables a user (e.g., a content template creator) to create a new presentation template. In one embodiment, the client application 118 includes a presentation button 204 that enables the user to view previously created templates. The client application 118 may include a slide button 206 that enables the user to view, download, and / or modify a plurality of presentation slides (e.g., within the slide library of the application database 112a). In one embodiment, the client application 118 includes a user button 208 that enables the user to manage various settings associated with the user account and / or the system 100. In some embodiments, the client application 118 includes a search bar 210 that provides a search function that enables the user to search for specific slides (e.g., from the slide library) and / or specific users (e.g., potential audience members).
[0027] After creating a user account, the user may be prompted by the client application 118 to generate a fingerprint. In other embodiments, the user may initiate the fingerprint process via the user button 208 to create a new fingerprint or modify / update an existing fingerprint. In some embodiments, the user may be able to generate a fingerprint for someone other than themselves (e.g., a member of the same company as the user, a friend of the user, etc.).
[0028] Figure 3A is an exemplary view 300 of client application 118 according to aspects described herein. In one embodiment, view 300 corresponds to the initiation of a fingerprint generation process. In some embodiments, the fingerprint generation process is configured to determine a user's visual preferences, story selection (e.g., storyline) preferences, and data style preferences when browsing or receiving content. The user may select a "Discover My Fingerprint" button 312 to initiate the fingerprint generation process.
[0029] In some embodiments, the fingerprint generation process includes the step of presenting a plurality of questions (or queries) to the user. For example, Figure 3B illustrates a view 320 of client application 118 for determining a user's image preference. View 320 includes a first question 322 presented to the user (e.g., "Which slide do you prefer?"). In some embodiments, an explanation is provided with the first question 322 to provide context to the user (e.g., "This will help understand your image preference"). At least two options are presented to the user for selection in response to the first question 322. In some embodiments, the user may select one option, however, in other embodiments, the user may select more than one option. In the illustrated embodiment, a first option 324a and a second option 324b are presented to the user for selection. In one embodiment, options 324a, 324b correspond to exemplary presentation slides. In some embodiments, the user may select an option by clicking (or tapping) directly on the option. Alternatively, the user may select an option by selecting a button or other UI element.
[0030] The fingerprint generation process may continue by presenting additional questions (or queries) to the user. For example, FIG. 3C illustrates a view 330 of a client application 118 for determining a user's presentation preference regarding a logical discourse. The view 330 includes a second question 332 presented to the user (e.g., "Which slide makes for a better argument?"). In some embodiments, an explanation is provided along with the second question 332 to provide context to the user (e.g., "This will help us understand your preferences regarding logical discourse"). At least two options are presented to the user for selection in response to the second question 332. In some embodiments, the user may select one option, however, in other embodiments, the user may select more than one option. In the illustrated embodiment, a first option 334a and a second option 334b are presented to the user for selection.
[0031] Similarly, FIG. 3D illustrates a view 340 of a client application 118 for determining a user's data presentation preference. The view 340 includes a third question 342 presented to the user (e.g., "Which slide is more persuasive to you?"). In some embodiments, an explanation is provided along with the third question 342 to provide context to the user (e.g., "This selection will help us learn your data preferences"). At least two options are presented to the user for selection in response to the third question 342. In some embodiments, the user may select one option, however, in other embodiments, the user may select more than one option. In the illustrated embodiment, a first option 344a and a second option 344b are presented to the user for selection.
[0032] Figure 3E illustrates a view 350 of the client application 118 for determining the user's top (or most important) preferences. The view 350 includes a fourth question 352 presented to the user (e.g., "When someone else presents to you, what are some of your top preferences that they should know?"). In some embodiments, an explanation is provided with the fourth question 352 to provide context to the user (e.g., "To share this information with your colleagues, they can build a presentation that you'll love!"). A plurality of preference options 354 are presented to the user for selection in response to the third question 352. In one embodiment, the preference options 354 represent the user's "pet peeves". In some embodiments, the options included within the plurality of preference options 354 correspond to the top (or most popular) options of all users (or a subset of users) across the platform. For example, the fingerprint engine 106 may be configured to monitor and analyze the top preferences of users across the platform and derive the plurality of preference options 354. In some embodiments, the user may be able to select one or more of the options 354. In some embodiments, the user may select the option 356 to provide their own unique, specific preferences (e.g., write or type).
[0033] Four exemplary questions 322, 332, 342, and 352 are described above, but it should be understood that the fingerprint generation process can include any number of questions or inquiries. For example, the fingerprint generation process may include questions targeting a user's image preferences, color preferences, illustration preferences, logical discourse preferences, data preferences, data visualization preferences, or any other type of relevant preferences. In some embodiments, various options (e.g., 324a, 324b, etc.) can be presented to the user with minimal context (e.g., "Which slide do you prefer?"). In some embodiments, the questions and / or corresponding options may be presented in different formats (e.g., text only, video, etc.). Additionally, more than two options can be presented with each question.
[0034] Once all the questions (or inquiries) are presented, the fingerprint engine 106 is configured to generate a fingerprint for the user based on the user's selections (or inputs). In some embodiments, the fingerprint engine 106 uses one or more algorithms to generate the fingerprint. In some embodiments, the fingerprint engine 106 uses one or more lookup tables (e.g., stored within the application database 112b) to generate the fingerprint. In some embodiments, the fingerprint engine 106 includes a machine learning model to generate the fingerprint. Generally, any suitable machine learning technique can be used, such as, for example, gradient boosting, random forest, regression, neural network, decision tree, support vector machine, Bayesian network, other types of techniques, etc.
[0035] In one example, a fingerprint represents a user's visual preferences, story selection (e.g., storyline) preferences, data style preferences, and other personal preferences. In some examples, a fingerprint may indicate one or more characteristics of a user. For example, FIG. 3F illustrates a view 360 of a client application 118 corresponding to a user fingerprint. In one example, the fingerprint is classified as a fingerprint type 362 (e.g., "Doer"). The fingerprint type 362 may be selected by a fingerprint engine 106 from a plurality of fingerprint types such as, for example, architect, director, navigator, doer, producer, scholar, scientist, and surgeon. In some examples, the fingerprint type 362 has a corresponding symbol 364. In some examples, the fingerprint type 362 is selected based on one or more fingerprint attributes 366. In the illustrated example, the user has a "vivid" visual preference attribute 366a described as "accepts bold images and colors", a "deductive" story selection attribute 366b described as "logic and facts first, listening second", and a "story" data style attribute 366c described as "supplements the discourse with data". In some examples, a fingerprint includes a user's personal preferences 368. For example, the personal preferences 368 may correspond to a user's selection from a plurality of preference options 354 and / or user-provided preferences. In some examples, a per-user fingerprint is stored within a user database 112b.
[0036] In some embodiments, the fingerprint engine 106 can process and analyze existing content (e.g., a slide show presentation) to derive a fingerprint. For example, a user may upload an exemplary presentation via the client application 118. The fingerprint engine 106 can analyze the presentation and extract the user's visual preferences, story selection preferences, data style preferences, and other personal preferences. In such embodiments, the fingerprint engine 106 may include a topic model (e.g., a Latent Dirichlet Allocation (LDA) model) to process and analyze the user-provided content. In some embodiments, the fingerprint engine 109 may be configured to process and analyze XML data associated with the user-provided content.
[0037] In one embodiment, the system 100 uses a user-specific fingerprint to create a content template tailored to a target audience. FIG. 4 is a flowchart of a method 400 for creating a content template according to aspects described herein. In some embodiments, the method 400 corresponds to processes performed by the application server 102 and the client application 118.
[0038] In step 402, the fingerprint engine 106 receives at least one target audience parameter. In this context, a "target audience" corresponds to the intended or expected audience for which a content template is being used to deliver content. In one embodiment, the at least one target audience parameter includes the names of the members in the target audience. In some embodiments, the at least one target audience parameter includes the name of a group, team, club, organization, company, or another type of group that includes one or more individuals. In some embodiments, the at least one target audience parameter includes at least one fingerprint type (e.g., architect, surgeon, etc.). In some embodiments, the fingerprint engine 106 is configured to access, read, or download the corresponding user fingerprint from the application database 112a.
[0039] In one embodiment, the target audience parameter is provided from the client application 118 to the fingerprint engine 106. The client application 118 may be configured to collect various parameters from the user creating the content template. For example, FIG. 5 illustrates a view 500 of the client application 118 for collecting template information from the user. In one embodiment, a text entry box is provided to allow the user to enter a title 502 regarding the content template (or content). The client application 118 may provide the title 502 to the fingerprint 106 or another engine of the application server 102 (e.g., the context engine 107).
[0040] In some embodiments, a search function is provided such that a user can add one or more audience members 504 to a target audience. In other embodiments, a drop-down menu or other UI element may be provided for the user to add audience members. In some embodiments, the user can add an individual who is a user of the platform (e.g., has a fingerprint). In some embodiments, the user can add an individual who is not a member of the platform (e.g., does not have a fingerprint). The user may be prompted to provide contact information (e.g., an email address) for each non-member so that an invitation or fingerprint inquiry can be sent. In some embodiments, the client application 118 is configured to provide one or more audience members 504 to the fingerprint engine 106 as at least one audience parameter.
[0041] In step 404, the context engine 107 receives at least one context parameter. In one embodiment, "context" corresponds to the intended type, purpose, and / or goal of the content for which the content template is created. In some embodiments, the "context" of the content corresponds to the tone of the content (e.g., good news, bad news, etc.). In one embodiment, the at least one context parameter includes a content type. For example, if the content is a presentation, the content type may be one of an all-hands meeting, board meeting, brand performance review, brand plan, budget overview, business case, business plan, communication plan, company introduction, corporate policy, competitor analysis, corporate responsibility update, customer deep dive, customer onboarding, customer pitch, employee performance review, financial performance, forecast update, market entry strategy, internal audit update, investor pitch, IT deep dive, journey line, knowledge transfer, leadership meeting, leadership review, M&A proposal, manager meeting, market research results, monthly review, new employee orientation, new market entry, operations deep dive, organizational update, partner deep dive, portfolio review, pricing plan, product development plan, product launch plan, product performance review, project update, purchase decision, R&D research results, recruitment update, request for proposal, rewards and recognition, product demonstration sales, salesperson contest, staff meeting, staff placement update, operations committee meeting, strategic plan, tactical plan, team meeting, town hall, training materials, webinar, or any other suitable presentation type.
[0042] In one embodiment, the context parameter is provided from the client application 118 to the context engine 107. For example, as shown in FIG. 5, a drop-down menu is provided such that the user can select a content type 506 regarding the content template. In other embodiments, a search function or other UI elements may be provided for the user to select the content type 506. In some embodiments, the client application 118 is configured to provide the selected content type 506 to the context engine 107 as at least one context parameter. In one embodiment, the content type displayed to the user is provided by the UI engine 110. The context engine 107 may be configured to maintain and / or update a list of content types and provide the refreshed content type list to the UI engine 110. In some embodiments, the user may upload or create their own custom content types. These custom content types may be stored in the application database 112a or the user database 112b. In some embodiments, the custom content types are "private" and may be displayed only to one or more users (e.g., the creating user, users in the same organization, etc.). In some embodiments, the custom content types are "public" and may be shared with all users once created.
[0043] In step 406, the outline engine 108 generates an outline (or story line) regarding the content template. In one embodiment, the outline engine 108 is configured to generate a story line based on at least one audience parameter and at least one context parameter. For example, the fingerprint engine 106 may provide at least one audience parameter and / or the corresponding user fingerprint to the outline engine 108. Similarly, the context engine 107 may provide at least one context parameter to the outline engine 108. In one embodiment, the outline engine 108 generates a story line that is optimized for the content type (e.g., all-hands meeting, brand plan, etc.) and the preferences of the target audience members (e.g., fingerprint).
[0044] In some embodiments, the outline engine 108 is configured to generate a story line that includes a plurality of segments. Each segment of the plurality of segments may include one or more content items (e.g., slides). FIG. 6 illustrates a view 600 of a client application 118 for displaying a presentation story line generated by the outline engine 108. In one embodiment, the story line includes a plurality of segments 602. For example, a first segment 602a represents the "beginning" of the presentation, a second segment 602b represents the "middle" of the presentation, and a third segment 602c represents the "end" of the presentation. It should be understood that in other embodiments, the story line may include more or fewer segments and / or different types of segments. As shown, each segment 602 includes a set of slides. For example, the first segment 602a includes a first set of slides (e.g., title, agenda, executive summary, vision, goals, and team), the second segment 602b includes a second set of slides (e.g., strategy, success factors, insights, messages, recommendations), and the third segment 602c includes a third set of slides (e.g., milestones, future plans). In some embodiments, each segment 602 includes a unique set of slides. In other words, each slide type (e.g., insight, message, etc.) is included in only one of the segments. In other embodiments, each slide type can be used multiple times throughout the presentation. For example, the first and third segments 602a, 602c may each include an "insight" slide.
[0045] In some embodiments, the user can modify the generated storyline. For example, the user may change the slide order within each segment 602 and adjust the order generated by the outline engine 108. Similarly, the user can drag and drop slides and move slides between different segments. In some embodiments, the user can delete or remove slides added by the outline engine 108. Additionally, the user may add slides that were not included in the storyline generated by the outline engine 108. For example, the user may drag and drop a slide from the idea gallery 604. In some embodiments, the idea gallery 604 includes a search function that enables the user to search for new slides to add.
[0046] In some embodiments, rather than providing a storyline, the outline engine 108 may provide a list of slides based on at least one audience parameter and at least one context parameter. For example, when the "custom" content type is selected, the outline engine may provide a list of slides that the user can then compose and / or modify the storyline by themselves. In some embodiments, the user can save the storyline as a custom storyline.
[0047] In step 408, the style engine 109 selects (or creates) a style profile for the content template. In one embodiment, the style engine 109 is configured to select (or create) a style profile based on at least one audience parameter (e.g., user fingerprint), at least one context parameter, and the content template storyline. For example, the user fingerprint can be used to determine image preferences, color preferences, illustration preferences, presentation preferences for logical discourse, presentation preferences for data, and / or preferences for visualizing data for each member of the audience composition. As described above, the style profile includes one or more style attributes of the content template and / or the content. In one embodiment, the style engine 109 is configured to select a pre-rendered style profile from a plurality of style profiles (e.g., a style profile library stored in the application database 112a). In some embodiments, the style engine 109 is configured to create a style profile that includes one or more of a template theme, a font theme, a color theme, and a layout theme. In some embodiments, the style profile includes XML data that can be used to implement corresponding style attributes in various content editing tools (e.g., Microsoft PowerPoint, Google Slides, etc.).
[0048] In some embodiments, the weighting system may be used when the target audience includes two or more individuals. For example, a weight (or ranking) may be assigned to each audience member. When two or more audience members have conflicting preferences, the weight (or rank) of each member can be used to determine the preference to be adopted by the content template (e.g., using the highest-ranked preference). In some embodiments, the weight (or rank) is assigned by the user creating the content template. In other embodiments, the weight (or rank) may be assigned by the client application 118 or the application server 102. For example, a title (e.g., CEO, CFO, etc.) or description (e.g., supervisor, manager, etc.) associated with each audience member may be used to determine the weighting / ranking. Alternatively, conflicting preferences may be split across the target audience such that the preferences of each member are equally represented in the content template.
[0049] In step 410, the user may change at least one target audience parameter and / or at least one context parameter. For example, the user may add members to the target audience and / or remove members from the target audience to change at least one target audience parameter. In some embodiments, the fingerprint engine 106 may detect a change in the fingerprint of one or more audience members and, in response, update at least one target audience parameter. Similarly, the user may modify at least one context parameter by changing the context type. In one embodiment, the change of at least one target audience parameter and / or at least one context parameter is provided to the outline engine 108. The outline engine 108 is configured to dynamically update the storyline of the content template (step 406). In some embodiments, the style engine 109 is configured to dynamically modify the style profile for the content template based on the updated storyline, the change of at least one audience parameter, and / or the change of at least one context parameter (step 408).
[0050] In step 412, the content template is generated by the style engine 109. In some embodiments, the content template is generated by applying a style profile to the storyline generated by the outline engine 108. In one embodiment, the style profile is applied by selecting one or more slides included in the storyline from the slide library with style attributes that match the style profile. In some embodiments, the style profile is applied by creating one or more slides included in the storyline with style attributes that match the style profile.
[0051] Once generated, the content template is presented to the user via the client application 118. FIG. 7 illustrates a view 700 of the client application 118 for displaying the content template. As shown, the user may browse (or preview) the content template before downloading. In one embodiment, the user can download the content template by selecting the download button 702. In some embodiments, after selecting the download button 702, the user is presented with a prompt to select a desired file format (or type) for the content template. For example, the UI engine 110 may provide an export service that enables the content template to be downloaded in various formats (e.g., PDF, Microsoft Word, Microsoft PowerPoint, etc.). In some embodiments, the content template can be directly imported into a content editing tool (e.g., Microsoft PowerPoint, Google Slides, etc.). Thus, the user may utilize one or more content editing tools to "fill in" the content corresponding to the content template.
[0052] In step 414, the user may modify one or more features or characteristics of the content template. For example, the user may review the content template and decide to change the node count, layout, image, font, color, working area, shape, chart, graph, icon, text, brand, or any combination thereof of the template. In some embodiments, the changes (or change requests) identified by the user are received via the client application 118 and directed to the corresponding engine (e.g., the style engine 109) of the application server 102. In one embodiment, the style engine 109 is configured to automatically transform the content template based on the user's changes and modifications. In some embodiments, the style engine 109 is configured to apply the user's changes by dynamically generating a new content template (step 412).
[0053] As described above, the system 100 can use a user-specific fingerprint to create a content template tailored to the target audience. In some embodiments, the system 100 may use a user-specific fingerprint to transform existing content so that the content is tailored to the target audience. FIG. 8 is a flowchart of a method 800 for transforming content according to aspects described herein. In some embodiments, the method 800 corresponds to a process performed by the application server 102 and the client application 118.
[0054] In step 802, the application server 102 receives a user-uploaded presentation. In one embodiment, the presentation corresponds to a slide deck. In some embodiments, the presentation may be uploaded by the user via the client application 118. Various engines of the application server 102 may analyze the presentation and identify and classify the content included in the presentation. For example, the outline engine 108 and / or the style engine 109 may decompose the presentation and analyze the content of the presentation. In some embodiments, the engines 108, 109 may include a topic model (e.g., an LDA model) to process and analyze the content of the presentation. In some embodiments, the engines 108, 109 are configured to process and analyze XML data associated with the content of the presentation. In some embodiments, the engines 108, 109 include a machine learning model configured to analyze and process the content of the presentation. Generally, any suitable machine learning technique such as, for example, gradient boosting, random forest, regression, neural network, decision tree, support vector machine, Bayesian network, other types of techniques, etc. can be used.
[0055] In one embodiment, the content of the presentation is extracted from the presentation and stored in one or more content data structures (e.g., within application database 112a). For example, data from a chart included in a user-uploaded presentation may be extracted and stored as a content data structure having a content tag of "chart". Similarly, data (or content) from the instructions included in the user-uploaded presentation may be extracted and stored as a data structure having a content tag of "instructions", and so on. In some embodiments, engines 108, 109 can add tags to the slides and / or objects of the user-uploaded presentation. In one embodiment, the tag may indicate that the slide and / or object contains convertible content that will be tailored to the target audience. In some embodiments, the tag may provide a link (or location) to the corresponding content data structure stored in application database 112a.
[0056] In step 804, outline engine 108 and / or style engine 109 may "sanitize" the user-uploaded presentation. In one embodiment, engines 108, 109 are configured to sanitize the presentation by removing any references to confidential, proprietary, personal, and / or non-public information from the presentation (or the content of the presentation). In other words, the sanitization process may generalize the presentation. The level of sanitization provided may be adjusted by the user via client application 118. In some embodiments, the user may be prompted to review the results of the sanitization process before proceeding with the content conversion.
[0057] In step 806, the fingerprint engine 106 receives at least one target audience parameter. In this context, a "target audience" corresponds to the intended or expected audience for which the content is tailored. In one embodiment, the at least one target audience parameter includes the names of the members of the target audience. In some embodiments, the at least one target audience parameter includes the name of a group, team, club, organization, company, or another type of group that includes one or more individuals. In some embodiments, the at least one target audience parameter includes at least one fingerprint type (e.g., architect, surgeon, etc.). In some embodiments, the fingerprint engine 106 is configured to access, read, or download the corresponding user fingerprint from the application database 112a. In one embodiment, the target audience parameter is provided from the client application 118 to the fingerprint engine 106. The client application 118 may be configured to collect various parameters from the user who converts the content.
[0058] In step 808, the context engine 107 receives at least one context parameter. In one embodiment, "context" corresponds to the intended type, purpose, and / or goal of the content. In some embodiments, the "context" of the content corresponds to the tone of the content (e.g., good news, bad news, etc.). In one embodiment, the at least one context parameter includes the content type. In some embodiments, the context parameter is provided from the client application 118 to the context engine 107. In other embodiments, the context engine 107 may be configured to derive the content type from the user-uploaded presentation (or the content included therein).
[0059] In step 810, the outline engine 108 generates an outline (or story line) regarding the content. In one embodiment, the outline engine 108 is configured to generate a story line based on at least one audience parameter and at least one context parameter. For example, the fingerprint engine 106 may provide at least one audience parameter and / or the corresponding user fingerprint to the outline engine 108. Similarly, the context engine 107 may provide at least one context parameter to the outline engine 108. In one embodiment, the outline engine 108 generates a story line that is optimized for the content type (e.g., all-hands meeting, brand plan, etc.) and the preferences of the target audience members (e.g., fingerprint). In some embodiments, the outline engine 108 is configured to generate a story line that includes a plurality of segments. Each segment of the plurality of segments may include one or more content items (e.g., slides). In some embodiments, rather than providing a story line, the outline engine 108 may provide a list of slides based on at least one audience parameter and at least one context parameter. For example, when the "custom" content type is selected, the outline engine may provide a list of slides that the user can then compose and / or modify the story line by themselves. In some embodiments, the user can save the story line as a custom story line.
[0060] In step 812, the style engine 109 selects (or creates) a style profile for the content. In one embodiment, the style engine 109 is configured to select (or create) a style profile based on at least one audience parameter (e.g., user fingerprint), at least one context parameter, and the content storyline. For example, the user fingerprint can be used to determine image preferences, color preferences, illustration preferences, presentation preferences for logical discourse, presentation preferences for data, and / or preferences regarding visualizing data for each member of the audience. As described above, the style profile includes one or more stylistic attributes of the content. In one embodiment, the style engine 109 is configured to select a pre-rendered style profile from a plurality of style profiles (e.g., a style profile library stored in the application database 112a). In some embodiments, the style engine 109 is configured to create a style profile that includes one or more of a template theme, a font theme, a color theme, and an arrangement theme. In some embodiments, the style profile includes XML data that can be used to implement corresponding style attributes in various content editing tools (e.g., Microsoft PowerPoint, Google Slides, etc.).
[0061] In some embodiments, the weighting system may be used when the target audience includes two or more individuals. For example, a weight (or ranking) may be assigned to each audience member. When two or more audience members have conflicting preferences, the weight (or rank) of each member can be used to determine the preference to be adopted by the content (e.g., using the highest ranked preference). In some embodiments, the weight (or rank) is assigned by the user who converts the content. In other embodiments, the weight (or rank) may be assigned by the client application 118 or the application server 102. For example, a title (e.g., CEO, CFO, etc.) or description (e.g., boss, manager, etc.) associated with each audience member may be used to determine the weighting / ranking. Alternatively, conflicting preferences may be split across the target audience such that each member's preference is equally represented in the content.
[0062] In step 814, the content is automatically converted by the style engine 109. In some embodiments, the content is converted by applying a style profile to the story line generated by the outline engine 108. In one embodiment, the style profile is applied by selecting one or more slides included in the story line from the slide library with style attributes that match the style profile. In some embodiments, the style profile is applied by creating one or more slides included in the story line with style attributes that match the style profile. The style engine 109 is configured to access the tagged content data stored in the application database 112a and integrate the content data into the presentation based on the content story line and the style profile.
[0063] In step 816, the converted presentation is analyzed to find slides and / or objects corresponding to the tagged content data. In one embodiment, the tagged content data is updated (e.g., within application database 112a) based on the representation of the content within the converted presentation. In some embodiments, the tagged content data is saved and used to generate subsequent presentations (e.g., tailored to multiple target audiences). In one embodiment, the tagged content data is used to generate different forms of content. For example, the tagged content data from a presentation may be used to generate a memo, an email, etc.
[0064] In step 818, the user may change at least one target audience parameter and / or at least one context parameter. For example, the user may add members to and / or remove members from the target audience to change at least one target parameter. In some embodiments, the fingerprint engine 106 may detect a change in the fingerprint of one or more audience members and, in response, update at least one target audience parameter. Similarly, the user may modify at least one context parameter by changing the context type. In one embodiment, the change in at least one target audience parameter and / or at least one context parameter is provided to the outline engine 108. The outline engine 108 is configured to dynamically update the story line of the content (step 810). In some embodiments, the style engine 109 is configured to dynamically modify the style profile for the content based on the updated story line, the change in at least one audience parameter, and / or the change in at least one context parameter (step 812).
[0065] Once generated, the content is presented to the user via the client application 118. In some embodiments, the UI engine 110 may provide an export service that enables the content to be downloaded in various formats (e.g., PDF, Microsoft Word, Microsoft PowerPoint, etc.). In some embodiments, the content can be directly imported into a content editing tool (e.g., Microsoft PowerPoint, Google Slides, etc.).
[0066] FIG. 9 illustrates a slide library 900 according to aspects described herein. In one embodiment, a user can access the slide library 900 by selecting the slide button 206 of FIG. 2. The slide library 900 may be stored within the application database 112a and managed by the engines 106-110 of the application server 102. In some embodiments, the user may access the slide library 900 and preview slides corresponding to different user fingerprints, context types, and style profiles. In one embodiment, the user may use an interface to assist in selecting an appropriate context type when creating a new content template. In some embodiments, the user may use an interface to check slides associated with their own unique fingerprint.
[0067] FIG. 10 illustrates a template management interface 1000 of the client application 118. In one embodiment, a user can access the template management interface 1000 by selecting the presentation button 204 in FIG. 2. The content of the template management interface 1000 can be stored in the application database 112a and / or the user database 112b and may be managed by the UI engine 110 of the application server 102. In some embodiments, a user may use the interface 1000 to view content templates they created (e.g., via tab 1002). Similarly, a user may use the interface 1000 to view content templates assigned to them for review (e.g., via tab 1004). In some embodiments, a user may use the interface 1000 to view content templates they created or are creating in collaboration with other users (e.g., via tab 1006).
[0068] The above embodiments describe the creation of content templates for presentations (e.g., slide shows), but it should be understood that the system 100 can be adapted for other types of content. For example, the system 100 can be configured to generate templates for email, memo, spreadsheet, report, letter, or any other type of content or media. Thus, the system 100 can generate content templates that are compatible with various content editing tools and platforms such as, for example, Microsoft PowerPoint, Microsoft Office, Microsoft Excel, Google Slides, Microsoft Outlook, Gmail, Adobe Acrobat, etc.
[0069] As described above, a system and method for creating a content template based on audience preferences and context factors are provided herein. In at least one embodiment, a content storyline is generated based on parameters of a target audience and the context of the content. In one example, the parameters of the target audience correspond to the preference fingerprints of audience members. In some embodiments, a style profile is selected or created for a content template based on parameters of the target audience, the context of the content, and the storyline. (Hardware and Software Implementations)
[0070] FIG. 11 shows an example of a general computing device 1100 that may be used in conjunction with some of the techniques described in this disclosure (e.g., as user device 116 or application server 102). Computing device 1100 includes, among other components, a processor 1102, a memory 1104, an input / output device such as a display 1106, a communication interface 1108, and a transceiver 1110. Device 1100 may also include a storage device such as a microdrive or other device, providing additional storage. Components 1100, 1102, 1104, 1106, 1108, and 1110 are interconnected using various buses, and some of the components may be mounted on a common motherboard or in other manners as appropriate.
[0071] Processor 1102 can execute instructions within computing device 1100, including instructions stored in memory 1104. Processor 1102 may be implemented as a chipset of chips including separate and multiple analog and digital processors. Processor 1102 may provide coordination of other components of device 1100, such as, for example, control of the user interface, applications launched by device 1100, and wireless communication by device 1100.
[0072] Processor 1102 may communicate with a user through a display interface 1114 coupled to a control interface 1112 and a display 1106. The display 1106 may be, for example, a TFT LCD (Thin Film Transistor Liquid Crystal Display) or an OLED (Organic Light Emitting Diode) display, or other suitable display technology. The display interface 1114 may comprise appropriate circuitry for driving the display 1106 and presenting graphics and other information to the user. The control interface 1112 may receive commands from the user and convert them for submission to the processor 1102. Additionally, an external interface 1116 may be provided in communication with the processor 1102 to enable near area communication of the device 1100 with other devices. The external interface 1116 may provide, for example, wired communication in some implementations, or wireless communication in other implementations, and multiple interfaces may also be used.
[0073] Memory 1104 stores information within computing device 1100. Memory 1104 can be implemented as one or more than one of a computer-readable medium or media, a volatile memory unit or units, or a non-volatile memory unit or units. Extended memory 1118 may also be provided and may be connected to device 1100 through an expansion interface 1120, which may include, for example, a SIMM (Single In-line Memory Module) card interface. Such extended memory 1118 may provide additional storage space for device 1100 or may also store applications or other information for device 1100. Specifically, extended memory 1118 may include instructions for performing or complementing the processes described above and may also include secure information. Thus, for example, extended memory 1118 may be provided as a security module for device 1100 and may be programmed with instructions that enable secure use of device 1100. In addition, secure applications such as placing identification information on the SIMM card in a non-hackable manner may be provided via the SIMM card along with additional information.
[0074] The memory may include, for example, flash memory and / or NVRAM memory as discussed below. In one implementation, a computer program product is tangibly embodied in an information carrier. The computer program product contains instructions that, when executed, implement one or more than one method such as those described above. The information carrier is a computer or machine-readable medium such as memory 1104, extended memory 1118, memory on processor 1102, or a propagated signal that may be received, for example, via transceiver 1110 or external interface 1116.
[0075] Device 1100 may communicate wirelessly through a communication interface 1108, which may include a digital signal processing circuitry if necessary. In some cases, the communication interface 1108 may be a cellular modem. The communication interface 1108 may provide communication under various modes or protocols, such as GSM (registered trademark) voice calls, SMS, EMS, or MMS messaging, CDMA, TDMA, PDC, WCDMA (registered trademark), CDMA2000, or GPRS. Such communication may occur, for example, through a radio frequency transceiver 1110. Additionally, short - range communication may occur using Bluetooth (registered trademark), WiFi, or other such transceivers (not shown). Additionally, a GPS (Global Positioning System) receiver module 1122 may provide additional navigation and location - related wireless data to device 1100 as appropriate, by an application running on device 1100.
[0076] Device 1100 may also communicate audibly using an audio codec 1124 that can receive spoken information from a user and convert it into usable digital information. The audio codec 1124 may similarly generate audible sounds for the user, for example, through a speaker within the handset of device 1100. Such sounds may include sounds from a phone voice call, recorded sounds (such as voice messages, music files, etc.), and also sounds generated by an application operating on device 1100. In some embodiments, device 1100 includes a microphone for collecting audio (e.g., speech) from the user. Similarly, device 1100 may include an input for receiving a connection from an external microphone.
[0077] As shown in FIG. 11, computing device 1100 may be implemented in several different forms. For example, it may be implemented as a computer (e.g., a laptop) 1126. It may also be implemented as part of a smartphone 1128, smartwatch, tablet, personal digital assistant, or other similar mobile device.
[0078] Some implementations of the subject matter and the operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, or in combinations of one or more of them, including the structures disclosed in this specification and their structural equivalents. Implementations of the subject matter described in this specification can be implemented as one or more computer programs, i.e., as one or more modules of computer program instructions encoded on a computer storage medium for execution by, or to control the operation of, a data processing apparatus. Alternatively, or in addition, the program instructions can be encoded on a machine-generated propagated signal, e.g., an electrical, optical, or electromagnetic signal generated by a machine for transmission to a suitable receiver apparatus for execution by a data processing apparatus. A computer storage medium can be, or can be included in, a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination of one or more of them. Moreover, a computer storage medium can be, or can be included in, one or more separate physical components or media (e.g., multiple CDs, disks, or other storage devices). A computer storage medium can also be, or can be included in, a source or destination of computer program instructions encoded in an artificially generated propagated signal.
[0079] The operations described herein can be implemented as operations performed by a data processing apparatus on data stored on one or more computer-readable storage devices or received from other sources.
[0080] The term "data processing apparatus" includes, by way of example, any kind of apparatus, device, and machine for processing data, including programmable processors, computers, systems on a chip, or multiple of the foregoing or combinations thereof. The apparatus can include special purpose logic circuitry, such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit). The apparatus can also include, in addition to hardware, code for creating an execution environment for the computer program, such as processor firmware, protocol stack, database management system, operating system, cross-platform runtime environment, virtual machine, or code constituting one or more of them in combination. The apparatus and the execution environment can realize various different computing model infrastructures, such as web service, distributed computing, and grid computing infrastructures.
[0081] A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiler-type or interpreter-type languages, declarative or procedural languages, and can be developed in any form, including as a stand-alone program or as modules, components, subroutines, objects, or other units suitable for use within a computing environment. A computer program may, but need not, correspond to a file in a file system. The program can be stored within a single file dedicated to the program, within a file that holds other programs or data (e.g., one or more scripts stored within a markup language resource), or within multiple cooperating files (e.g., files that hold one or more modules, subprograms, or portions of code). A computer program can be deployed to be executed on one computer, located at one site, or distributed across multiple sites and executed on multiple computers interconnected by a communication network.
[0082] The processes and logical flows described herein can be implemented by one or more programmable processors executing one or more computer programs to perform actions by operating on input data and generating output. The processes and logical flows can also be implemented by special purpose logic circuitry, such as an FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the apparatus can also be implemented as such.
[0083] Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read only memory or a random access memory or both. Essential elements of a computer are a processor for performing actions in accordance with instructions, and one or more memory devices for storing the instructions and data. Generally, a computer will also include, or be operatively coupled to, one or more mass storage devices for storing data, such as, magnetic, magneto-optical disks, or optical disks, or receive data therefrom, or transfer data thereto, or both. However, a computer need not have such devices. Also, a computer can be embedded in another device, such as, by way of example only, a mobile phone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a global positioning system (GPS) receiver, or a portable memory device (e.g., a universal serial bus (USB) flash drive). Devices suitable for storing computer program instructions and data include, by way of example, semiconductor memory devices, such as, EPROM, EEPROM, and flash memory devices, magnetic disks, such as, internal hard disks or removable disks, magneto-optical disks, and CD-ROM and DVD-ROM disks, including any form of non-volatile memory, media, and memory devices. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
[0084] To provide interaction with a user, implementations of the subject matter described herein can be implemented on a computer having a display device, such as a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user, and a keyboard and a pointing device, such as a mouse or trackball, by which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user. For example, feedback provided to the user can be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback, and input received from the user can be in any form, including acoustic, speech, or tactile input. Additionally, the computer can interact with the user by sending resources to and receiving resources from devices used by the user, such as by sending a web page to a web browser on the user's client device in response to a request received from the web browser.
[0085] Implementations of the subject matter described herein can be implemented in a computing system that includes, for example, a data server, includes backend components, or includes middleware components, such as application servers, or includes frontend components, such as a graphical user interface or a web browser through which a user can interact with an implementation of the subject matter described herein, or any combination of one or more such backend, middleware, or frontend components. Components of the system can be interconnected by any form or medium of digital data communication, such as by a communication network. Examples of communication networks include local area networks ("LANs") and wide area networks ("WANs"), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks).
[0086] A computing system can include a client and a server. The client and the server are generally remote from each other and typically interact through a communication network. The relationship between the client and the server is created by computer programs that run on separate computers and have a client-server relationship with each other. In some implementations, the server transmits data (e.g., an HTML page) to the client device (for the purpose of, e.g., displaying the data to a user interacting with the client device and receiving user input from the user). Data generated at the client device (e.g., as a result of user interaction) can be received at the server from the client device.
[0087] One or more computer systems can be configured to perform a particular operation or action by having software, firmware, hardware, or a combination thereof installed on the system that, when operating, causes the system to perform the action. One or more computer programs can be configured to perform a particular operation or action by including instructions that, when executed by a data processing apparatus, cause the apparatus to perform the action.
[0088] This specification contains many specific implementation details, but these should be construed as descriptions of features specific to particular implementations of a particular invention rather than as limitations on the scope of any invention or of what may be claimed. Certain features described herein in the context of separate implementations may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented separately in multiple implementations or in any suitable sub-combination. Also, features that have been described and may even initially be claimed as acting in a certain combination may, in some cases, be excised from the claimed combination, and the claimed combination may be directed to a sub-combination or a variant of a sub-combination.
[0089] Likewise, operations are depicted in the drawings in a particular order, but this should not be understood as requiring that the operations be performed in the particular order shown or in a sequential order, or that all of the illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Also, the separation of various system components in the implementations described above should not be understood as requiring such separation in all implementations, and it should be understood that the described program components and systems may generally be integrated together in a single software product or packaged into multiple software products.
[0090] Accordingly, specific implementations of the subject matter have been described. Other implementations are within the scope of the following claims. In some cases, the actions recited in the claims may be performed in a different order and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order or sequential order shown to achieve desirable results. In certain implementations, multitasking and parallel processing may be advantageous.
[0091] The claims are as follows.
Claims
1. A method for creating a template for content, comprising: receiving at least one audience parameter representing at least one preference of a target audience when receiving the content; receiving at least one context parameter representing the context of the content; determining a content storyline based on the at least one audience parameter and the at least one context parameter; generating a content template based on the content storyline .
2. The method according to claim 1, wherein the target audience is a single individual.
3. The method according to claim 1, wherein the target audience is two or more individuals.
4. The method according to claim 1, wherein the at least one audience parameter represents one or more of the target audience's image preference, color preference, illustration preference, presentation preference regarding logical discourse, presentation preference regarding data, and preference regarding visualizing data.
5. presenting at least one preference inquiry to the target audience; deriving at least one preference of the target audience when receiving the content based on a response to the at least one preference inquiry; generating at least one preference fingerprint regarding the target audience based on the at least one preference of the target audience .
6. The method according to claim 5, wherein the at least one preference fingerprint includes the at least one audience parameter.
7. The method according to claim 1, wherein the at least one context parameter corresponds to one or more of the type, purpose, and goal of the content.
8. The method according to claim 1, wherein the content storyline corresponds to one or more of the sequence, order, and flow of the content.
9. The method according to claim 1, further comprising selecting a style profile based on the at least one audience parameter and the at least one context parameter.
10. Generating the content template includes generating the content template based on the content storyline and the style profile, the method according to claim 9.
11. The style profile corresponds to one or more of a content theme, a font theme, a color theme, and an arrangement theme of the content, the method according to claim 9.
12. The content is a presentation, and the content template corresponds to a slide deck for the presentation, the method according to claim 1.
13. The method according to claim 1 further includes exporting the content template to at least one content editing application.
14. A system for creating a template for content, comprising: At least one memory for storing computer-executable instructions; At least one processor for executing the instructions stored on the memory, wherein the execution of the instructions: Receiving at least one audience parameter representing at least one preference of a target audience when receiving the content; Receiving at least one context parameter representing the context of the content; Determining a content storyline based on the at least one audience parameter and the at least one context parameter; Generating a content template based on the content storyline; Programming the at least one processor to perform operations including: A system comprising.
15. The system according to claim 14, wherein the target audience is a single individual.
16. The system according to claim 14, wherein the target audience is two or more individuals.
17. The at least one audience parameter represents one or more of an image preference, a color preference, an illustration preference, a presentation preference regarding logical discourse, a presentation preference regarding data, and a preference regarding visualizing data of the target audience, the system according to claim 14.
18. The execution of the instructions: Presenting at least one preference inquiry to the target audience; Deriving at least one preference of the target audience when receiving the content based on responses to the at least one preference inquiry; Generating at least one preference fingerprint regarding the target audience based on the at least one preference of the target audience; Programming the at least one processor to perform operations further including the above, the system according to claim 14.
19. The system according to claim 18, wherein the at least one preference fingerprint includes the at least one audience parameter.
20. The system according to claim 14, wherein the at least one context parameter corresponds to one or more of the type, purpose, and target of the content.
21. The system according to claim 14, wherein the content storyline corresponds to one or more of the sequence, order, and flow of the content.
22. The execution of the instructions selecting a style profile based on the at least one audience parameter and the at least one context parameter; Programming at least one processor to perform operations further including the above, the system according to claim 1.
23. The system according to claim 22, wherein generating the content template includes generating the content template based on the content storyline and the style profile.
24. The system according to claim 22, wherein the style profile corresponds to one or more of the content theme, font theme, color theme, and composition theme of the content.
25. The system according to claim 14, wherein the content is a presentation, and the content template corresponds to a slide deck for the presentation.
26. The execution of the instructions exporting the content template to at least one content editing application; Programming the at least one processor to perform operations further including the above, the system according to claim 14.
Citation Information
Cited By
An integrated ai-based content production system and method including box-office metric-based plot optimization and character attribute synchronization
KR102973093B1