11–20 of 52 posts
And in parallel create something specific to React which demonstrates your skills and at the same time useful to others.
All the very best.
To me, part of the joy of small personal sites is that you can sidestep all of the tooling and compilation stuff and instead just write and publish. But I’ve also seen some highly interactive portfolio apps that run on React or similar, so a lot depends on your vision and what excites you.
If you are looking for a front end role, a great idea, otherwise it's not a bad idea. But, I would suggest going with Next over React for static content, this a great starter https://vercel.com/templates/next.js/nextjs-boilerplate and your build process will be all set from the set and tied to the created GitHub main branch, best of luck!
If this was a work task, you would consider those things, plus time to deliver, cost and existing skill in React (versus need to upskill resources).
My advice would be to go through that process. What are your requirements, both from a functional and organizational point of view? From there, what options do you have to achieve the requirements? And finally, what are the costs, benefits and potential risks/rewards of both?
That level of technical analysis would be an excellent addition to a portfolio.
If you want to show off React, do a demo somewhere other than your main website. It's really offputting to see gratuitous interactivity on personal sites that just gets in the way of actually reading what's there.
You should use “resume” to show off your skills. Nobody is looking at a portfolio site.
If you want to do a portfolio regardless, especially for non job hunting purposes, do it however you'd like and spend however much time you want, ONLY IF you enjoy creating such a website. Otherwise anything that is not ugly is ok, and my personal preference would be to give the website a somewhat "modern" look, although not fancy.
Focus on the content of the portfolio and don't sweat the invisible details.
If you are looking for a front end role, a great idea, otherwise it's not a bad idea. But, I would suggest going with Next over React for static content, this a great starter https://vercel.com/templates/next.js/nextjs-boilerplate and your build process will be all set from the set and tied to the created GitHub main branch, best of luck!
If you are looking for a front end role, a great idea, otherwise it's not a bad idea. But, I would suggest going with Next over React for static content, this a great starter https://vercel.com/templates/next.js/nextjs-boilerplate and your build process will be all set from the set and tied to the created GitHub main branch, best of luck!
Agree, you can use the React-isms to easily compose html into reusable components while statically generating everything or React Server Components.