4 ms·
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
by ladidahh 2y ago
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 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!
- bhhaskin 2y agoNextjs is the way.
- langcss 2y agoOr Vite. It is a close call. Vite seems to more configurable but the trade-off is you spend more time figuring out how to set stuff up like SSR and routing. NextJS had it all set up but Vercel make some weird choices like rolling out the app router and saying it is recommended when it felt very beta still. My preferred thing is NextJS or Vite but constrain it to front end only. Use a better back end stack than Node. Any of the major ones will do.
- reducesuffering 2y agoAgree, you can use the React-isms to easily compose html into reusable components while statically generating everything or React Server Components.
- emseetech 2y agoOr they could just write html and css.