Nicely done. Wish this was the starter kit for most websites.
A Starter Kit for Emergency Websites
11–20 of 113 posts
Re: A Starter Kit for Emergency Websites
#12> progressively enable offline-support w/ Service Worker I'm a bit confused about this point. If it's a basic static site why would this be needed?
So that you can revisit the information even in the event that you loose internet access
In an emergency context where vital information is likely to change often, this seems a little strange. perhaps with a little (opt-in?) funding SMS could be used - surely that would be more available than internet
Re: A Starter Kit for Emergency Websites
#13I've been using exactly the same approach for spinning up local COVID-19 support groups around London, one nice example is at https://holloway.coronacorps.com/. Really like the branch to subdomain mapping feature from them.
Re: A Starter Kit for Emergency Websites
#14I like the idea of this but the process required to deploy it needs to be more carefully thought out. As it is, this currently assumes that any local agency or whatever contractor it works with will:
* Be familiar and comfortable with npm
* Be familiar and comfortable with netlify
* Be aware of this as a possible option
The bar for these folks is pretty darn low. A lot of organizations end up contracting with individuals or organizations not because they're up to speed on modern web development but because they knew them from somewhere else.
Setting this up as some kind of hosted service would probably be a good next step.
Re: A Starter Kit for Emergency Websites
#15Earlier quoted context omitted.
So that you can revisit the information even in the event that you loose internet access
In an emergency context where vital information is likely to change often, this seems a little strange. perhaps with a little (opt-in?) funding SMS could be used - surely that would be more available than internet
A Service Worker would give access to what could be important information vs no information. Given the nature of an emergency site it probably means a heightened chance of people losing internet availability.
If there is an updated version a Service Worker can check for that and pull it in if there is a connection.
Whilst imperfect to have potentially out of date information, that only happens if the person has no internet and the information has changed since they accessed it - I think it is worth the trade off of people not having any information.
For critical things, SMS probably makes more sense, but I'm not sure that is what they are trying to solve here.
Re: A Starter Kit for Emergency Websites
#16Earlier quoted context omitted.
So that you can revisit the information even in the event that you loose internet access
In an emergency context where vital information is likely to change often, this seems a little strange. perhaps with a little (opt-in?) funding SMS could be used - surely that would be more available than internet
I think offline access is really useful. Using time stamps and letting the user know they're offline will let them be able fo determine how stale the information their getting is
Re: A Starter Kit for Emergency Websites
#17I mean, call me crazy, if this is for an emergency, wouldn't it make more sense to provide a small archive with the source files in it, no third party at all.
requires an unarchiver, and a text editor.
Re: A Starter Kit for Emergency Websites
#18Earlier quoted context omitted.
So that you can revisit the information even in the event that you loose internet access
In an emergency context where vital information is likely to change often, this seems a little strange. perhaps with a little (opt-in?) funding SMS could be used - surely that would be more available than internet
SMS is usually displayed to the user as a linear chat history, and may not work well enough for large and complex content.
If vital information changes, it’s incredibly difficult to consolidate (where in the SMS thread was the latest update on topic XY again?)
SMS also can’t use pictures, requires stateful server infrastructure, is not easy to bookmark, is irretrievable when deleted, and can’t be shared as quickly as a URL.
Re: A Starter Kit for Emergency Websites
#19I like the idea of this but the process required to deploy it needs to be more carefully thought out. As it is, this currently assumes that any local agency or whatever contractor it works with will: * Be familiar and comfortable with npm * Be familiar and comfortable with netlify * Be aware of this as a possible option The bar for these folks is pretty darn low. A lot of organizations end up contracting with individ…
I agree, I'd love to see this as a docker container or Makefile where dependencies are automatically pulled in if not present on the host machine.
Re: A Starter Kit for Emergency Websites
#20As 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 need to use the API / register an app.
example https://buletin.de/InitiativeDeAjutor/ https://github.com/pax/covid19ro-linkdump