For pricing, please ??
see our
detailed pricing chart, or ??
call 1-800-555-8866 to speak with our knowledgeable sales staff.
Figure 10-2. The example on the left shows frequently asked questions in a single, linear
format; the example on the right demonstrates how that same list can be shortened with
simple expand/collapse JavaScript functionality.
This, like the earlier example, presents the questions like a table of contents, but can still
be used when JavaScript is disabled. It also gives each FAQ entry a unique URL, such as
www.acmetextiles.com/faq.html#customfabric, so that they can be individually bookmarked
or referenced from another page.
When a FAQ begins to expand, the section must branch out beyond a single web page.
One central list of all questions can be maintained on one page, but each question links to
a separate, individual web page for the entry, so a user might arrive at a URL like
www.acmetextiles.com/faq/custom-color. This flattened architecture allows for a more
scalable system.
Bear in mind that if a multi-page hierarchy becomes necessary, the content begins to
stretch the fundamental definition of a FAQ, and we find ourselves reaching the next stop
along the knowledge management train ride: the knowledgebase.
Pages:
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444