fix: use Hugo content-based 404 pages for proper multilingual support

Created language-specific 404 pages (content/en/404.md and content/it/404.md)
instead of using JavaScript detection. Hugo now properly routes 404 errors to
the correct language context, allowing .Lang and i18n to work correctly.
Removed JS language detection hack.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

1 files changed, 0 insertions, 12 deletions

diff --git a/themes/danix-xyz-hacker/assets/js/not-found-page.js b/themes/danix-xyz-hacker/assets/js/not-found-page.js
index 78e3591..6ec8895 100644
--- a/themes/danix-xyz-hacker/assets/js/not-found-page.js
+++ b/themes/danix-xyz-hacker/assets/js/not-found-page.js
@@ -31,17 +31,5 @@ document.addEventListener('alpine:init', () => {
     }
   }));
 
-  Alpine.data('notFoundNav', () => ({
-    get homeLink() {
-      return window.currentLang === 'it' ? '/it/' : '/';
-    },
-    get articlesLink() {
-      return window.currentLang === 'it' ? '/it/articles/' : '/articles/';
-    },
-    get contactLink() {
-      return window.currentLang === 'it' ? '/it/is/here/' : '/is/here/';
-    }
-  }));
-
   console.log('notFoundPage Alpine component registered');
 });