-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestion: add "custom responsive grids" tutorial #50
Comments
I've got this next on my list. This will be done soon. Thanks! |
Because Gantry 5's responsive grid is managed so vastly differently, and without any need of direct coding on the part of the user, we will likely not be doing a 1:1 equivalent documentation for G5. We do provide YAML documentation describing the setup of a layout preset, as well as documentation on breakpoints and other important features that will help someone customize their layout. Closing this at this time, however we will continue to expand on documentation regarding Gantry 5's layout structure. |
Just wanted to note that as far as creating responsive content within an article or module, we are working on this documentation. I'll follow-up with our dev team in the morning. :) |
Yup, that's what I was looking for. In my experience it's not just as easy as saying "use the size-xx" classes on your divs because they get changed at mobile size to 100% and you probably don't want that to happen on your own content within a module or particle. Looking forward to outcome of follow-up - thanks. |
Hey Ryan would this help [url= http://www.rockettheme.com/forum/gantry5-for-joomla/252864-dang-where-was-that-guide-now?start=80#1263651 ][b][color=#FF0000] |
In Gantry 4 we had this documentation:
http://www.rockettheme.com/docs/joomla/basic/creating_responsive_content.md#custom-responsive-grids
We could do with equivalent documentation for Gantry 5 for those members wishing to create responsive grids within their articles and modules.
Sorry if I missed this somewhere put I couldn't find it.
The text was updated successfully, but these errors were encountered: