Web site content change management

• US 7,543,005 B1
• Filed: 03/30/2007
• Issued: 06/02/2009
• Est. Priority Date: 12/30/2002
• Status: Expired due to Term

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Treder, Douglas, Edelman, Alexandre, Lopez, Gus
• Primary Examiner(s): Rodriguez; Paul L
• Assistant Examiner(s): OSBORNE, LUKE R
• Application Number:
  US11/694,578
• Time in Patent Office: 795 Days
• Field of Search: 707/103.R, 707/203, 707/10, 705/9
• US Class Current: 1/1
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

A facility for specifying and previewing changes to a web site is described. Sets of changes to a web site are scheduled for release at a specified time. While the changes are being specified using a tool/interface, methods for showing the change as it will appear on the live web site are implemented. Inconsistencies between specified changes and changes in future releases may be identified as the changes are specified. Web page preview functionality is provided to allow any release to be viewed before publication to a live web site. The preview further allows inconsistencies between selected changes and changes in other future releases to be identified.

Claims

1. A method in a computer system for specifying changes to a web site, the method comprising:

in the computer system, receiving a request for a first change to the web site, the first change scheduled for release at a first specified time;

in the computer system, receiving information for the first change;

prior to the specified time for release of the first change, in the computer system, receiving a request for a second change to the web site, the second change scheduled for release at a second specified time;

upon receiving the request for the second change, in the computer system, automatically determining whether the release of the second change would result in an inconsistency once both the first change and the second change are released;

generating a simulation of the appearance of said web site as if the first change and the second change were applied to the web site, wherein said simulation of web site appearance simulates an appearance of said web site as if the web site were launched live and accessible to one or more clients; and

where the release of the second change would result in an inconsistency, in the computer system, providing an indication of the inconsistency within said simulation.

2. The method of claim 1 wherein the first change is scheduled for release prior to the second change.

3. The method of claim 1 wherein the second change is scheduled for release prior to the first change.

4. The method of claim 1, further comprising receiving an indication of the requests for change via a tool configured to receive an indication of products to display on the web site.

5. The method of claim 1 further comprising, receiving an indication of the requests for change via a tool configured to receive an indication of a browsing structure of the web site.

6. The method of claim 1 further comprising, receiving an indication of the requests for change via a tool configured to add images to the web site.

7. The method of claim 1 further comprising, receiving an indication of the requests for change via a tool configured to add new products to the web site.

8. The method of claim 1 wherein the indication of the inconsistency is a warning message.

9. The method of claim 1 wherein the inconsistency is a broken dependency.

10. The method of claim 1 wherein the first change is scheduled for release prior to the second change and wherein the first change is a deletion of a parent browse node and the second change is an addition of a child browse node to the parent browse node deleted by the first change.

11. The method of claim 1 wherein the second change is scheduled for release prior to the first change and wherein the first change is an addition of a child browse node to a parent browse node and the second change is a deletion of the parent browse node.

12. The method of claim 1 wherein the first change is scheduled for release prior to the second change and wherein the first change is a modification of an image and the second change is a modification of a textual description associated with the modified image.

13. The method of claim 1 wherein the determining includes:

retrieving data associated with the first change according to a process for generating the web site as specified by the first change; and

analyzing the second change to determine if data associated with the second change is consistent with the retrieved data.

14. In a system for updating a web site using releases indicating a set of content changes, a method for specifying releases, the method comprising:

receiving a request to create a first release for the web site, the first release scheduled for a first specified time;

based on the received request to create a first release, providing a first environment suitable for receiving information for the first release;

receiving information for the first release via the provided first environment;

storing the received information for the first release;

prior to the specified time for the first release, receiving a request for a second release for the web site, the second release scheduled for a second specified time, wherein the second specified time is later than the first specified time; and

based on the request, providing a second environment suitable for receiving information related to the second release, the second environment providing an indication of the received information for the first release, wherein providing the second environment includes;

retrieving the stored information for the first release; and

creating a preview display, the preview display applying the content changes associated with the first release to a representation of the web site so that information for the second release can be received in a context of the first release, as if the first release has already actually occurred.

