7/13/2012 5:22:35 AM
RE:ASPX Master Page for Portal Templates
What you describe is principle of a page template. Template is something “in common.”
You could use either user widget, which is bound per document and is not shared, or clone a page template as ad-hoc template. Then it will become independent and will not influence other pages.
If you want to show/hide some webpartzone classes dynamically, according to current page, you can do it via custom macro called in the Visible property for the given webpartzone element. Within the code, you can evaluate some context value (like current document name) and decide whether to show it or not.