Absolutely. Most projects that would be considered "websites" rather than "web applications" are likely candidates for jQuery. It's still extraordinarily useful.
Pick the right technology to solve the problem you're trying to solve.
Some inexperienced devs just try and cram every single technology they've ever heard of into a simple project when it's not needed. You're not at Facebook's scale just yet where many of these abstractions are anything other than an extra complication and a waste of time and future liability.
Your average simple website for a law firm, bike repair shop, or a pizza delivery place doesn't need 93 different libraries/frameworks/technologies/build systems/etc to show/hide a couple products or submit a form or two. You can go pretty far with just jQuery in many cases.
It gets a little more complicated as you go from simple site to more complex site to app to more complex app, but I see too many developers trying to be trendy and over engineering simple problems and wasting a lot of time and money.
jQuery had it's time. Now you just use "vanilla" JS and it is enough. No external dependencies for your landing-page / non-web-app site.
Yes, "you might not need jQuery". But, the first time you have to log real hours fixing a cross-browser bug that the jQuery team already took care of, I'm fucking firing you. Choose wisely.
"If you make a mistake try to cover it up rather than be honest about it, because your arse is on the line".