Using foundations for testing
Ok, so previously I covered some of the benefits of using a foundation project. I forgot to go into detail about how we plan to use the foundation for testing.
If you’ve set things up with all your templates in a foundation project and put all your content into a child project, you’re probably thinking that you’re wasting a project. Not so. Have a think about it for a second and it may become clearer. You’ve got a nice testing area before you push a change out to the live projects, so why not make use of this fact?
Create some example pages in your foundation project and put example components anywhere and everywhere they are usable. For example, we have two components and two containers; container one can only have component 1, whereas container 2 can have components one and two.
This gives us an easy way of testing any changes to an individual component or a stylesheet without having to go add the component to a page each time.
Without some careful management your foundation projects will get into a mess; which is why one of our unlucky developers is going to have to do this to our two foundation projects sometime soon 
|
|
|
|
|
 |