There's a tags option on siteConfig objects to load custom defined tags from a doc project's own folders.
Loading custom tags is set-up in such a way that it is impossible to require and use the common built-in helper functions such as lib/tags/helpers/tagNameDescription without nasty workarounds.
Currently, I've resorted to creating a librequire.js module that crawls back up the stack of parent modules until it finds a module originating from a /node_modules/documentjs/ folder and then it uses its fully resolved filename to pull up relative references.
There's a
tags
option on siteConfig objects to load custom defined tags from a doc project's own folders.Loading custom tags is set-up in such a way that it is impossible to require and use the common built-in helper functions such as
lib/tags/helpers/tagNameDescription
without nasty workarounds.Currently, I've resorted to creating a
librequire.js
module that crawls back up the stack of parent modules until it finds a module originating from a/node_modules/documentjs/
folder and then it uses its fully resolved filename to pull up relative references.i.e.
This is not something you want to burden your framework users with, is it?