Live data from Hacker News

Websites have evolved back to static HTML/CSS/JS files

paramaggarwal.substack.com

191–200 of 313 posts

Re: Websites have evolved back to static HTML/CSS/JS files

#191
post #172

Earlier quoted context omitted.

There's https://www.netlifycms.org/ if you want a static site generator with a CMS, FYI.

Are you aware of any open source applications as a CMC for static generators like Jekyll? Would be very convenient to have one with a a simple github login/auth settings page and then add/edit page/post options and the ability to select or upload a theme would be great.

NetlifyCMS works with Jekyll, Hugo, Gatsby, Middleman and a few others.

https://www.netlifycms.org/docs/jekyll/

Re: Websites have evolved back to static HTML/CSS/JS files

#192

Earlier quoted context omitted.

SPAs being the darks ages is over-the-top, but being an SPA when other web architectures could better serve the user is a dark pattern . That tax app doesn't need to be an SPA. JavaScript powered interactions make the experience nicer for the user, but that doesn't mean it needs or is improved by being a single page.

If it's a web-based user interface as this tax app sounds to be, it is arguably improved purely by being an SPA. Requiring full page reloads just to submit or change some tiny bit of data in a page is objectively bad UX.

Mostly I want my forms to be reliable, that doesn't seem to be the case for many SPA's. Getting a blank page is a very common experience and much worse than a barely discernible delay submitting a form.

Re: Websites have evolved back to static HTML/CSS/JS files

#194
post #35

Earlier quoted context omitted.

Somehow everyone I know is happy with GMail and find a full-featured email client incomprehensible. I can't stand GMail's slow UI.

I don’t understand how anybody can like gmail’s interface. It’s so convoluted and unintuitive.

Quite the opposite, it does its job pretty well for me. It has good keyboard shortcut support, and the UI is only lagging if I go into 80-100 long email threads otherwise pretty good.

What's unintuitive about a list of emails and few simple features? You also bog my mind :)

Re: Websites have evolved back to static HTML/CSS/JS files

#196
post #179

Earlier quoted context omitted.

For this typical use case, a statically rendered page with some kind of editing interface would work great, no need for databases.

Why is this downvoted? I'm a big fan of PHP, but I feel something like Netlify CMS + Jekyll on Netlify is appropriate for this. It would be super fast (statically generated and on Netlify CDN) and secure (no database or app scripts) and includes an editing interface. With WordPress I don't worry about the PHP part, but for the tendency of people to bloat it by installing plugins and not updating it enough.

How does something like Netlify CMS work for an end user?

I mean how do you skip the "storing some sort of state in DB including a users table" step?

It is very typical for a small to medium business site client to want a minimal CMS and ability to add a few more users with edit rights.

With Netlify CMS it seems the build happens from a git repo so wouldn't it require for end user to learn git?

I love how fast and easy it is to publish static sites on Netlify but I do not see how one could host client sites on Netlify without requiring constant hand holding.

Re: Websites have evolved back to static HTML/CSS/JS files

#197

There's nothing wrong with static HTML/CSS/JS. There's also nothing wrong with a rich SPA. And again, there's nothing wrong with using some kind of dynamic server-side HTML/CSS/JS presentation (like WordPress). Where there is a problem is the culture of software engineering, and the tendency to select the newest technology stack of the day for inappropriate applications. I think any seasoned software engineer has acq…

Another problem is that Google and some other search engines have only just started interpreting JS and since they determine the fate of most projects based on their search index, you'd better use a design that Google is able to turn into indexed pages.

Google was able to parse and execute JS for at least 6 years, I remember having a complex SPA in 2015 that didn’t pose any problem to Google.

Re: Websites have evolved back to static HTML/CSS/JS files

#198
post #179

Earlier quoted context omitted.

For this typical use case, a statically rendered page with some kind of editing interface would work great, no need for databases.

Why is this downvoted? I'm a big fan of PHP, but I feel something like Netlify CMS + Jekyll on Netlify is appropriate for this. It would be super fast (statically generated and on Netlify CDN) and secure (no database or app scripts) and includes an editing interface. With WordPress I don't worry about the PHP part, but for the tendency of people to bloat it by installing plugins and not updating it enough.

Netlify and Jekyll are kind of more oriented towards develoeprs, not Janine in reception.

Regarding WordPress and plugins:

    

Re: Websites have evolved back to static HTML/CSS/JS files

#199

There's nothing wrong with static HTML/CSS/JS. There's also nothing wrong with a rich SPA. And again, there's nothing wrong with using some kind of dynamic server-side HTML/CSS/JS presentation (like WordPress). Where there is a problem is the culture of software engineering, and the tendency to select the newest technology stack of the day for inappropriate applications. I think any seasoned software engineer has acq…

I'm not sure it's junior/senior so much as personal taste: Plenty of junior engineers use Vim and Emacs, neither of which are trendy in any meaningful way, and I'm sure there are senior engineers who use Visual Studio with all of its whiz-bang. Similarly with websites, some have ideas which need AJAX and, possibly, WASM, and others have ideas which need static sites or, at most, "slightly dynamic" websites with only a little JS mutating the DOM.

More specifically, it isn't always up to the engineers:

> We need to build a basic company website.

Marketing is inherently trendy and the people designing the website, as in dictating what it needs to do and look like, are the marketers, who are influenced by the "cool" websites they've seen. Marketers follow trends. It isn't really negotiable in that profession. The engineers do their best to deliver on what marketing wants, and if that requires a WASM re-implementation of NyanCat to prove that we're retro-hip and DownToFax, so be it.

Re: Websites have evolved back to static HTML/CSS/JS files

#200

> And so was born PHP, it feels like a natural extension to HTML itself. My ageing memory may be failing me, but wasn't Perl the first widespread language to be used for CGI ?

Well, C was there first in that sense, but yes, you're broadly correct. But that misses the point. PHP was developed and released as a templating language - something anybody with a bit of basic HTML knowledge (and, frankly, all HTML knowledge was basic HTML knowledge back then) could use to build an interactive site by using HTML-like tags to employ code written by somebody else as widgets in an HTML page. Perl meant writing the whole thing, including emitting HTML from the code.
Post reply on HN