Skip to main content

· 8 min read

Docusaurus 3.0

Upon reading the release notes on Docusaurus Version 3.0, it is primarily an upgrade to the foundation. Now that version 3.0 is in place they plan to release new features in the future. At the time of this writing, Docusaurus Version 3.1.1 has been released. This is a minor version that does not have breaking changes. You can go directly to 3.1.1 but because of the timing I first went from 2.4.1 to 3.0 and then did the minor upgrade to 3.1.1. Although I said this version is mainly laying the foundation it is not without some new useful features.

Some of the features that are included in Version 3.0:

· 4 min read

Transitioning to a new data source

One of the data sources that I use in my data models is from Netsuite ERP. To access the data I am using SQL Server Integration Services with an ODBC driver going through the SuiteAnalytics Connect service. Netsuite has deprecated the current data source that I am using - I am in the process of transitioning everything to the newer analytics data source named Some tables have been pretty straight forward but with different column names. One of the instances where it became more complex is with the General Ledger tables which require joining 3 or more tables whereas in the older data source it may have only required 2 tables. The table that I thought would have been straight forward but ended up requiring some investigation was the Accounting Period table.

· 6 min read

A feature that I love about docusaurus is that it uses Prism for syntax highlighting. With Prism, there is support for almost every language you can name. There is support for Power Query (M) and DAX thanks to Peter Budai. My current code samples are mainly in Javascript but I will be writing samples in DAX and Power Query so this is an important feature. Here is how I configured Docusaurus to support the additional languages and how to change themes.

· 5 min read

Using environment variables allows us to to store configuration values outside of the source files. During the build, the reference to the environment variable will be replaced with the values specified. The configuration data is the part of the project that can vary between test and production. Storing the configuration values in one place it makes it easy to update the values outside of the source code. As dotenv points out this is based on The Twelve-Factor methodology of storing configuration data separate from the code. I will show how I added environment variables to Docusaurus.