Frontend Overview

the frontend module module m2 frontend creates a base for other frontend modules to inject data into the frontend module itself has no knowledge of category navigation, recommendations, search or metadata they are added via their own modules module m2 frontend categorynavigation , module m2 frontend recommendations , module m2 frontend search and module m2 frontend metadata more modules may be added in the future to support new frontend solutions removal of modules if you are not signed up for all klevu frontend solutions you may remove the modules for the solutions not in use by updating your composer json remove category navigation "replace" { "klevu/module m2 frontend metadata categorynavigation" " ", "klevu/module m2 frontend categorynavigation" " " }, remove recommendations "replace" { "klevu/module m2 frontend metadata recommendations" " ", "klevu/module m2 frontend recommendations" " ", }, remove search "replace" { "klevu/module m2 frontend metadata search" " ", "klevu/module m2 frontend search" " " }, if you are using klevu headless sdk to build the frontend of your store then you can remove all klevu frontend modules composer remove "klevu/module m2 frontend" logging the frontend group of modules implement dedicated logs to segregate them from other areas, grouped by store name these logs are found at /var/log/klevu/\[store code]/klevu \[store code] frontend log to control the level of detail included in frontend logs (configurable on a store by store basis), please use the klevu > developer settings > logging > frontend log level setting see logging for more information