Posts by GravityDept

686 posts Magento Elite & Gravity Maker
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $125,000+ on Envato Market
  • Located in United States
  • Has been part of the Envato Community for over 4 years
+3 more
GravityDept says

Ticket #QLB-490-55284

Seems to only happen in Chrome. Safari and Firefox work on Mac.

686 posts Magento Elite & Gravity Maker
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $125,000+ on Envato Market
  • Located in United States
  • Has been part of the Envato Community for over 4 years
+3 more
GravityDept says

The “You can reply to the comment here:” link is broken in comment notification emails. Started noticing this a week or two ago. It just redirects to a white screen.

686 posts Magento Elite & Gravity Maker
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $125,000+ on Envato Market
  • Located in United States
  • Has been part of the Envato Community for over 4 years
+3 more
GravityDept says

@ ShivakaminiSomakandarkram — That’s a legitimate problem for any widely adopted platform. It’s not pretentious to observe that and design an experiment to test it. It is pretentious to call the experiment pretentious and add nothing of value. Ahem.

686 posts Magento Elite & Gravity Maker
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $125,000+ on Envato Market
  • Located in United States
  • Has been part of the Envato Community for over 4 years
+3 more
GravityDept says

Not sure where you were going with that because I see three different examples. I’m assuming the markup is identical if you’re using a grid framework or a custom grid.

In that case, to manage the full viewport range you’d need to employ a grid framework AND a custom grid. That’s two design systems. That’s bad for maintainability and extensibility.

It would be better to NOT use the framework and just use a custom grid, so you can target the specific content in play. Then you only have one design system applied to one set of content. That gives you more control for writing very little new code.

The only reason frameworks don’t dictate grid splits below 768 is because some content can’t compress well (but some can). So they pick a high value that ultimately leads to a less-than-useful layout in many cases.

That’s what I’m advocating not applying the framework if you intend to have non-linear layout beneath 768px. Otherwise it’s fine to use the generic grids a framework provides. The argument I’m making is for a separation of concerns. Both approaches “work” technically.

686 posts Magento Elite & Gravity Maker
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $125,000+ on Envato Market
  • Located in United States
  • Has been part of the Envato Community for over 4 years
+3 more
GravityDept says

As they say, if you have to ask…

Personally, it completely depends on the attitude of the customer. I’ve exchanged 20+ emails with some customers because they were pleasant to help. Others not so much, and they get a totally different quality of support.

It’s better to be kind than clever or good looking.

686 posts Magento Elite & Gravity Maker
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $125,000+ on Envato Market
  • Located in United States
  • Has been part of the Envato Community for over 4 years
+3 more
GravityDept says

@ QBKL — That’s not as efficient or maintainable. What you’re suggesting is using one design system (grid framework) to manage a content’s layout above 768px and using another design system (custom per content ID) to manage its layout below 768px.

I’m saying just use the grid framework where it applies, but where it doesn’t just write a one-off grid tailored to the content across all breakpoints. Then you never have two systems affecting one piece of content. It’s the single responsibility principle.

It’s not about feasibility, it’s about simplifying the architecture.

686 posts Magento Elite & Gravity Maker
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $125,000+ on Envato Market
  • Located in United States
  • Has been part of the Envato Community for over 4 years
+3 more
GravityDept says


Bad: placing everything on a grid that dissolves under 768px, which almost every responsive grid system does.
Which is why we have classes, IDs, media queries for. If grid dissolves below 768px it means you basically get a full-width box ready to be targeted and restyled as you wish through your own CSS. Correct me if I’m wrong…

Why bother? Just build the right grid in the first place. It’s only two lines of extremely simple CSS. The point was a grid framework doesn’t solve all the needs of a complex system. It can for simple sites, but there’s an expectation to always use the grid if you have it and that’s negatively impacting some layouts.

686 posts Magento Elite & Gravity Maker
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $125,000+ on Envato Market
  • Located in United States
  • Has been part of the Envato Community for over 4 years
+3 more
GravityDept says

Good: using grid principles for consistency.

Bad: placing everything on a grid that dissolves under 768px, which almost every responsive grid system does.

It’s better to write some generic grids, but tailor the majority to the content at hand. Rarely can that can be bundled into a theme or pattern library.

686 posts Magento Elite & Gravity Maker
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $125,000+ on Envato Market
  • Located in United States
  • Has been part of the Envato Community for over 4 years
+3 more
GravityDept says

Walk over the Brooklyn Bridge, use the subway, Top of the Rock, 9/11 memorial, Apple store pilgrimage.

686 posts Magento Elite & Gravity Maker
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $125,000+ on Envato Market
  • Located in United States
  • Has been part of the Envato Community for over 4 years
+3 more
GravityDept says

Stay on Earth. Obey gravity.

by
by
by
by
by
by