Hello engineers, Today I tried to implement a basic structure for internationalization using the i18next package. However, the documentation seems a little vague. I decided to abandon that idea and go with the suggested alternative - next-intl. It appears to have up-to-date documentation and seems straightforward. I will try the next step tomorrow.

Hi EveryOne! I am a complete beginner in coding and i want to know how i can start my learning journey in coding to learn web development. Looking forward to learn and connect with everyone inside here to become successful💯 @Karol Szykula Thank you so much for having me in your amazing community🔥

I was investigating today which internationalization package to use. The Next.js docs page lists several options to consider. Each has pros and cons (according to Perplexity): - next-intl: Pros: Middleware routing, TypeScript-first, great dev tools, production-ready Cons: Learning curve, less flexible for custom setups - next-international: Pros: Zero-config setup, simple API, excellent DX Cons: Younger project, smaller community - next-i18n-router: Pros: Clean URL routing, SEO-optimized, lightweight Cons: Manual translation handling required - paraglide-next: Pros: Compile-time safety, tiny bundles, blazing fast Cons: New ecosystem, fewer integrations - lingui: Pros: ICU message format, CLI extraction, framework-agnostic Cons: JSX macro setup, more configuration - tolgee: Pros: Visual translation editor, in-app editing, headless Cons: Paid tiers for scale, vendor dependency - next-intlayer: Pros: Edge runtime support, streaming-friendly Cons: Early development, limited documentation - gt-next: Pros: AI-powered translations, quick setup Cons: Relies on external translation service - i18next: Pros: Mature ecosystem, huge plugin library Cons: Heavy bundle, complex Next.js config I'm leaning toward i18next - its mature ecosystem and strong maintenance make it appealing. It should be reasonably easy to install and set up according to these pages: - https://github.com/i18next/next-i18next - https://www.locize.com/blog/i18n-next-app-router/

Hello engineers, Adding typography with the shadcn/ui library is super easy. There are already prepared typography components. They aren't in the installed library by default, but you can easily copy/paste them. Next thing solved by the library. I love it :) Link to the typograpy. Link to the diff in the repository.

Hello engineers, Have you ever wondered how to easily create a sign-up page in your application? In the past, developers had to write everything from scratch - the entire form. Now, with the shadcn library, you can use predefined blocks with just a few clicks: - On their website, in the top left corner, there's a "Blocks" link. - Choose the block you need, like "Sign Up". - Install it with the single command displayed. - Now you can use it on any page you want. It's that easy! :) Below is an example I added to FarmAssistant. It still needs some adjustments for colors and such, but it's already looking really great!