I think the confusion here is in what is “pinnable/unpinnable” content.
In this case the stack in question a customer 3rd party stack where the images are configured in the info-sidebar. i.e. the images are part of the settings of the stack, not a part of the content.
This is a pretty subtle detail and for those that learn by example a little better, I made a video about what exactly is unpinnable:
https://dl.dropboxusercontent.com/u/433436/forum/Unpinned.mp4
In summary:
-
content (text/images you add to the main edit area) CAN CHANGE in each use of a partial – to do that you unpin that content.
-
settings (stuff that you edit in the sidebar) CANNOT CHANGE in each use of a partial – they just stay the same everywhere.
But what if I want to change the settings
Watch the video. At the end I discuss using an unpinned one column stack to wrap around other content – that content can be completely unique to each partial instance.
But why is Stacks like this?
For simplicity. Sometimes powerful features decrease the ease of use of software and you have to eliminate some things to keep things usable by mere mortals like us. That’s the case here. Earlier similar features of Stacks 2 (like globals) allowed changing both content and settings. It becomes very complicated very quickly. This made the learning curve to using those features very steep.
As partials are better understood no by many users, I will likely add this feature back in (perhaps in a somewhat limited way) in the future if I can find a way that doesn’t complicate things too much.
Isaiah