Generate Markdown from doc-comments.

Inserts/replaces API documentation derived from inline doc-comments into Markdown format, inside Markdown documents. It supports JavaDoc, JSDoc, PhpDoc and is easily extensible to many more languages.

Unlike other software I could find, docblox2md does not generate any file. It looks for placeholders in your existing (presumably Markdown) documents and edits them in place. This suits my small projects much better than more complex documentation generators.

Table of Contents

• Installation
• Usage
• Supported Languages
• MIT License

$ npm install docblox2md

This tool only modifies files, it does not generate any. You are thus in full control of your overall structure. This is best suited for smaller projects (bigger ones benefitting from heavier tools such as Doxygen).

Anywhere you want to insert the documentation for a specific file, insert an HTML comment telling docblox2md which file to process:

...markdown content...

<!-- BEGIN DOC-COMMENT src/example.php -->
<!-- END DOC-COMMENT -->

...markdown content...

The generated Markdown documentation will be inserted between these two comments. If there was already anything between them, it will be replaced by freshly generated documentation, so it is very easy to keep your Markdown files up to date.

To better adapt to your documents, you can optionally specify the header level to start with before the file name. For OO projects, this will be the header level for classes, and properties and methods will get the next level after that. It is H1 by default.

...markdown content...

<!-- BEGIN DOC-COMMENT H3 src/example.php -->
<!-- END DOC-COMMENT -->

...markdown content...

The above would title root-level comments with ###, the next level with #### if applicable.

Simply run with a list of Markdown files to update. For example:

$ docblox2md docs/*.md

Every placeholder in each input file will be processed. Any placeholder leading to a missing file or a file which doesn't parse properly will be emptied.

To omit protected in addition to items (in language where this makes sense), specify --skip-protected:

$ docblox2md --skip-protected docs/*.md

Conversely, to include private items in addition to public and protected ones, specify --include-private:

$ docblox2md --include-private docs/*.md

This initial release supports /** ... */ comment blocks and languages based on {} blocks and/or ; statement delimiters. This includes:

• C++
• Java
• JavaScript
• PHP

Recognized additional tags are:

• @access private|protected|public

As this is geared more towards end-user documentation, most tags are silently ignored. Recognized tags are:

• @{class|module|interface} [type] name
• @implements type
• @private, @protected, @public
• @param[eter] type name [[-] description...]
• @return[s] type [description...]
• @ignore

Throughout, type may be of the form {type} as well.

When @class, @module or @interface is encountered, it is itself documented with a header at the level specified in your placeholder and the following items are at one level deeper. Since code is not analyzed, those cannot be nested and any subsequent @class, @module or @interface will still be at the base level. For similar reasons, even though PHPDoc doesn't require such tags, here they are necessary to recognize depth changes.

As its name implies, the presence of @ignore hides a doc-comment.

• @endclass, @endmodule, @endinterface

If more documentation follows the contents of a group, and isn't a group itself, a lone docblock with one of the above tells docblox2md to go back to its original header level. This is not necessary if what follows is another class, module or interface.

For languages which declare property and method visibility, such as C++, Java and PHP, docblox2md will automatically skip documentation for which the next line of code (anything before { or ;) contains the private keyword, or if documentation includes the @private tag.

Similarly, docblox2md can also skip @protected items if invoked with argument --skip-protected. (See Usage.)

docblox2md is structured in three distinct sections:

• The source parser — creates a basic AST with all documentation of a source file.
• The Markdown generator — creates Markdown documentation from an AST.
• The document splicer — inserts/updates documentation sections between placeholders.

So adding the following shouldn't be too much of a pain:

• NROFF/TROFF (man-page) output
• Regular HTML output
• Perl input (no tags, very loose formatting...)
• Python input (might adhere to Doxygen tags to simplify this one)

Copyright (c) 2017-2022 Stéphane Lavergne https://github.com/vphantom

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.