User interface development

1. A method for developing a user interface, the method comprising:

receiving changes to the user interface to be previewed in a preview user interface;

preparing an environment for displaying the preview user interface by copying links including first links and second links to web assets associated with a live user interface into preview web assets, wherein the web assets are developed by a plurality of development teams including a first development team and a second development team, wherein the changes are developed by the first development team, wherein the first development team cannot change the web assets developed by the second development team;

inserting the changes into the preview web assets, wherein inserting the changes includes overwriting a portion of the first links to the web assets with the changes such that the preview web assets includes the changes and the first links links to the web assets that were not overwritten;

generating the preview user interface of the live user interface in a display by constructing the preview user interface from the preview web assets such that the changes are presented in a context of the live user interface and such that the preview user interface is generated from the changes and the live web assets associated with the first links that were not overwritten.

2. The method of claim 1 , further comprising receiving a plurality of changes from each of the plurality of development teams.

3. The method of claim 1 , wherein inserting the changes into the preview web assets includes overwriting the portion of the first links with files included in the changes.

4. The method of claim 3 , wherein the preview user interface corresponds to the live user interface except for a component corresponding to the changes.

5. The method of claim 1 , further comprising:

performing a security check on the changes before inserting the changes into the preview web assets;

determining whether the changes includes integration errors prior to inserting the changes into the preview web assets;

determining whether a scope of the changes conflicts with a scope of any portion of the preview web assets prior to inserting the changes into the web asset.

6. The method of claim 1 , wherein inserting the changes into the preview web assets includes at least one of:

deleting the portion of the first links from the preview web assets,

adding assets from the changes to the preview web assets, and

overwriting the portion of the first links in the preview web assets.

7. The method of claim 1 , further comprising setting a cookie in a browser such that the preview user interface is generated by a user interface server.

8. A method for approving one or more plugins to include in a live user interface, the method comprising:

generating an approval user interface that allows an approver to approve changes to the live user interface;

displaying a list of changes in the approval user interface;

displaying a section that allows an approval to be input from the approver in the approval user interface;

selecting at least one of the changes from the list of changes;

extracting the selected changes into preview web assets, wherein the preview web assets includes links including first links and second links to web assets associated with the live user interface, wherein extracting the selected at least one changes includes overwriting a portion of the first links to the web assets with the second links to new assets associated with the selected changes such that the preview web assets includes the selected changes and the first links to the web assets associated with the live user interface that were not overwritten, wherein the web assets are developed by a plurality of development teams including a first development team and a second development team, wherein the selected changes are developed by the first development team and where in the first development team cannot change the web assets developed by the second development team;

generating a preview user interface of the live user interface that includes the selected changes from the preview web assets such that the selected changes are presented in a context of the live user interface and such that the preview user interface is generated from both the selected changes and the web assets associated with the first links that were not overwritten.

9. The method of claim 8 , further comprising generating a different preview user interface by selecting different changes from the list of changes.

10. The method of claim 9 , further comprising adjusting the preview web assets to include the first links to the web assets that were not overwritten and files from the selected different changes.

11. The method of claim 8 , further comprising regenerating the preview user interface each time a different set of changes is selected from the list of changes.

12. The method of claim 8 , further comprising approving one or more of the changes in the list of changes.

13. The method of claim 12 , further comprising incorporating the approved one or more of the changes into the web assets associated with the live user interface such that the live user interface, when generated, includes the approved one or more of the changes.

14. The method of claim 12 , further comprising providing feedback to developers for changes in the list of changes that were not approved, wherein the feedback is received into the approval user interface.

15. A method for developing a user interface, the method comprising:

receiving changes for a user interface;

preparing an environment for displaying the changes in a preview user interface, wherein the preview user interface includes links to web assets;

adding the changes to preview web assets such that the preview web assets are associated with a live user interface and the changes, wherein adding the changes includes overwriting at least some of the links to the live web assets with the changes, wherein the web assets are developed by a plurality of development teams including a first development team and a second development team, wherein the changes are developed by the first development team and where in the first development team cannot change the web assets developed by the second development team;

previewing the changes in the preview user interface which is generated from the preview web assets such that the changes are presented in the context of the live user interface;

submitting the changes for approval; and

merging the changes into the live web assets after the changes are approved.

16. The method of claim 15 , wherein submitting the changes for approval includes displaying the preview user interface including the changes to an approver that approves the changes.

17. The method of claim 15 , further comprising receiving a plurality of changes from each of the development teams.

18. The method of claim 15 , wherein inserting the changes into the preview web assets includes overwriting the links included in the preview web assets with files included in the changes.

19. The method of claim 15 , further comprising performing a security check on the changes before inserting the changes into the preview web assets.

20. The method of claim 15 , wherein the changes are associated with a component of the live user interface, wherein all links to the web assets associated with the component are overwritten or deleted when the changes are inserted into the preview web assets such that the preview user interface corresponds to the live user interface if the plugin were approved.