DPDK Architecture  ->  Library (v3.4.4)

Configuration

Before you start using the Hydrate function (and working on the project in general) it's important to add the proper configuration based on the project requirements like multilingual support.

Because the hydrate function handles all data for the application it uses all of these values under the hood.

Is this website multilingual?

Add the multilingual setting to the config and set enabled to true. Don't forget to specify a fallback to redirect a user when they navigate to the website directly.

{
  "multilingual": {
    "enabled": true,
    "fallback": {
      "url": "nl",
      "statusCode": 307
    }
  }
}

If the website is not multilingual, set enabled to false.

A non-multilingual website can still be setup in a way to potentially support it later on. For this reason you should still specify the fallback url and make sure it matches with the content from the CMS.

Example: We make a Dutch (for now) website. Set it to nl and make sure the content from the CMS is saved as dutch.

Is there glossary coming from the CMS?

Add the glossary setting to the config and set enabled to true.

{
  "application" {
    "glossary": {
      "enabled": true
    }
  }
}

This setting is only important when glossary from the CMS should override the glossary that's defined in the project. For more information about how to use the glossary, please look at useGlossary.

Last modifiedMonday, August 30, 2021, 2:00:02 PM UTC
Last authorColin van Eenige
Commit IDfd08685