gendoc

gendoc is a tool for generating documents using the built-in document generation feature of D language compilers.

This is forked from dxml/gendocs.d, and file search and specification of compilation options based on dub package information are added.

Sample Pages

• Default style: http://shoo.github.io/gendoc
• Candydoc: http://shoo.github.io/gendoc/candydoc

How to build

dub build

How to use

To use gendoc, move current directory to the dub project and enter the following command:

gendoc

Or, can be run using dub package manager:

dub run gendoc

You can apply CanDyDoc style:

dub run gendoc:candydoc

In addition, to import template document styles using gendoc's dub package:

dub build gendoc -c=init

CanDyDoc:

dub build gendoc:candydoc -c=init

When you want to know the detail of usage, you can use the help command to display help messages:

gendoc -h

Settings

You can change the settings of the directory where the *.ddoc, *.dd, *.html etc. source files are placed according to your preference. The directory is searched using the following procedure:

Search settings in the following order(Top item in list has highest priority):

1. Command line argument specifiered
   1. (--gendocConfig=<jsonfile>)
   2. (--gendocConfig=<directory>)/settings.json
   3. (--gendocConfig=<directory>)/gendoc.json
   4. (--gendocConfig=<directory>)/ddoc and (--gendocConfig=<directory>)/docs
   5. (--gendocConfig=<directory>)/ddoc and (--gendocConfig=<directory>)/source_docs
2. Search current directory
   1. ./.gendoc.json
   2. ./gendoc.json
   3. ./.gendoc/settings.json
   4. ./.gendoc/gendoc.json
   5. ./.gendoc/ddoc and ./.gendoc/docs
   6. ./.gendoc/ddoc and ./.gendoc/source_docs
   7. ./ddoc and ./source_docs * (docs may be a target)
3. Search $(HOME) (POSIX) or %USERPROFILE (Windows) directory
   1. $(HOME)/.gendoc.json
   2. $(HOME)/gendoc.json
   3. $(HOME)/.gendoc/settings.json
   4. $(HOME)/.gendoc/gendoc.json
   5. $(HOME)/.gendoc/ddoc and $(HOME)/.gendoc/docs
   6. $(HOME)/.gendoc/ddoc and $(HOME)/.gendoc/source_docs
