Iām still confused though what grid markup heās forcing you to use though. I mean if you were going to use a two column layout, grid framework or no grid framework, youāre going to want (e.g. two columns float) youāll want a parent and then two children elements.
Foundation and Bootstrap all āforceā that on you but youād do that same approach anyway! Thatās what I donāt understand.
And no you are correct most donāt allow fractions, and while itās amazing jeet offers this (since itās annoying that 12 columns must be spread over 100%) itās not exactly something Iād switch over to for in exchange of all the functionality of Foundation or Bootstrap.
What HTML could you possibly want though that frameworks force you to avoid? Thatās what I donāt get. A two column floated layout will make you (if you know what you are doing) have a parent and then two floated elements side by side. A framework encourages that idea with their structured approach.
Iām still waiting on an example that shows where this isnāt feasible with frameworks.
Again, not trying to be rude but I just donāt see what frameworks are restricting here. Give me an example.
Also, using grid layout basically only sets the width and floats - leaving design and everything else up to you.
I might very well be having a brain fart and there is an obvious restriction that Iām not thinking of! Not saying Iām right here at all; genuine curiosity here. Wasnāt aware of any HTML restriction with frameworks.
If youāre adding ācontentā directly into a div that has some utility classes for a grid system, like Bootstrap or Foundation. Youāre tying that content to that grid.
The idea is to abstract the grid from the content, a separation of concerns, so that itād make it more portable if needed. Jeet getās rid of the need for the grid div elements as itās in the CSS (Sass) which Iād suggest is a lot easier to edit than picking through various divs with grid classes added to it for responsive web design.
Obviously there are two trains of thought here in regards to using a grid system within your markup or within your CSS. I, personally, prefer to add it to the CSS, like Jeet does.
Ah ok I understand what you are trying to say now. I understand that.
I think the article does a poor job of explaining this (actually I donāt think they explain that at all) so thanks for the help on that.
I do understand the usefulness (albeit Iām not sure how OFTEN this would come up? Iāve managed everything so far without the need for this but I can imagine situations which this would have been useful) that Jeet is offering here. Thanks!
I wasnāt trying to insinuate I had conflicting views. Merely stating that I failed to see the authors point (again, because no explanation was given so I was left to imagination.) I actually do see your point and agree there are cases where this is useful.
I pitched an article to them (just an idea; I didnāt say Iād write it) over 3 weeks ago, even sent Sitepoint a message on FB, and the survey that Sitepoint gave out, I EVEN sent it in there (with also a request to check their e-mail)) but STILL no one has responded. Iām a bit offended/shocked that no one appears to be checking their e-mail; or at the very least I didnāt get a response.
It wasnāt a ground breaking article anyway; just something that I saw the internet lacked on.
Thanks for taking the time to read the article. The advantage of Jeet is its flexibility. Frameworks such as Bootstrap and Foundation require extra markup (div) that can be difficult to maintain. Of course, you can make your code more efficient if you customize them. On the other hand, Jeet doesnāt need any additional div or customization. All you have to do is to define a class name and then apply the mixins you want to it. So, the complexity is in CSS which is handled by mixins.
Hey Ryan ā which address did you send your pitch to? I havenāt gone through all survey results yet (there are a lot), but if youāre still interested, you can pitch an article directly to me via PM here, or to @Adam, or to one of the SitePoint editors (like @sturobson or @louislazaris).
Thanks, Stuart got in touch directly. And it turns out that it was 11/17/14 that I originally sent the e-mail so itās beyond 2 months; not 3 weeks like I thought .
I had e-mailed an undisclosed e-mail (donāt want to say who I sent it to publicly) but I only pitched an idea; didnāt want to actually write it myself. Those who have read my own website articles probably are frustrated at my writing .
Back to the topic at handā¦
@georgemarts, I am able now to see what flexibility this offers. It saves some of the ground work that youād have to otherwise do. I can appreciate how this will be useful. Thanks for the great article (although Iām holding true that I think it should have been explained better; but Iām just a disgruntled person since I didnāt get it right away; thatās my own fault)
Keep up the good work.
@Ophelie Stuart (in this thread) messaged me and I talked to him. If you really want to know who I sent it to, then you can follow up with him. I donāt want the person to get in any trouble.
Agreed. This doesnāt really seem like anything new to me. I wrote a āgrid on demandā like this some time ago called Ignition and popped it on GitHub, although I donāt manage to do much development in anger any more to actually use it. Susy is great, too.
However, having more people work on tools like this is generally a good thing - It gives developers more choice, and can lead to better ways being found to deal with the obstacles we face every day.
Great article - thanks for explaining Jeet. The use of fractions could help solve a few design problems.Thereās a misconception about Bootstrap mixins though.
Bootstrap comes with mixins such as .make-row(); and .make-sm-column(6);, as well as .make-sm-column(6,0); to remove padding from column declarations. Declare those at the correct breakpoints and you donāt need to declare col-sm-6 in your HTML.