This folder contains source code for the generation of uno's documentation

Download and install docfx on your computer.

brew install docfx

choco install docfx

Use a node version manager or the version of node specified in the .nvmrc file nvm or nvs

nvs use

or

nvm use

Then install the dependencies

npm install

The process of generating implemented views is documented on this page. Building docs website locally with DocFX. As stated in the documentation, it will probably fail, but it will create stub files and let DocFx build without errors. By default, the build swallows DocFx errors (it prints them in the console), that is for simplicity since you don't need the implemented views. To test DocFx and break on error run the npm run strict command.

DocFx will use the content of the styles folder when building. When working locally, source-maps are generated to help debugging the site; the javascript and css are not minified for the same reason. It's very important that the build command is ran just before committing your work; this will minify the code, clean up the styles and _site folders and build the DocFx according to the docfx.json. The CI only runs the DocFx command, it will not regenerate the styles folder.

With browsersync and gulp watch, any changes in the sass, js and Docfx templates should be rebuilt automatically. This command starts the project with the debug flag. This prevents the js from being minified and generates source-maps (easier debugging). It will concatenate all the js into one docfx.js file.

npm start

Will build the docfx documentation according to the docfx.json file, will minify and concatenate all javascript everything in the docfx.js file (exceptmain.js) and will compile and minify the sass. This command needs to be run before committing any changes to the repos.

npm run build

This command is similar to start, but it will minify the js and the sass and won't generate any source-maps.

npm run prod

The reference pages are generate by the CI and are not there locally. This causes errors when building docfx. You can generate stub pages (see in the Generate Implemented Views section). Since generating those is often unnecessary, it's faster to generate them only if they are needed. When running the command strict, it is the same as running the Prod command but the errors won't be ignored.

npm run strict

This command will erase the content of the styles and _site/styles folders.

npm run clean

The templating files are in the folder layout and partial. The javascript and scss files associated to a component are in the component directory. The javascript functions and utilities are in the service folder. The shared constant are in the constant.js file. The render order of the component is important; the functions are called in the render.js file. Every js file is concatenated into the docfx.js file in the styles folder and every scss file is concatenated into the main.css.

The docfx.vendor.* files in the vendor folder are there to freeze the dependencies. To update them, delete the files and copy the newly generated files from the _site/style folder.

Every file in the styles folder is automatically generated and should not be modified manually.

Spell-checking for the docs is done as part of a GitHub Action.

If you'd like to perform the same check locally, you can run:

• npm install -g [email protected] to install the cSpell CLI
• cspell --config ./cSpell.json "doc/**/*.md" --no-progress to check all the markdown files in the doc folder.

Markdown linting for the docs is done as part of a GitHub Action.

If you'd like to perform the same check locally, you can run:

• npm install -g [email protected] to install the markdownlint CLI
• markdownlint "doc/**/*.md" to lint all the markdown files in the doc folder.

You can also install the markdownlint Visual Studio Code Extension to easily check markdown linting and style while writing documentation.

The local environment is usually located on port 3000 unless another process is already using it.

You have to remove the docs fragment from the WordPress menu to reach your local documentation server.

For detailed instructions on how to run DocFx locally, please refer to the DocFx Local Setup Guide.