Not signed in (Sign In)
SkillShare - A place to discuss Web Standards and Web Design topics
Categories
Vanilla 1.1.9 is a product of Lussumo. More Information: Documentation, Community Support.
- Friends
-
Alex Giron, I am very disappointed in you for adding the "20 Pro Tips" article to the news section.
I would expect that from a Digg Newb, where I originally saw it, not from you, . That article is rubbish.
Tip 02
------
He mentions GoLive, which is known by everyone to extremely buggy, almost unusable.
He mentions 3rd party HTML editors that are not TextMate, TopStyle, nor HomeSite.
Tip 03
------
He mentions Netscape 4.x. I have not seen a Netscape 4 article on A List Apart for years. This is 2006.
Tip 04
------
That is a weak tip.
Tip 05
------
I can still read months old code. Other people can still read my months old code.
I do not write spaghetti code. The fix is to not write spaghetti code, not add comments to spaghetti code.
Tip 06
------
For Server Side Includes, one should use Server Side Includes. Why use PHP? That's like going after a mosquito with a bazooka (Monty Python).
Tip 08
------
Add additional divs to fix IE's box model. WTF?
Tip 09
------
Advocates inline CSS.
Tip 14
------
Advocates semantic markup contradicting tip 09.
Tip 17
------
Contradicts Tip 14 by adding the align attribute the img tag. -
- CommentAuthorPettyRider
- CommentTimeJul 20th 2006 edited
haven't read it yet, but it sounds pretty awful
I think all you need to become a web designer includes:
Text Editor - (for xhtml, css, js, php, ruby, whatever)
FTP - (for uploading files)
Photo Editing software - (graphic design)
Internet connection -
From what I've seen the bottom line (IMHO) is: It's an article for beginners to explain what you can do and some basic pointers towards how to do it (which is exactly how and why the vast majority of visitors come to the beauty as well, to see how things can be done and then look into how to do them). Coming straight out of the chute nobody gets it right and the flaws that this article would leave you are minor compared to what I'm sure we'd all agree would be the much larger issue of going back to tables/etc. for layout and structure.
It's not THAT bad, it's just aimed at beginners. -
Just read the article and I think it has good intentions. It isn't meant for most people who participate in this forum -- it is more of a starter-guide of sorts.
When you read it for what it is, it can be an extremely helpful tool. He doesnt proclaim that we all should use GoLive, he simply says that if you have it, use it "IF" you are intimidated by hand-coding HTML. I don't think CSS Beauty is just for the savvy designers -- its for those just learning and articles like that are helpful and insightful. They help make the initial steps in learning less frustrating.
For those that didn't read it, here is his 20 points
- Planning
- Do it by hand
- Stylesheets: importing vs linking
- Smarter gradient backgrounds
- Commenting
- Use simple PHP to build sites
- Set fonts using ems
- IE Box Model Hack
- Space saver
- Test, test and test again
- Format fundamentals
- The ‘title’ and ‘alt’ attributes
- The correct format for pseudo classes
- Use semantic mark-up
- Favicons
- Change capitalisation using CSS
- Wrapping text around images
- Universal character sets
- Print styles
- Learn from others
-
Sorry to be redundant; I appear to type three minutes slower than nifkin. It is the AIM distraction, i swear!
-
Tip 02:
Whether or not Golive is good is a matter of opinion.
TextMate, TopStyle, or HomeSite are not the only text editors in the world... I've used both Ace and BBedit and did not have any problems with them.
Tip 03:This can be used to your advantage to feed one stylesheet to modern browsers and another to Netscape 4.x, which would otherwise choke on more complex CSS
Believe it or not there are still people out there that use netscape4... what do you do with them? lowest denominator.. HELLO?
Tip 04:
Not weak, too bad IE doesn't work well with png, but using an image that is as long as the gradient and 1px wide, and being able to repeat that along the y or x axis is something I use often and is very handy.
Tip 05:
Commenting your code is very useful, even if your code is clean. You never know who might need to edit this code, comments help a lot cases where someone not so HTML or CSS savy might need to edit something.
Tip 06:
I use PHP for this purpose all the time... SSI is not enabled in every server.
Tip 08:
He mentions it's the easiest solution... which I tend to agree in some cases the use of an extra div might solve things quicker than trying to come up with the CSS for hacks for it.
Tip 09:
Pay attention, he says "Simply add the following CSS to your stylesheet".
Tip 14:
read my response to Tip 09.
Tip 17:
I actually agree with you on this one, and thought about it before posting a link to the artcle... However, using align is sometimes the quickes dirtiest way to achieve the text wrap effect.
These might not seem like good tips for you, but I'm sure somebody else might find them useful. Hell it might teach somebody a thing or two that they didn't know before.
Most of your replys are just personal opinion, which might mean nothing to many. -
Tip 03:
I'm sure that there are still people that use Netscape 4.0. But, these people are between 0% and 1%. They are the people that never upgrade. Should we support them until they die?
Tip 05:
I did not claim that I don't comment. I said that comments are not a solution for fixing spaghetti code; not writing spaghetti code is the solution. -
What if a percentage of your target audience is some school in some poor area, or in some undeveloped country where computers/browsers are no upgraded often, or at all?
yeah yeah I know, probably not many projects like that, but it could happen...
Regarding commenting your code... you can only be so descriptive with code itself... adding comments HELPS read the code...
sigh giving up here.
1 to 8 of 8