commit 6213431da2fde6c6c20683ce685688ab6f6a5a6f
parent 2d1ac07bd1c79e88642487b0ee72d73521184e5f
Author: viznut_web <viznut_web@web>
Date: Wed, 8 Jun 2022 12:30:17 +0200
empty web commit
Diffstat:
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/WWW.mdwn b/WWW.mdwn
@@ -59,12 +59,13 @@ software, see [[web browser]])
Some questions to ask when building something on the web:
+ * Is this project something that actually needs the web or networking? If it can run locally, support running it locally.
* What does the site require on the client side? (The size and system requirements of the smallest browser it can be used with, the energy requirements of the client-side scripting (if used), bandwidth requirements)
* What does the site require on the server side? (Bandwidth, disk space, the memory/cpu requirements of the server-side scripting (if used))
* How easy is it to use the resources offline? (If the site consists of multiple static files, think about giving the option of downloading the content as a single file)
* Are you fine with the idea of people sharing your content on their own sites? (If yes, put it available under a free content licence and encourage people to spread it)
* Are there ways to use the site with a non-web protocol/client? ([[Permacomputing wiki]] can be edited via [[Git]], for example)
- * What are you planning to use as a server? Purchasing of dedicated hardware should be avoided, but using something your community already has is a good idea. Using a time-sharing account to a small, local webhotel is usually a better idea than buying "cloud computing" from a multinational corporation.
+ * What are you planning to use as a server? Purchasing of dedicated hardware should be avoided, but using something your community already has is a good idea. Using a time-sharing account to a small, local webhotel is a better idea than buying "cloud computing" from a multinational corporation (even if you'll only get 99.9% uptime instead of 99.999%).
## Software
