FAO Web guide: detail

Web Guide home 1. Introduction 2. Web publishing basics 3. Planning 4. Content collection 5. Design 6. Construction 7. Testing 8. Launch 9. Maintenance 10. Writing for the Web Resources 1.1 FAO and the Internet: What is an FAO Web site? 1.2 Quality criteria of Web sites 1.3 An introduction to Web accessibility at FAO 1.4 Electronic publishing at FAO 2.1 Content quality 2.2 Roles in Web publishing 2.3 Web site quality clearance and continuity 2.4 Policy and legal matters 2.5 Language coverage policy 2.6 Web site traffic monitoring 2.7 Static and dynamic content 2.8 Really Simple Syndication (RSS) 2.9 Social Media Guidelines 2.10 Current server structure at FAO 3.1 What and (who) is the site for and what is it about?3.2 Define the Web site subject scope 3.3 Define your audience 3.4 Identify resources 3.5 How to track and share planning decisions 4.1 Developing a content inventory 4.2 FAO content repositories 4.3 Metadata 5.1 Review user needs 5.2 Defining information architecture 5.3 Prepare interface design 5.4 Define technical implementation 5.5 Tracking design implementation 6.1 Management of files/naming 6.2 HTML and coding 6.3 Use of style sheets 6.4 Graphics 6.5 Conversion of electronic documents 6.6 Language encoding 6.7 Link management 6.8 Printable pages 6.9 Providing access to search 6.10 Domains, URLs and aliases 6.11 Tools 7.1 Testing approaches 7.2 How to use the test environment 8.1 Launch checklist 8.2 Promotion 9.1 Quality assurance and routine checking 9.2 Update procedures for Web sites 9.3 Web usage analysis 9.4 Evaluation of Web sites 10.1 Writing a page of text 10.2 Organizing your text on the page 10.3 How to optimize content for search engines 10.4 How to write feedback, error messages 10.5 Quotations 10.6 Non-discriminatory language Checklists Acronyms Newsletter Guidelines Policies Procedures Web resources Tag cloud Contacts 2.3a Data ownership 2.3b Regulation of access to servers 2.3c Clearance of Web sites by OCP 2.4a Country names, flags and maps 2.4b The fao.org domain, subdomains and root directories 2.4c Use of FAO emblem and logos 2.4d Politically sensitive material 2.6a FAO Web sites: the user perspective 2.6b How to gather user information: user research 2.6c Designing for the user 2.6d Page size and downloading 2.7a Static content 2.7b Dynamic content 2.7c Content Management Systems (CMS) 2.9a FAO and Facebook 2.9b FAO and Flickr 2.9c FAO and Google+2.9d FAO and LinkedIn 2.9e FAO and SlideShare 2.9f FAO and Twitter 2.9g FAO and Wikipedia 2.9h FAO and YouTube 4.3a What is metadata?4.3b Why embed metadata in Web pages?4.3c How to embed basic metadata in the HTML head section 4.3d How to create or improve current metadata 4.3e FAO standards for encoded metadata 4.3f Metadata, search engines and their robots 5.2a Identify Web pages and subject categories 5.2b Define navigation 5.2c Define metadata and search requirements 5.3a Corporate visual identity 5.3b Web site design usability principles 6.1a How to use the FTP server 6.2a HTML and XHTML 6.2b Browser compatibility 6.2c New windows and pop-ups 6.2d JavaScript 6.2e HTML title and metadata tags 6.3a CSS and Web accessibility 6.3b Cascading Style sheets (CSS) and browser compatibility 6.4a Graphic formats 6.4b Use of images on the Web 6.4c Photos 6.5a Converting Word documents into PDF 6.6a Guidelines for language encoding 6.6b Multilingual interfaces 6.7a Linking files across languages 6.7b Links to the FAO home page, FAO copyright and AskFAO 6.7c Absolute and relative links 6.7d Avoid spamming on e-mail addresses 6.8a How to prepare print-safe Web pages using CSS 6.8b Other ways of preparing print-safe Web pages 6.11a Recommended editing tools for Web site construction 6.11b Graphics, document and conversion tools 9.1a Maintaining quality 9.1b Content freshness
	Web Guide > webguide > Resources > Newsletter
	See also in the guide All Web Guide Newsletter articles References and resources 7 usability guidelines for websites on mobile devices - Webcredible dotMobi Device Atlas 05/01/2012 Designing for the mobile web - Organizing content Background The mobile Web refers to accessing the Internet on mobile devices, such as smartphones or tablet computers, via a wireless network. Over the last few years, mobile Web usage has increased considerably, bringing with it issues for Web site developers. This includes: bandwidth issues, even with 4G significantly reduced screen size cross-platform compatibility problems together with the possibility of each device using any number of mobile web browsers. The Web Guide will be releasing guidelines on designing for the mobile Web, but in the meantime we will highlight some points to consider. Selecting and organizing content The choice of content has a profound effect on the achievement of the objectives of a Web site, this phase of selection and organization of content must follow a specific logic. The content selected must be correct and appropriate to the aims of the site, the style of the text must be suitable for the Web, the information must be appropriate and relevant, it must be reliable and up to date. The organization of the content should be made following the pattern of an inverted pyramid: the first level of content must essentially be a summary, while the details are placed in the second and third level pages. How to organize the content Adapt the content When planning for the desktop Web, content is generally designed for the resolution most generally used, i.e., 1024 x 768 pixels. In the mobile arena, however, this process needs discussing more thoroughly; there are many devices with very different displays as well as resolutions. To find out about the display characteristics of various mobile devices in circulation and then to design and present the content correctly, a useful tool called the Device Atlas can be used. This was developed by dotMobi Company and builds upon a large database of devices. Most common screen resolutions Content and usability The increasing number of people accessing Web sites on mobile devices can be given a much better user experience by following these guidelines: Reduce the amount of content. Single column layouts work best. Present the navigation differently from desktop sites. Minimise text entry. Decide whether you need more than 1 mobile site. Design for touchscreen and non-touchscreen users. Take advantage of inbuilt functionality that comes with mobile devices.