Anyone here "web developing"?

[Tzesi]

Well I know some basic HTML and javascript.
Actually today I'm going to start learning HTML and CSS until I master those and then with PHP,MySQL and Javascript.

So does anyone here know anything about building websites etc.. ?

 

[Crayo]

RE: Anyone here "web developnig"?

Anonymous does a lot. I know HTML and tiny bits of CSS n JS. I want to use 2012 to expand my knowledge specifically in PHP and CSS.

 

[Sage.]

Nope, wish I knew more though.

 

[Tzesi]

Nope, wish I knew more though.

HTML is really easy to learn, why don't you start? I can provide you with a good ebook.

Anonymous does a lot. I know HTML and tiny bits of CSS n JS. I want to use 2012 to expand my knowledge specifically in PHP and CSS.

Never expected you to know HTML, nice .
Btw why don't you edit the google checkout button to open in a new page?

 

[Lith]

Yeah, I know a lot about HTML 5, PHP, MySQL, and some Python.

 

[Tzesi]

Yeah, I know a lot about HTML 5, PHP, MySQL, and some Python.

Well HTML 5 needs years to be completed and that's why I won't learn it, at least of now.I've also heard that not all the browsers support HTML 5.

Do you actually use it?

 

[Lith]

Hardly, I'll use it once all browsers are supported. But it's fun to use nonetheless. It's very cool.

 

[Crayo]

Surprised I know HTML? I'm offended.

 

[Lith]

Surprised I know HTML? I'm offended.

:stupids:

 

[Anonymous]

There's no reason why you shouldn't be learning or even using already developed technologies in the HTML 5 spec just because they're "not finished yet."

Now obviously I'm not expecting you to jump straight into HTML5 and CSS3 before learning the fundamentals, but keep an open mind and welcome this spec after you feel comfortable enough with the general structure of HTML and CSS.

One very easy to read resource is 'Dive into HTML5' by Mark Pilgrim. Sadly Mark recently left the internet, taking all of his connections and resources with him. You'll still find a mirror up on google of the free guide, but it's not likely to be updated as the spec progresses, so use it more as an introduction and not a realtime reference guide*.

Getting yourself familiar with the planned features will mean your website isn't at risk of getting left behind when the specifications are finished and everyone else has already been using things you're only just learning about.

Most modern browsers are already supporting a huge range of HTML5 technologies, so you'll be missing out on the power of the canvas, audio and even video elements just to name a few.

There's things you can be doing in your markup that may not take effect just yet for all browsers, but will leave you free to ignore changing anything once other browsers do support it.

Also, the CSS3 spec also technically falls under HTML5, and a huge majority of the features are already supported by most modern browsers; Web fonts, animations and transformations, advanced ways to select elements, etc. You'll be missing out on all of those features.

* If you're not afraid of heavy reading, the best source for up-to-date information on the HTML 5 spec is on the W3C website. W3C is in charge of developing the spec (and most other web related specs), so there really isn't a better resource to use as a reference than that one.

Good luck and have fun on your journey, and remember to always test your markup in all browsers (except maybe IE, unless you like the idea spending hours rewriting all of your code).

 

[Crayo]

That post was 10/10 because you insulted IE. Anyone use IE?

 

[Tzesi]

There's no reason why you shouldn't be learning or even using already developed technologies in the HTML 5 spec just because they're "not finished yet."

Now obviously I'm not expecting you to jump straight into HTML5 and CSS3 before learning the fundamentals, but keep an open mind and welcome this spec after you feel comfortable enough with the general structure of HTML and CSS.

One very easy to read resource is 'Dive into HTML5' by Mark Pilgrim. Sadly Mark recently left the internet, taking all of his connections and resources with him. You'll still find a mirror up on google of the free guide, but it's not likely to be updated as the spec progresses, so use it more as an introduction and not a realtime reference guide*.

Getting yourself familiar with the planned features will mean your website isn't at risk of getting left behind when the specifications are finished and everyone else has already been using things you're only just learning about.

Most modern browsers are already supporting a huge range of HTML5 technologies, so you'll be missing out on the power of the canvas, audio and even video elements just to name a few.

There's things you can be doing in your markup that may not take effect just yet for all browsers, but will leave you free to ignore changing anything once other browsers do support it.

Also, the CSS3 spec also technically falls under HTML5, and a huge majority of the features are already supported by most modern browsers; Web fonts, animations and transformations, advanced ways to select elements, etc. You'll be missing out on all of those features.

* If you're not afraid of heavy reading, the best source for up-to-date information on the HTML 5 spec is on the W3C website. W3C is in charge of developing the spec (and most other web related specs), so there really isn't a better resource to use as a reference than that one.

Good luck and have fun on your journey, and remember to always test your markup in all browsers (except maybe IE, unless you like the idea spending hours rewriting all of your code).

Nice post man.I'm really looking to master HTML 4 first and then go slowly to 5.
You didn't tell us what you use/know though?

 

[Lith]

There's no reason why you shouldn't be learning or even using already developed technologies in the HTML 5 spec just because they're "not finished yet."

Now obviously I'm not expecting you to jump straight into HTML5 and CSS3 before learning the fundamentals, but keep an open mind and welcome this spec after you feel comfortable enough with the general structure of HTML and CSS.

One very easy to read resource is 'Dive into HTML5' by Mark Pilgrim. Sadly Mark recently left the internet, taking all of his connections and resources with him. You'll still find a mirror up on google of the free guide, but it's not likely to be updated as the spec progresses, so use it more as an introduction and not a realtime reference guide*.

Getting yourself familiar with the planned features will mean your website isn't at risk of getting left behind when the specifications are finished and everyone else has already been using things you're only just learning about.

Most modern browsers are already supporting a huge range of HTML5 technologies, so you'll be missing out on the power of the canvas, audio and even video elements just to name a few.

There's things you can be doing in your markup that may not take effect just yet for all browsers, but will leave you free to ignore changing anything once other browsers do support it.

Also, the CSS3 spec also technically falls under HTML5, and a huge majority of the features are already supported by most modern browsers; Web fonts, animations and transformations, advanced ways to select elements, etc. You'll be missing out on all of those features.

* If you're not afraid of heavy reading, the best source for up-to-date information on the HTML 5 spec is on the W3C website. W3C is in charge of developing the spec (and most other web related specs), so there really isn't a better resource to use as a reference than that one.

Good luck and have fun on your journey, and remember to always test your markup in all browsers (except maybe IE, unless you like the idea spending hours rewriting all of your code).

I like to add a line that redirects IE users to Mozilla or Chrome

 

[Anonymous]

Nice post man.I'm really looking to master HTML 4 first and then go slowly to 5.
You didn't tell us what you use/know though?

I've dabbled in most web-related server-side languages (or simply just languages with web-related sub-features) like Perl, Python and Ruby (mainly with Ruby on Rails), but I have the most experience in, and feel most comfortable using PHP. I've chosen to ignore ASP, possibly if only just because it's a micosoft technology.

As for client-side, I'd class HTML, CSS and Javascript as required skills.