documon
Version:
A documentation system for mortals. Use with any language.
62 lines (38 loc) • 2.05 kB
Markdown
# Supported Tags
The following flags are processed:
, ,
: The three basic kinds of entities normally found in a class or module. Example: ` {type} name - description`
,
: Generally only one per page, but can have to. See the "Package / Namespace" section below. To Documon and are the same thing. They can be used interchangablly, since Documon treats them identically.
Example: ` foo.bar`
,
: Both entities are treated equally, but appear in the final rendered docs as "class".
Example: ` name`
, , , ,
: Items with these flags can be shown/hidden/filtered.
Example ``
, , ,
: These items page HTML will incorporate inherited parent properties, methods and events, which can be toggled.
: Incorporates a list of dependancies that a module or class needs to run. Generally shows up in the "meta" section.
Example ` package.Class`
: Generally used in conjunction with a class/module, and places a colored tag near the definition.
: Multiple examples can exist per item. A nice to have for templating, so the examples can be moved around and they don't have to be hard-coded into the main description. See the "Examples" section below.
: Classes, modules and methods can have multiple params. See "Params" section below.
,
: Can incorporate a {type}.
Example ` {object}`
: See "Type" section below
: By default, everything is sorted alphabetically. Use this flag if you need things to appear in a specific order.
Example: ` 10.4`
: Used to push a general informational entry to the top of a list. See the "Header" section below.
, (not fully tested, since the inline approach is better)
: Used for a method's paramter that has a default value.
: Use this to link to similar or related things. See "See Also" below.