Getting started with Docify for generating static sites

Docify is available as .NET Core Global Tool and published on

Installing And Updating Docify

Docify can be installed by running the following command:

> dotnet install -g docify

To update to newer version run

> dotnet update -g docify

Once installed, explore the options by calling the --help of docify

> docify --help

Development Environment

Docify files are plain text file and any compatible text editor can be used. The recommended text editors are Visual Studio Code, Notepad++, Atom, Visual Studio

Building site using Docify in Visual Studio Code
Building site using Docify in Visual Studio Code

Building Static Sites

To build a simple site, use the following command

> docify build --src C:\MySite --out C:\MyOutput --url

All files from the C:\MySite folder will be published to the C:\MyOutput.

It is possible to specify multiple folders for compilation

> docify build --src C:\MySiteDir1 C:\MySiteDir2 --out C:\MyOutput --url

This can be useful to separate the content and the frames and layouts.

If --src is not specified, current working folder is used as the source for the site.

Using Libraries

In order to use custom library use --l switch and specify the path to the library directory

> docify build --src C:\MySite C:\MySiteDir2 --out C:\MyOutput --url --l D:\MyLibrary

To use the secure library, specify the path to manifest and public key XML separated by |

> docify build --src C:\MySite C:\MySiteDir2 --out C:\MyOutput --url --l D:\MySecureLibrary.manifest|D:\SecureLibraryPublicKey.xml

To use standard library specify * as a library path

> docify build --src C:\MySite C:\MySiteDir2 --out C:\MyOutput --url --l *

On Linux systems (such as ubuntu) or MacOS it is required to protect the * library symbol, by enclosing it into quotes '*'

Using Environment

Environment is an optional --env parameter allowing to define the current environment of the site, e.g. test, staging, production. Some includes or plugins may refer the environment to enable or disable certain functionality

> docify build --env test

Serving The Site

For design purpose, site can be served, in this case site will be built to temp location (unless explicitly specified) and served in the localhost so it can be accessed i nany browser without the need to configure the host.

> docify serve

The url of the site as well as temp directory will be output to the console. Press any key to stop the host and delete all temp files.

Explore more options of serve command by using the --help switch

> docify serve --help


Docify will output the common errors into the console allowing to investigate the cause of an issue. It is additionally possible to log additional information, such as exceptions stack trace and detailed steps report by using --verbose option.

> docify build --src C:\MySite --out C:\MyOutput --url --l * --verbose


  • Create a folder at D:\MySite
  • Add new text file
  • Place the following content into the file
# My Site

Hello World from [Docify](!
  • If not already installed, run the following command to install docify (note, do not copy > symbol, it is used to indicate the command line):
> dotnet install -g docify
  • Run the following command to build the site
> docify build --src D:\MySite --out D:\MyOutput --url
  • As the result static markdown is converted into index.html page:

Example html page opened in internet browser
Example html page opened in internet browser

<h1 id="my-site">My Site</h1>
<p>Hello World from <a href="">Docify</a>!</p>

Follow this user guide to learn more features of Docify which allows you to create websites for your blog or technical documentation. This help documentation itself is generated by Docify. You can explore the source code for documentation here

Powered by Docify