101–110 of 113 posts
What’s wrong with just plain HTML and Nginx or Apache?
Same question. Netlify CMS and Eleventy seem like un-necessary complexity here. Apache or Nginx web servers can be setup with a one click install on most web hosts.
Earlier quoted context omitted.
Same question. Netlify CMS and Eleventy seem like un-necessary complexity here. Apache or Nginx web servers can be setup with a one click install on most web hosts.
Well if you are looking at unnecessary complexity, there are simpler static HTTP servers than nginx and Apache. (-:
Earlier quoted context omitted.
I think even Docker might be a big ask. I mean, my experience so far has been that a lot of the people that this is targeted towards are still using platforms like Wordpress, Drupal, and Magento (all php...). Heck, git adoption still isn't 100% in this market; I just recently received sftp credentials from an agency that works in this niche.
Command line would be the only necessity. You can write a script that could download docker & run it. That's what I meant by Makefile too.
Scale this up to a government organization, and the chance of it happening is basically zero, especially in an emergency. And even if they host their own web servers and manage to get access to them, the chances of them being able to run Docker or really anything besides what they were set up for without unreasonable effort are slim at best.
I'm not saying Netlify is a good solution, but it's one that a single creative tech could figure out and set up in a day and would be almost guaranteed to work well.
I'll add two more points: - Remove all non-essential scripts: ads, analytics, fonts, social, liveperson, disqus, truste, foresee, cookielaw, etc. - Scale down or omit images
- and after the emergency is over, keep it that way
Am I old school if I'm just asking for plain HTML, CSS3 and using SFTP to upload the stuff? I don't get why it's cool to use NPM, a static site generator and netlify for an emergency website.
And even if you don't have anyone on-hand, it is, unfortunately, cheaper, easier and faster to learn all this crap and deploy to Netlify, than it is to set up a solid Web server from scratch (or even get good enough "just a folder" web hosting).
Earlier quoted context omitted.
Well if you are looking at unnecessary complexity, there are simpler static HTTP servers than nginx and Apache. (-:
Seeking out relatively unknown and unsupported HTTP servers itself becomes unnecessary complexity.
Earlier quoted context omitted.
Seeking out relatively unknown and unsupported HTTP servers itself becomes unnecessary complexity.
You are making the error of thinking that everything apart from nginx and Apache has to be "sought out". That's simply narrow minded, bespeaking a lack of wide experience, and certainly not at all supported by even looking at Debian's or Arch's package repositories let alone at (say) the FreeBSD ports collection.
It's a non-sequitur to say since I don't endorse using other servers in this instance, I must lack knowledge of them. It's not about me or you, it's about the lowest common denominator of technical person necessary to maintain a static website.
Following your path, the complexity becomes contemplating why one should use lesser known web servers instead of what one is more likely to be familiar with.
Earlier quoted context omitted.
You are making the error of thinking that everything apart from nginx and Apache has to be "sought out". That's simply narrow minded, bespeaking a lack of wide experience, and certainly not at all supported by even looking at Debian's or Arch's package repositories let alone at (say) the FreeBSD ports collection.
Yes, being narrow minded is sufficient in removing the complexities necessary to host a static website . It's a non-sequitur to say since I don't endorse using other servers in this instance, I must lack knowledge of them. It's not about me or you, it's about the lowest common denominator of technical person necessary to maintain a static website . Following your path, the complexity becomes contemplating why one sho…
You were not not endorsing them, you were claiming that they had to be sought out and that that was unnecessary complexity. It is no more added complexity to install some other Debian/Arch/FreeBSD/Fedora/whatever package than it is to install those operating systems' nginx and Apache packages, and saying otherwise is really looking for any excuse to reinforce an existing narrowminded prejudice rather than a real evaluation of complexity.
Earlier quoted context omitted.
Yes, being narrow minded is sufficient in removing the complexities necessary to host a static website . It's a non-sequitur to say since I don't endorse using other servers in this instance, I must lack knowledge of them. It's not about me or you, it's about the lowest common denominator of technical person necessary to maintain a static website . Following your path, the complexity becomes contemplating why one sho…
And now you are trying to squirm out of what you said. You were not not endorsing them, you were claiming that they had to be sought out and that that was unnecessary complexity. It is no more added complexity to install some other Debian/Arch/FreeBSD/Fedora/whatever package than it is to install those operating systems' nginx and Apache packages, and saying otherwise is really looking for any excuse to reinforce an…
Read what I wrote again. "Seeking out" is not limited to just choosing a different package, it includes the cognitive costs of exploring an option that is hitherto unknown to oneself.
You only think I'm squirming because you are qualifying what "seeking out" means to a narrow view, ironically.
How would one who is unfamiliar with those "simpler HTTP servers" even know the fact without diving into comparing the complexities of Apache and nginx against the other options? Why dive into that complexity if one is already familiar with Apache and nginx, in this use case (I'm sure you'd agree that the average person tasked for this would be more likely to be familiar with those)? This is the point you're missing.
As the most bootstrap solution I could think of, a link dump with google sheets as backend -> rendered as static html with a few extra formatting options. Quick & dirty but something that most people are able to edit without needing to get used to a new GUI or create new accounts. We then have a google form for public submission that feed the same sheet. The document is 'published to the web' as csv, so there's no ne…