One place to document and access everything needed for a TiddlyWiki portal website.
Things like content, processes/communications to update content.
TiddlyWiki has wicked strengths in regards to recording/maintaining information, componentizing information, aggregating information, searching/presenting information, etc.. Although TiddlyWiki can successfully be used as an alternative to a website, why would we use TiddlyWiki to create websites when it doesn't behave like a website? (For example: try using the back button in your web browser.)
TiddlyWiki, in a stellar way, behaves like a single page web application. As a website, it is cumbersome.
So for a product website, why not use something that excels at the job of being a website?
Whether a true portal website or a TiddlyWiki instance, any information gathered here helps figure out what kind of resources the TiddlyWiki community wants/needs.