Sorry, I have not had these things right in front of me for a few days, so I am not articulating it very well.

I guess elements pinned to the parent Frame (previously the artboard) works for me. All my issues arise when I nest a frames and all the inner elements pin to it instead of the artboard.

I also copied that element to use outside that frame visually, but forgot to move it from being a child of the frame, so when I moved the frame it came with.

In that example, and I only have examples from one project so far, in the article card, I moved the 'category' to the bottom left of the box not realizing it was still pinned and changed just the top padding and it got pushed out of view and I did not movie for a while.

Then after an hour of working on an element, I decide the padding needs to change, thats when this happens.

Sorry for the confusion, I missed the part where I was already trying to adapt and the issue was cause by human error.

I want the freedom to expand the boundaries of the element, even the top left corner, without the inner elements moving. So to work with the new system I am trying to get in the habit of turning pinning off as soon as I add an element, but I get into the flow and sometimes I miss a few.

(Still Yann just from another account) The main use-case I was excited about was to use a frame as a group with a background color. But early in a design I have no idea what type of padding I might be used. So maybe I am working on a header, menu, article card, , footer, anything with a background.

If you want the #TeslaTakedown #ProtestArt #PublicDomain source files to remix and create new stuff you can download a zip file with #Inkscape #SVG and fonts here: drive.proton.me/urls/9ACY0NE... 2/2

Yeah, I realized it still might be useful, but I don't need the full Linktree UI if I don't have to update it often. And if I don't need that, then they don't need my click data, so I just made my own: card.3n.design