You want to look at and create information in whatever way works for you, and Wagn lets you do that with many special URLs (web addresses) that take you exactly where you want to go, and show you just what you want to see.
Examples
http://www.wagn.org/search/fruit
http://www.wagn.org/new/Support_Ticket
http://www.wagn.org/new/Support_Ticket?_status=answered (see setting default content with links)
http://www.wagn.org/card/edit/Web_address_for_everything
http://www.wagn.org/card/changes/Web_address_for_everything
http://www.wagn.org/card/options/Web_address_for_everything
http://www.wagn.org/card/related/Web_address_for_everything/*plusses
http://www.wagn.org/card/view/1031
http://www.wagn.org/wagn/Web_address_for_everything+howto?layout=noside
http://www.wagn.org/wagn/Web_address_for_everything+howto?layout=blankhttp://www.wagn.org/wagn/Web_address_for_everything+howto?layout=none
http://www.wagn.org/wagn/Web_address_for_everything+howto?view=content
http://www.wagn.org/wagn/Web_address_for_everything+howto?layout=blank&view=naked
http://www.wagn.org/wagn/Recipe+*type+by_name?item=open
http://www.wagn.org/wagn/Image+*type+by_update?item=change
http://www.wagn.org/wagn/User+Image+*type_plus_right+by_create?item=titled
http://www.wagn.org/wagn/NewCardName?type=Image
How To
To make links that do simple searches, replace "/wagn/cardname" in a regular address with "/search/what you're looking for".
To make a link to add a card, after the base address put "/card/new".
To make links that create new cards of a specific card type, replace "/wagn/cardname" with "/new/cardtype of new card". Examples above also show setting default content with links.
By default when you go to a card's page you are in the View tab. You can link directly to a card's other tabs by replacing /wagn/ in the address with "/card/edit/", "/card/options/", etc. You can even link directly to the Related tab's subtabs using addresses like "/card/related/cardname/config".
Every card in Wagn is identified internally by a number, which you can use instead of its name with "/card/edit/" or "/card/options/", etc.
The rest of these use the usual URL syntax for key/value pairs — the URL is followed by a question mark, and each key/value pair is expressed as "key=value", with an ampersand to separate each key/value pair (e.g. [[/wagn/Wagn_News?layout=noside&view=content]]) :
To see a card without some or all of the usual surrounding interface you can specify a layout and/or a views:
- remove the header links and footer credit — "layout=blank"
- remove all HTML outside the card itself — "layout=none"
- eliminate the card interface around the card itself — "view=content"
- eliminate the card interface and any HTML around the card — "view=naked"
You can override the views of items in a Pointer or Search with "item=" and the name of the view you want to apply.
You can specify the type of a named card (if it doesn't exist yet, so that clicking on it offers to add it) with type=|card type|
You can specify the size of images with "?size="
Tips
- The styling of internal and external links is different, and Wagn treats anything with a complete web address (beginning with http) as external. To make these links so that Wagn recognizes them as internal, just skip the first part of the address. For example you'd edit http://wagn.org/search/fruit down to just/search/fruit — so [[/wagn/search/fruit|search for fruit]] ends up looking like search for fruit.
- adding a "file ending" to a card's name can return a variety of file formats, for exampleL: http://www.wagn.org/wagn/web_address_for_everything+Tips.txt
- Cards can be referred to by their numerical ID as well as by a name (this is helpful sometimes when troubleshooting). On any page, you can find the main card's ID number by viewing source then searching for 'div id="main"' and then in that tag, '"cardId"="|number|"'. Once you have the ID, you can construct addresses such as "/card/view/1031", "/card/edit/1031", etc.
- Some of these can be powerfully combined by using inclusions inside of links, especially with contextual names. (Note that you will want to use the naked views in such cases, to avoid unwanted HTML that otherwise goes before and after inclusions.) Also see contextual web addresses.
Some of this will be changing. See RESTful Web API.
