I am so excited to be a part of Web Administration. I look forward to sharing information and my experiences through this blog. Feel free to give feedback by commenting on any of our posts.

As a journalist, my curiosity is never ending. I constantly like to “be in the know” and I think you should too! There are constantly new developments in technology and new applications for existing technology, and the best part about it is - we’re just touching the tip of the iceberg.  I’m looking forward to my time here - sharing information with you about the things we are doing in Web Administration and all around the Gator Nation.

And just so you know, we love feedback! So please feel free to comment on any and all of my blog posts.

Sounds great, right? It gets better.

The Summit Series is entirely online, meaning you can skip the hotel reservations, the 5-hour flight delays and those little bags of peanuts the airlines give you while they secretly lose and/or destroy your luggage.

Our office purchased the meeting pass and watched the Summit in our conference room, but attendees are certainly allowed to participate from the comfort of their own home or office.

The CSS Summit, the first installment of the Summit Series put together by Christopher Schmitt and Environments for Humans, featured CSS-specific presentations from some of the top names in the business like Molly Holzschlag, Dave McFarland, Jason Cranford-Teague, and others.

Here’s a summary of some of the key takeaways from each of the speakers at the conference:

CSS and Troubleshooting IE6 with Kimberly Blessing

“Support does not mean that everybody gets the same thing”. Kim led her presentation off with this quote because it’s such an important point to remember when troubleshooting cross-browser inconsistencies. *cough* IE6 *cough*

The goal when troubleshooting IE6 is not to match the look pixel-for-pixel, but rather to try to preserve a similar and enjoyable user experience across all browsers. In order to do this you need to do determine what level of support you are going to give IE6, decide which factors will influence when support for IE6 will end, and document a technical strategy to cover coding techniques for dealing with IE6.

Kimberly also mentioned End of Life messages (EOLs), which are basically scripts that display a message prompting IE6 users to upgrade their browser. She mentioned a few sites that use this technique like YouTube and Facebook, but she didn’t officially condone them

Object-oriented CSS with Nicole Sullivan

Nicole’s three-prong web development philosophy is simple:

1. Work out of respect for the design
2. Designers make our code beautiful and clever on the outside as it is on the inside
3. Respect the original design vision. Consistent design = clean code = fast site

Object-oriented CSS is all about leaner code and easier maintenance. Elements like headings should be treated as the most basic reusable building blocks of a site. Anytime you can reuse them, you’re getting a performance freebie. You should avoid location-dependent style because it can easily lead to code bloating down the road.

One great suggestion to promote lean code Nicole shared was to create modules. In a module you would separate an object’s code into two parts: 1. A container and the content and 2. The structure and skin. One class solves the browser bugs, positioning, presentational elements and generally does the heavy lifting of CSS. The other class “skins” the object, adding the style. The goal is very predictable skins in which the complexity is absorbed.

Tomorrow’s CSS3 Today with Dave McFarland

Dave covered some of the highlights of CSS3 including advanced CSS3 selectors as well as some of the CSS3 properties that you can begin using today. the key takeaway frmo his talk was that while the modern browsers (Safari 4, Firefox 3, Chrome, etc…) are beginning to ship with increasing CSS3 support, these versions of the browsers simply don’t have a great enough market share to warrant widespread use of CSS3.

In short, use CSS3 at your own risk. If you believe your target audience is likely to use browsers with adequate CSS3 support, then using CSS3 properties and selectors to enhance to your designs may not be a bad idea. However, if your analytics show that many of your users are still browsing with IE6/IE7 and older versions of other popular browsers, then it’s probably only going to hinder your sites usability.

The key is to use CSS3 sparingly to progressively enhance your designs while making sure that you don’t alienate or hinder your users that aren’t using a modern browser with CSS3 support. For more information on CSS3 selectors and properties, visit http://www.css.info or www.w3.org/Style/CSS/current-work.

CSS & Fluid Width Typography with Jason Cranford-Teague

The main focus of Jason’s presentation was the future of web typography. Scalable Inman Flash Replacement (sIFR) has been the popular pick for accessible custom typography since its release in 2005, but its drawbacks, namely its requirement of both Flash and javascript to be enabled in the user’s browser, clearly leave the door open for something better to come along.

Enter the @font-face rule.

The implementation is simple. Embed the font of your choice with the @font-face rule, then call it with the font-family property like you would any standard browser font. The problem lies in the file formats. Modern browsers, besides IE, are beginning to support the Trutype (.ttf) and OpenType (.otf) formats (IE only supports Embedded Open Type .eot). However, fonts are considered intellectual property meaning, of course, that embedding them through @font-face is subject to EULAs (End User License Agreements).

Another stalemate for the time being? Perhaps, but these are exciting times for the future of web-native fonts. Jason pointed to Small Batch, Inc.’s Typekit service, Kernest.com, and Cufon as evidence that a new era in web typography is coming soon.

CSS & Flexible Layouts with Zoe Gillenwater

Why bother with flexible layouts? Zoe Gillenwater asks, “why not?”

The benefits of flexible layouts are pretty clear: they respect the user’s preferences, they increase usability, readability and accessibility, they maximize typographic control, and they take advantage of screen real estate while preserving design proportions.

Reaping these benefits, however, takes a good deal of planning. It’s important to realize that not every comp can be successfully turned into a liquid or elastic layout. You have to design the site differently from the start, taking into consideration which features are not compatible with a fluid-width layout such as fixed heights for anything containing text.

When putting together a site with a flexible layout there are a few general techniques to stay away from: irregular shapes defining a text area, text matched with images that can’t expand, and horizontal alignment across columns, just to name a few. Instead, try using scalable images or images that can slide along with the resizing of the window.

CSS & Coding Layouts with Stephanie Sullivan

