Look ma, no React: I recoded my portfolio site with vanilla everything
1–10 of 192 posts
Re: Look ma, no React: I recoded my portfolio site with vanilla everything
#2Also I find the colour scheme hard to read but maybe it’s just me.
Re: Look ma, no React: I recoded my portfolio site with vanilla everything
#3Re: Look ma, no React: I recoded my portfolio site with vanilla everything
#4Re: Look ma, no React: I recoded my portfolio site with vanilla everything
#5Yes you don’t need React for a static site. Is this news at this point? Also I find the colour scheme hard to read but maybe it’s just me.
Re: Look ma, no React: I recoded my portfolio site with vanilla everything
#6Proceeds with a distracting animated image of the old portfolio, thought that was funny.
Re: Look ma, no React: I recoded my portfolio site with vanilla everything
#7Yes you don’t need React for a static site. Is this news at this point? Also I find the colour scheme hard to read but maybe it’s just me.
[flagged]
It’s a great way to templatize your code. Is it the only way? No. Do you even need to templatize your code? No.
Re: Look ma, no React: I recoded my portfolio site with vanilla everything
#8Re: Look ma, no React: I recoded my portfolio site with vanilla everything
#9> Coding a basic vanilla multi-page application (MPA) saves time in development (goodbye babel/postcss/SSR config) and builds are fast (this site builds in less than 1.2 seconds).
I'd hope that builds would be on the order of a small pile of milliseconds! (or zero: a site like that could just be handcoded, really).
> I'm only using these 2 lines of Javascript to add the current year in the footer copyright tag
This could also be eliminated. At least in the US, there is no legal reason to add a copyright notice at all, and you certainly don't have to add a year. Those requirements were removed years ago.
But, if all you want is the year, why not do that server-side? Or bake it into the html and set up a bit of automation to replace the year with a new one every Jan 1.