Ask us about:
- Foundation 6.4
- Foundation 7
- XY Grid
- How to get involved
- Webpack integration
- Responsive web design
- Front-end development
- The future of the web
Message from the host 💬
What an incredible AMA! Thank you all so much for spending your afternoon with us, we hope we were able to answer all your questions fully and share a few insights along the way. We want to extend a special thank you to our contributors and in particular, the Yetinauts who have been working incredibly hard to take Foundation to the next level. YOU GUYS ROCK! We’re stoked about the future of Foundation, and we’ll be sharing some of our thinking very soon our blog.
💻 Be sure to bookmark http://zurb.com/blog and check back frequently in the next few weeks for updates!
✉️ Sign up to the Foundation Insider to get the inside scoop before anyone else: http://foundation.zurb.com/learn/foundation-insider.html
📚 The best way to learn Foundation is directly from our team. We offer two live online courses that will build up the in-demand front-end development skills employers are looking for:
• Intro to Foundation: http://zurb.com/university/foundation-intro
• Advanced Foundation: http://zurb.com/university/advanced-foundation-training
⁉️ If you have questions, want to get involved, or need help, feel free to reach out to us @ZURBFoundation on Twitter or through email: foundation (at) zurb (dot) com!
👋 Thanks again and keep in touch!
Thanks for introducing me to hashnode!
For how long will the the majority of websites stick to floating grids, before moving on to new methods like CSS Grid and flexbox? Is it just Browser Support that holds us back, or do developers just need more time to adapt it? Lemme hear your thoughts!
The extra effort you all put in with XY Grid is really appreciated. I'm looking forward to it!
Yay! Yetti is here... :D
Hey Zurb team, Great work on the foundation framework. I have been using both Foundation for Sites and Foundation for Emails.
I think some work is needed in Foundation for Emails. Is there a way to get in touch with the development team and fix issues quickly? Something like intercom support would be really good.
I know it's an open source project and intercom would be very expensive to the team. But, an easy way to get solutions will be good.
I built myself a WordPress starter theme, using the base underscores & Foundation 6.3.*, using Codekit to compile & minify. 6.4 seems to be completely different in the architecture & files. How much work am I likely to encounter to update my starter theme to foundation 6.4?
Is 6.4 same as version 7? Why are some people already talking about version 7 when 6.4 is yet to be launched on Tuesday? To me a lot of difference exist between versioning 6.4 and 7. If version 7 will launched any time soon, why launch 6.4 on Tuesday, rather than waiting for 7?
Can Zurb create some sort of tool or workflow for easier upgrades from 6.3 to 6.4 to 7.x etc?
EDIT: Yes! "Migration" is a more correct term than "upgrade" here. Thank you!
EDIT 2: As for other full on tools that need to deal with changes to Foundation versions - I'd point to CoffeeCup's "Foundation Framer" and Humane Technologies "Pinegrow" apps - both need to update every time there's a new version. As to how they do that internally, I've no idea. I only know they somehow update the apps. Perhaps the existing site projects break - both are GUI front ends to help the user visualize as they build.
One of the stated goals of v7 is to be "accessible in every framework." I have high hopes that this will be the case and 6.4 is a big step toward making that possible. In the meantime, though, it can still be tricky to architect a front-end codebase around, say, Foundation and React without two different repos, two different builds, etc... which can get confusing pretty quickly. Given the amount of overlap in tooling, dependencies, and structure, I would love to see a harmonious single project codebase that would allow me to build out Foundation and React (or any other js framework without having go to great lengths to glue them together. Any thoughts on what that might look like or how I should organize projects for use with React?
I'm really excited to see webpack and babel making it in to the project :D Now that we have webpack available for bundling, though, will Foundation continue to rely on Gulp or is there a plan to transition fully to webpack for scss bundling and browser-sync as well? Also, jQuery's great and all but, again - now that babel's in the mix, is it possible that we'll see a movement away from jQuery in favor of vanilla es6 any time in the near future?
There are many questions here already about 6 vs 6.4 vs 7. My question is, with the big changes in 6.4, and the assumed changes in 7, will the concept be to keep the naming conventions of the grid the same throughout, with minimal changes needed; or will Foundation use new classes with each new grid (flexbox vs a future css grid, for example)?
Love Foundation (6) and integrated it into a major overhauled manufacturer website recently, with Kentico Enterprise.
In the very beginning of the overhaul, we used Orbit (5) for the product page slider and realized it had some issues that caused some headaches (we got it to work cross-browser however). Ultimately we switched to the recommended slick slider. It's great, but I noticed Oribit is still documented under v6 Foundation. Is it being supported again?
Congrats on 6.4 :D The road map says that "high quality integrations" for react and angular "exist" for 7. Could you talk about what those integrations are or where I can find more info about that effort? I'm using the react-foundation package (it's nice) and I wonder if that's the integration that "exists" or if there are other more robust projects that refers to. Thanks!
This may be elementary, I'm somewhat a newbie. I noticed that jquery.js & what-input.js files are not included with 6.4, are they no longer needed? Also, there's no index.html in the download, is the HTML Starter Template still valid? It does reference the above 2 files.