Hi Nathan,

I have reservations about using something like Meyers CSS reset.
People get accustomed to their browser's default styles for input
elements and such, which seems to appeal to them.

You make a legitimate point.

I think different developers have different philosophies on this matter. This developer likes CSS resets for his purposes: http://ageekandhisblog.com/css-reset-vs-normalize-css-learn-the-difference/. Other developers prefer normalize.css, which appears to be easier for debugging: https://the-pastry-box-project.net/oli-studholme/2013-june-3. Yet another developer recommends leaving both CSS resets and normalize.css alone and creating your own foundation: http://jaydenseric.com/blog/forget-normalize-or-resets-lay-your-own-css-foundation.

Do any of these approaches appeal to you?

The Meyer CSS reset worked well on my first responsive site. However, the team that manages our corporate web site uses normalize.css. So I think I want to have all of the above approaches in my toolbox--be ready to use a CSS reset, normalize.css, or create a custom CSS foundation.

BTW - I did make one minor modification to the Meyer CSS reset in my web site. I removed lists (ol, ul) from the first reset statement. This keeps the browser's default indenting of lists. I kept the Meyer CSS reset to list-style:none because I wanted to play around with the list styles to see which ones I liked best. I ended up going with the browser default list styles, so I could have removed the list-style:none from the Meyer reset as well.

Eric Meyer says this about his CSS reset:
"I don't particularly recommend that you just use this in its unaltered state in your own projects. It should be tweaked, edited, extended, and otherwise tuned to match your specific reset baseline. Fill in your preferred colors for the page, links, and so on. In other words, this is a starting point, not a self-contained black box of no-touchiness."

Thanks,
Kelly


-----Original Message-----
From: WEB400 [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Nathan Andelin
Sent: Saturday, July 04, 2015 4:45 PM
To: Web Enabling the IBM i (AS/400 and iSeries)
Subject: Re: [WEB400] 7 lessons from my first responsive web site

Kelly,

Thanks for sharing. Part of the appeal of your site is that it encapsulates a meaningful message and a cohesive theme. Layout and navigation are simple and nothing detracts from the site's subject matter. Overuse of images, animations, and effects may detract, for example.

I visited first from my cell phone, then my iPad, then my laptop.
Adaptations from small to medium to large screen sizes do not disappoint.

Responsive design is one of my current interests and it's nice to see some convergence of our parallel tracks.

Regarding device emulators, I have gained some benefit from the one included with Chrome developer tools, which are part of the browser.

I have reservations about using something like Meyers CSS reset. People get accustomed to their browser's default styles for input elements and such, which seems to appeal to them.

Perhaps the next step in your site's evolution may be to fit it into a single page paradigm. That would eliminate the need to embed common CSS, JavaScript, and navigational elements in every page, and make the transitions from page to page more fluid.

HTH,

Nathan.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list To post a message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/web400.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.