Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
First - I understand what "Mobile First" means when it comes to designing websites.
At the company I work for, some of the developers are claiming that "Mobile First" in development means to write the mobile styles at the top of a CSS file then having desktop CSS override it via media queries instead of the other way around.
They claim this is the way to do it AND it will cut down on loading times in a mobile environment.
Does anyone have a definition on Mobile First for Development? Can anyone prove that writing the mobile style sheet before the desktop stylesheet (with the intent to have desktop override mobile) will improve loading times?
This is exactly how it has been explained to me before. There is a huge downside with this method though: IE8 and down do not support media queries, making your site look horrible. I use this workaround for those cases. You would just put that JS file inside of an IE8 statement.
I personally do not think this method matters that much. I believe that mobile-first is correct for design though since it will help show what is the most important in its most basic state.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 6 years ago.
Improve this question
I was able to create a web site 10 years ago with Microsoft Frontpage without learning anything, today with a copy of Adobe Dreamweaver CS6, I can't even figure out a way to change the font size of a simple text. CSS is the thing, so I went through the CSS tutorials in w3 and I get it now. It's a good idea, but It is also a good idea to kill creativity, ie all sites like similar, see screenshot below. It sucks floppy disks.
My questions will be:
Does web 2.0 really kill creativity?
Is there a "modern" web design application that I don't need to go into these CSS thing?
Is there a way to create a circular navigation menu like this using css? I want to have this menu in the middle of the page, and with a button on the corner to activate it.
No it doesn't
You don't have to use CSS. You can use inline styles,
but it won't be right. Using the CSS is a good coding practice and
you just need to learn it better.
Yes. If you google it, you'll find several links. Here is just some examples:
https://css-tricks.com/building-a-circular-navigation-with-css-clip-paths/
http://www.cssscript.com/pure-css-circle-menu-with-css3-transitions-transforms/
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
So this has been a topic of debate between me and another coder. We are using foundation for a project and he really likes following the system they provide. I like to venture out when it doesn't fit exactly.
An example was this was when I was doing the login form and I wanted a singular sized view that looks the same on every view. I created a login form with a solid width and centered with margins. He comes back to the code and puts it in foundation with large/medium/small columns. The justification was that they know how to handle responsiveness better than us. I just wanted stack overflow's opinion on this one.
When is it right to use a css framework and when should you go outside of it?
I guess on big projects, where you'd like to use each an every feature that a css framework provides, you should go for it. Whereas in small websites, using Bootstrap/Foundation would be a slow-down factor.
Otherwise if you are confident with building a responsive framework yourself, you should go ahead. But, if you feel you aren't take help from others in the form of css frameworks.
This question is way too broad and there can be many possible answers. The above is just my point of view.
First of all if you already have experience with one framework, unless you're doing it for research stick with it.
Otherwise you could check this comparison.
Also if you're using a web framework like Rails, Spring MVC, etc, check the integration status between the both frameworks.
Another point you should care is the community, and in my humble opinion bootstrap wins (as my personal perception).
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 9 years ago.
Improve this question
I see HTML5 mentioned often in discussions of responsive web design. Although I'm not sure why someone would want to use HTML5 for a simple responsive web design.
Are either of these statements untrue?
HTML5 is not needed for responsive web design
CSS and media queries will do the job fine
If you have a text only website, what is the benefit to using HTML5 for your responsive web design? It can't replace media queries. CSS works fine for fluid grids and images.
Here's some of what I'm referring to:
http://www.amazon.com/Responsive-Web-Design-HTML5-CSS3/dp/1849693188/ref=sr_1_2?ie=UTF8&qid=1383016419&sr=8-2&keywords=responsive+web+design
http://www.amazon.com/HTML5-CSS3-Responsive-Design-Cookbook/dp/184969544X/ref=sr_1_7?ie=UTF8&qid=1383016419&sr=8-7&keywords=responsive+web+design
http://www.amazon.com/The-Modern-Web-Multi-Device-Development/dp/1593274874/ref=sr_1_12?ie=UTF8&qid=1383016419&sr=8-12&keywords=responsive+web+design
Media queries were added in CSS3. Browsers that support CSS3 tend to support reasonable parts of HTML5 so they tend to go together but they are not technically dependent on each other.
If you want to use media queries and then id and class attributes on all of the elements to determine how they resize (or disappear) you are free to however proper semantics in general make styling easier for most people. Also there other benefits besides just styling. Proper semantic markup can help screen readers.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
How can I be sure that my web site can be viewed in smatphones (with different resolutions and screen's size) without any problem.
Is there a way to convert the couple html/css of a classic web site to be compatible everywhere.
Best regards.
I use http://mite.keynote.com/ to help test websites on mobiles that I don't have physically available. It's not perfect, but it's about the best testing suite I've seen and will definitely give you an idea of whether or not your design will work.
As for the actual design methodology, just make sure you don't specify anything in pixels or points, all dimensions should be specified with em's (or ex, etc) or percentages. From there, it's just a matter or trying things to see if they work.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
I use CSS to stylize my pages. I use % style instead of using px values. However, since I need to add several elements of different sizes in different positions, I end up spending more time in designing the layout than the coding.
I tried using a WYSIWYG editor but it uses px style coding. Can someone help me with a solution so that I can design the layout quickly and proceed to real part? I use WordPad right now.
The best thing to do is practice more. Get better at coding them, and reuse parts from prior projects where it makes sense.
There is no WYSIWYG tool that will save you time, for most projects. They all write garbage code, because editing with such a tool is a bit ambiguous. It is up to you as a web developer to write your markup and styles in a way that will be interpreted correctly across many user agents.