Skip to main content

Posts

Showing posts with the label Web Design

teeny tiny links can hurt usability

Consider the following Web site navigation: Home | Priorities | Giving | Council | Alumni Efforts | Foundation Challenge You might be able to guess that this is the main navigation for an alumni site of some school. But aside from Home , can you formulate a clear idea of where any of these links will lead? always crashing in the same car: recurring mistakes and misuses of the web Supposing your goal is to join this institution's alumni association. Which of these links would you follow first? Would you follow any at all? And what exactly is a Foundation Challenge, anyway? You see this all over the Web: critical navigation distilled down to as few words as possible--preferably a single word. Design teams hold meetings in which everyone struggles to come up with the right word to describe a category of activities, a diverse collection of information, a whole branch of services. It's mind-numbing work, and for a good reason: few single- or two-word descriptions ar...

replicate, replicate, replicate

Aside from the usual reasons why it's silly to duplicate static content from Web page to Web page, here is yet another: If your Web site has content copied and pasted from one page to another, it is very likely that Google is filtering out some or all of the involved Web pages from search results. The reason: The Google search engine does its best to optimize user experience by returning unique content. Because no one wants search results listing page after page of the same stuff. always crashing in the same car: recurring mistakes and misuses of the web Higher Education and other organizational Web sites tend to needlessly replicate content. This happens perhaps most frequently when information is repurposed as marketing material. The same content ends up appearing at its original source as well as at one or two marketing pages. Unfortunately, if this marketing material resides above the core content in the site hierarchy - and it usually does - it can end up replacing the core ...

the user feedback myth

Soliciting Web site user feedback. Posting online surveys. E-mailing listservs. Pulling together focus groups. Is this the long and the short of the plan for guaging the effectiveness of your Web site? If so, you will be rewarded with a wide scattershot of commentary, much of which is neither accurate nor usable. always crashing in the same car: recurring mistakes and misuses of the web In fact, implementing this ilk of "user feedback" can be detrimental to your site's health. Think about it. If you were overseeing the construction a classroom building, would you conduct focus groups and surveys to determine what materials should be used, where the doors and stairways should go, how strong the load-bearing walls should be? No? You would rely on qualified architects? Then why on earth would you open the door for individuals who have no understanding of how the Web works to step in and have a direct hand in your site design? When this type of free-form user feedback enters ...

how to make the worst of your content management system

I recently heard tell of the following activity, parading as content migration to an enterprise level content management system. I am not making this up: Copy large volumes of Web-content-to-be, page by page, into separate Dreamweaver files containing the design (created and sliced up in FireWorks) Copy/paste said Dreamweaver files into content wells of the content management system Repeat this activity ad infinitum until an entire Web presence is constructed in this fashion always crashing in the same car: recurring mistakes and misuses of the web When I heard this, something inside me snapped. Aside from the stunning inefficiency inherent in creating all these disparate Dreamweaver files, this activity points to a fundamental lack of understanding of what exactly a content managment system is. In the interest of quelling this misunderstanding in others, here follows a list of what not to do with a CMS: Dump a bad Web site into a good CMS. If your organization's Web presence is a ...

customizing wordpress

I've been experimenting with creating custom themes in WordPress, one of which is the interface of this blog. WordPress is remarkably easy to customize.

the case for incremental redesign: part ii

If you are in any way responsible for a Web site, you should have some understanding of the principles of Extreme Programming . Cultivated as a discipline of software development, it is a combination of ensuring that designs remain uncomplicated, centering changes around user requirements, and employing the concept of the "Whole Team." The result is that small changes are released as they are needed - and endorsed - by the client. Not surprisingly, Extreme Programming speaks well to Web management. Consider its core values: simplicity, communication, feedback, and courage. These are the bedrock incremental redesign. Simplicity - Integrate all site changes in small doses. Avoid tectonic disruption of the entire Web presence. Document faithfully, but do not get bogged down in over-documenting. Or overplanning. Leverage reusable objects. Better yet, get the site into a content management system - one that is scaled to its requirements. Eliminate unmanageable code morass by fol...