# Having a design survive a theme change **URL:** \ **Category:** RapidWeaver Classic\ **Created:** [March 19, 2019, 12:48pm UTC](https://forums.realmacsoftware.com/t/having-a-design-survive-a-theme-change/25859 "2019-03-19T12:48:39Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![PaoloT](https://avatars.discourse-cdn.com/v4/letter/p/ee59a6/32.png) [@PaoloT](https://forums.realmacsoftware.com/u/PaoloT)\ **Post date:** [March 21, 2019, 11:50am UTC](https://forums.realmacsoftware.com/t/having-a-design-survive-a-theme-change/25859/5 "2019-03-21T11:50:35Z")
I found an older discussion trying to approach an issue that looks similar to mine. After some tests, it seems the original poster decided that too much nesting could have been causing problems. Therefore, having separate parts unrelated in the page could have been a safer solution. On the contrary, someone invited him to continue thinking to nested stacks as a full page layout. > [@Foundation, TotalCMS and Stacks 3 Partials](http://forums.realmacsoftware.com/t/foundation-totalcms-and-stacks-3-partials/4538/6): > > Thanks Brad that information is very helpful. I need to rebuild my my master site. The idea was to use a 1 Column Stack as a Container for the Layout, then create the Partial and unpin the stacks that needs to have changes at the new page - but I see, that don’t work. I think that create a Partial for each part of the Site will solve the problem… Paolo --- _[View the full topic](https://forums.realmacsoftware.com/t/having-a-design-survive-a-theme-change/25859)._