[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):

 We should write down the "why" and some goals for the new website.

 For example, "maintainability" seems implicit above since _one_ reason
 "the design is stale" is because no current developers have easy access to
 change things in Trac. In the past, "make it a wiki" was one approach to
 maintainability (as also used by Trac and now GitHub + GitLab) the idea
 being that many people can easily edit the site -- how will this need be
 addressed in a new site? Taking the "wiki" motivation: how does a reader
 who discovers a mistake and is motivated to fix it do that? How is that
 fix deployed?

 Do we have any interactive requirements that might lead us to have to run
 a _particular_ Web server? Or can it be a fully static site that could be
 hosted on approximately any Web-hosting infrastructure?

 Does "the web site" include the documentation? Currently, there is some
 documentation hosted on ReadTheDocs for example -- how does that fit in?

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