Programming

Yes, you should use third party tools (just don't take credit for them, maybe even credit the tools used in the footer). In a real job, you would leverage third party libraries to work more efficiently, so you should do the same when showing off your skills.

Absolutely fine.

Could you imagine if every developer recreated the wheel for every project?

That would be a demonstration of your ability with said libraries/frameworks. I don’t see the issue. Unless you are talking about using just the tools with little customization, then it wouldn’t be very impressive. Still not an issue tho.

Please tell me you’re not reusing an existing web server to host your site! Employers want to see that you can handle server programming. Obviously this would be hosted on an operating system of your own design, which is handy because you need to design the CPU too. Don’t forget to smelt your own copper for the wiring!

Naturally the answers to your questions depend on who is looking at the website, but from my experience...

Does the ideology of ‘using other people’s tools to create a better product’ apply here in this context

Yes.

or would it be considered plagiarism?

Absolutely not. It's showing that you can incorporate the works of others to build something great rather than spend time reinventing the wheel. Nobody's going to look at your website's source (assuming you link to it somewhere), see a bunch of .ts or .jsx files, and think "oh this person invented Typescript/React/whatever".

Should you need to reinvent Javascript, your browser, your OS, etc..? Probably not, and as long as you're using something built by others to build your website (vscode, node.js, etc), there's no reason to feel like using a library wouldn't be the same. Also, for most real world projects, you'll be using libraries you didn't write. This is just showing that you know how to use them.

Where it would be unacceptable is if you claimed to have created those libraries/tools yourself.

It's only ethical if you build the server yourself from materials found in nature.

All of society is built upon the foundation laid by others. As long as you're not misleading people into thinking you created something you didn't, I don't see any problem.

Everyone has good answers but I would check the license of more obscure libraries to just be sure you're not violating it. GitHub has a handy feature that explains the license (if one exists) in easy to understand terms. I've never ran into this issue myself but it's a good habit to have. Especially when you're working for a company.

Yes, of course. Just make sure you're abiding by their license, that'll tell anyone who cares how it may and may not be used.

Absolutely not considered plaigarism - If i built a website using React + Material UI, that shows im capable using common industry tools. That also demonstrates (to an extent) familiarity with vanilla JS and CSS.

You could have an "about this website" section that lists the tools and packages you used, and so on. If I saw that on a candidates website (a little section detailing how the page was made and crediting sources) I'd be insanely impressed. That's the kind of person you know you can work alongside.

Do i have to resort to coding my portfolio website with pure css and js to demonstrate my credibility and experience as a candidate employee?

If you did that, I'd think you're an idiot. Using libraries is standard practice.

Would you use them when building things for a client? If yes, then yes. No one gets mad at a carpenter for buying nails.

As a hiring manager, I’m always interested in seeing a candidate’s exercise of their skills. But “from absolute scratch” is not something we really do in the working world if we can possibly avoid it, so I wouldn’t expect it in your portfolio. If you’ve got some amazing JS or CSS to show off, definitely do so, but point it out because I’m otherwise expecting frameworks.

Ethically there are no problems with libraries and frameworks. If you’re using them consistently with the creators’ licenses, we’ll, that’s what those things exist for.

Everyone else uses website builders for their static websites, I don't see why I wouldn't. On the job I would expect you not to reinvent the wheel if you don't have to

Of course. It also shows that you know how to make use of third party libraries, which a lot of employers like to see.