Re:Static web – back to the roots?
by neya on Saturday May 25, 2019 @03:28AM
(#20007596)
At some point your Wordpress installation version will be so far ahead that it may break your unmaintained theme eventually. Which is why I avoid this route if I can. It's hard to make promises to clients based off something so fragile.
[ Parent
| on HN ]
Re:Static web – back to the roots?
by mediascreen on Saturday May 25, 2019 @04:29AM
(#20007760)
Well, you have just built a custom theme to support the data from Netlify. I guess you could just as well have built a custom theme for Wordpress to avoid being stuck with an unsupported theme.
The difference is for my use case, Netflfy isn't a full CMS per se, the theme I built is for Jekyll which runs on top of netlify. It's just compiled static HTML files. There's nothing you can hack.
Re:Static web – back to the roots?
by icebraining on Saturday May 25, 2019 @04:48AM
(#20007809)
Why would your WP installation version be ahead?
If you're on WP and you forget about your website for say a year, WP version would be way high compared to the unmaintained theme that was built for an older version which would eventually break your site.
This isn't the case with a static website.