feat: add trilingual /about page with generateMetadata and footer link #31

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

TommiLindfors merged 1 commit into clarvia-org:main from HirenGajjar:feat/about-page

May 27, 2026

Merged

feat: add trilingual /about page with generateMetadata and footer link #31

feat: add trilingual /about page with generateMetadata and footer lin…

Annotations

10 warnings

Lint: src/app/[lang]/sections/TrustSection.tsx#L59

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

Lint: src/app/[lang]/sections/TrustSection.tsx#L16

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

Lint: src/app/[lang]/sections/TestimonialsSection.tsx#L7

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

Lint: src/app/[lang]/sections/FoundingSection.tsx#L19

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

Lint: src/app/[lang]/sections/FooterSection.tsx#L9

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

Lint: src/app/[lang]/page.tsx#L30

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

Lint: src/app/[lang]/layout.tsx#L2

'l' is defined but never used

Lint: src/app/[lang]/layout.tsx#L2

'COUNTRIES' is defined but never used

Lint: src/app/[lang]/contribute/page.tsx#L17

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

Lint: src/app/[lang]/about/page.tsx#L75

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element