Systems and methods for processing and producing content for web sites
First Claim
1. A non-transitory computer readable storage medium storing thereon computer executable instructions for development of web content, wherein said instructions are executed to:
- record at least one request for production of web content, wherein said at least one request is made via a request form interface in order to start the production of content for at least one web site by submitting the at least one request and wherein said at least one request includes a designation of a destination of the content and said request form interface includes selectable components at least of;
a description of an impact if said content is not approved, a risk rating associated with the content, and a description of points of integration associated with the content;
provide a stage for development of code that at least in part serves as the basis for said content, wherein a number of versions of said code are stored according to a number of heuristics associated with changes to the code and a preferred version of the number of versions of said code is selected for passage to a next stage according to how said content functions;
provide a stage for the testing of said code;
store said content for a predetermined period time during a staging stage;
publish said content in a form of said at least one web site, when said content has arrived at a publishing stage; and
via a second interface, track said content and log a stage said code is currently in, a stage said code has previously been in, and a stage the code is likely to be in at a future time;
wherein the second interface enables submitting said content along any stage of said development stage, said testing stage, and said publishing stage;
inquire of a requesting entity whether there is an emergency associated with the at least one request;
receive in response to the inquiry, via the second interface, an indication of the emergency associated with the at least one request; and
expedite a processing of the content associated with the emergency according to the indication, wherein expediting includes omitting, without an approval, at least one of the stage for development of said code, the stage for the testing of said code, the staging stage, and the publishing stage.
1 Assignment
0 Petitions
Accused Products
Abstract
Mechanisms for the publication of web content are disclosed. Various stages can be used in a general publishing framework in moving content to publication. For instance, a development stage for the content can be used, where the development stage allows entities, such as developers, to code any materials associated with the content. Also, a testing stage can be used in order to test content developed in the development stage. Once these two stages are complete, a staging stage can be used for storing the content, and a production stage can be used for the actual publication of the content. Moreover, various interfaces can be used to allow entities to make requests to submit content and to log the state of such content in the framework. Lastly, various entities can collaborate on the publication of web content using the framework.
33 Citations
18 Claims
-
1. A non-transitory computer readable storage medium storing thereon computer executable instructions for development of web content, wherein said instructions are executed to:
-
record at least one request for production of web content, wherein said at least one request is made via a request form interface in order to start the production of content for at least one web site by submitting the at least one request and wherein said at least one request includes a designation of a destination of the content and said request form interface includes selectable components at least of;
a description of an impact if said content is not approved, a risk rating associated with the content, and a description of points of integration associated with the content;provide a stage for development of code that at least in part serves as the basis for said content, wherein a number of versions of said code are stored according to a number of heuristics associated with changes to the code and a preferred version of the number of versions of said code is selected for passage to a next stage according to how said content functions; provide a stage for the testing of said code; store said content for a predetermined period time during a staging stage; publish said content in a form of said at least one web site, when said content has arrived at a publishing stage; and via a second interface, track said content and log a stage said code is currently in, a stage said code has previously been in, and a stage the code is likely to be in at a future time; wherein the second interface enables submitting said content along any stage of said development stage, said testing stage, and said publishing stage; inquire of a requesting entity whether there is an emergency associated with the at least one request; receive in response to the inquiry, via the second interface, an indication of the emergency associated with the at least one request; and expedite a processing of the content associated with the emergency according to the indication, wherein expediting includes omitting, without an approval, at least one of the stage for development of said code, the stage for the testing of said code, the staging stage, and the publishing stage. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. A non-transitory computer readable storage medium storing computer executable instructions for publishing web content, said instructions executed to:
-
utilize a publishing framework for publishing said web content, wherein said framework includes; a development stage, wherein a number of versions of code are stored according to a number of heuristics associated with changes to the code and a preferred version of the number of versions of the code is selected for passage to a next stage according to how the code functions, a testing stage for testing the code, a staging stage for storing said content for a predetermined period time, and a production stage for publishing said content in the form of at least one web site; record at least one request for production of said web content, wherein said at least one request is made via a request form interface in order to start the production of content for said at least one web site by submitting the at least one request and wherein said at least one request includes a designation of a destination of the content and said request form interface includes selectable components at least of;
a description of an impact if said content is not approved, a risk rating associated with the content, and a description of points of integration associated with the content;via a second interface, track the content and log a stage said code is currently in, a stage said code has previously been in, and a stage the code is likely to be in at a future time; wherein said second interface for submitting said content along any stage of said publishing framework, including said development stage, said testing stage, said staging stage, and said production stage; inquire of a requesting entity whether there is an emergency associated with the at least one request; receive in response to the inquiry, via the second interface, an indication of the emergency associated with a submission of content; expedite a processing of the content associated with the emergency according to the indication, wherein expediting includes omitting, without an approval, at least one of the development stage, testing stage, the staging stage, and the production stage; and wherein said second interface also provides controls for giving approval for any content that is submitted, and wherein said interface keeps a log of said submitted content upon the granting of said approval. - View Dependent Claims (8, 9, 10, 11, 12)
-
-
13. A non-transitory computer readable storage medium storing computer executable instructions for publishing web content in a collaborative fashion, said instructions executed to:
-
receive requests made via a request form interface for publishing said web content, wherein said requests include a designation of a destination of the content and said request form interface includes selectable components at least of;
a description of an impact if said content is not approved, a risk rating associated with the content, and a description of points of integration associated with said content;instantiate a publishing framework with a plurality of stages configured to be used for publishing of said web content including; a development stage, wherein a number of versions of code are stored according to a number of heuristics associated with changes to the code and a preferred version of the number of versions of the code is selected for passage to a next stage according to how the code functions, a testing stage for testing the code, a staging stage for storing said content for a predetermined period of time, and a production stage for publishing said content in the form of at least one web site; record the requests, via a content submission interface, track the content and log a stage said code is currently in, a stage said code has previously been in, and a stage the code is likely to be in at a future time; provide a first interface to a first entity to submit a first portion of said web content; provide a second interface to a second entity to submit a second portion of said web content; inquire of a requesting entity whether there is an emergency associated with the requests; receive in response to the inquiry, via one of the first user interface and the second user interface, the indication of an emergency associated with one of the submitted first portion and submitted second portion; expedite a processing of the content associated with the emergency according to the indication, wherein expediting includes omitting, without an approval, at least one of the plurality of stages; and accept submissions of said first portion of said web content to a first stage of said plurality of stages, and said second portion of said web content to a second stage of said plurality of stages. - View Dependent Claims (14, 15, 16, 17, 18)
-
Specification