Just for the few of you who might not already be subscribed, 24 Ways -- an advent calendar of web dev artices in its fourth year of publication -- is in full swing again this year, and each year it seems there's at least one article that has a real impact on how I approach my work. This year, it might be this one:
http://24ways.org/2008/easier-page-states-for-wireframes It outlines a simple but possibly very effective way of illustrating the multiple states a page may have (logged-in, not-logged in, admin view, newly-created, etc.) using a jQuery plugin and some simple HTML classes. The article bills this as a great way to prep prototypes for backend developers' reference, but I could also see this being incredibly useful for the design review process, especially for showing the full impact of a redesign in progress to clients or other teams in your company. To the folks who do a lot of server-side dev, if you've read the article: do you see this as an effective way to take a handoff from an interface designer/developer, or do you think it just adds a degree of disorganization and/or cruft that you just have to remove later on? Ho, ho, ho - RL --~--~---------~--~----~------------~-------~--~----~ Our Web site: http://www.RefreshAustin.org/ You received this message because you are subscribed to the Google Groups "Refresh Austin" group. [ Posting ] To post to this group, send email to [email protected] Job-related postings should follow http://groups.google.com/group/Refresh-Austin/web/refresh-austins-job-posting-guidelines. We do not accept job posts from recruiters. [ Unsubscribe ] To unsubscribe from this group, send email to [email protected] [ More Info ] For more options, visit this group at http://groups.google.com/group/Refresh-Austin -~----------~----~----~----~------~----~------~--~---
