Currently we're spamming localizers everywhere. While creating specific NotComponents only for localization may be overkill at this stage, we should make sure to use Localizer internally in existing Not* components.
This maybe de-prioritized unless we can identify concrete business targets for first clients before mid-August, in which case we'll probably try to localize the demo for those potential clients
Overview
NOTE: This may not be necessary, because MudBlazor supports localization
Currently we're spamming localizers everywhere. While creating specific NotComponents only for localization may be overkill at this stage, we should make sure to use Localizer internally in existing Not* components.