4. Search (gendocExeDir) directory
   1. (gendocExeDir)/.gendoc.json
   2. (gendocExeDir)/gendoc.json
   3. (gendocExeDir)/.gendoc/settings.json
   4. (gendocExeDir)/.gendoc/gendoc.json
   5. (gendocExeDir)/.gendoc/ddoc and (gendocExeDir)/.gendoc/docs
   6. (gendocExeDir)/.gendoc/ddoc and (gendocExeDir)/.gendoc/source_docs
   7. (gendocExeDir)/ddoc and (gendocExeDir)/source_docs * (docs may be a gendoc's document target)
5. Search (gendocExeDir)/../etc directory
   1. (gendocExeDir)/../etc/.gendoc.json
   2. (gendocExeDir)/../etc/gendoc.json
   3. (gendocExeDir)/../etc/.gendoc/settings.json
   4. (gendocExeDir)/../etc/.gendoc/gendoc.json
   5. (gendocExeDir)/../etc/.gendoc/ddoc and (gendocExeDir)/../etc/.gendoc/docs
   6. (gendocExeDir)/../etc/.gendoc/ddoc and (gendocExeDir)/../etc/.gendoc/source_docs

gendoc.json / .gendoc/settings.json

You can change the gendoc settings by adding gendoc.json or .gendoc/settings.json to the dub package.

Example:

{
    "//": "Same to --gendocDdocs option. (Run-time arguments are preferred.)",
    "//": "Specify a directory path where the relative path from the root of dub package.",
    "//": "The directory where the `*.ddoc` files to be specified in the compilation",
    "//": "argument when generating HTML are stored.",
    "ddocs": [ "ddocs" ],
    
    "//": "Same to --gendocSourceDocs option. (Run-time arguments are preferred.)",
    "//": "Specify a directories path where the relative path from the root of dub package.",
    "//": "`*.dd` files are compiled and other files are simply copied.",
    "sourceDocs": [ "source_docs" ],
    
    "//": "Same to --gendocTarget option. (Run-time arguments are preferred.)",
    "//": "Specify a directory path where the relative path from the root of dub package.",
    "//": "The resulting HTML is generated in this directory.",
    "target": "docs",
    
    "//": "Specify names there exactly match the path.",
    "//": "For the path, specify the relative path from the first one of the",
    "//": "importPaths of dub settings.",
    "//": "Matched files are excluded from document generation.",
    "excludePaths": ["src/_internal", "src/ut.d"],
    
    "//": "Specify regex patterns there match the path.",
    "//": "For the path, specify the relative path from the first one of the",
    "//": "importPaths of dub settings.",
    "//": "Matched files are excluded from document generation.",
    "excludePatterns": [
        "(?:(?<=/)|^)\\.[^/.]+$",
        "(?:(?<=[^/]+/)|^)_[^/]+$",
        "(?:(?<=[^/]+/)|^)internal(?:\\.d)?$"
    ],
    
    "//": "Specify a name that exactly matches the full dub package name.",
    "//": "Matched packages are excluded from document generation.",
    "excludePackages": ["gendoc:example", "gendoc:test"],
    
    "//": "Specify regex patterns there match the full dub package name.",
    "//": "Matched packages are excluded from document generation.",
    "excludePackagePatterns": [
        "(?:(?<=[^:]+/)|^)_[^/]+$",
        ":docs?$"
    ],
    
    "//": "Specify pair of key and regex pattern that exactly matches the full dub package name.",
    "//": "Matched dub packages are combinined into key name. The dub packages also includes sub-packages.",
    "combinedDubPackagePatterns": {
      "gendoc": [
          "^gendoc(?::.+)?$"
      ]
    }
}

For ddocs, sourceDocs and target, the following variables can be used:

mustache

You can use mustache as a way to embed information that is difficult to manage manually, such as a list of modules, in a ddoc file. Save it with the extension *.ddoc.mustache, *.dd.mustache, such as module_list.ddoc.mustache.

MODULE_MENU={{# dub_pkg_info }}
$(MENU_DUBPKG {{ name }}, {{ version }},
  {{# children }}{
    "file": "_module_info",
    "map": {
      "tag_pkg":"MENU_PKG",
      "tag_mod":"MENU_MOD"
    }
  }{{/ children }}
)
{{/ dub_pkg_info }}

Available tags are as below:

{{ children }}

As it appears above, {{# children }} {{/ children }} is special. Recursive embedding is done to represent the package tree structure. At that time, it is possible to change the contents with the information described inside. The information is in JSON format or mustache format.

• If the literal start token of {, [, " is included in the same line with {{# children }} start tag, it is treated as JSON format.
  • In the case of JSON format, it is possible to take one of three types: string, array, or object.

    • string: Treat the string as "mustache".
      Example:

      {{# children }}"foo{{ xxx }}bar"{{/ children }}
      

    • array: Interpret as like command line arguments.

      Options	Type	Description
      (first argumenet)	string	file name or path of mustache
      -i / --import	string[]	search path of mustache file (first argument)
      -m / --map	string[stirng]	define additional variable
      -u / --use	string[]	usable section
      Example:

      {{# children }}[
        "_module_info",
        "-m=tag_pkg=INFO_PKG",
        "-m=tag_mod=INFO_MOD"
      ]{{/ children }}
      

    • object: Interpret the data structure.

      Field	Type	Description
      file	string	file name or path of mustache
      imports	string[]	search path of mustache file (file field)
      contents	string	mustache (File field takes precedence)
      map	string[stirng]	define additional variable
      useSections	string[]	usable section
      Example:

      {{# children }}{
        "file": "_module_info",
        "map": {
          "tag_pkg":"INFO_PKG",
          "tag_mod":"INFO_MOD"
        }
      }{{/ children }}
      

  • If the file is specified above, rendering will be performed with the target file.
• If none of the above, JSON parsing fails, or a muctache string is specified even in JSON format, treat it as a mustache string.
  • If a mustache-style string is specified in either way, the string is rendered directly as mustache instead of a file.

{{ rdmd }} and {{ command }}

{{# rdmd}} {{/ rdmd}} and {{# command}} {{/ command}} are also special. The result is replaced with the contents of stdout and stderr after the program is executed.

{{ rdmd }} executes the string contained inside as dlang source code with rdmd --eval

{{# rdmd }}
  writeln("Hello, world!");
{{/ rdmd }}

{{ command }} executes the contained string as a single command line. Line breaks are interpreted as delimiters for arguments. In the case of a line break delimited, invoke the process directly. In the case of one line, the command is invoked in the shell.

{{# command }}
  dmd
  -ofbuild directory/foo
  main.d
{{/ command }} {{# command}}echo "xxx"{{/ command}}

In either case of {{ rdmd }} or {{ command }}, the invoked program can interact with gendoc through stdio.

gendoc responds to requests from the launched guest program. One request or response communicates via a JSON object without lines. Guest program requests are passed line by line to the stderr. gendoc responds to requests with one line. The request starts with ::gendoc-request::, followed by a JSON string.

::gendoc-request::{ "type": "ReqEcho", "value": {"msg": "test"} }

The response type corresponds to the request type.

Each piece of information is composed of a JSON object composed of type and value as follows, and the value includes a payload. The following examples include line breaks and indents for readability, but do not break lines in the data actually used.

{
 "type":  "ReqInfo",
 "value": { }
}

License

gendoc is licensed by Boost Software License 1.0

gendoc depends on:

• dub (MIT)
• mustache-d (BSL-1.0)

Generated html by dendoc depends on:

• jQuery (CDN) (MIT)