It takes a village to raise a portal

#1

Just a thought I had.

A simple sentence that I think captures the intertwingled mess of thoughts I have about a TiddlyWiki portal, the benefits of it, and the success of it.

Some of which, in this ramble …

Related to the challenges that fascinate me:

  • how to make it easy to generate content/knowledge/information/documentation with whatever makes the most sense for each type of content/knowledge/information/documentation, and located wherever is the most suitable place, yet all available in a place that organises and shows it all (i.e. the portal.)

A critical element for success: trying to set things up (and convincing folk to set things up) so that anything that could be useful in a portal, (i.e. of benefit to TiddlyWiki) happens such that it is easy to display, as-is and direct from the source, in a portal.

Because if it requires effort to grab content/knowledge/information/documentation from a source, and then copy it, massage it, and place it somewhere such that it can be included in the portal, or requires somebody to enter it twice … it probably won’t happen.

If it is worth the time for a question to be typed, and for answers to be typed, that stuff is of value, and there’s got to be a way to easily maximise that value long-term vs just short term benefit until it goes out of sight and out of mind.

And suddenly another thought: everything seems scattered.

Or maybe it isn’t, and I missed something.

Or maybe it is, but there is no way out of it.

Man, intertwingulitis…

#2

@Charlie_Veniot here is some “Prior Art” years ago of mine. Its a WordPress site which may still be the best way to manage multiple users , but review the menus to see some of the ideas. eg Demos. I was think of making custom posts for each of the tiddlywiki elements such as edition, plugins, etc… but also publish in imbedded tiddlywiki’s this wold support search, curation and publishing along with multiple users.

http://www.colabteam.net/tiddlywiki

I thought I could use OpenID and give users permissions, and see if I could tie these permission’s to TW Receiver PhP save in imbedded wikis. At the time I did not raise enough interest or collaborators to proceed.

1 Like
#3

That is quite frigging fantastic.

In this “requirements phase” that I’m in, your site fills in so much of the picture regarding what a TiddlyWiki portal should display.

The other requirements I’m figuring out: TiddlyWiki Portal Development Processes, kind of like Software Development Process, in the sense of: how do we manage this thing? As one massive whole, or as a collection of parts? I lean towards collection of parts, so then: what are the development/maintenance/operation workflows of each part?

What the tool is, or tool(s) are, don’t really care yet. Gotta nail down every type of thing needed, and figure out processes for each kind of thing, and the best tool for the job for each thing and workflow.

Something like that. Too much in my sponge to write it all out.