typedoc-light-theme
v1.1.0
Published
TypeDoc theme that adds some useful options (header links, custom style and script, ability to create files etc)
Downloads
6,107
Maintainers
Readme
typedoc-light-theme
TypeDoc theme that extends default theme and adds some useful options so that:
- to include extra links in header;
- to specify markup that is placed before project name;
- to customize project name;
- to change toolbar background;
- to show "Go top" link;
- to add custom CSS and JS;
- to create some files in documentation directory;
- and others.
Usage ↑
Installation:
npm install typedoc-light-theme --save-dev
To apply the theme instead of the default theme add --theme
option with path to the theme files for typedoc
command. For example:
typedoc --out docs --readme README.md --theme ./node_modules/typedoc-light-theme/src ./src
By default the generated documentation does not differ much from the one of the default theme. But you can use TypeDoc options file to set necessary parameters in order to customize the generated documentation.
typedoc --options typedoc-conf.js --out docs --readme README.md --theme ./node_modules/typedoc-light-theme/src ./src
For example:
// typedoc-conf.js
module.exports = {
"projectName": {
"link": true,
"style": "color: #c0f0d0;",
"beforeLinks": " | "
},
"links": [
{
"text": "GitHub repo",
"href": "https://github.com/gamtiq/wrapme",
"normal": true
"style": "font-size: 12px; color: #cdc;",
"target": "_top",
"id": "github_link"
},
],
"style": ".tsd-page-toolbar .header__link { color: #dd0fcc; }",
"toolbarBackground": "rgba(255, 197, 197, 0.5)",
"showGoTop": 300,
"createFile": ".nojekyll"
};
All supported options are optional and described below.
createFile: object | string
A file or set of files that should be created inside output directory after documentation is generated.
You can specify content for each file.
See description of first argument of makef.createFile
for details.
Example:
"createFile": {
".nojekyll": "",
"version.dat": 237
}
headerStart: string
Any HTML that should be placed before project name in the header.
Example:
"headerStart": "<b>></b> "
links: array
Describes a set of links that should be added into the header.
Each link should be described by object with the following fields (the only required field is href
):
class: string
- value forclass
attribute of the link; default value istitle header__link
.href: string
- value forhref
attribute.id: string
- value forid
attribute.normal: boolean
- when set totrue
,header__link_normal
will be added into value forclass
attribute to show the link with normal font weight; default value isfalse
which means that the link will be rendered with bold font.style: string
- value forstyle
attribute.target: string
- value fortarget
attribute; default value is_blank
.text: string
- any HTML that should be used as content of the link; by default value ofhref
is used.
Example:
"links": [
{
"text": "GitHub",
"href": "https://github.com/gamtiq/mixing"
},
{
"text": "npm",
"href": "https://www.npmjs.com/package/mixing",
"normal": true
}
]
linkDivider: string
Any HTML that should be used to separate links specified by links
option.
Default value is  
.
Example:
"linkDivider": " | "
projectName: object | false
Specifies whether and how project name should be rendered in the header.
Default value is { link: true, beforeLinks: ' ' }
.
Use false
to remove project name link from the header.
To customize project name element you can specify object with the following fields
(all are optional so it is possible to use an empty object as option's value):
after: string
- any HTML that should be placed after project name.before: string
- any HTML that should be placed before project name.beforeLinks: string
- any HTML that should be rendered afterafter
but before links when they are specified bylinks
option.class: string
- value forclass
attribute of the element that is used to display project name; default value istitle header__project
.href: string
- value forhref
attribute of the project link whenlink
field is set totrue
; by default relative URL forindex.html
is used.link: boolean
- when set totrue
,<a>
tag will be used as the element to display project name, otherwise<span>
will be used.name: string
- text that should be used instead of project name.style: string
- value forstyle
attribute of the element that is used to display project name.
Example:
"projectName": {
"link": true,
"before": "<span class=\"title\">☆ </span>",
"after": "<span class=\"title\"> ☆</span>"
}
script: string
Any JS that should be inlined into documentation pages. Can be used to customize behavior.
Example:
"script": "console.log('message from light theme');"
showGoTop: number
Whether "Go top" link should be added in documentation pages.
Set to 0
to exclude links.
Any positive value specifies percentage of viewport height that should be scrolled before "Go top" link will be displayed.
Default value is 80
.
Example:
"showGoTop": 300
style: string
Any CSS that should be inlined into documentation pages. Can be used to redefine and/or add some styles.
Example:
"style": "body { font-size: 12px; } .tsd-page-toolbar .header__project { color: #00c; font-size: 1.2rem; }"
toolbarBackground: string
Background style for the header.
Example:
"toolbarBackground": "linear-gradient(#def, #fff)"
Related projects ↑
- jsdoc-file - JSDoc plugin to create files inside directory of generated documentation (e.g.
.nojekyll
etc). - makef - a utility to create files inside specified directory.
License ↑
Copyright (c) 2020 Denis Sikuler
Licensed under the MIT license.