How to Add Meta Tags and Scripts  -  Styles  -  Links to MSN TV® PageBuilder Head Tags INTRODUCTION      This website is a simplistic demonstration of my suggestion for correctly adding meta tags, style sheets, and javascipt to an MSN TV® document head tags. I have correctly added several additional meta tags, provided space for styles and scripts, and different body tag code. This is in response to several posts from naysayers that suggest that we cannot access the PageBuilder document head tags to correctly add meta tags, styles and scripts.      It is possible to add additional meta tags, style sheets, and javascript code in the head tag of an MSN TV® PageBuilder. It can be done by a slight change to the "comment method" posted by h17@webtv.net in the news:alt.pagebuilder.help news group. Beth Candy's step-by-step tutorial called "Advanced Editor for Page Builder" thoroughly explains the implementation of h17's "breakthrough" for enhancing WebTV PageBuilder options. In case you missed it, Pwilliamandx@webtv.net put H17's orignal post on a website, and recently followed-up with a list of PageBuilder Advanced Editor Method tutorials from several PageBuilder experts.

SOURCE CODE      The validated source code will be close together and hard to read. I could not space the code out, because every time you put a space return in the large text box, even if it is in the head section code, you put a space on the top of the webpage which pushes the body text down the page, leaving a long blank space at the top of the page, depending on how many spaces you enter in the code. Therefore, I had to type the head tag code without a return key space. This creates a problem if you "View Source" (click "View" on the "Menu Bar," select "View Source") with a computer – the source code appears in long lines across the full window width, requiring you to scroll through all the screens to the right to view the code. Just highlight and copy the source code, paste into a "Note Pad" (or Word Pad) document, edit, preview, and print-out the code. Or, a shortcut, just click "Print" on the window toolbar while viewing the source code screen, and the code will be automatically loaded into a notepad window and printed out.

PROCEDURE      To add additional meta tags, styles, and scripts inside the PageBuilder head tags, you must disable the PageBuilder built-in closing head tag so that the document head section can be extended into the large "Add text" box, where you can add additional meta tags, style sheets, javascript, base href, and links. This is done by not putting the closing head tag in the title text box as suggested by h17 and Beth's Advanced Editor. Instead, I suggest that you put in your title, a closing title tag, and your beginning comment tag in the title text box. This will block-out and disable the built-in head closing tag that immediately follows the title text box in the PageBuilder code. I repeat, do not put a closing head tag in the "Title text" box. A closing head tag will be added in the large "Add text" box after the additional meta tags, styles, scripts, and links. In summary, the comment tag entered after the title closing tag is extended to the large "Add text" box which disables the PageBuilder built-in closing head tag, body tag, and beginning body table tags.      Print this page for reference. Take this webpage to your favorite validator to view and print the source code. Take note of the PageBuilder built-in tags that are disabled by being inside the comment tags. The blocked built-in PageBuilder code will appear between comment tags, like this: <!-- begin code block....(blocked code here)....end code block -->. These comment tags begin in the "Add title" text box and end at the beginning of the large "Add text" box. Verify that the added meta tags and other head section content is correctly within the added head closing tag which I added in the large "Add text" box. I put several comments in the added head section for explaination. To verify that I have added additional meta tags, you need to check the "Check search engine compatibility" option when you validate this page. Dr. Watson validator said: "You have a 19-word description of your site in a META tag, good! You have a nice, short list of 58 important keywords in a META tag, good!"That proves that this method for adding meta tags works because my added meta "keywords" are acceptable to the strict HTML code syntax checker of the Dr. Watson Validator.      Also, I used a <style> tag in the extended head tag to define the backgrounds for this webpage. I used a background gif from the Netscape website, and a blue-white bgcolor to display until the background gif was loaded. I also used a <script> tag in the extended head tag to define my "welcome" and "goodbye" message alerts as functions. The welcome message alert function had to be defined in the head tag so I could "call" it in an "onLoad" event handler in the new Advanced Editor <body> tag. The appearance of the background gif and welcome message alert verifies that the extended head tag HTML code syntax works OK for adding CSS style sheets and JavaScript!      When you view the source code, please remember my comments above about replacing the PageBuilder table "template" tags that are blocked out by the Advanced Editor comment tags shown at the top of the code and replaced near the bottom of the code after the new body tag! The replaced table tags must exactly match the blocked tags! Always make sure your table tags are in correct and legal HTML syntax; ie, matched in pairs of required opening and closing tags, in proper sequence, and properly nested with each other and other display formatting tags! If you have table tag syntax errors, your webpage may not be displayed, or will not appear as you intended. MSN TV® browsers are still somewhat lax with HTML syntax for many tags; but, the new browser upgrades, especially our client 2.6.1 upgrade; all Netscape browsers, and the new MSIE 5.5 upgrade are very sensitive to, and strict, about HTML table tag syntax! If you have problems with your PageBuilder webpage not being displayed correctly, check your table tags first!

