Content PlacementWhenever possible, all of the flash content (including text, links, images, additional SWFs, audio, and video) should be loaded from files external to the SWF. The most common exceptions to this would be embedded fonts and basic framework graphics. External Content PathsThe paths to all external content should be referenced in an XML data file. The path for the XML data file should be referenced in the HTML/JavaScript embedding code. Paths to content and data files should not be hard coded in the flash files except as default values for development and testing purposes. The directory structure of the flash files and related assets should be completely flexible. Assets may need to be hosted in a different directory structure than the developer(s) create. There should be no developer-imposed requirements for related files to be contained in the same directory. Cisco's Web EnvironmentFunctional tests should be done on Cisco.com early in the development process. This can help identify relative path, cross-domain, or server configuration issues when they are usually much easier to resolve. Cisco's web environment has many restrictions. Don't make assumptions about which technologies or file formats will work for a given project. Ask us even if it seems like the answer is obvious. Alternate ContentA non-flash, and preferably screen-reader friendly, version of the content should be delivered prior to launching the flash content on Cisco.com. Cisco uses "Jaws" as a test for screen-reader content compatibility. Metrics DataNearly all flash content on Cisco.com needs to send metrics data for reporting purposes. The web metrics team should be engaged early to ensure that metrics functions are built into the flash piece. The web metrics team can be contacted at webmetrics@cisco.com. Embedding MethodSWFObject 2.1 should be used to load flash onto Cisco.com. Non-flash alternate content should be placed within the DIV tag where SWFObject will load the flash content. Video & AudioWhenever possible, Cisco's standard flash video player should be used to play back both video and audio content. Cisco's current standard flash video player is a customized version of the JW Media Player. For information on its use, contact embeddedvideo@external.cisco.com. Video files should be in FLV format. Encoding specs will vary based on individual project requirements. Audio files should be in MP3 format. CaptionsVideo and audio content should have the capability to display captions or a text transcript. Since captions and transcripts are sometimes only available after go-live, the captions functionality should be easy to enable and disable without flash code modifications. GlobalizationMany flash projects are repurposed globally and in multiple languages. A representative from the global web team should be consulted during the requirements gathering phase on how the flash can be developed to maximize the ease of re-use, translation, and localization. PreloadersA preloader should be used whenever the user will experience a noticeable delay while content is loading. There's not necessarily a specific file size above which a preloader is required. Testing over a non-corporate internet connection (such as Cable or DSL) is an appropriate indicator for where and when a preloader is a good idea.
|