Great design is all about overcoming challenges and making things work. A website is made up of its content; the information, sales, marketing, etc… If the content is the core of any website, doesn’t it make sense the layout of that content is key in any website’s design?

Think about these questions when drawing up your next wireframe or comp: How do you best present this content? How do you want your user to interact with this content? Make sure to be logical and create a flow through the site.

CSS & The Open Web: A Brave New World with Molly Holzschlag

Last, but certainly not least, was Molly Holzschlag. Author of over 30 books on Web Design and related topics, Molly brought her experience in to discuss the ever-growing importance of open standards on the web. As the popularity of web apps continues to grow, standards are becoming more and more vital.

Designing with a foundation in standards not only helps to ensure more positive user experiences across the board, but can also prove to be cost effective. Some of the benefits of designing with standards are that it provides infrastructure and process, it offers a variety of content delivery options and allows for effective scaling and growth.

Next Up: The DIY Summit

If you missed out on the CSS Summit, don’t worry, the Summit Series continues on Sept. 17. with the DIY Summit. According to the event description, the DIY Summit is “for those who go it alone, designing and managing entire websites by themselves, either by choice or by chance. Whether they are freelancers or in-house webmasters in a larger company or university, our goal for the DIY Summit is to streamline the workflow for those who don’t have a team to fall back on.” Register now! You won’t be sorry.

Thanks to Al Kirby, a designer working in University Relations; Prof. Dave Stanton in the College of Journalism and Communications; and Ken Schwencke, a UF journalism senior.

34 Amazing Tumblr Themes, Twitter could never look this good!!!

Thirty-four cool themes for Tumblr.

Typeface Anatomy and Glossary

A glossary of common type terminology.

101 High Quality CSS And XHTML Free Templates And Layouts

A ton of free (and beautiful) templates.

Twitter And (Not) Monetizing The Attention Economy

A piece from Business Week about how a lack of advertising is not smart for Twitter.

Service-Oriented Architecture: Using Our APIs Internally

In Stanton’s words: “NYTimes builds its site by using its own API instead of direct-fed from the CMS. Love this concept of ‘eating your own food.’ Great SxSW panel on this topic.”

On D.C. Streets, the Cellphone as Lifeline: Homeless People Turn to Technology to Track Assistance and Opportunities

An article on how essential some technologies have become.

Atlas: a visual IDE for desktop-like web apps

From the site: “With its Atlas IDE for building web apps in Cappuccino and Objective-J, 280North is set to make web app programming as easy as drag-and-drop. Ars talks with 280North’s Ross Boucher to get the skinny.”

Steve Pritz, University Registrar and Chair of the IT Advisory Council Data Infrastructure Committee (ITAC-DI), recently sent an email on this topic to the ITAC-DI membership.

He noted: “As we implement this change, it is sobering to find more than 56,000 references to grades in UF web sites and links.”

He asks for assistance reviewing those pages and updating the information.

The UF catalog always has the current policy on grades.

Additional information on minus grades  is available at

• Provost memo (DDD) regarding minus grades
• Frequently asked questions about minus grades
• Minus grades presentation

You can reach the Office of the University Registrar by e-mail or by phone at (352) 392-1374.

Spring of Web will take place April 10 at Emerson Alumni Hall and feature speakers who will discuss Web-related issues, including advanced HTML and CSS, site analytics, search engine optimization and usability testing.

The speakers come from both outside and inside UF’s Web community. They have varied backgrounds and include consultants, developers and communication specialists.

Visit the official Spring of Web 2009 site for updates and to RSVP (required).

After some searching, I found this and a list of a few others I would recommend to the web community.  If you find more, let us know!

• Web Standards Solutions by Dan Cederholm
• CSS Mastery: Advanced Web Standards Solutions by Andy Budd, Cameron Moll
• Research-based web design & usability guidelines

Thanks, Ben!

We are looking for someone with one to three years of experience in communications and Web publishing. A good command of Web development tools - HTML editors, Web accessibility testing, and content management - is essential. Our ideal candidate will also have a strong eye for detail, be able to work autonomously as well as a team member, and possess outstanding editing skills. A good sense of design as well as general familiarity with current Web standards and best practices is also desired. Applicants must be currently enrolled UF students.

What You’ll Be Doing:

• Web content updates
• Implementing design into code
• Copy writing, editing
• Training content authors

Required Skills

• XHTML/CSS
• Copy editing
• Web Standards
• Web Accessibility
• Customer service (email, phone, and voice-mail)

Bonus if you know

• Perl, Javascript/jQuery, PHP
• Photoshop/Graphics
• WordPress
• Subversion
• Mac OS
• Catalyst

What You Get

• Between 10-20 hrs/week
• $8 - $10 per hour, depending on experience
• Interesting coworkers
• To work at the football stadium. Seriously.

To Apply: send a cover letter with resume, qualifications, and links to at least two sites you’ve created to webmaster@ufl.edu.

What you seemed to enjoy:

• The food. Classic Fair catering provided both breakfast and lunch for the event.
• Meeting others who work on the web. This was huge for us, as our intent was to make sure that the UF web community got a chance to connect and converse with each other.
• The informal, but inspiring tone.
• The overall quality of the presentations.

What we need to improve or add:

• Transitions between speakers. We agree and will try to develop better ways of moving from one person to the next.
• More advanced topics. It would seem that our community is clamoring for CSS, HTML and scripting information. Sounds good to us! We wanted to make sure that everyone was aware of CSS and got a taste of it. Now that you have, we’ll look into advanced workshops on these topics.
• Better preparation for attendees. We could have done a better job of explaining that this event was meant to get everyone “back to basics”. We will make sure to prep everyone for our next event, which will likely be in the spring.