• HTML5-and-CSS3-What-About-SharePoint.pdf (968 KB)
• SharePoint-Goes-Mobile.pdf (1.4 MB)

I’ve been working with SharePoint for a long time now, and going beyond the basics is a challenging barrier to overcome. Many of the free online resources pertaining to SharePoint customization (and many of the paid ones) only cover the most simple of changes that you can make to your design. Learning how to implement a more comprehensive design is difficult, to say the least. In this new class, we are taking these advanced techniques head-on, and we’ll show you how to implement awesome changes like responsive layouts, comprehensive themes, and amazing enhancements using jQuery.

At least some experience with SharePoint customization, HTML, CSS, and JavaScript are highly recommended: we’ll be diving head-on into the world of SharePoint design. For more information, you can read all about the upcoming class here:

http://susqtech.com/training/classes/Pages/SharePoint-Designer-2010-Styling-and-Branding-Training.aspx

SharePoint Saturday: Virginia Beach

Can’t make it to the class in January? You’ll also see me speaking at the free SharePoint Saturday event at Virginia Beach on January 7, 2012.  I’ll be doing two sessions at this event: “SharePoint Goes Mobile” and “HTML5 & CSS3: What about SharePoint?”

http://sharepointsaturday.org/virginiabeach/

I’m very fortunate for having attended An Event Apart in Boston this week. I talked to thought leaders, design experts, tech gurus, and many more interesting and successful people during the event. I’m accustomed to being the only “UI guy” in the small organizations that I’ve worked for, so it was nice to meet other people who do what I do. One of the most interesting things that I took away from the event was the fact that design leaders are strongly pushing for web design to move in a new direction (well, I’m not sure if it’s fair to call it “new,” but the push is stronger than ever before).

What I mean when I say this is that many designers are asking you to stop using rounded corner techniques that require extraneous HTML (use the CSS property border-radius instead).  Stop using semi-transparent PNG images for background colors (use rgba instead).  Stop doing all those little extra things that you do in order to make sure your site is pixel-perfect on every single browser and operating system. Like I said, it’s certainly not a new subject to bring up, but I was surprised at the ferverous support behind it at the conference. I had briefly touched on this subject in my post about CSS rounded corners, where I seem to have agreed with these experts on a number of levels. My opinion is that you should never choose to increase page load times for everyone just simply to ensure that IE users can see rounded corners.

I think Dan Cederholm said it best when he referred to these little design touches (such as rounded corners) as “design rewards” for users who are using the most common OS/browser combinations. Don’t think them as design features, but rather as rewards for users who can utilize them. This makes your site faster, more flexible, and easier to develop. Dan is so passionate about this concept that he created a website to convey his feelings:

Do websites need to look exactly the same in every browser?

I’m not saying we should do away with rounded corner techniques entirely. In fact, I use my own Karate Corners all the time, but I do it when it’s necessary and appropriate.  If I’m working on my own project (where I am the primary stakeholder), I will most certainly go the pure CSS route, but as designers, we know that our clients don’t always agree. The most prominent argument against this concept is that our clients don’t really understand the benefits of using pure CSS to create corners and other design “rewards.” The only thing the client can understand is that Mr. CIO uses IE6 on his Windows 2000 desktop and he wants to see the rounded corners that were shown to him in the design concept.

It’s a difficult thing to manage client expectations, and sometimes it’s necessary to bite the bullet and give the client exactly what they want, even if you disagree with them. The best thing we can do is to make the benefits of this technique clear to the client, and hope that they can let go of the aging concept that your website has to be identical on all possible combinations of platform and browser.

There’s certainly a discussion to be had, and I’d love to hear your thoughts on the subject. Let the debate begin…