sounds pretty good! As you suggested, the button must enforce jumping to a dedicated discussion thread, the one and only thread officially devoted to discuss modifications to that particular doc page.
proximity is king, true! Definitely! The ‘nearer’ the better. That’s why I had wikimedia’s discussions in mind as a solution to take as a reference model.
It is the jumping that cognitively kills me.
Hence why I’m pushing hard for anything that can do what Google Sites and Notion can do: discussion is right there beside the thing being discussed.
Links from one web page to some other web page, one being discussion, the other the thing discussed, is really rough.
Maybe we are talking the same thing, I don’t know. If you can lob a picture into the discussion, that would be awesome.
hmmm, I guess there is some misunderstanding that must be cleared here, because I think we have basically the same vision: editing things in place! When I speak of ‘jumping’ from the doc page to the discussion’s it is only for the sake of preserving a clean, readable doc page, nothing more. That said, the discussion page might well be made of an exact ‘replica’ of the doc page, edited and commented on at will. Yours indeed is a very effective approach, though it must be said in my opinion that comments in Google docs are a very limited tool, unsuitable to edit more than just a few words…
Let’s not get too hung up on Google Docs. There are all kinds of tools that do the same thing.
That aside, a full and focused discussion in Google Drive anything seems to work well for me.
Good luck getting anybody to give it a proof-in-the-pudding college try with me.
I think, it would be possible to establish links form the tiddler info area, or the “pink banner” to this forum.
There is a possibility to automatically create new topic with Discourse using URL links. … BUT I don’t know, how this mechanism behaves, if a topic already exists.
See: How to create a new topic link with pre-filled information - faq - Discourse Meta
Someone other than me would need to read the stuff and make some experiments.
As I understand it, we ought to be able to embed Discourse discussion threads in TW, allowing something very similar to wikipedia’s Talk pages (albeit with the restriction that one needs to visit talk.tiddlywiki.org to actually leave a comment). See this earlier discussion:
2 Likes
I think the biggest problem (also with Wikipedia) with those discussions is, they are “out of date” as soon as a change has been made to the documentation. So the discussion – or parts of the discussion – have to be marked as obsolete, if the changes discussed have been made.
The discussions that happen on GitHub pull requests are automatically “closed” with the PR but they are there for ever in the database.
Good point. If (if!) threads could be automatically generated on talk, then an accepted PR of a tiddler (i.e in github) could have as a consequence that a new discussion thread will be created, to start blank. I.e the generated URL’s could for example be:
https://talk.tiddlywiki.org/<modified-date>/<tiddlername>
I.e the modified date serves as a version number. So the discussion thread automatically shown on tiddlywiki.com relies on this url, so the shown discussion is always for the latest version of the tiddler.
Since the content of this first post is editable for those who have the right to do so, it is easy enough to manually add links to previous discussions if the need arises. Do consider that we’re mostly talking about docs, in contrast to real code dev which happens on github. So as long as we have the “EDIT THIS POST” feature here, it is simple to dig up and link to any previous threads in the rare case that they are still interesting!
Here’s a full hypothetical workflow:
- In a tiddler on tiddlywiki.com there is a “Discussion” button (compare to wikipedia pages)
- Clicking it presents the discussion (e.g it either flips the view because it is a tab or maybe it just opens a dedicated tiddler). For posting, there is a link that navigates to the discussion on talk.tiddlywiki
- …and/but if there exists no such discussion thread then the link (or possibly the button described in bullet 1) asks if the user wants to navigate to the forum and, in the process, also automatically create a new thread which has its URL autogenerated based on the tiddler title and modified date.
2 Likes
Posts here can be edited for a limited amount of time, for the exact same reason. …
eg:
- I post: “Ths is a test”
- You post: "There is a typo in ‘Ths’ it may be “This”
- I change my first post to: “This is a test”
The reader will see
- My post: “This is a test”
- Your post: "There is a type in “Ths” it may be “This”
So the only typo is in your post now. … For that reason editing is locked after some time. Threads can become super strange, if there are replies already.
So you volunteer to be responsible for manually fixing discussions about documentations … 24/7. … right?
IMO It has to be automated as much as possible.
OK, well, the idea to edit the top post is only for convenience for the reader. I guess anyone can just make a regular post to the thread with a link to any older versions of the discussion. Again, I suspect it won’t be that common to want to bring up old versions of docs. My point is to solve the problem with “out of date discussions” that you bring up, and I think this is easily solved if we use this “modified” url to simply create a new discussion thread whenever a doc tiddler is updated. The old thread is still available, but it is not what is presented as the discussion.
Simple.
See my last reply before this one. The idea to include links to old discussions is only for convenience, a luxury.
I can envision automated solutions (either put on the tiddlywiki.com side or on the talk.tiddlywiki side) but I think it would be overkill. How often do you wish you had access to outdated docs on tiddlywiki.com ??? And even if you do wish this, is it really necessary with direct links if you could just use the search engine?
This detail is a side track. What do you think of the workflow I describe?
The problem is, that we have a system that is designed to deal with exactly those problems.
General discussions about docs can happen here.
But as soon as something is pushed using 7 Steps to Improve the TiddlyWiki Documentation the discussion about the single fix has to be at github.
We (the devs) need it there. … Linking back from a pull request with eg: 2 or 3 minor changes, to a TiddlyTalk discussion with 50 or more posts, is completely unusable.
There is not enough time to read 50 posts, just to find the 2 that are valid for the proposed change.
I don’t understand what you’re saying. Maybe there’s some premise one of us has misinterpreted:
My interpretation is that on tiddlywiki.com there should be a feature to show an active discussion about the tiddler. This discussion should take place here on talk. A main point is to co-develop the tiddler but it is not a PR. Anyone can start this discussion (if it is not already started) by – as per my proposal – clicking a link in the tiddler which triggers some magic to create a new thread here.
To avoid outdated such discussion threads, I am suggesting that the thread URL makes use of the modified field, which is obviously also accessible on tiddlywiki.com so it is simple to automatically show the correct and latest thread there.
To make the actual PR is another matter. Just like currently, whenever someone feels the urge to make the PR then this person can simply copy the resulting text from here and make a PR using your 7 steps or however he wants.
As I wrote here: Reader-driven documentation development - #23 by pmario There is a high probability that it is possible to create “dynamic links” as you describe. …
Someone could test the functionality described at: How to create a new topic link with pre-filled information - faq - Discourse Meta … If it does work to create a “dynamic” thread, that is linked to a specific tiddler with a specific “modified” date. … I don’t know.
1 Like
Would it be possible that the GitHub PR merge process itself automatically generates a new message in the TTW thread ?
If so, a reader coming back to the thread later could see that the object of the discussion has been merged in the documentation, maybe with a link to the PR.
GitHub has a very powerful notification mechanism. But I’m not sure, where the possibilities for open source accounts end. … but probably yes
Discourse also has a powerful mechanisms to receive new content. Also a yes here.
Techy stuff
Discourse docs
GitHub docs
It might be possible to customize Discourse comment threads to work inside TWs dynamic nature.
I know it will work out of the box on the static docs.