If you're doing all of this within the content tree you can use content inheritance to do the heavy lifting for you. It would really be no different than having a locations section in your site. This is what I've done in the past for similar items:
- Create a page type (locations) and add all the necessary fields to it, avatar being one of them
- Create a page template and add webparts to it to display the details of the location as your design requires.
- In this page template, we'll call it Locations Master, you'll add a repeater in place of where the image goes to dynamically get the image from the page type. You'll set the path to
/{0}/{1}. This will dynamically get the actual location each time no matter what location you are selected on (as long as your path is /Location/location-1 format).
- Also in the Locations Master page template you'll add a pages placeholder webpart. This will allow you to dynamically nest another template under it and choose to hide or show webparts on the Locations Master template by setting the show for child pages property.
This may or may not work as you'd expect for the workgroups but it gives you an idea on how it could work. Good luck!