/prog/ - Programming

>>1764
im learning some bootstrap, I think maybe learning a framework for css can help. Though im not positive but well see

>>1774
Yeah, bootstrap is good enough if you don't want to bother with web design but you don't want a 90s looking page. Still, it's so widely used you page may look bland and generic. I'd suggest taking a closer look at alternatives like Ink, HTML5 Kickstart or Pure.

>>1775
yes as I started learning bootstrap it became obvious that its been used ALOT. Even some of the websites I visit have been using it but I didnt notice before so it has become generic.
But lets say if I build a generic website with it of a fake company and show it to an employer while im looking for work, will that be a good idea? Or should I just learn other frameworks like Pure to stay atleast alittle original?

>>1756
I'm a pretty bad designer too. It's a different skillset. But I'm also a firm believer that websites are properly done when they are simple. Like http://motherfuckingwebsite.com/.

But when you deal with clients, you can always copy another design or use templates and so on.

Anyone ever used dreamweaver? What you think? Easy to pick up? Is it a tool you will never stop using?

Draw it on paper first.

Always draw your page on paper first, at least three times. The first time should be the fastest. Jot down the general shape of things. Write/draw utilities like menus and links.

Now start over, and do it better.

Finally, start over and do it better, but this time, add in effects. Cool stuff that makes your website better, like ad placement, CSS stuff, like shiny shit or extra flat metro shit, or whatever you need that will make your site unique.

Now make it with HTML and CSS. It's just boxes within boxes.

>>1810
Don't bother.

Best to just do it by hand. It's easy once you get good at it, but when you get into complicated backend stuff, you'll be happy you made it yourself.

>>1812
This this this. Lay everything in paper first, define the containers, draw complicated parts separately. After that you should begin coding everything.

MathML proves that the W3C are retards, you will wrestle with CSS until you get an idea of it.

>>1812
> It's just boxes within boxes.
It has insane inheritance rules though which can completely break your boxes.

Another idea is to get the website readable without any CSS at all to get an idea on your priority of information.

>>1943
>nother idea is to get the website readable without any CSS at all to get an idea on your priority of information.

This.

You're probably trying to write them elegantly more than make pretty pages.

It's a programmer trap. Go to a page you find pretty view source on it. It will look like complete garbage vomited by dreamweaver. Because whoever made it was clicking around in a wysiwyg editor looking at the page until it looked pretty not an ide looking at html.

>>1756

Rule no 1.

Choose the right font for your page. Yes font type makes the most important expect of the beauty in your webpage. Google apis have a whole bunch of fonts for you to choose specifically to be use for your website , if you don't mind using google apis, download the whole set of the fonts and explore each of them. Choose which one you like most.

Rule no 2.

Know all the features in css. Explore each of them on what it can do to your website. Some of notable features that I like are the fade in/out and transition.

Rule no 3.

Be creative, creative in web designing doesn't mean it has be all full fledge featured css. It can also be in a form of simplicity and neat. It's like ricing your computer desktop theme, I bet your desktop computer look really ugly then.

the YouTuber codetheweb has tutorials, and his websites look good.