Migrate Hardcoded Strings to i18n for Localization Support - For Maintenance, NotFound, PageSpeed, Settings, StatusPage, Uptime Directories

[Cihatata]

Currently, some text strings in the project are hardcoded (e.g., <div>Add</div>). To improve localization support, these strings should be replaced using the useTranslation hook from i18n.

Tasks:

• Identify and replace all hardcoded text strings with t('key').
• Add the corresponding translation keys to the gb.json file.
• Ensure that all affected components display the correct translated text.
• Contact @gorkem to add the new keys to POEditor.

Example:

Before:

<div>Add</div>

const { t } = useTranslation();
<div>{t('add')}</div>

gb.json

{
   "add": "Add",
}

This update will make the project more scalable for multiple languages.

SCOPE: Maintenance, NotFound, PageSpeed, Settings, StatusPage, Uptime Directories

[renatoka]

@gorkem-bwl Did someone take this? If not, I will.

[gorkem-bwl]

@renatoka currently @Br0wnHammer is working on this but thanks for your interest!