Tailwind CSS

Although I use Hugo instead of React (and don't have experience with Ant Design), I'd highly suggest using Tailwind. The main reason I like it is because I can't tell if a site is using Tailwind or regular CSS, whereas once you've seen a Bootstrap site, you'll see Bootstrap everywhere whenever it's used (and I'd assume the same with Ant Design).

Most probably you don't want to create component's logic from scratch. As you already have an app, try to make a list of all components that you'll need - modals, dropdowns, etc. And then try to find a library that has all of them, because some components are rare (like a range selector).

There's some libraries built with/for tailwind, for example https://headlessui.com. It's pretty basic, but maybe it'll be enough for you.

It's not that when you're using tailwind you're not touching css. It's just a convenient way to write it and it gives you a nice design system by default.

I would not suggest that, as Material-UI and TailwindCSS are CSS frameworks, and using them together might be conflicting. Try to stick to one framework if possible. You can find some of the ready-to-use components here https://headlessui.com, it is maintained by the same team who made TailwindCSS and you can style those components with TailwindCSS. I hope this helps you.

yes you can do it but I don't see the point using them both. I would strongly recommend you to stick to one of them instead.

If you know CSS or are a beginner, Tailwind is well documented and has a large community. Tailwindcss gives you more flexibility with the approach of utility classes compared to Bootstrap; and apart from that, you get to learn more about Pure CSS while using it. I've heard developers arguing about tidiness because of too many class names. Still, with Tailiwndcss that's achievable too by separating your CSS and HTML and then moving your classes to your css file. Tailwindcss config file allows you to modify or add custom class names or use the arbitrary value if you will use the value once or twice.

Bootstrap and Tailwind are different tools with different uses and for different occasions, and not mutually exclusive.

Bootstrap is a set of components made with CSS.

Tailwind is a compiler to extract individual CSS styles to its own class name.

And so, you could recreate each component from Boostrap with Tailwind, since Tailwind is just a tool to write CSS in a less verbose way.

If you don't want to design but rather edit what others have done to quickly scaffold a site, use Boostrap.

If you want to write less CSS and already use a template engine that doesn't need CSS' modular nature, use Tailwind.

If you don't want to design and at the same time use Tailwind, check a component library built on Tailwind such as daisyUI

Tailwind is just an easier way to write regular CSS. It doesn't give you prebuilt components. Bootstrap on the other hand gives you a massive collection of pre-built components at your disposal. Bootstrap websites are super-easy to build, but look very generic. Tailwind on the other hand looks unique, but takes some extra thought and design ability to build. Also, Tailwind is lighter because it is essentially a compiler, and strips out all the classes you don't use - unlike Bootstrap. I recommend Tailwind, as it forces you to create a way more interesting site, unless you want something simple and easy to build, then I recommend Bootstrap.

Generally speaking help desk systems do not interface "deeply" with email providers. Generally speaking either a) copies of messages are forwarded to the help desk (making a copy) b) the help desk periodically checks for new messages and downloads them (making a copy)

The copies can then be organized within the help desk as required. The original emails can be managed as the user requires. Replies are sent out over the SMTP.

Does this help?

If you are already committed to Python for the data analysis then it would make sense to use Django for the framework and stick with Python throughout. In general the fewer technologies you use (unless there is real justification) will improve process and long term costs.

All things being equal the fact you would not have less (likely no) licensing costs with a Python based solution will overall reduce your long term costs.

If you will be doing data analysis and complex algorithms Django is best suited for this because of it' maturity and the huge communities providing lots of Python libraries for data analysis and more.

Everything below is personal opinion.

Personally, I do not believe you should tightly couple front & back ends, or particular frameworks (both front & back-end).

Learn the underlying language(s) and use modern practices with them. This is much more important than learning a framework, as the framework will eventually be something you utilize instead of being a crutch. Find a local developer group/slack/discord and ask for suggestions on where to learn from. Pay more attention to official language documentation than stackoverflow when looking for language-level answers.

Go will likely get you better pay than PHP, but PHP will be much easier to get up and running with. Security is not tightly coupled to anything. You just need to know how to do things well... you can code crap in any language.

Unless you want to be a poor soul being wrung out by a startup or dev shop, I would not try for "full stack" immediately. Get good at one thing and expand out from there. You will likely learn some bits of the other side as you grow.

The market is flooded with JS devs from bootcamps (I do not believe the pandemic has changed that), so I would say to try your hand as a back-end developer. Of course, if you feel you are more of a visual person, you should stick with front-end work since you will be happier there.