Bob Visser wrote:
The off-canvas in the portfolio template only uses 2 containers I think? Also you can reach way deeper nesting when including a subgrid for example.
The way I'm using it involves one container for the off-canvas-wrapper, one inside that for the off-canvas-wrapper-inner, and then inside of that go the rest of your containers (one for each of the off-canvas elements and one for the the rest of your page content), which is 3 deep. I'll look into the subgrids, but I personally prefer to work with containers.
For now, I've decided to make my project in two separate files and export them separately, then merge the code before upload which should allow me to set it up how I want. I'm just looking for a perfect tool to suit my specific needs, which isn't really a thing (nor would I ever expect it to be), so I'll work with what I've got.
Bob Visser wrote:Krysten Hohman wrote:
EDIT: Alongside this would be the ability to give names to our containers in the outline so you can quickly find the element you want to work on. This would be especially helpful concerning off-canvas or accidentally hidden items.
Yes, we have been discussing adding the class name(s) to the drop down or dom tree inspector. Good feedback, thanks, this should make it in the app one of these days
I'm excited to hear this. It will take the usability up a notch for sure.