SOURCE CODE VALIDATORS      There are many good validators that Webbers use to validate their websites. I regularly use Dr. Watson because they are here in my home town of Jacksonville, FL – home of the NFL Jacksonville Jaguars. Dr. Watson has options for different browsers, images, links, styles, word count, loading time, and search engine compatibility. The WebLint Validator gives short, precise error summaries.      The W3C Validator gives the most comprehensive summary of your source code syntax errors; and, if you understand the HTML DTD, W3C has an option for checking the source code's "Parse Tree" - the structural integrity of your code. A "parse tree" view and/or printout will show the hierarchical structure of all your document's HTML tags in the exact sequence you have coded them in your webpage. It is the easiest way to see missing or improperly nested HTML tags in complex documents.      The cleanest, pure code source viewer is Thunderstone© WebTV Source Code Viewer - the source code is shown without the HTML syntax error comments that other validators provide - it's a pure source code viewer rather than an evaluation report validator. Many MSN TV® help sites use the Thunderstone Validator. You can use the Thunderstone validator at MadRabbit, or Hipster. I have a link at the bottom of this webpage that you can just "Click" to view the source code of this document from Thunderstone that I published on a PageBuilder webpage, with additional comments on the PageBuilder webpage code structure. I also have a link for you to see how to add the Thunderstone© WebTV Source Code Viewer to your webpages.      Also, you need to "Search" for meta tag info and generators, and take your websites to Website Garage, or Net Mechanic for "tune-up" checks. If you want your website rated for accessibility, go to CAST's Bobby check, which would not certify the old WebTV PageBuilder's websites because the ugly, black ink wasting Barnes and Noble banner did not have "ALT" text in the image tag code, for the text readers used by vision-impared surfers.

CHECK THE CODE      Just use color markers to highlight the disabled code contained between the comment tags, and by highlighting every other tag and comment, your validator print-out will be easy to understand. Also, I commented out all the "placeholder" tags and added explainatory notes that I used to show where other head tag content is placed. Using different highlight marker colors to distinguish the various components of the webpage contents will make it easy to understand.      Also, you will see a lots of empty html tags and redundant, superfluous code in your validator printout. This is because MSN TV® PageBuilder is a "template" type of webpage builder, which has many built-in "marker" or "placeholder" html tags for all the many options available for creating webpage content. It's a good program for beginning PageBuilders, but has limited options for advanced users.      MSN TV® PageBuilder needs a true Advanced Editor option on the sidebar in the PageBuilder Index screen. This Advanced Editor option would simply be a blank screen form option with all memory available after scrapbook requirements; which would allow PageBuilders to hard code, cut-and-paste scripts, etc, and build their complete website content from start-to-finish. But; in the absense of a blank screen text editor, as a minimum, my proposed PageBuilder Advanced Editor would have: beginning <!doctype>, <html>, and <head> tags; the meta generator (PageBuilder version) tag; additional meta tags, such as: keywords, author, published date, etc; or an extended head tag text box that users could use to add meta tags, styles, and scripts; a large text box for code and text, that could be coded for frames instead of tables on the web (Note: our browsers would still convert the frames to tables for display on non-horizontal scrolling TV screens); and a better design for the MSN TV® link and future sponsor banners at the bottom of our webpages. Macromedia designed PageBuilder for MSN TV® and could very easily design a much-improved program; but if sponsors can't be found to pay for it, we won't get many improvements!      I imagine many of you have wondered why we cannot put a beginning comment tag at the end of the "Page description" text box, block out all the interviening code, and extend the page description to the large text box, so we can add page description content beyond the 128 character limit of the description text box. This would really extend the advanced editor options, but it is impossible. The description meta tag is a singleton html tag with the closing angle bracket (>) outside the text box. You cannot enter a comment tag in the text box because you cannot "nest" a comment tag inside any individual html tag – only specific html and events "attributes" are legal inside individual html tags. Also, note: you cannot "nest" comment tags inside other comment tags – the first inside (nested) ending comment tag (-->) will terminate the comment, and the outside ending comment tag will appear as plaintext in your document. If the description meta tag closing angle bracket were inside the text box; we could erase it, enter a beginning comment tag, and block out all built-in code all the way to the large text box, and even extend the "Page Description" to more than 128 characters in the large text box. This would enhance our advanced editor options.      Prior to the December 1999 PageBuilder upgrade, we could not put a title closing tag and beginning comment tag only in the title text box so we could move the title down below the meta tags; but, since the upgrade, we have been able to close off the built-in title with an ending title tag in the title text box and relocate the title tag below the added meta tags I suggest in this tutorial, and the relocated title will properly display in the title bar at the bottom of our TV screens, and the title bar at the top of computer windows. Relocate the title only if you want to put the title after the meta tags. But, it really doesn't matter, you can legally place the meta tags and title in any order in the head tag. In fact, having the title follow the page description, may be the best order for search engines; but, I just don't think it looks correct in the code to have the built-in "Description" meta tag split from the other meta tags with the title between them. Use your own personal preferences in Advanced Editing. Note: I left it that way in this tutorial so you can see what I mean in the source code for this webpage.

THIS IS A CLOSED EDITOR METHOD      When you have entered the comment tags in both the title box and first text box, your webpage contents will disappear from the Basic Editor Screen. You will only see a closed box, instead of your webpage contents, until you disable the beginning comment tag, as explained below, in the title text box. This is the only objectionable problem with using this method that causes disfavor among PageBuilders who prefer one of the new open-editor PB AE methods! This method is strickly legal according to the W3C HTML DTD! The HTML comment tags may be used anywhere within a document - head tag or body tag!      Shortly after I published this variation of H17's PB AE comment method in March 2000, my friend Paul Dutton, aka PaulWayn@webtv.net, published his new PB AE open-editor Defeat method on May 27, 2000! Paul was first to discover a simple way to disable the "closed-editor effect" of the PB AE comment tag method, using a "hybrid" looking variation of the HTML comment tags, so our basic editor screens would stay open! Paul's method soon became a very popular, preferred method for PB advanced editing, because of the ease-of-use of open-editor methods! Check out Paul's method at the link above. Paul initially used this syntax in his PB AE comment tags: <!--//> ... </-->; but, soon after I published my PB AE Script Method, he changed his editor tags to: <!--/*> ... <*/-->, by incorporating the javascript multiline comment tags I used in my new PB AE Script Method into his editor tags. Why, I don't know? The javascript comment tags have absolutely no functional value when used within HTML tags, or anywhere else outside script tags - the javascript multiline comment tags are strictly for javascript, style, and programming languages like C/C++! Paul's comment tags were just fine as he originally published them! I show several variations of Paul's comment tags that work equally well below.      And, subsequently; I have published several new PB AE open-editor methods that also enjoy a great amount of popularity among PB advanced editing advocates. See a list of all my PB AE tutorials at the bottom of this webpage! Also, note: The basic PB AE method's procedural premise is exactly the same for all the advanced editing methods. You just use any particular method's HTML tags in exactly the same manner as the HTML comment tags are used in this method. See my additional comments on this subject below.

ADDITIONAL PROCEDURES      Beth and Saverio cautioned us about the disappearing Basic Editor text box with all your webpage content, and explained how to disable the beginning comment tag. The basic editor screen disappears because the "Add" options are forms that place content into the document body on the Basic Editor page as a temporary viewing screen. When you block out the body tag with the Advanced Editor comment tags; your body content, which is "pasted' into your Basic Editor screen, disappears. This is really a good omen – when the Basic Editor text screen disappears, it means you have successfully blocked out the built-in body tag. At this point, you can "Preview" the page. But, don't forget, you always still have to "Publish" and click "Done" – when in doubt, "Publish" and click "Done" again. Remember: when the Basic Editor screen disappears, you can click "Preview" to view your page. The preview screen is just another temporary viewing screen like your Basic Editor screen, but the preview screen is formatted exactly like your webpage will appear on the web. The content you see in the temporary Basic Editor screen is actually stored in the various option forms memory. This is why you have to click-on an item in the Basic Editor to return to the form that contains the item in memory so you can change it. When you publish your page on the web, all the items you have in the memory forms is manipulated by javascript (pasted) into the PageBuilder template" on the web.      To get back to the Basic Editor text box screen when using Advanced Editor, you have to "Edit (the) title" and erase, or disable, the beginning comment tag (<!--) you entered in the "Title" text box to block-out the PageBuilder built-in body tag. Beth Candy published the step-by-step procedure for opening the Basic Editor screen in an Advanced Editor webpage. You have to erase the comment tag in the title text box so the content in the large text box form can be "pasted" back into the built-in body tag in the Basic Editor screen. From the "Index page", click-on your website, click-on "Change public listing," erase the comment tag in the title box, click "Done," then your Basic Editor will come back up. When you are finished editing and publishing again, click-on "Edit title" on the sidebar and put your beginning comment tag back in the title box and click "Done." Follow the procedure Beth outlines for "How to Edit" your page when you don't have a Basic Editor screen to click-on the items you want to edit.      My additional suggestions for editing an Advanced Editor webpage, after the Basic Editor screen disappears and you see a blank Basic Editor, are: click-on "Edit title" and erase the beginning comment tag in the title text box, click "Done" and your Basic Editor text box will come back up. Then edit your page, click "Done" and return to your Basic Editor screen. Then click "Edit title" again and put the beginning comment tag back in the title text box and click "Done" – your Basic Editor screen will again disappear. "Preview" if you like, and if OK, "Publish" and click "Done." Also, I suggest that as soon as you publish an advanced editor page, you come back and open your basic editor page as outlined above, so you will be ready to edit (update) your page anytime you have added information. Again, I remind you to always click "Done" before you leave a screen that has "Done" at the bottom.

EDITING PROBLEMS      Here's an irritating problem that will try your patience. When you type a lots of text in the large text box, you will begin to notice that your keyboard text entries become slower and slower apearing on screen in the large text box. All you can do is be patient and wait for the text to appear. You can type ahead and the text will fill in shortly. Just be concious of your words and carefully enter your keyboard text, or you will discover missed spaces and misspelling that you will have to go back and correct. This happens because PageBuilder allocates a reasonable amount of space (memory) for a webpage's text box entries. If you have an excessively long text box entry, the PageBuilder program has to allot more Hard Drive space to your added text, and rewrite the text below where you are editing, which causes your editing changes to get slower and slower as you edit near the top of a long document. The keyboard text entry slowdown decreases as you edit near the bottom of a long document because less text has to rewritten in the long text box. This problem also exasperates your loading time when switching and re-writing between your text box, Basic Editor, and Preview screens; because your files get fragmented on the server hard drive when additional memory space is assigned to long text box entries. This problem gets really bad during web "high-traffic" periods in the evening hours. Also, during "Preview" you may see "disabled" HTML code in your document because of missing spaces, broken links, lost angle brackets (<...>) and quotes ("...") around attribute values. Just "Preview" and edit your page until it is corrected, and "(Re)Publish." Be patient and don't try anything to force editing changes – you may lose some editing changes you just made! Never hit your "Back" key, except when returning to editing from "Preview" – you'll lose editing changes if you don't always clicik "Done!"      Now here's another warning note about a problem many of you have sometimes experienced. When you are finished editing a long webpage in the large text box and click "Done," it takes a long time for the PageBuilder program to re-write your Basic Editor screen. Just be patient and wait for your Basic Editor screen to come back up. The program takes longer to overwrite the old page. And, very important, remember this warning: after editing, don't ever "Power-off" or leave the large text box screen after you click "Done" and are waiting for your Basic Editor screen to reappear! Be patient and let the hardware rewrite the Basic Editor form memory to bring up the revised Basic Editor screen, or you will lose the editing changes you just made! Also, when you publish an edited (updated) page and try to visit your new page, you still see your old page. Don't panic, and think you have done something wrong. You are just loading your old page from your browsers' cache of all your most recently visited webpages. Also, this problem is exasperated in old WebTV "Plus" terminals that also cache recently visited webpages (and messages being written and paused for later completion) on their hard drives for a week, or until they are pushed out of the HD cache by new website visits. Also, if you visited your old page during your current" session, the old page will be cached in your "Recent" cache. Just "Reload" (Cmd-R) and your new, updated webpage will be down-loaded and again "cached" in your browser, in your "Recent" session cache, and old Plus terminal's HD's. But sometimes, and I don't understand why, you may have to "Power-off" and "Power-on" again, to clear your "Recent" cache to get your new page to load.      A few of my PageBuilder friends say they wait until the "wee hours" of the morning (PDT) when web traffic is at a minimum, to publish changes to their webpages. I tell them this is unnecessary – it doesn't matter when or how long you edit your pages. You can edit your Basic Editor screens as long as you desire – it won't affect your published webpage. Your PageBuilder Basic Editor and webpage are on separate server groups – the webpage is on the webservers and the Basic Editor files are in our subscriber file servers behind the MSN TV® corporate firewall. When you publish a webpage, it only takes an instant for the PageBuilder javascript to copy the page from your Basic Editor files to your PageBuilder "template" on the webservers. If someone is viewing your webpage while you are re-publishing an upgraded webpage, it doesn't affect your viewers at all. They are viewing your webpage that has been downloaded into their browser's ram. And, if someone was trying to access your website at the exact time you were re-publishing an update, they would just have to watch the "spinning globe" and stalled "temperature bar" a few seconds longer while your webpage is being updated.      Another matter I warn others about is that you should never unpublish a document before you re-publish an updated (same title) webpage. Always allow the PageBuilder program to re-write (overwrite) an existing page so you will keep your customized short URL's and webpage titles. Check my PageBuilder URL tutorial noted below for additional information on this procedure.

QUICK ACCESS TO EDITOR      So go ahead and erase, or disable, that beginning comment tag in the title box and open your Basic Editor anytime. In fact, it only takes less than 10-seconds after you publish a webpage, to click-on "Edit title" and "disable" the beginning comment tag, by removing only one "dash" (-); ie, change it to: "<!-," which is not a comment tag – I always do this so all my Advanced Editor webpages' Basic Editor screens are always open. Take your time editing and previewing your webpage changes. When you get your edited webpage just like you want it; put the "dash" (-) back on the comment tag, click "Publish," and click "Done." Then you can come back and open your Basic Editor screen again for more changes if you like. Keep "tweeking" those PageBuilder webpages, folks! Never be satisfied. Continous changes will make your website more appealing to repeat visitors. Always announce recent updates to your websites in all the appropriate MSN TV® newsgroups. And, most important, always keep notice of your upated PageBuilder "help" websites posted in the PageBuilder newsgroups. All PageBuilders want to learn all the latest techniques for enhancing PageBuilder procedues that you publish on your PageBuilder help webpages.      Typically, it takes six (6), or more, keystrokes to reach any of your webpage Basic Editor screens from your "Home page" – but, you can use your "Favorites" folders and "Hot-Keys" to allow access to any of your webpages' Basic Editor screens in as little as two (2) "keystrokes." Here's how: When I make an Advanced Editor webpage, I always disable the comment tags to keep all the AE Basic Editor screens open. I save all the "opened" Basic Editor screens in a Favorites "folder" named "PB Edit," BEFORE I put the comment tag in the "Title" text box and "Publish." After publishing my AE webpage, I come back and drop the last "dash" off the comment tags, as noted above, to disable them so I can access any of my webpages' Basic Editor screens from my "Favorites" folders with "Hot-keys." I put all my AE Basic Editor webpages' screens in this one folder, and also put a link to this folder inside the same folder; ie, a link inside the folder to the folder itself, so I can link to the folder by assigning one (1) "Hot-key" to this PB editing folder. I also save my PageBuilder "Index" page in this folder, and could assign (if I had any left) a "Hot-key" to my PageBuilder "Index" page – but, I just prefer to "Hot-key" a link to the "PB Edit" folder, instead of my "Index" page. Why? Because you can also save other PageBuilder editing pages, such as large text boxes you are working on. As an example, I have a link to the large (and I mean large, folks!) text box for this long webpage, that I'm continually editing and adding updates to. When I want to edit a PageBuilder webpage, I just hit my "Hot-key" to open my PB editing folder and click-on the "visible" (AE) Basic Editor sceen I want to edit. This is the fastest way to access and edit a PB AE webpage from your Home page – as little as two (2) keystrokes – and is far faster than the six (6) or more keystrokes required for normal access from your Home page!      Here's some "quirky" notes for using the folder method described above to access your AE Basic Editor screens. All your Basic Editor pages will be saved in the folder as a "Change your Web page" links, because that is the name of the PageBuilder page you are saving; so all you have to do is just save the webpage editor screens in the very same order that your webpages are listed in your PageBuilder Index page, so you know what each is. In the folder, you will see your individual webpages listed first, in the order you saved them. Your PB Index page will be listed last, and your PB Edit folder will be next to last in your folder, unless you start the folder name with an "a" or "b" so it comes before your "Change your Web page" (Basic Editor screens) links – your folder links are saved alphabetically. You cannot put the links to your PB Index or editor pages on a published webpage, because links from our PageBuilder program are only accessible by each individual user behind the MSN TV® corporate firewall. When you select the option to use links from your favorites on your webpages, you will discover that the links to your AE Basic Editor webpages are not listed for you to select, because they cannot be accessed from outside your individual user (firewalled) Home pages.

ADD BUG ALERT SCRIPTS      Since the original introduction of the WebTV browser, our browsers are referred to as an internet terminal, are now a part of the Microsoft Network, and known as MSN TV® Internet terminals. Our browsers are designed to be very low-priced alternatives to computers, for websurfing, email, etc; and have limited ROM and RAM memory, and comparatively slow processors.      Due to limited ROM programming memory capacity, our browsers use "lean" programming code for all functions. This effects the way our MSN TV® browsers displays websites. Many functions of the latest browsers are not supported by our browsers. Our browsers have always been plagued with the infamous WebTV JavaScript Bug, that's due to a limited implementation of javascript's error checking procedures because of our terminal's limited amount of available ROM programming memory.      Our browsers convert frames and other webpage content to a basic table template layout for display on our TV screens. This table conversion uses javascript to build the table formatted webpages. The limited javascript error checking program code within our browsers sometimes allows javascript errors to prevent the correct display of webpages with javascript. This has become known as the regularly recurring "WebTV JavaScript Bug" we are all familiar with.      When the bug occurs, the table formatting and javascript in a webpage will not function correctly, if at all. Early on, Webbers realized the necessity of using javascript bug alert scripts on our webpages to alert viewers to reload a webpage to clear the JS bug. Several versions of WebTV bug scripts have been devised and effectively used by Webbers for several years. The <noframes> tag scripts have proved to be most popular and effective, because our browsers do not respond to the <noscript> tag, because we cannot disable javascript. The infamous WebTV JS bug ignores the noscript tag.      Now, generally; most all WebTV bug scripts use some variations of the HTML <noframes> tags. The only problem with using the <noframes> tags is that the small number of computer using surfers who disable frames can see the WebTV noframes javascript bug warning. You can include a warning that computer users must have frames enabled to view your webpage, or use the proprietary WebTV <limittext> tag inside the <noframes> tags so only WebTV browser users can see the bug alert warning. The proprietary WebTV <limittext> tag was created for the purpose of displaying webpage messages that only the WebTV browser can display, like the proprietary <audioscope> tag.      As far as I know, Paul Erickson was one of the first to explain the use of the <limittext> tag in the news:webtv.users NG in early 1998. And, I believe the first WebTV JS Bug script I saw that used the <limittext> tag was written by Webber Prototype. Our fellow PageBuilder, Pwilliamandx, also has a WTV JS Bug alert script that uses the <limittext> tag inside the <noframes> tags on his website.      All Webbers should add MSN TV® javascript bug scripts to all their webpages by using the <limittext> tag inside <noframes> tags, like this: <div align="center"> <noframes> <font color="red"> <limittext value="WARNING: MSN TV® JavaScript Bug – Please Reload (Cmd-R)!"> </font> </noframes> </div>      The <limittext> tag also supports the width (number of pixels wide) and size (number of characters wide) attributes. Also, the <limittext> tag is a singleton tag – no closing tag needed; but, some Webbers use a closing tag, which doesn't matter.      So, folks; I suggest you start using the proprietary WebTV <limittext> tag inside your <noframes> tags in your webpage javascript bug alert scripts, as shown above. Your javascript bug warning should be at the top of your webpage, immediately following the document's body tag. On multipage documents, you need the bug warning script on the top of each page, because our PageBuilder multipage document individual pages are actually separately published webpages linked together by navigational <a> tag links.      Also, I'm sure you all realize that you can use the <limittext> tag, without having to use a javacript browser detection script, to write a message on your webpages that only MSN-TV users can see! As an example, put the following greeting in a limittext tag on your webpages, and only MSN-TV browsers will display the message: <limittext value="Greetings fellow MSN-TV user - Thanks for visiting my website - I hope you enjoyed your visit - Please return soon for revisions to this webpage!"> This code will appear as below to all MSN-TV browser users who view your webpage:

THIS PROCEDURE NEEDS TESTING      I realize most of you who help others in this NG have limited time outside your special interest projects, but if you can find a few moments of spare time, please test the premise of editing the head tag of a PageBuilder document that I present here. We all may be able to better use PageBuilder if all the many PageBuilder pioneers, experts, and wizards would thoroughly test, modify, tweek, add personal preferences, and add this information to their PageBuilder help websites for others to use. It would help many other PageBuilders if the functions noted below were thoroughly tested and verified. I posted the source code in the PageBuilder NG's for you to copy, but it would be better if you validated this webpage to see to code structure yourself.      Disreguard the "author" and "copyright" meta tags in the code. They were added as an example of meta tags only. I did not originate and author all the basic premises of my suggestions for this procedure. I gave full credit herein to others who provided information for me to understand and propose this suggestion. Please feel free to use this information any way you like, test it, change it, improve it, add your personal touch and any revisions you desire to make and add the procedure to your PageBuilder help websites.      Check the following possibilities for use of the suggestions I outline:      1. Put styles and javascript in the head tag separately, and together for DHTML, to determne if they function correctly in the PageBuilder template on the web.      2. Use the meta refresh tag in the head section to reload from an opening fancy splash-screen. Use the link, rel=next, to preload the refresh (redirect) webpage, ie, verify that the next page will preload in ram so refresh page will load instantly.      3. Use the base href tag for your outside websites (Geocities, Tripod, etc) URL's, in the head section and use both absolute and relative addressing, for external files, in the body of a PageBuilder webpage.      4. Use framesets in place of body tag and load frames consisting of files from your other (Geocities, Tripod, etc) websites. Use absolute addressing and base href relative addressing for your frame content external files.      The above list is only a few suggestions and not any limit on the ways to test this procedure. Devise your own additional personal preferences for testing. It is almost impossible for any one person to thoroughly test a procedure like this. Generally it is necessary for many individuals with a wide diversity of areas of expertise to properly test any suggested procedure. This procedure needs to be thoroughly tested by many expert PageBuilders. Any additional thoughts on this procedure should be posted in the PageBuilder NG's!

PAGEBUILDER UPGRADES      Hopefully, the PageBuilder webpage editing program will be regularly upgraded. This PageBuilder Advanced Editor procedure will probably be modified by the next PageBuilder upgrade, anticipated to be released in early 2001. The next PageBuilder upgrade will probably have several added features, many of which we are currently using with "work-a-rounds" like this procedure, that will make procedures like this Advanced Editor unnecessary! Stay tuned to the PageBuilder NG's, folks! MSN TV® PageBuilder will just keep getting better and better; by both regular upgrades, and all the many expert PageBuilders experimenting with new ways to work-a-round the PageBuilder Editor limitations. As soon as the new PageBuilder upgrade is released, let's all try to help each other understand the new features as soon as possible, by posting our new-found methods for using both Basic Editor and Advanced Editor procedures! All PageBuilders who post helpful information in the NG's have really made PageBuilder webpage building an enjoyable experience for us all! And all PageBuilders are truly thankful to all the experts who have set up additional PageBuilder help NG's, and published extensive PageBuilder help websites to further expand our knowledge database! Thanks for all your help, folks! MSN TV® PageBuilders are a great group of people!

SUMMARY      In summary, follow Beth Candy's instructions step-by-step with the minor changes I suggest here. Note how Beth explains when to enter the html code in the title box so you don't get the code in your URL. I published a short Tutorial about customizing PageBuilder URL's that, although written for new beginning PageBuilders, may help you.       The information presented here is not any great PageBuilder "breakthrough" like Uncle Hughy's work, but simply a further application of his basic premise. The real credit goes to h17, Beth and all the many other PageBuilder Pioneers for all the clear, concise, step-by-step instructions we see in the NG's. These helpful, gracious Webbers make it so easy for us all to more fully understand each new PageBuilder "breakthrough" so that we may continue to find new ways to use PageBuilder and pass the information along to others, as I have tried to do here.      Please excuse my failure to mention all the many other PageBuilder experts who so graciously help us in all the PageBuilder News Groups. I did not mean to slight anyone by referring only to Beth Candy's and Pwilliamandx's work. I mentioned Beth because she is a good friend who has helped me so very much, and her tutorials are very easy to understand. Also, many of you remember that Pwilliamandx was one of the first PageBuilders to publish webpages, and post in the NG's, articles precisely explaining the many problems, the tricky "nuances," many functional variations, and unknown procedures that were so very hard for us all to grasp when PageBuilder was first released. There is now so many very highly skilled PageBuilder experts dedicated to giving the best PageBuilder help available in several PageBuilder News Groups. All PageBuilders should visit these NG's to receive help for any problem, to readily give help in your area of expertise, and show your support for all PageBuilders. And, don't forget to support the sponsors of our PageBuilder webpages. Please visit, support, and participate in the following PageBuilder News Groups. news:alt.pagebuilder.help news:alt.discuss.clubs.public.html.help.poorboyinc news:alt.discuss.webtv.page-builder news:alt.discuss.homepage.pagebuilder news:alt.discuss.webtv.pagebuilder.html news:alt.discuss.webtvsites There are many other special interest newsgroups. Use the search feature at the "Discuss" webpage linked from your MSN-TV home page. The largest and fastest moving NG, for beginners and experts alike, is the "users" NG, at: news:webtv.users      Many of our most talented PageBuilders, like my friend Curly Roe, aka PoorBoyInc@webtv.net, whose Club NG is listed above, are also starting their own "alt.discuss.clubs.public" (or private) NG's in the areas of their expertise. Please keep an eye out for announcements of these new clubs as they come online. Please visit, contribute, and support their dedicated efforts to bring us the very latest PageBuilder news. These dedicated PageBuilders are continually adding new information to our PageBuilder database, which makes the PageBuilder program so much easier and enjoyable for everyone to use. We all really appreciate and cherish all the many PageBuilder "Helpers," and we are all so thankful that we have the opportunity to be associated with the finest, most gracious, and helpful group of individuals you will find anywhere! I am so thankful for all the help I have received; and I feel obligated to contribute, in my small way, at my every opportunity!      I published a webpage with the code for the Advanced Editor "expanded" <head> tag section I suggest here with all the additional meta tags and additional webpage formattng comments, at: http://community-2.webtv.net/jaxred/Source/. Please check this webpage for many more comments about webpage structure and HTML code syntax that I did not discuss here! I published a webpage about using short titles in your webpage URL's, and a webpage about PageBuilder navigation options. View the of this webpage at the Thunderstone© WebTV™ Source Code Viewer. Put a Source Code Viewer on your webpages.      You will get a clean copy of the source code for this document without any comments, for your print-out. Please excuse this excessively long webpage – I made it one page so you can make a continous print-out without having to switch pages. Return to the validators paragraph above.

OTHER ADVANCED EDITOR METHODS      I have published two other PageBuilder Advanced Editor method tutorials, using noscript and script tags. Check these tutorials, at: http://community-2.webtv.net/jaxred/noscript/ http://community-2.webtv.net/jaxred/script/ I also published PageBuilder Advanced Editor multipage document tutorials, at: http://community-2.webtv.net/jaxred/Test/ http://community-2.webtv.net/jaxred/NSMulPge/ I recently published a tutorial about seven (7) new PB AE methods, at: http://community-2.webtv.net/jaxred/misc_ae/ I also published a PB AE tutorial which uses a CSS style sheet in an extended head tag for all the body tag style code, at: http://community-2.webtv.net/jaxred/style1/ Webbers, SolarBunny and CTPaso collaborated on a simple PB AE that works on all MSN-TV browsers, except 2.6 - 2.6.1, at: http://community-2.webtv.net/jaxred/SimPBAE/ Click here to return to the closed-editor discussion above. ALL PB AE METHOD PROCEDURES ARE SIMILAR Experienced PageBuilders will recognize that you can use all the PB AE methods with these step-by-step procedures to create single or multipage documents - ie; just use your favorite AE method, whether it be the Comment, Defeat, Noscript, Script, Style method, or any other method; like this: for the HTML comment method (H17), use: <!-- ... ­->; for the Defeat Method (Dutton), use: <!--//> ... </--> (these beginning comment tags also work with the Defeat method: <!--/ /, <!-->, or <!-- >); for the noscript method (JaxRed), use: <noscript> ... </noscript>; for the script method (JaxRed), use: <script> /* ... */ </script> or <script> <!-- /* ... */ // --> </script>; or for the new style method (JaxRed), use: <style> <!-- /* ... */ --> </style> method, as you prefer; in the same manner that the HTML comment tags are used in this tutorial - just substitute any other advanced editing method's tags for the comments tags I use in this method!      You may freely use any and all the information in all my Advanced Editor tutorials for your own personal Advanced Editing tutorials! Add any variations and personal preferences you desire to make more helpful PageBuilder Advanced Editor tutorials for all the new PageBuilders coming online in need of helpful resources! Post your additional information in the PageBuilder NG's. But, I remind you, as a common courtesy, you should acknowledge the works of others that you use in your tutorials, and give full credit to others when appropriate!      Each of our expert PageBuilders have unique ideas, specialties, and skills that are continually adding to our knowledge base of PageBuilder webpage editing – check out the great work of these PageBuilder helpers in all the many PageBuilder NG's! Folks, there's an answer to every PageBuilder's problems in our PageBuilder NG's – all you guys have to do is ask for help, and you'll get many great possible solutions to your problems. Don't be afraid to ask! There's no such thing as a dumb question to the experts – they've "been there", folks; with every conceivable PageBuilder problem! And, remember: as you receive help, you should always try to help others when you can!

JaxRed © 2000 The Weather Underground, Inc. Site Visitors Since 04/20/00 Thanks For Visiting My Site, Folks!