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.
Websites have evolved back to static HTML/CSS/JS files
191–200 of 313 posts
Re: Websites have evolved back to static HTML/CSS/JS files
#192Earlier 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.
Re: Websites have evolved back to static HTML/CSS/JS files
#193My ageing memory may be failing me, but wasn't Perl the first widespread language to be used for CGI ?
Re: Websites have evolved back to static HTML/CSS/JS files
#194Earlier 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.
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
#195Re: Websites have evolved back to static HTML/CSS/JS files
#196Earlier 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.
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
#197There'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.
Re: Websites have evolved back to static HTML/CSS/JS files
#198Earlier 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.
Regarding WordPress and plugins:
Re: Websites have evolved back to static HTML/CSS/JS files
#199There'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…
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 ?