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

 '''"Why?"'''

 The most important why is that the community thinks one is needed, why
 does the community think so? It's a collective responsibility. I did put a
 couple motivations why a new website might be required from my point of
 view.

 Just like you talked about "maintainability", if anyone knows of other
 "why's" here is a good place to put it as those would help in the shaping
 of the requirements or functionalities of the website.

 '''Requirements'''

 The requirements are implied by the design which was inspired by how this
 organization currently uses trac.

 ''
 _one_ reason "the design is stale" is because no current developers have
 easy access to change things in Trac.''

 The above statement seems to suggest that Trac works well "except that
 it's not maintained" and so it is a good starting point.

 Moreover the website has been designed a showcase for Tahoe that show
 basic information that we want visitors to find immediately they on the
 website.

 '''Hosting and deployment'''

 Unless there's a huge bottleneck with hosting non-static applications
 there's no need to require that website is static. The functions of the
 website should speak, for example it I envisage a blog/news section. (Some
 static site generators can power blogs too).

 There are all kinds of hosting platforms with stand procedures on hosting
 various kinds of applications on different stacks like LAMP, MERN,
 whatever.

 Unless we are working with a totally strange and outlandish stack, I think
 hosting is not top our our list of worries.


 '''Documentation'''

 The website is at least according to my understanding some sort of
 showcase and "marketing" tool, the wiki is not part of this and would only
 be linked.

 About having multiple locations where documentation could be found, that
 is not a good thing and the website should not be shaped around that
 bottleneck, however at best we would have a single link leading to "the
 wiki" at worst links to all the wikis.

 IF we move to gitlab, the wiki's can live there with the code.



 The design is open for updates, modification, corrections whatever... It
 was only  head start.

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