Saving a site as a Blueprint

### What

I just saw the video about adding a Blueprint site and very much like the new feature which I look forward to trying out.

The next step to make it even easier creating a Blueprint would be to save a site as blueprint.

### Why

Create a site and saving it as a Blueprint would making Blueprints a lot easier. As one could setup various aspects of a site. Themes, plugins, pages, posts, various settings etc. Save it as a Blueprint and the next time one goes to create the identical setup is already in place.

### How

A mockup. Showing a dedicated Blueprints section and a Save as Blueprint feature.


### Taking it a step further

One could even move the Blue Print feature into a backup feature. As suddenly one can begin to create multiple backups using a more advanced BluePrint feature. Having a kind of versioning history of a site.

The issue names no files, tests, or entry points. Start by reviewing the existing Blueprint creation flow and the attached mockup, then determine the scope needed to save a configured site and restore its themes, plugins, pages, posts, and settings; done would include an agreed design and verified behavior.

Written by the indexing model from the issue text.