I'm back! Thank you @kristenpol and @jessebaker for your feedback, especially the clarification on the delete behavior.
Lauri and I met to review, iterate, and make design decisions on sections. Here's a quick overview of where we landed:
10/29 update: Designs have been updated to better reflect section behavior. Sections use groups of non-synced elements + components that have been saved for reuse in the library. When initially creating a section, a modal appears to name that section in both the library and on the canvas. That section can be renamed in the library; however, it will not be reflected on the canvas as they are not synced. Similarly, deleting a section from the library does not affect any instance of that section used on the canvas.
I also added a link to the Figma file if anyone is interested in getting a closer look.
gΓ‘bor hojtsy β credited bostonjillian β .
I agree with Laurii, as this is a similar pattern that we see across other visual builders. Here's an example from our last design mock:
catch β credited bostonjillian β .
This is a really interesting problem. While adding an additional filter is one solution to this problem, I wonder if ensuring that non-installed modules populate to the top of the search results is a simpler solution. An example of this pattern is similar to what exists in applications like Grubhub (where restaurants that are open populate to the top).
chrisfromredfin β credited bostonjillian β .