Before testing the tool locally, ensure you have the following prerequisites installed on your system:
- Quarto
- Babel Quarto
- Node.js and npm (Node Package Manager)
To test the tool locally, follow these steps:
-
Install the cli package from NPM:
npm i -g @oscsa/jsquarto
-
Install Quarto, to do this refer to the official Quarto installation guide
-
Install Babel quarto, refer to the official Babel Quarto installation guide
Once the dependencies are installed, you can navigate to the root directory of your project and follow the steps below:
-
To generate the documentation run the following command
jsq doc:generate source=<path to source files>
This will extract the JSDoc comments from the js files and write them to their corresponding Quarto Markdown files.
If the
sourceflag is not provided, the tool will setdocs/sourceas default.The generated
.qmdfiles can be found in thedocs/outputfolder, you can change the output directory by providing theoutputflag. -
To preview the generated documentation run
jsq doc:preview
This will generate the documentation, preview with quarto and open a link to preview the docs
-
The generated
.qmdfiles can be found in thedocs/outputfolder, you can change the output directory by providing theoutputflag.jsq doc:generate source=<path to source files> output=<path to output dir>
-
To include tutorials in the generated documentation, provide the
tutorialsflag.jsq doc:generate source=<path to source files> tutorials=<path to tutorials directory>
Alternatively, you can leverage the config.json file to store your custom settings and avoid specifying them each time you run the JSquarto tool. By modifying the fields in the config.json file, you can customize the documentation generation process according to your requirements.
To use a configuration file follow the steps below:
-
Initialize the configuration file using the command below:
jsq config:init
This will create a
config.jsonfile in the.jsquartodirectory within your project structure. You might have an already existing config file, for this case you can tell jsq to use this file instead by running;jsq config:set config=/path/to/your/directory
-
Set the desired configuration settings in the
config.jsonfile according to your preferences. To set the source files directory runjsq config:set source=/path/to/your/source/files
To set the tutorial files directory run
jsq config:set tutorial=/path/to/your/tutorial/files
To set the output directory run
jsq config:set output=/path/to/your/output/directory
To set the supported languages run
jsq config:set languages=en,fr,es
To include localized versions of the generated documentation run
jsq config:set include_localized_versions=true
This will update the config.json file with the specified settings, which will be used by the JSquarto tool during the documentation generation process.
You can also manually edit the config.json file to modify the configuration settings according to your requirements.
| Command | Description |
|---|---|
jsq config:init |
Initialize the configuration file |
jsq config:set |
Set or update configuration settings |
jsq config:get |
Get current configuration settings |
jsq doc:generate |
Generate the documentation |
jsq doc:preview |
Preview the generated documentation |
jsq doc:clean |
Delete the existing docs |
jsq doc:serve |
Serve html files in browser (if translation workflow is used. See) |
For more information on how to integrate translation tools like Crowdin with JSquarto, refer to the Crowdin Worflow guide.
For more details on using JSquarto and to see an example of the generated documentation, visit the JSQuarto documentation