Re: [EXTERNAL] Re: Fluid Grid for Responsive Design [WAS: Re: Express, React, Node.JS]

On Thu, Mar 1, 2018 at 10:41 AM, Kelly Cookson <KCookson@xxxxxxxxxxxx>
wrote:

Are you talking about the simple fluid grid page?
http://www.kellycookson.info/fluidgrid/

Yes.

I do change my font sizes for my personal website:
http://www.kellycookson.info/ The fonts on this page and the pages in the
navigation drop-down should be easier to read on mobile devices.

Yes, that's easier to read on mobile devices. It's also more responsive to
screen size.

I have a question, though. In the CSS code, you set the .w2 class to a
specific width.

* Suppose I want a row where the first column takes up 25 percent
of the page and the second column takes up 75 percent of the page.

* Then, in the next row, I want three columns that each take up 33
percent of the page.

* Then I want another row with two columns, where each column takes
up 50 percent of the page.
One of my web pages actually does this: http://www.kellycookson.info/
service/index.html. Using your system, wouldn't I have to define a number
of CSS classes, not just the single .w2 class set at a specific width?
Right now that seems like the advantage of a fluid grid framework. But I'm
not very familiar with your approach. Maybe I am missing something.

In regard to your question about assigning various fixed percentage widths
to column classes, that's what caused the compression and tiny font problem
in your "fluidgrid" page. On your main page you resolved that problem by
using a @media rule that overrode all the column widths to 100%, which
enabled them to flow left-to-right, top-to-bottom, on small screens.

Wouldn't you agree that using a @media rule to override and change the
attributes of a base class adds a layer of complexity to your .CSS?
Something that might lead to unexpected behavior in a different
application? Something that might confuse a novice?