Presentation is loading. Please wait.

Presentation is loading. Please wait.

Copyright © 2006 Quest Software Best Practices for Web Content Eric Myers, Director, Internet Marketing Ed Mauss, Manager, Marketing Communications Chris.

Similar presentations


Presentation on theme: "Copyright © 2006 Quest Software Best Practices for Web Content Eric Myers, Director, Internet Marketing Ed Mauss, Manager, Marketing Communications Chris."— Presentation transcript:

1 Copyright © 2006 Quest Software Best Practices for Web Content Eric Myers, Director, Internet Marketing Ed Mauss, Manager, Marketing Communications Chris Peters, Search Marketing Manager

2 1 Good Web Writing A factor in customer satisfaction Essential to search engine optimization Helps visitors make better, faster decisions Three aspects: –Orientation: how information is organized on a page –Information: how clear, concise and correct the content is –Action: how the content helps visitors navigate >You'll succeed by putting yourself in the shoes of your site's visitors – our customers and prospects.

3 2 Remember: Writing for the web and writing for print are quite different: –79% of users scan the page instead of reading word-for-word –Reading from computer screens is 25% slower than from paper So: a web page should have scannable text and use best practices proven to increase usability for customer

4 3 The F-Shaped Pattern Left to right: an "about us" page; a product page; a search results page Heat maps from user eye-tracking studies of three web sites: red= areas most viewed; yellow=fewer views; blue=least viewed; gray=no views.

5 4 Best Practices: Pages Overview pages: Brief summary of challenges and our solution, then topic statements linking to more background, if needed Title and/or subhead repeated on each page: for context, so page can stand alone Active, concise language: use the second-person (you) and as few words as possible; avoid jargon Images that add value and dont interrupt message (consider thumbnails linked to full size and aligned right) Consistent organization

6 5 Best Practices: Paragraphs Precise, unique titles Meaningful subheads (not clever or cute ones) every one to two paragraphs Brief paragraphs (chunks of information), with just one idea expressed in each Text hierarchy no deeper than four levels (title, subhead, body copy/bullets, teaser links)

7 6 Best Practices:Text Avoid all caps, italicized sentences and underlines except for links Use bold or color to emphasize key words Keep lists to no more than 10 items Use link text to describe whats next; avoid Click here No unnecessary words (e.g., existing and underlying) and redundant sentences Simple words: diverse not heterogeneous

8 7 Telling a Story Consider this as lead paragraph on Stat page: Towson University, of Baltimore, Md., was seeking a comprehensive change management solution for its PeopleSoft environment and chose Quest's Stat® for PeopleSoft. The result? It has increased its development teams productivity by 65 percent as well as dramatically improved the IT team's response time to change requests.

9 8 Huh????? [Our] service-oriented management solutions provide a modular and future-proof approach to managing highly diverse and widely distributed IT infrastructures [The product] integrates service impact management with event processing automation to build a service model that maps IT components to the business services they support, consolidating, enriching, and correlating events, as well as determining root causes and the impact of events on business services. [The product] provides a proven suite that adapts to processes to align identities and access requirements, offering capabilities that include user administration & provisioning, password management, Web access management, directory management & visualization, federation, audit and compliance

10 9 Quest.com Content Samples of Good Pages –http://www.quest.com/jprobe/http://www.quest.com/jprobe/ –http://www.quest.com/foglight-release-manager/http://www.quest.com/foglight-release-manager/ –http://www.quest.com/application-and-services-management/http://www.quest.com/application-and-services-management/ –http://www.quest.com/intelligent-messaging/http://www.quest.com/intelligent-messaging/ Real-Time Critiques –Volunteers?

11 10 Advice from Pros Eric Myers: Always write content that is going to be helpful to customers. Does it answer the obvious questions they will want to ask? Andrew Kordek: Be strategic, relevant and credible. Ernest Hemingway: Remember – prose is architecture, not interior design. Isaac Asimov: "Try to write reasonably well". –Don't agonize over every little word when you're drafting content –Get your thoughts down, starting with an outline. –Fill in the outline –Fine-tune to check the flow of information and cut extra words –When you've finished that, then do it again Remember, everyone needs an editor, no matter the skill level or experience. –Marcom queue for new/revised pages –Ongoing review of current pages

12 11

13 12 Additional Resources Jacob Nielsen, Web Guru: Dont Make Me Think: Elements of Style (Strunk & White): Any bookstore or Amazon.com Great article about writing for the customer: Customer Focus Message Calculator – The We We Monitor : Key word popularity measurement: Key word competitiveness measurement:

14 13 Questions and Comments?

15 14 Appendix: Before and After Before Since the database is at the core of todays mission-critical applications, it is essential to an organizations success that it is available and performing as well as possible. DB2 LUW is at the heart of many mission critical applications and with that comes high level of expectation that the database remain available and performing well under many types of conditions. To prevent database downtime requires that data be collected about the database and the associated tiers. After DB2 LUW drives many mission-critical applications, so it must be available 24X7 and perform well under all conditions. To ensure this, you need the tools to easily collect, view and act on detailed data about the database and the associated application tiers.

16 15 Appendix: Before and After Before SQL Server DBAs are often faced with making changes to their SQL Server database environment. These changes can be driven by a number of different factors: changes to the application the database is supporting; configuration changes to improve database performance; business-related changes due to data retention requirements, data security issues; or other internal and external initiatives. What makes managing change even more daunting is that changes in one area of the database could affect changes in another area. After SQL Server DBAs must often make changes to their SQL Server database environments. These changes can be driven by:Enhancements to the application the database is supportingConfiguration adjustments to improve database performanceBusiness-related mandates for data retentionData security issues Managing change can be daunting because changes in one area of the database could affect changes elsewhere.


Download ppt "Copyright © 2006 Quest Software Best Practices for Web Content Eric Myers, Director, Internet Marketing Ed Mauss, Manager, Marketing Communications Chris."

Similar presentations


Ads by Google