linguist VS taxonomy

Released a new version Linguist 5.0 - browser extension to translate and learn languages. Linguist is all-in-one translator, it supports translation of selected text, full-page translation, and translation of any text you input. Linguist has a text-to-speech feature and a dictionary to save translations and remind some words and phrases later. You can choose any translation service, including Google, Bing, and DeepL. Linguist supports custom translators, so you can add your favorite translation service, for example, use ChatGPT as a custom translator.

Look at https://github.com/translate-tools/linguist This is a popular browser extension built with typescript. This repository illustrate a high code quality and development best practices

One question. What type of license does Linguist use? In the GitHub repository it indicates that it uses a BSD-3-Clause license, but in the add-ons store webpage it is licensed under the GPLv3. Could you clarify it? Thanks.

Try Linguist for your browser: - Chrome - Firefox

with the custom translator that you can point to your personal LibreTranslate server.

I am building this app with inspiration from Taxonomy and Acme corp so a lot of the design comes from there.

View on GitHub

Now, I must confess that I'm primarily a back-end engineer, and crafting a beautiful front-end was, well, a bit of an adventure. To keep things straightforward, I opted for simplicity. I figured I could enhance it as my customer base grew, as the real value, of course, lies in the robustness of the API and its backend. Looking back, I might consider using a template like https://tx.shadcn.com/ if I were to start all over again. It appears to be a great starting point for any SaaS, but the setup might pose some challenges.

Check out these two GitHub repositories: https://github.com/sadmann7/skateshop/ and https://github.com/shadcn/taxonomy/. They both use Next.js 13 and have well-structured folders and well-written code. Next.js provides performance optimization. To improve it further, avoid loading unnecessary items and use a CDN for fast content delivery. Both not loading unnecessary content & lazy loading) and CDN is 2 individual topics to dive into.

I've also been inspired by this repo, but the Vercel template seems more achievable for me at this point.

In addition to the repository I mentioned in my original post, I've also been inspired by another repository (Taxonomy Repo) which has implemented a similar Stripe integration. However, this one is a bit more complex and I'm finding the Vercel template to be more achievable for my current skill level.

I'm currently working on a Next.js project where I'm trying to integrate Stripe for payments and webhooks. I've been following the Taxonomy GitHub repo for guidance, particularly for setting up the app router and the lib files.