Just a quick one - one of the main issues i’ve had with using grid is the classes that are auto generated on export (long strings of arbitrary numbers). I’ve found these also are often re-generated when exporting again, which makes tricky when updating the CSS on external CMS’s.
Is there any change to this for the new grid update?
Quick question: Do you review the beta requests before you send an email with the access to the beta?
I sent a request with both of my accounts and didn’t get an email back.
I’m jumping on my chair right now because I’m so hyped and can’t wait to get access
Hey @webflow / @Lindapham can you briefly explain what happens when the current grid 1.0 gets merged with the new one in the upcoming update? I’m currently building a site using grids, should I wait or is it perfectly fine to continue using Webflow’s grid 1.0 ? Will there be any complications?
Shouldn’t be any. All the grid items that you have set up manually will be treated as such. In case you will want them to be automatically placed you’ll have to re-insert them.
Problem with placing image into a grid-block that is manually placed: you can’t drop directly an image into div-block of a collection:
so solution that is not good: click first the div-block of the collection, second: click onto the image-block into the side panel
please check it out
Karel
Note: working whitout shift+drop manually should need to work with shift+arrowDown/Up/Left/Right… because with lang grids that is more simple look to Portfolio an ‘What we do’ in the website I reconstruct www.beastanimation.com
Hey @Hype - everything you build today or built in the past will work smoothly after we make these updates. Grid 2.0’s main feature is the introduction of autoflow positioning for grid children, in addition to the manual positioning option you’re currently using.
After the release, you’ll be able to switch grid items between being manually positioned or autoflow positioned — while with the current version, you’re only able set use manual positioning.