15. The method of claim 14 wherein at least one of the first or second environments includes a tool configured to receive an indication of product descriptions to add to the web site.

16. The method of claim 14 wherein at least one of the first or second environments includes a tool configured to receive an indication of images to add to the web site.

17. The method of claim 14 wherein at least one of the first or second environments includes a tool configured to receive an indication of product-specific images to add to the web site.

18. The method of claim 14 wherein at least one of the first or second environments includes a tool configured to receive a selection of a page layout for the web site.

19. The method of claim 14 wherein at least one of the first or second environments includes a tool configured to receive an indication of non-product-specific content for the web site.

20. The method of claim 14 wherein at least one of the first or second environments includes a tool configured to schedule automated content for the web site.

21. The method of claim 14 wherein at least one of the first or second environments includes a tool configured to receive an indication of a browsing structure for the web site.

22. The method of claim 14 wherein providing the second release environment further includes:

retrieving stored data objects associated with the first release.

23. The method of claim 14 wherein the indication of information related to the first release is a warning message.

24. The method of claim 14 wherein the indication of information related to the first release is a preview page of the web site showing changes that will result when the first release is published to the live web site.

25. The method of claim 14 wherein the first release includes a deletion of a browse node and the second release includes an addition of a child browse node to the browse node deleted in the first release.

26. The method of claim 14 wherein the first release includes a deletion of a browse node and the second release includes an addition of new or modified product information, wherein the product information is related to the browse node deleted in the first release.

27. In a system for releasing new content on a live web site, a method comprising:

providing an indication of saved releases, each of the saved releases scheduled for future release at a respective specified time;

receiving a selection of a particular saved release of said saved releases;

based on the respective time at which said particular saved release is scheduled for release, identifying saved releases scheduled to occur prior to the selected saved release;

determining changes to a page of the web site after the identified saved releases and the selected saved release are applied to a representation of the web site in chronological order; and

displaying a preview page including a representation of the resulting page of the web site including the determined changes.

28. The method of claim 27 further comprising:

where there is an inconsistency between the changes in the selected saved release and the identified saved releases, identifying the inconsistency; and

providing an indication of the inconsistency on the displayed resulting page of the web site.

29. The method of claim 28 wherein the indication of the inconsistency is a warning message displayed with information related to the inconsistency.

30. The method of claim 28 wherein the indication of the inconsistency is a warning message displayed on the resulting page of the web site.

31. The method of claim 27 wherein the indication of saved releases are provided in a report, the report indicating each change associated with the selected saved release.

32. The method of claim 28 wherein the indication of the inconsistency is displayed on the preview page, wherein the preview page is generated using a single code path, and wherein the single code path used to generate the preview page is also configured to generate the live web site after the selected release is scheduled to occur.

33. The method of claim 28 wherein the indication of the inconsistency is displayed on the preview page, wherein the preview page is generated using data, and wherein the data used to generate the preview page is also configurable to generate the live web site after the selected release is scheduled to occur.

34. The method of claim 27 including providing an option to approve the selected saved release.

35. The method of claim 27 including providing an option to modify the selected saved release.

36. The method of claim 27 including providing an option to modify the identified saved releases.

37. The method of claim 27 wherein the selected release includes deletion of a browse node.

38. The method of claim 27 wherein the selected release includes addition of a browse node.

39. The method of claim 27 wherein the selected release includes addition of a product description.

40. The method of claim 27 wherein the selected release includes addition of an image.

41. The method of claim 27 wherein the selected release includes addition of a product-specific image.

42. The method of claim 27 wherein the selected release includes a selection of a page layout.

43. The method of claim 27 wherein the selected release includes addition of non-product-specific content.

44. The method of claim 27 wherein the selected release includes addition of automated content.

45. The method of claim 27 wherein the selected release includes deletion of web site content.

46. A system for releasing new content on a web site, the system comprising:

means for providing an indication of saved releases, the saved releases scheduled for future release at a specified time;

