[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3892: Tahoe Website Makeover

[Tahoe-LAFS]

#3892: Tahoe Website Makeover
-------------------------+-----------------------
     Reporter:  fenn-cs  |      Owner:
         Type:  defect   |     Status:  new
     Priority:  normal   |  Milestone:  undecided
    Component:  unknown  |    Version:  n/a
   Resolution:           |   Keywords:
Launchpad Bug:           |
-------------------------+-----------------------

Comment (by meejah):

 p.s. nothing against Flask at all (I've used it in my sites) but a fully
 static web-site can use any web-server at all essentially which may make
 things easier.

 My site https://meejah.ca is served directly from Git blobs via a Twisted
 web server -- this means that "how to deploy" is very easy: I just `git
 push` the new or edited content. I'm not sure if that's appropriate here,
 but something to think about (it's thus _not_ a "static web site" and does
 need to run particular software on an internet-connected machine).

 A fully static website could answer the "how to deploy" question by using
 a CI pipeline to build and push the content to the static host. That's
 kind-of how ReadTheDocs works; a WebHook tells their service that there's
 new code and it builds and deploys it.

 From a "user" perspective, I think it's important to have a small amount
 of time between "edit the docs" and seeing them live on the internet. This
 encourages more participation in the project. It can be discouraging to
 add some documentation only to see it sit in a Git repo and _not_ get
 deployed for weeks/months.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3892#comment:4>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage