expand_less
The styling of internal and external links is different, and Wagn treats anything with a complete web address (beginning with http) as external.
adding a "file extension" to a card's name can return a variety of [[file formats]], for example: http://www.wagn.org/wagn/web_address_for_everything+Tips.txt
You can override Wagn's special handling based on a file extension with "explicit_file=true"
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 adding ?view=id. Once you have the ID, you can construct addresses such as "/~1031", "/~1031?view=edit", 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 "core" [[view]] in such cases, to avoid unwanted HTML that otherwise goes before and after inclusions.) Also see [[contextual web addresses]].
The styling of internal and external links is different, and Wagn treats anything with a complete web address (beginning with http) as external.
adding a "file extension" to a card's name can return a variety of [[file formats]], for example: http://www.wagn.org/wagn/web_address_for_everything+Tips.txt
You can override Wagn's special handling based on a file extension with "explicit_file=true"
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 adding ?view=id. Once you have the ID, you can construct addresses such as "/~1031", "/~1031?view=edit", 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 "core" [[view]] in such cases, to avoid unwanted HTML that otherwise goes before and after inclusions.) Also see [[contextual web addresses]].