Review common issues and resolutions.
Review the table below for some common issues and their potential cause. Please file a bug report if you believe you have encountered an unknown issue.
Incorrect styling of your published website may have several causes:
The stylesheet refers to the incorrect location
Be sure to update the
The certificate of your website has expired or is not set up correctly
Hinode adds an
integrity check and
crossorigin validation to protect against manipulation of the site’s stylesheet. Most browsers will refuse to load the stylesheet if the website’s certicate is invalid. Ensure your certificate is valid and properly loaded, for example by clicking on the
lock icon in the address bar of your browser. Check with your hosting provider if the certificate is invalid.
The DNS is not updated yet
You typically need to update address the records of your DNS provider when using a custom domain. For example, the website
CloudFlare as DNS provider and
Netlify as hosting provider. The CloudFlare DNS records includes a
CNAME record that links
gethinode.com to the endpoint
gethinode-docs.netlify.app. It may take some time for all DNS records to have been propagated properly.
The browser has cached a previous version of the website
Your browser might retain an older copy of your website and its resources in memory. Clear the browser cache if needed and reload your website. Google Chrome provides the option to empty the cache and perform a hard reload for a specific site when using the developer tools. You can add
?nocache=1 to your address in Safari to bypass the cache.
assetsfolder instead of the
staticfolder. See the documentation about images and figures for more details.
img-fluidto your vector image, for example
<img src="/img/logo.svg" class="img-fluid">.
purge = true in the
style section of your site parameters instructs Hinode to purge any unused styles from your generated stylesheet. The purger requires several npm packages to be installed, else it will throw an error such as
Cannot find module '@fullhuman/postcss-purgecss'. You can use the
Hinode template as a starting point to set up npm and the required packages. Refer to the
optimization guide for more context.
build.transpiler = "dartsass" in the
main section of your site parameters instructs Hinode to use the Dart Sass transpiler. Unlike the default
libsass transpiler, the
dartsass binary needs to be installed seperately on your machine. This includes any production servers used for
automation and deployment. If Dart Sass is not required, you can revert back to
build.transpiler = "libsass". Else follow the
installation instructions on how to install the binary.