Note that there are some explanatory texts on larger screens.

plurals
  1. POCreate grids with arbitrary columns counts in different responsive layouts
    primarykey
    data
    text
    <p>I have an Rails app I am building with Foundation. I am having trouble figuring out how to display an arbitrary number of columns per row and keep it responsive in the small/medium/large layouts.</p> <p>For example, lets say I have a model <code>Department</code> which has many <code>Employees</code>. I am trying to build the department page and display a list of the employees in the department. One department may have 10 employees. Another may have 6. It's arbitrary. </p> <p>I want to do 4 columns in <code>large</code>, 2 columns in <code>medium</code> and 1 column in <code>small</code>. (See my wireframe below). However, the columns need to be wrapped in a <code>div.row</code>. This requirement means I have either of the following two situations:</p> <ul> <li><strong>Case #1</strong> (<a href="http://jsfiddle.net/ag3Ys/" rel="nofollow noreferrer">jsfiddle</a>) I have 2 elements per row and the <code>large</code> layout only gets 2 elements because it is getting cleared by the <code>.row</code>.</li> <li><strong>Case #2</strong> (<a href="http://jsfiddle.net/jeffrod/YQ33R/1/" rel="nofollow noreferrer">jsfiddle</a>) I have 4 elements per row and the columns don't clear properly when in the 2-column, <code>medium</code> layout because there are 4 in a row.</li> </ul> <p>This seems like it should be a pretty standard situation but I cant seem to figure it out. How do I do this? Is Foundation the wrong tool?</p> <p><img src="https://i.stack.imgur.com/hFB9H.png" alt="enter image description here"></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload