<?xml version="1.0"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
 <channel>
	<title>Nexi - Recently Changed Pages matching Node</title>
	<link>http://nexi.com/</link>
	<description>Nexi - a Resource for Daily Living</description>
	<language>en-us</language>
	<copyright>Copyright 2005 Nexi.  This content is made available to you under a creative commons license that permits free reuse, but no commercial use or resale.  Visit http://nexi.com/ for more information.</copyright>
	<lastBuildDate>Mon, 20 May 2013 00:27:02 -0400</lastBuildDate>
	<ttl>360</ttl>
  <item>
   <title>Bullets and Numbered Lists - v4</title>
   <link>http://nexi.com/77</link>
   <description>Keywords: Site:Nexi Help Node Editing Basics<br/>= Lists<br/><br/>Bullet lists are a handy way to organize thoughts.  Numbered lists make following step-by-step instructions easy.<br/><br/>Start each item of a list on a new line.  For bullet lists, place an asterisk as the first character, followed by a space.  For numbered lists, use a dash then a space.<br/><br/>A list item must be one continuous line of text.  <br/><br/>&lt;code&gt;<br/>== Party Attendees<br/>* Frank<br/>* Joe<br/>* Nancy<br/>== ToDo List<br/>- Reserve Hall<br/>- Order Cake<br/>- Order Tables/Chairs<br/>== Definition List<br/>&gt; Term 1<br/>&gt;&gt; Definition 1<br/>&gt; Term 2<br/>&gt;&gt; Definition 2<br/>&gt; Term 3<br/>&gt;&gt; Definition 3<br/>&lt;/code&gt;<br/>&lt;sample&gt;<br/>== Party Attendees<br/>* Frank<br/>* Joe<br/>* Nancy<br/>== To Do List<br/>- Reserve Hall<br/>- Order Cake<br/>- Order Tables/Chairs<br/>== Definition List<br/>&gt; Term 1<br/>&gt;&gt; Definition 1<br/>&gt; Term 2<br/>&gt;&gt; Definition 2<br/>&gt; Term 3<br/>&gt;&gt; Definition 3<br/><br/>&lt;/sample&gt;</description>
   <pubDate>Tue, 10 May 2005 17:10:56 -0400</pubDate>
  </item>
  <item>
   <title>All Taglink Options - v3</title>
   <link>http://nexi.com/89</link>
   <description>Keywords: Site:Nexi Help Node Editing Advanced<br/>Placeholder for more useful help text later -- just here to keep my notes intact.<br/><br/>&lt;code&gt;<br/><br/>{{<br/>  keyword list;<br/>  header: Header Line;<br/>  noheader: If specified, there will not be a header line<br/>  nonew: if specified, there will not be a + to add a new page<br/>  newtitle: If specified, will be the title of a new page<br/>  newpage: If specified, will be the caption at the top of the new page editor<br/>  bullets; if specified, items will appear in a UL/LI list.<br/>  new: If specified, creates a full text link to add a new page (with given text)<br/>  template: If specified, items will use template matching &quot;Special:Link (given text)&quot;<br/>  limit: limits number of items listed.  really useful only with time sort<br/>  sort: title, created, or modified<br/>  flow: specifies that items should be comma separated like the [[ ]] style list.<br/>  ifheader: Will not draw a header IF there are no items to show.  Makes the list invisible if it isn't needed.<br/>}}<br/><br/><br/>&lt;/code&gt;<br/><br/>== Using Templates for List Items<br/>This needs explained.<br/><br/>== Passthru Variables<br/>You can actually put anything before a colon in a list option.  All of these values are made available to templates that are drawing the list by using the format ''$$variablename$$''.    <br/><br/>== special template codes for lists<br/><br/>* ''##object##'' returns object id.  useful in creating links.<br/>* ''##title##'' returns page title.<br/>* ''##created-date##'' returns date page was created<br/>* ''##edit##'' creates a small &quot;edit&quot; link to edit the page.<br/>* ''##modified-date##'' returns date page was last edited<br/>* ''##comments##'' shows comment tree in-place<br/>* ''##commentform##'' shows comment form in-place<br/>* ''##commentline##'' shows the comment count, plus an add-a-comment link..<br/>* ''##keywords,1,2,3,...##'' shows keywords of page EXCEPT 1,2,3,....<br/><br/><br/>= More Notes<br/><br/>* ''{nav{keywords}}'' builds a navigator link<br/>* ''{rss{keywords}}'' builds an rss feed for NEW pages matching<br/>* ''{rssmod{keywords}}'' builds an rss feed for MODIFIED pages matching<br/>* ''{searchform{keywords}}'' displays a small full text search form that will launch the navigator with the given keys.</description>
   <pubDate>Tue, 10 May 2005 17:30:15 -0400</pubDate>
  </item>
  <item>
   <title>2002-12-27 - Williamsburg, Virginia - v6</title>
   <link>http://nexi.com/40</link>
   <description>Keywords: Site:Catbear Tour Node<br/>= Williamsburg<br/>[cw_library.jpg;left]<br/><br/>----<br/>= Colonial Williamsburg<br/>[cw_brxck_graffiti.jpg;left]<br/>[cw_mossy_roof.jpg;left]<br/>[cw_church_pano.jpg;left]<br/>[cw_house_pano.jpg;800;left]<br/><br/>----<br/>= College of William and Mary<br/>[cw_pipe_organ_pipes_1.jpg;left]<br/>[cw_pipe_organ_pipes.jpg;left]<br/>[cw_pipe_organ_detail.jpg;left]<br/>[cw_bricks_and_trees.jpg;left]<br/>[cw_bricks_and_window.jpg;left]<br/>[cw_house_trees.jpg;left]<br/>[cw_light_on_wall.jpg;left]</description>
   <pubDate>Sat, 07 May 2005 15:02:51 -0400</pubDate>
  </item>
  <item>
   <title>2002-12-26 - Blairsville, GA - v3</title>
   <link>http://nexi.com/95</link>
   <description>Keywords: Site:Catbear Tour Node<br/>The start of the trip.  Tinkering with layout, mostly.  <br/><br/>= The Starting Point<br/>text and stuff here.<br/><br/>[forest_drive_in_blairsville.jpg;left]<br/>[snow_on_christmas_in_blairsville.jpg;left]<br/>[blairsville_house.jpg;left]<br/> [forest_in_blairsville.jpg;left]<br/><br/>----<br/>= What was Left Behind<br/>more text here.<br/>[brent_bikes_in_the_snow.jpg;left]<br/>[sam_and_mei-mei.jpg;left]<br/>[blurry_cristmas_tree.jpg;left]<br/>[biking_in_the_snow.jpg;left]</description>
   <pubDate>Fri, 03 Jun 2005 12:56:45 -0400</pubDate>
  </item>
  <item>
   <title>Creating Page Templates - v4</title>
   <link>http://nexi.com/88</link>
   <description>Keywords: Site:Nexi Help Node Editing Advanced<br/>This is an advanced topic.  You must be at least this ----&gt; tall to read.<br/><br/>= Why would I want to use a Template?<br/><br/>Normal pages on AllAbout are freeform.  You type your page content in one great big text box, putting headers and so on wherever you want.  This is fine when you're creating lots of different kinds of pages.  It's not so much fun when you're making lots of the same kinds of pages, like recipes.  <br/><br/>Recipes have things in common with each other, such as a list of ingredients and a set of directions.  A recipe template would allow you to build an input form with fields called &quot;Ingredients&quot; and &quot;Directions&quot; and so on.  The template would take the information in those fields and create a nicely formatted page with the appropriate headers.<br/><br/>This saves a lot of time when entering recipes, and ensures that all recipes have a common appearance.<br/><br/>= What is a Template?<br/><br/>A template is a page on AllAbout with at least two keywords.  The first keyword must be the special keyword: ''Special:Template''.  The second keyword describes the particular sort of template, and should be similar to this: ''Template:Recipe''. <br/><br/>The template itself is a normal AllAbout content page with headers and formatting.  It also has, instead of regular content, special commands embedded in it to describe the fields that make up the template.<br/><br/>= A Sample Template<br/><br/>We'll continue the Recipe example because it is simple and straightforward.  Here is a template for a simple recipe with ingredients and directions:<br/><br/>&lt;code&gt;<br/>= Recipe Ingredients<br/><br/>Here are the ingredients you'll need:<br/><br/>%%ingredients%%<br/><br/>= Directions<br/><br/>Step-by-step directions:<br/><br/>%%directions%%<br/>&lt;/code&gt;<br/><br/>As you can see, the template has two header lines, a little bit of text, and two field names surrounded by double % marks.<br/><br/>The field names represent the data that you'll type into the recipe page when the template is assigned to it.  When you edit a Recipe page, instead of the big &quot;Page Text&quot; text box, you'll get two smaller text boxes, labeled &quot;ingredients&quot; and &quot;directions&quot;.<br/><br/>When the page is shown to the user, they'll see the headers, the text, and then the ingredients and directions right where they belong -- without you having to type them over and over.<br/><br/>= How do I place a Template on a Page?<br/><br/>To use a template on a page, include the ''Template:Recipe'' (or whatever you called it) keyword in the page.  Since that keyword is also used on another page with the ''Special:Template'' keyword, AllAbout knows to apply the template.<br/><br/>= Changing a Template<br/><br/>You can change a template even after it has been used in other pages.  This can be to add more formatting, rearrange the fields, or to even add other fields.  Be sure, however, to keep the NAMES of your fields the same.  If you change the field names, you'll have to go back to all the pages that use that template and fix the field data.<br/><br/>= Advanced Template Features<br/><br/>=== Field Size<br/>To change the size of the edit area for a field, specify how many lines of text should be presented after the fieldname with a comma: <br/><br/>* ''%%comment,10%%''.<br/><br/>That would make the field labeled comment be ten lines high.<br/><br/>=== Field Instructions<br/>You can add instructions about the field that's shown to the right of the field when editing the data by appending it after the fieldname (and/or field size) with a vertical bar character, like this: <br/><br/>* ''%%price,1|Enter price as one to three dollar signs, representing &quot;inexpensive&quot; &quot;moderate&quot; or &quot;luxury&quot;%%''<br/><br/>That would create a one-line high field named &quot;price&quot; with some explanatory text next to it to help the person filling out the form.<br/><br/>=== Optional Areas<br/>If you enclose portions of your template in double parentheses, like these: ((  ))  , the portion of the template inside the parentheses will only be drawn if the fields used inside the parethesis are non-blank.<br/><br/>This makes it easy to build versatile templates and entry forms that can handle a variety of situations without having ugly pages with lots of blank headings for fields that simply don't apply.  <br/><br/>= How Templates *Really* Work with regards to Keywords<br/><br/>The rule for finding a template to apply to a page is as follows:<br/><br/>* All of the keywords on the template (except ''Special:Template'') must appear on the page.<br/>* If more than one template qualifies, pick the *most specific* one -- the one with the most keywords.<br/>* If there are multiple templates still matching, then (right now) I have no idea what happens.  But in the future, the system will review keyword counts.<br/><br/>To use the recipe example again, the way the current Recipe Site works, the template has these keywords: ''Special:Template Site:Recipes Recipe''.  Thus, the template matches pages with the ''Site:Recipes Recipe'' keywords, without having to create a special template-specific keyword like ''Template:Recipe''.<br/><br/>However, there's no shame in using a template-specific keyword when you want to, or when you need to, to specifically reference a certain template.<br/><br/>= More Template Goodness<br/>The following special tokens work in templates as described.  They are most useful when creating list templates, but can be used otherwise.<br/><br/>* ''##edit##'' Makes a small &quot;edit&quot; link to the page.<br/>* ''##created-date##'' Displays the date the page was created.<br/>* ''##modified-date##'' Displays the date the page was last modified.<br/>* ''##title##'' Displays the title of the page.<br/>* ''##keywords##'' Displays the keywords of the page.<br/>* ''##keywords,keywords to omit##'' Displays keywords except those appearing after the comma.<br/>* ''##object##'' Shows the page number of the page.  Useful in creating links, e.g.  ''[##object##]'' makes a link to the page.<br/>* ''##comments##'' Allows on-page comments<br/>* ''##commentform##'' Builds a comment form onto the page itself.</description>
   <pubDate>Tue, 10 May 2005 17:29:42 -0400</pubDate>
  </item>
  <item>
   <title>2003-03-15 - Bennington, Vermont - v3</title>
   <link>http://nexi.com/45</link>
   <description>Keywords: Site:Catbear Tour Node<br/>Just some images to start.<br/><br/>[robert_frosts_gravesite.jpg;left]<br/>[spire_monument_in_bennington_vermont.jpg;left]<br/>[henry_bridge_detail.jpg;left]<br/>[llamas_in_vermont.jpg;left]</description>
   <pubDate>Sat, 07 May 2005 15:04:20 -0400</pubDate>
  </item>
  <item>
   <title>Images and Graphics - v8</title>
   <link>http://nexi.com/81</link>
   <description>Keywords: Site:Nexi Help Node Editing Basics<br/>Using images on your pages is easy.  This page is a basic reference to be fleshed out.<br/><br/>= Image Upload<br/><br/>Before you can use an image, it must be [/image_upload.php|uploaded] to the Image repository.  You can upload JPEG and GIF format images.  JPEGs of any size can be uploaded; they will be resized to be under 200K if they are too large.  GIF images larger than 100K will be rejected; you should probably be using JPEG if the image is GIF and that large.<br/><br/>= Using Images<br/><br/>To place an image on the page, put the image filename you were given after the image was uploaded -- including ''.jpg'' or ''.gif'' -- between a single set of square brackets ''[]''.  Example: ''[sanctuary_snow_railing.jpg]''. The image will break the flow of text and appear framed with the image's title and credit.  <br/><br/>You can change the appearance of the image by adding commands after the filename, separated by semicolons.  For example: ''[sanctuary_snow_railing.jpg;left;caption]''.  The command reference below explains each command, and there are examples at the bottom of the page.<br/><br/>= Command Reference<br/><br/>* ''left'' or ''right'' -- force text to flow around the image.<br/>* ''center'' -- centers the image horizontally (doesn't work with ''left'' or ''right'').<br/>* ''full'' -- make the image full size.<br/>* ''bare'' -- removes the title and credit lines.<br/>* ''caption'' -- adds the full image caption.<br/>* ''inline'' -- makes the image flow along with the text.<br/>* any number -- makes the image the given width.  (example:  ''100'').<br/>* number x number -- makes the image fit in the given size.  (example: ''200x150'').<br/>* ''nolink'' - do not make the image a hotlink to the image viewer.<br/>* ''link'' - link the image to the url that follows.  if what follows is a number, link to that page.<br/>* ''zoom'' - the image is linked to the fully zoomed image viewer.<br/><br/>= Samples<br/><br/>''[sanctuary_snow_railing.jpg]'' - Draws the image in a frame with image name and credit.  Image will be no larger than 250 pixels wide or high.  The image will be by itself on a line.  The user can click on the image to zoom in. <br/> <br/><br/>[sanctuary_snow_railing.jpg]Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.<br/><br/>----<br/>''[sanctuary_snow_railing.jpg;left]'' - ''left'' and ''right'' force text to wrap around the image, which will &quot;float&quot; to the side of the page you specify.<br/> <br/><br/>[sanctuary_snow_railing.jpg;left]Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.<br/><br/>----<br/>''[sanctuary_snow_railing.jpg;bare;left]'' - ''bare'' draws the image in a frame with no image name or credit*.  The user must click on the image to learn more about it.<br/> <br/><br/>[sanctuary_snow_railing.jpg;bare;left]Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.<br/><br/>----<br/>''[sanctuary_snow_railing.jpg;80;bare;left]'' - A number controls how wide the image will be.  The image will be resized to be no wider than the given value.  If you specify numbers like this: ''300x200'' the image will be resized to fit in no more than 300 by 200 pixels.<br/>   <br/><br/>[sanctuary_snow_railing.jpg;80;bare;left]Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.<br/><br/>----<br/>''[plant_icon.gif;inline]'' - Using ''inline'' makes the image flow along with the text rather than breaking around it.  Generally this is only useful with very small images, such as formulas or icons.<br/>   <br/><br/>Lorem ipsum dolor sit amet, [plant_icon.gif;inline]consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.<br/><br/>----<br/>''[sanctuary_snow_railing.jpg;full;caption;center]'' - ''full'' makes the image full size: the size you uploaded.  ''caption'' adds the caption to the bottom of the image frame as well as the credit.  ''center'' places the image in the horizontal center of the screen.<br/>   <br/><br/>[sanctuary_snow_railing.jpg;full;caption;center]Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.<br/><br/>----</description>
   <pubDate>Tue, 10 May 2005 17:15:37 -0400</pubDate>
  </item>
  <item>
   <title>Special Taglink Techniques - v2</title>
   <link>http://nexi.com/86</link>
   <description>Keywords: Site:Nexi Help Node Editing Advanced<br/>= Negating a Tag<br/><br/>Sometimes, when pages haven't had enough Tags added in order to tell them apart from each other, you'll get pages you don't want in your list.  There are two things you can do to solve this problem.<br/><br/>The best solution is to add more Tags to the affected pages so that you *can* build a Tag link that shows just the pages you want it to.<br/><br/>The other approach is to build a Tag link with a negated Tag.  Normal Tags, when grouped together, operate like &quot;Car *and* Sedan *and* Honda&quot; all at once.  By adding a negated Tag, you can create something like &quot;Car *and* Sedan *and* Honda *but not* Civic&quot;.<br/><br/>To add a negated Tag to your link, place an exclamation point just before the Tag, like this: ''[[Car Sedan Honda !Civic]]''.  Notice that there is no space between the exclamation point and the Tag that follows it.<br/><br/>= Additive Tags<br/>* quick note:  You can code  ''{Car Sedan+Coupe}'' and  get both sedans AND coupes.<br/><br/>= The special *My* Tag<br/><br/>When you're building your Tag links, you can use the Tag *My* in addition to regular Tags.  <br/><br/>*My* is translated into a Tag that is actually the page number of the *current* page.   So if you have a link that looks like this: ''[[My Notes]]'' on your homepage, and your homepage is page number 3437, the Tag link really functions like this: ''[[#3437 Notes]]''.  You'll see this happen in the examples below, when you click on the pages in the links.<br/><br/>What good is this?  Well, it means that you don't need to make up new Tags all the time when you just want to add some detail information for the topic that is presented on a single page.  For example, you could create an add-a-page link like this: ''{{My Feedback}}'' on a piece of poetry.  Then users could easily add feedback just by clicking the plus sign.<br/><br/>*Note:* My is not a guarantee of privacy, or of restriction.  Pages added with the *My* Tag are as visible as any other, they just have a special, unique Tag on them that makes it easy to attach them to a parent page.<br/><br/>&lt;code&gt;<br/>{{My AllAbout:Test MyComments}}<br/>&lt;/code&gt;<br/>&lt;sample&gt;<br/>{{My AllAbout:Test MyComments}}<br/>&lt;/sample&gt;<br/><br/>When you click on the +, you'll see the actual Tags given to the new page are ''#14 AllAbout:Test MyComments''.  That makes sense, because this is page #14.<br/><br/>The *My* Tag is particularly useful in [51|templates]!  Can you figure out why?</description>
   <pubDate>Tue, 10 May 2005 17:28:32 -0400</pubDate>
  </item>
  <item>
   <title>Adding New Pages - v3</title>
   <link>http://nexi.com/82</link>
   <description>Keywords: Site:Nexi Help Node Editing Linking<br/>Editing pages is easy.  You click &quot;Edit&quot; and there you go.  How do you add a new page?<br/><br/>= How do I add a new page or set of pages?<br/>*&quot;That depends on where that page should go.&quot;*&lt;br&gt;<br/>Not a very helpful answer in that it doesn't really answer the question but instead asks another, because how you go about adding a page does depend on where that page appears on the site.<br/><br/>Here's the thing: Where a page appears doesn't depend on its page number or on its page title.  The only thing that determines where a page appears is its tags.  Tags are everything.  <br/><br/>== &quot;I don't want to think about that, I want to start typing.&quot;<br/>Click **Attach New Page**, which appears in the command bar at the *bottom* of every page.  This gets you to an editor quickly so you can capture whatever idea is burning in your mind.   <br/><br/>=== Where the page winds up<br/>Linked to the bottom of the page you started from.  Why? Its tags are ''My AttachedTo''.  When a page has a page number and ''AttachedTo'' as tags, a link to that page will appear at the bottom of the page with the given page number. <br/><br/>Once the page is saved and you are less uptight about writing content, you can adjust its tags so it shows up where it belongs.<br/><br/>Or, maybe that IS where it belongs.  Maybe you just want to create a simple site with pages that are attached to each other and to nothing else.  That's cool.<br/><br/>== &quot;I want to make a page similar to the one I'm looking at.&quot;<br/>Click **Add Sibling Page** in the command bar.  The editor opens on a new page with *the exact same tags* as the page you were viewing.<br/><br/>=== Where the page winds up<br/>Since the page has exactly the same tags as the page you started at, it appears in all of the same lists. <br/><br/>== &quot;I want to make a new list of pages.&quot;<br/>Go to a page that the list should appear on.  Click the **Edit** tab.  Find where the list should go, then create a *List Link*.  They look like this:<br/><br/> ''{{Keyword1 Keyword2 Keyword3}}''<br/><br/>Where ''Keyword1'' and so on are a set of tags unique to this list.  When you save, the list will appear as a header line with a + appearing after it.  Click the + to start adding pages with these tags.<br/><br/><br/>=== Where the pages wind up<br/>All of the new pages are attached to the original page -- the one with the list link on it.  They can also appear on other pages, if those pages have lists with matching tags.</description>
   <pubDate>Tue, 10 May 2005 17:18:13 -0400</pubDate>
  </item>
  <item>
   <title>Linking to Other Pages - v4</title>
   <link>http://nexi.com/83</link>
   <description>Keywords: Site:Nexi Help Node Editing Linking<br/>There are four ways to link to other pages on Nexi.  <br/><br/>= The Title Link<br/><br/>You can link to another page by its title. Place the title, or the first few words of the title, between single curly braces like this ''{Page Title}''.<br/><br/>Since there may be more than one page that matches, Tags are compared between the current page and all potential links. The page with the most Tags in common are chosen. If more than one page has the same number of matching Tags, they are all shown in a comma separated list.<br/><br/>If you want to be sure that you are linking to a certain kind of page with a title link, you can provide &quot;hints&quot; in the form of Tags.  Hint Tags must be found in the destination pages or they don't qualify, even if their titles match.  Hints are just a list of Tags, followed by a colon, like this: ''{Tag1 Tag2: Page Title}''.<br/><br/>If no pages at all match, a link will appear instead which will add a new page when clicked on.  The page is given the title you specified in the link.  The page will also have default Tags: The Tags of the original page, plus any hint Tags.  You should remove any Tags that are incorrect before saving the page.<br/><br/>&lt;code&gt;<br/>* {Help and information}<br/>* {Lyric: If I Were}<br/>* {This should create a new page, because it won't match anything.}<br/>&lt;/code&gt;<br/>&lt;sample&gt;<br/>* {Help and information}<br/>* {Lyric: If I Were}<br/>* {This should create a new page, because it won't match anything.}<br/>&lt;/sample&gt;<br/><br/>*Title links are not reliable -- if the page they link to is renamed, the link will break.*<br/><br/>= The Direct Link<br/><br/>If you want to go to a certain page, and only that page, you can use a direct link.  They look like this: ''[''*''page number''*'']''.  (Those are square brackets.)  For *page number*, enter the page number shown on the upper right corner of the page.  (This page is page 54.)<br/><br/>&lt;code&gt;<br/>Page linking is explained here: [83].<br/>&lt;/code&gt;<br/>&lt;sample&gt;<br/>Page linking is explained here: [83].<br/>&lt;/sample&gt;<br/><br/>Notice how the title of the page is pulled into the link automatically.<br/><br/>= The Tag Link<br/><br/>If you don't know (or don't care, which is more likely) what the page number is, you can link to a page just by specifying Tags used on that page.  Like the direct link, you enclose the link information in square brackets.  Just put the Tags you want to match between the brackets, like this ''[[TagA TagB TagC]]''.<br/><br/>&lt;code&gt;<br/>My list of things to accomplish: [[AllAbout:Bugs ToDo]].<br/>&lt;/code&gt;<br/>&lt;sample&gt;<br/>My list of things to accomplish: [[AllAbout:Bugs ToDo]].<br/>&lt;/sample&gt;<br/><br/>If more than one page matches the Tags you give, then all of those pages will appear, separated by commas.  This works well when there are only a few similar items.<br/><br/>&lt;code&gt;<br/>Learn more about who is responsible for this site: [[AllAbout:Help Credits]].<br/>&lt;/code&gt;<br/>&lt;sample&gt;<br/>Learn more about who is responsible for this site: [[AllAbout:Help Credits]].<br/>&lt;/sample&gt;<br/><br/>= The Add-A-Page Link<br/><br/>If you use curly braces instead of square braces around your Tags, you get three special enhancements to the Tag link.  <br/>- The links appear as a list, one per line.<br/>- You get a nice header above the list.<br/>- An &quot;add-a-page&quot; plus sign appears in the list header.  If you click on the plus sign, you'll be prompted to add a new page.  This page will start up with the Tags given for the list.<br/><br/>Here's what it looks like:<br/>&lt;code&gt;<br/>{{Nexi:Bugs Bug}}<br/>&lt;/code&gt;<br/>&lt;sample&gt;<br/>{{Nexi:Bugs Bug}}<br/>&lt;/sample&gt;<br/><br/>= Note 1 - Link Targets will be Created Automatically<br/><br/>When using title links, Tag links and add-a-page links, **matching pages do not have to exist.**  In these cases, you are prompted to add a page when clicking on a Tag link that has no matching pages.  <br/><br/>This makes building new content very easy.  Just describe what the link should look like, then click on it.<br/><br/>&lt;code&gt;<br/>[[Nexi:Test FakePage]]<br/><br/>{{Nexi:Test Sandbox}}<br/>&lt;/code&gt;<br/>&lt;sample&gt;<br/>[[Nexi:Test FakePage]]<br/>{{Nexi:Test Sandbox}}<br/>&lt;/sample&gt;<br/><br/>This doesn't work for direct page links, of course.  A page must exist to have a number. <br/><br/>= Note 2 - Link Titles<br/><br/>To add a title to your link, place a vertical bar | after the Tags, then type in your title.  Finish the link with a closing bracket or brace as usual.<br/><br/>With a direct link, the title will override the title of the page.  This is handy if you want to use the link in the middle of a sentence and don't want the page title (which can be easily changed) to wreak havok on your writing.<br/><br/>With a Tag link, the title is used only when the target page(s) do not exist.  If you click on one of these links, the title will be filled in for you.  (Makes creating new pages very simple -- you can pre-create both their Tags and their title just by creating a link to that page).<br/><br/>With a add-a-page list, the title you give will always appear as the list header.  It will also appear as the title of a new page.<br/><br/>Here are some examples:<br/><br/>&lt;code&gt;<br/>It's [54|easy] to link to other pages.<br/><br/>[[Nexi:Test FakePage|This shouldn't lead to a new page, but it might, if someone clicks on it.]]<br/><br/>{{Nexi:Test Sandbox|Click here to add your own sandbox page!}}<br/>&lt;/code&gt;<br/>&lt;sample&gt;<br/>It's [54|easy] to link to other pages.<br/><br/>[[Nexi:Test FakePage|This shouldn't lead to a new page, but it might, if someone clicks on it.]]<br/>{{Nexi:Test Sandbox|Click here to add your own sandbox page!}}<br/>&lt;/sample&gt;</description>
   <pubDate>Tue, 10 May 2005 17:21:05 -0400</pubDate>
  </item>
  <item>
   <title>Linking to Other Sites - v2</title>
   <link>http://nexi.com/84</link>
   <description>Keywords: Site:Nexi Help Node Editing Linking<br/>= Off-Site Links<br/><br/>Links to other sites are as simple as links to pages on AllAbout.  Place the full URL between a single set of square brackets.  To add a title to the link, add a vertical bar, then type the title.<br/><br/>Here are some examples:<br/><br/>&lt;code&gt;<br/>* [http://gmail.com]<br/>* [ftp://ftp.openbsd.org/pub/OpenBSD/]<br/>* [http://weatheroffice.ec.gc.ca/city/pages/on-82_metric_e.html|Kitchener-Waterloo Weather]<br/>&lt;/code&gt;<br/>&lt;sample&gt;<br/>* [http://gmail.com]<br/>* [ftp://ftp.openbsd.org/pub/OpenBSD/]<br/>* [http://weatheroffice.ec.gc.ca/city/pages/on-82_metric_e.html|Kitchener-Waterloo Weather]<br/>&lt;/sample&gt;<br/><br/>== Even Easier<br/><br/>If you don't mind the link liiking like a link, you can just type it into your text and if it looks like a link, it will be converted into one.<br/><br/>&lt;code&gt;<br/>* www.allabout.com<br/>* ftp://ftp.example.com/pub<br/>* http://goober.com<br/>* frogs.com<br/>&lt;/code&gt;<br/>&lt;sample&gt;<br/>* www.allabout.com<br/>* ftp://ftp.example.com/pub<br/>* http://goober.com<br/>* frogs.com<br/>&lt;/sample&gt;</description>
   <pubDate>Tue, 10 May 2005 17:26:16 -0400</pubDate>
  </item>
  <item>
   <title>Special Link Commands - v2</title>
   <link>http://nexi.com/85</link>
   <description>Keywords: Site:Nexi Help Node Editing Linking<br/>= More Notes<br/><br/>* ''{nav{keywords}}'' builds a navigator link<br/>* ''{rss{keywords}}'' builds an rss feed for NEW pages matching<br/>* ''{rssmod{keywords}}'' builds an rss feed for MODIFIED pages matching<br/>* ''{searchform{keywords}}'' displays a small full text search form that will launch the navigator with the given keys.<br/><br/>*More Help Needed Here*</description>
   <pubDate>Tue, 10 May 2005 17:26:56 -0400</pubDate>
  </item>
  <item>
   <title>Text Dividers - v3</title>
   <link>http://nexi.com/80</link>
   <description>Keywords: Site:Nexi Help Node Editing Basics<br/>= Visible Divider<br/><br/>Enter four dashes (or more) on a line by itself to get a horizontal divider line.<br/><br/>&lt;code&gt;<br/>Above the line.<br/>----<br/>Below the line.<br/>&lt;/code&gt;<br/><br/>&lt;sample&gt;<br/>Above the line.<br/>----<br/>Below the line.<br/>&lt;/sample&gt;<br/><br/>= Invisible Divider<br/><br/>Entering just three dashes on a line by itself makes an invisible divider, which is useful for keeping text next to floated graphics.<br/><br/>Here is an example *without* an invisible divider:<br/>&lt;sample&gt;<br/>[fall_colors_1.jpg;bare;left]<br/>Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat.<br/><br/>[fall_colors_2.jpg;bare;left]<br/>Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.<br/>&lt;/sample&gt;<br/><br/>And here is an example with an invisible divider:<br/>&lt;sample&gt;<br/>[fall_colors.jpg;bare;left]<br/>Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat.<br/>---<br/>[fall_colors_2.jpg;bare;left]<br/>Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi.<br/>&lt;/sample&gt;</description>
   <pubDate>Tue, 10 May 2005 17:13:10 -0400</pubDate>
  </item>
  <item>
   <title>Tables - v3</title>
   <link>http://nexi.com/79</link>
   <description>Keywords: Site:Nexi Help Node Editing Basics<br/>= Simple Tables<br/><br/>You can easily construct simple tables with brief text elements by following this pattern:<br/><br/>* Each row of the table is one line of text.<br/>* The line must start with ''^^'' or ''||'' to identify it as a table row.<br/>* Each section  of the line that starts with ''^^'' will be turned into a *header* cell.<br/>* Each section of the line that starts with ''||'' will be turned into a *data* cell.<br/><br/>Here is what this looks like, building a simple timetable:<br/><br/>&lt;code&gt;<br/>^^Monday ||Meeting with Dave ||8:00 am<br/>^^Tuesday ||Meeting with Bob ||4:30 pm<br/>^^Wednesday ||Lunch with Dana ||11:30 am<br/>&lt;/code&gt;<br/>&lt;sample&gt;<br/>^^Monday ||Meeting with Dave ||8:00 am<br/>^^Tuesday ||Meeting with Bob ||4:30 pm<br/>^^Wednesday ||Lunch with Dana ||11:30 am<br/>&lt;/sample&gt;<br/><br/>= Advanced Tables<br/><br/>When you want to put more in a table cell than just a few words or numbers -- or when you want to use other formatting commands in the table cells -- you must use the advanced table commands, which look just like regular html table tags.<br/><br/>The advantage of using these advanced tags is that the contents of each table cell is run through the formatter as independent text, allowing you to use any formatting rules you'd like (except another layer of tables).<br/><br/>&lt;code&gt;<br/>&lt;table&gt;&lt;tr&gt;<br/>&lt;td&gt;= Location&lt;/td&gt;&lt;td&gt;= Hours&lt;/td&gt;&lt;td&gt;= Contact Info&lt;/td&gt;<br/>&lt;td&gt; 123 George Street<br/> Watership, KY  33847&lt;/td&gt;<br/>&lt;/tr&gt;&lt;tr&gt;<br/>&lt;td&gt; 338-555-2998&lt;/td&gt;<br/>&lt;td&gt;[http://neenerneener.com]&lt;/td&gt;<br/>&lt;/tr&gt;&lt;/table&gt;<br/>&lt;/code&gt;<br/>&lt;sample&gt;<br/>&lt;table&gt;&lt;tr&gt;<br/>&lt;td&gt;= Location&lt;/td&gt;&lt;td&gt;= Hours&lt;/td&gt;&lt;td&gt;= Contact Info&lt;/td&gt;<br/>&lt;/tr&gt;&lt;tr&gt;<br/>&lt;td&gt; 123 George Street<br/> Watership, KY  33847&lt;/td&gt;<br/>&lt;td&gt; 338-555-2998&lt;/td&gt;<br/>&lt;td&gt;[http://neenerneener.com]&lt;/td&gt;<br/>&lt;/tr&gt;&lt;/table&gt;<br/>&lt;/sample&gt;<br/><br/><br/>= Notes<br/><br/>At present, there is no way to span columns or rows in either sort of table.  Also, the advanced table tags brook no fiddling with attributes.</description>
   <pubDate>Tue, 10 May 2005 17:11:46 -0400</pubDate>
  </item>
  <item>
   <title>Preformatted Text (Lyrics, Poetry) - v3</title>
   <link>http://nexi.com/78</link>
   <description>Keywords: Site:Nexi Help Node Editing Basics<br/>= Poetry and other Preformatted Text<br/><br/>If you'd rather your lines were not specially formatted, you can do one of two things: Type a space as the first line of each text -- best for short poems:<br/><br/>&lt;code&gt;<br/>=== Bad Poetry<br/> This is a very bad poem<br/>   but latin, is (not)language, but passed away.<br/> Reality is a staircase leading nowhere.<br/>   The gypsies whirled 'midst bales of hay<br/>&lt;/code&gt;<br/>&lt;sample&gt;<br/>=== Bad Poetry<br/> This is a very bad poem<br/>   but latin, is (not)language, but passed away.<br/> Reality is a staircase leading nowhere.<br/>   The gypsies whirled 'midst bales of hay<br/>&lt;/sample&gt;<br/><br/>Or use the special ''&lt;pre&gt;'' / ''&lt;/pre&gt;'' commands -- which are great for wrapping large amounts of text.<br/><br/>They both do the same thing: Make your text appear just as you entered it.<br/><br/>&lt;code&gt;<br/>=== Worlds of Hurt<br/>&lt;pre&gt;<br/>Give it up fool, no one wants to ask you anything.	<br/>Two bachelors on the loose	<br/>hogijabbing fertesad monihjeftim deasrtcavet guy.<br/>and two umbrellas on a cruise	<br/>Comfort yourself and not some other<br/>did stab themselves into my bruise<br/>&lt;/pre&gt;<br/>&lt;/code&gt;<br/>&lt;sample&gt;<br/>=== Worlds of Hurt<br/>&lt;pre&gt;<br/>Give it up fool, no one wants to ask you anything.	<br/>Two bachelors on the loose	<br/>hogijabbing fertesad monihjeftim deasrtcavet guy.<br/>and two umbrellas on a cruise	<br/>Comfort yourself and not some other<br/>did stab themselves into my bruise<br/>&lt;/pre&gt;<br/>&lt;/sample&gt;</description>
   <pubDate>Tue, 10 May 2005 17:11:24 -0400</pubDate>
  </item>
  <item>
   <title>Basic Text Formatting - v3</title>
   <link>http://nexi.com/76</link>
   <description>Keywords: Site:Nexi Help Node Editing Basics<br/>= Basic Text Formatting<br/><br/>Just type into the text box.  Paragraphs are automatically formed by lines adjacent to each other.  To create a separate paragraph, leave one blank line.<br/><br/>&lt;code&gt;<br/>One line of text<br/>flows into the next line,<br/>so creating paragraphs is easy.<br/><br/>Here is another pagragraph.<br/>&lt;/code&gt;<br/><br/>&lt;sample&gt;One line of text<br/>flows into the next line,<br/>so creating paragraphs is easy.<br/><br/>Here is another pagragraph.<br/>&lt;/sample&gt;<br/><br/>= Headers<br/><br/>Headers help you organize longer pages.  Type one or more equal signs ''='' as the first character of a line, followed by a space, then the header text.<br/><br/>&lt;code&gt;<br/>= Top Level Header<br/>== Second Level Header<br/>=== Third level header<br/>&lt;/code&gt;<br/>&lt;sample&gt;<br/>= Top Level Header<br/>== Second Level Header<br/>=== Third level header<br/>&lt;/sample&gt;<br/><br/>= Italics, Bold, and Bold Italics<br/><br/>It's easy to emphasize text.  Put asterisks around it.  More asterisks, more emphasis.  It goes like this:<br/><br/>&lt;code&gt;<br/>I am normal text.<br/>*I am italic text.*<br/>**I am bold text.**<br/>***I am bold italic text.***<br/>&lt;/code&gt;<br/>&lt;sample&gt;<br/>I am normal text.<br/>*I am italic text.*<br/>**I am bold text.**<br/>***I am bold italic text.***<br/>&lt;/sample&gt;</description>
   <pubDate>Tue, 10 May 2005 17:10:28 -0400</pubDate>
  </item>
  <item>
   <title>What are tags? - v4</title>
   <link>http://nexi.com/75</link>
   <description>Keywords: Site:Nexi Help Node Editing Start<br/>=== Tags Describe<br/>Tags are words that describe content.  When you give a page a tag, you are making a statement about what information is on that page.  <br/><br/>=== Tags Classify<br/>Tags help organize information.  By giving pages that discuss similar subject matter the same tag, you associate those pages together, letting the system (and users) know that the pages are related.<br/><br/>=== Tags Work Together<br/>Tags work both singly, and in combination.  When pages have more than one tag in common, they are more tightly related together.  <br/><br/>=== Tags are Links<br/>Almost all links created between pages are made by referring to tags, not specific pages.  Nexi is an *Associative Web* of information.  Tags are the threads of the web.  <br/><br/>=== Tags Group Pages<br/>For organizational purposes, groups of pages use the same tag, often a site-specific tag such as *Site:Recipes*.  By including this tag in all of the pages in this group, it is easy to determine which pages are part of the group, and which are not.<br/><br/>= Tags Are the Heart of Nexi<br/>Consider this thought: If we have a database of recipes with tags like *beef*, *pork*, *chicken*, *entree*, *appetizer*, and so on, we don't need to know how many recipes there are, or what they are called, or what their page number is.  It just doesn't matter.<br/><br/>When we want to find a recipe, we just describe it by what tags it has: *I want a chicken entree*.  Given that simple piece of information -- those two tags -- Nexi will retrieve the chicken entrees.  Adding more tags will narrow down the results.  <br/><br/>Use the [/navigator.php|Keyword Navigator] to see this work in real-time.<br/><br/>= Making the Best Use of Tags <br/><br/>* When you are adding a new page, be sure to give it useful tags.  <br/>* If you are contributing to a &quot;site&quot; that already exists, there are probably some recommended tags that you can choose from.  You should also feel free to add more tags if you feel they will help describe the page better.<br/>* If you are creating a new group of pages, be sure to give them all a unique *Site:* tag so it will be easier to handle them en masse.<br/><br/>*More info here would be good*<br/><br/>= Sets of Tags <br/><br/>When you create a taglink, Nexi will link to every page that has all of the tags in the link.  This may be one page, or hundreds.  A taglink looks like this: ''[[tag]]''.  Every page that matches that tag will match it, and be shown.  <br/><br/>Often, this will capture pages you didn't really want to link to.  To narrow down the scope of the link, add more tags to the link.  Instead of ''[[Car]]'' you might write ''[[Car Sedan Honda]]''.</description>
   <pubDate>Tue, 10 May 2005 17:06:44 -0400</pubDate>
  </item>
  <item>
   <title>Extra Page Formatting Commands - v1</title>
   <link>http://nexi.com/87</link>
   <description>Keywords: Site:Nexi Help Node Editing Advanced<br/>= Short Examples<br/><br/>Wrapping text in two single quotes makes the text appear in monospace type.  It also causes any special formatting commands to be ignored.  It looks like this:  '' ' '[[PageLink]]' ' ''.  *Well, it looks like that except for the extra space between the quotes.  You shouldn't put them there, but I had to to get them to show up.... *<br/><br/>= Code Tags<br/><br/>You can wrap text in ''&lt;code&gt;'' and ''&lt;/code&gt;'' tags to get the same effect <br/>as the code fragments above.  <br/>(Special commands are ignored and your formatting is preserved.)<br/><br/>&lt;code&gt;<br/>You can wrap text in ''&lt;code&gt;'' and ''&lt;/code&gt;'' tags to get the same effect <br/>as the code fragments above.  <br/>(Special commands are ignored and your formatting is preserved.)<br/>&lt;/code&gt;<br/><br/>= Sample Tags<br/><br/>Wrapping text in ''&lt;sample&gt;'' and ''&lt;/sample&gt;'' is used above to show how the formatting works.<br/><br/>&lt;sample&gt;<br/>Wrapping text in ''&lt;sample&gt;'' and ''&lt;/sample&gt;'' is used above to show how the formatting works.<br/>&lt;/sample&gt;</description>
   <pubDate>Tue, 10 May 2005 17:29:17 -0400</pubDate>
  </item>
  <item>
   <title>2003-08-19 - Waterloo, Ontario - v1</title>
   <link>http://nexi.com/61</link>
   <description>Keywords: Site:Catbear Tour Node<br/></description>
   <pubDate>Sat, 07 May 2005 15:09:35 -0400</pubDate>
  </item>
  <item>
   <title>2003-08-11 - Kalamazoo, Michigan - v1</title>
   <link>http://nexi.com/60</link>
   <description>Keywords: Site:Catbear Tour Node<br/></description>
   <pubDate>Sat, 07 May 2005 15:09:22 -0400</pubDate>
  </item>
 </channel>
</rss>
