I've ranted considerably about the reasons and benefits of the blueprint. Well, here's a further explanation.
As I've said ad nauseam, when the TSDG staff create your site, they work directly from the blueprint. As you know, the copy, the text for the headers, the navigation, the coding ... everything is taken from the blueprint.
This rant is to show you how the blueprint also tells the person who is actually building your site exactly how it is structured.
See the image above (you can see an enlarged version if you click on it).
This shows you how your site is arranged into directories. You are familiar with this type of menu tree from the files on your own computer. You'll see that several of those files are open.
A website is organised into 'files' and 'folders' in the same way you organise files on your own computer. You may have for example, a folder of photographs called OUR VACATIONS and within that, VACATION SUMMER 09, VACATION SPRING 09, etc. A website is organised in much the same way.
When your blueprint is created, all the files (pages) are put into the appropriate folders (directories). When your full graphics site is built, it is built in exactly the same way.
Another example of the blueprint working as a ... er ... blueprint.
Comments