The Lurker's Guide to Babylon 5
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

welcome.html 6.5KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161
  1. <html>
  2. <head>
  3. <title>Welcome to the New Lurker's Guide</title>
  4. <map name="toplevel">
  5. <area shape="RECT" coords="0,0,99,23" href="/lurk/universe/intro.html" alt="Universe">
  6. <area shape="RECT" coords="100,0,199,23" href="/lurk/episodes.php" alt="Episodes">
  7. <area shape="RECT" coords="200,0,299,23" href="/lurk/making/creators.html" alt="People">
  8. <area shape="RECT" coords="300,0,399,23" href="/lurk/resources/online.html" alt="Resources">
  9. <area shape="RECT" coords="400,0,499,23" href="/lurk/reference/episodes.html" alt="Encyclopedia">
  10. <area shape="RECT" coords="0,24,499,31" nohref>
  11. </map>
  12. <map name="titlebar">
  13. <area shape="RECT" coords="0,0,370,31" href="/lurk/lurker.html" alt="Home">
  14. <area shape="RECT" coords="371,0,412,31" href="/lurk/search.html" alt="Find">
  15. <area shape="RECT" coords="413,0,454,31" href="/lurk/toc.html" alt="Index">
  16. <area shape="RECT" coords="455,0,499,31" href="/lurk/help.html" alt="Help">
  17. </map>
  18. <link rel=parent href="lurker.html">
  19. <link rev=made href="mailto:koreth@hyperion.com">
  20. </head>
  21. <body>
  22. <p align=center nowrap><nobr><img
  23. align=middle border=0 usemap="#titlebar"
  24. src="/lurk/nav/titlebar.gif" width=500 height=32
  25. alt="[Home]">
  26. <br><img
  27. align=top border=0 usemap="#toplevel"
  28. src="/lurk/nav/bar-none.gif" width=500 height=24
  29. alt="">
  30. </nobr>
  31. <h1>Welcome to the new Lurker's Guide!</h1>
  32. If you've visited before, you probably noticed that things look a wee bit
  33. different now. The Guide has undergone a near-total overhaul; no page was
  34. left untouched (unless we've missed something!)
  35. <p>
  36. Why the change? A few reasons. First, as the Guide continued to grow, it
  37. started to burst at the seams in places, and the need for a more
  38. structured organization (for instance, of the Other Resources section) became
  39. increasingly apparent. Though you may have looked at the home page
  40. and thought, "Aha, they've added a bunch of pictures to slow things down,"
  41. there's actually a considerable amount of change to the structure of the Guide.
  42. <p>
  43. If you've spent much time in the Guide in the past, you know it's big. Big
  44. enough, in fact, that it was often difficult to track down information you
  45. were looking for. The new look and feel should make navigating around the
  46. Guide a lot more straightforward. You always have a clear view of where you
  47. are in the Guide, with a consistent set of navigation tools. It's simple
  48. to hop from place to place, even to completely different sections.
  49. <p>
  50. And, of course, I'd be lying if I said appearance had nothing to do with the
  51. change. We think we've come up with a fairly pleasing look for the Guide,
  52. functional and appealing without being garish or hogging obnoxious amounts
  53. of bandwidth. A bit more on that below.
  54. <p>
  55. Who's "we?" Primarily, me (Steven Grimm) and
  56. <a href="http://www.zocalo.net/~danwood/">Dan Wood,</a>
  57. who contributed
  58. enormous amounts of time and energy iterating through literally hundreds of
  59. different design elements, seeing what worked and what didn't.
  60. <a href="/~funkster/">Larry Hastings</a>
  61. also provided some valuable usability feedback early on in the game.
  62. <p>
  63. <a href="http://diglib.stanford.edu/~mogens/">Christian Mogensen</a>
  64. put together one of the major features (and perhaps the most useful one) of the
  65. new Guide: the "Find" function. If you select the "Find" icon in the title
  66. bar at the top of every page, or follow the "Find" link on the home page,
  67. you'll be able to search every JMS message from Usenet and GEnie, as well
  68. as all the episode synopses and guide pages -- a wonderful tool for folks
  69. who're trying to figure out where the story's going before it gets there.
  70. <p>
  71. There are still some rough edges, places we haven't fixed up as well as we'd
  72. like; if you spot any truly embarrassing ones, please
  73. <a href="mailto:koreth+lgfeedback@midwinter.com">send me mail.</a>
  74. The new Guide will continue to evolve over time, just like any other Web
  75. site. If you have comments on the new graphics, you can also
  76. <a href="mailto:danwood@karelia.com">send mail to Dan.</a>
  77. <p>
  78. We hope you'll find the new Guide a worthwhile, interesting, and fun place to
  79. visit.
  80. <h3>Some technical notes</h3>
  81. <p>
  82. As a general rule, I've tried to stick to widely-implemented parts of the
  83. HTML 3.0 draft standard. The one exception you'll see nearly everywhere
  84. is that I use the Netscape extension to remove the borders from linked
  85. inline images. As soon as HTML 3 stylesheets are common,
  86. I will of course switch to them to control that aspect of the
  87. presentation. I have no desire to make the Guide browser-dependent.
  88. At the same time, using that extension improves the appearance of pages with
  89. lots of buttons so much that I thought it was worthwhile. (For various
  90. reasons, imagemaps aren't suitable replacements for the rows of buttons. Trust
  91. me, I considered them.) I've done my best to include meaningful ALT attributes
  92. everywhere so text-only people can take advantage of the new interface as well.
  93. <p>
  94. Those of you who're on low-speed or high-latency net links may object to the
  95. use of inline images rather than text. We've done our best to keep the
  96. navigational images as small as possible, and to reuse images wherever we
  97. can so you'll be able to take advantage of caching. You may find your visit
  98. speedier if you visit the
  99. <a href="nav/">Cache Loader</a>
  100. page before exploring (you'll also find a link to it toward the bottom of the
  101. home page.) In the
  102. near future, I'll also begin soliciting mirror sites around the world, so
  103. there'll be a fairly close copy of the Guide no matter where you are.
  104. <p>
  105. If you find the current setup unbearably slow, please let me know.
  106. Investigating a text-only or minimal-graphics mode is on my to-do list,
  107. and if there's enough demand I can do it before some other things. Be sure
  108. to tell me where you are and what your connection to the net is like; it
  109. may turn out that your needs will be met by a well-placed mirror site.
  110. (I can't guarantee you an answer, since I expect I'll be getting a lot of
  111. mail about this change, but your letter won't go unread.)
  112. <p align=right>
  113. Steven Grimm<br>
  114. October 16, 1995
  115. <p>
  116. <a href="whatsnew.html">To the What's New page</a>
  117. <pre>
  118. </pre>
  119. <p nowrap>
  120. <nobr><a href="/lurk/lurker.html"><img
  121. align=bottom border=0
  122. width=64 height=24 src="/lurk/nav/foot-station.gif"
  123. alt="[Home] "></a><a
  124. href="#"><img
  125. align=bottom border=0
  126. width=72 height=13 src="/lurk/nav/foot-pagetop.gif"
  127. alt="[Top] "></a><a
  128. href="mailto:koreth+lgfeedback@midwinter.com"><img
  129. align=bottom border=0
  130. width=80 height=13 src="/lurk/nav/foot-comments.gif"
  131. alt="[Comments] "></a><img
  132. align=bottom
  133. width=284 height=13 src="/lurk/nav/foot-bare.gif"
  134. alt="">
  135. </nobr>
  136. </body>
  137. </html>