means for receiving a selection of a saved release;

means for identifying saved releases scheduled to occur prior to the selected saved release; and

means for generating a report, the report indicating each change associated with the selected saved release, and for each change, providing a link to a preview page, the preview page providing a simulation of web site appearance if the identified saved releases and the selected saved releases were applied to at least one page of the web site in chronological order;

wherein said simulation of web site appearance simulates an appearance of said web site if the web site were launched live and accessible to one or more clients.

47. A system for updating a web site, the system comprising:

a tools layer, the tools layer providing a framework for specifying and approving sets of changes to the web site, wherein the tools layer is configured to receive content information, including information related to content changes and information related to scheduling content changes, the tools layer configured to generate indications of changes scheduled for release to a web site, wherein each of the changes is scheduled for release at a specified time, wherein the tools layer is configured to, for a selected change of said changes scheduled for release, generate a simulated appearance of said web site including the selected change simulated within a context of one or more other changes identified as being scheduled for release at a time prior to the specified time for release of said selected change;

a data layer for storing received content information, including information associated with changes scheduled for release to a web site; and

a service layer for transmitting data from the data layer to the tools layer in response to requests for data by the tools layer, the service layer also configured for requesting data from the data layer to generate a live web site.

48. The system of claim 47 wherein the tools layer is configured to facilitate a process for generating a preview page, the preview page providing an indication of future scheduled changes to a web site.

49. The system of claim 47 wherein the tools layer, the data layer, and the service layer are configured to serve multiple vendors, each vendor having one or more distinct web sites.

50. The system of claim 47 wherein the tools layer, the data layer, and the service layer are configured provide web site access for multiple customers.

51. The system of claim 47 wherein the tools layer is configured to facilitate a process for generating a confirmation, the confirmation providing an indication of a requested change.

52. The system of claim 47 wherein the tools layer is configured to generate warning messages providing an indication of inconsistencies in a plurality of future scheduled changes to a web site, the inconsistencies identified based on information retrieved from the data layer by the service layer.

53. A computer-readable medium whose contents cause a computing system to provide services for creating content changes for a web site, by a method comprising:

receiving a request for a first release, the first release scheduled for release at a first specified time;

based on the received request for a first release, providing at least one tool for receiving information for the first release;

receiving information for the first release via the provided at least one tool, said information specifying a given change to be performed on said web_site;

prior to the specified time for the first release, receiving a request for a second release, the second release scheduled for release at a second specified time, wherein the second specified time occurs after the first specified time;

based on the request for the second release, providing the at least one tool for receiving information related to the second release, the at least one tool providing an indication of the received information for the first release including said given change to be performed on said web site;

subsequent to receiving the information related to the second release via the at least one tool, automatically determining whether an other change to the web_site specified by the second release would result in an inconsistency once both said given change and said other change are performed on said web_site;

generating a simulation of the appearance of said web site if said given change and said other change were applied to the web site;

wherein said simulation of web site appearance simulates an appearance of said web site if the web site were launched live and accessible to one or more clients; and

if an inconsistency is determined, providing an indication of the inconsistency within said simulation.

54. A computer-readable medium containing a data structure for use in a system for modifying content on a web site, the data structure including, for each of a plurality of releases, a release specification comprising:

a scheduled release time; and

an indication of a composite of data stored in a data store and managed by a plurality of release services, the composite of data corresponding to a set of changes to be made to the web site at the scheduled release time and providing a specification for generating a preview page using the plurality of release services, wherein the preview page provides a simulation of web site appearance if the set of changes associated with each of the plurality of releases with a scheduled release time that occurs on or before a specified time was applied to the web site;

wherein said simulation of web site appearance simulates an appearance of said web site if the web site were launched live and accessible to one or more clients.

55. The computer-readable medium of claim 54 wherein for each of the plurality of releases, the indication of composite data provides a specification for generating a live web page at the corresponding scheduled release time, the live web page generated using the plurality of release services.

56. The computer-readable medium of claim 54 wherein the preview page is configured to identify inconsistencies between changes in a selected release and a baseline.