Production wiki - how to

[JWHoneycutt]

I am a programming newbie, but am moderately comfortable with TiddlyWiki. My process is single file TW5.html's stored on Dropbox and opened from TiddlyDesktop. I have struggled with GitHub, but GitHub Desktop has finally "clicked".

I would like to share a ReadOnly wiki (Using Ton Gerner's $:/plugins/tg/ro) with 23 lot owners in a Costa Rican HomeOwners Association. My place is in this neighborhood: https://airbnb.com/h/LasPlataformasAndGuesthouse.

I have the wiki content and have created an initial production wiki - no SideBar, no end user editing. I am interested in a limited set of end users being able to comment, for me to moderate and revise the tiddlers.

On GitHub, I created a private repository (not sure if private status was needed) for the HOA. I think I can take the TW5.html file and rename it "index.html" in the repository. I can keep all image files in a subdirectory called "images" so the wiki doesn't get too big. (Should I use relative or canonical referencing to the PDF and JPG images?).

Theoretically, I could share a link to the repository that has this ReadOnly wiki in it. I have tested that the "add comment" feature now present in TiddlyWiki version 5.1.23 still works despite Ton's "ReadOnly" status.

We sorely need to revise our community rules. I am thinking of asking owners to sign in or register so comments are not anonymous and I can restrict visibility to owners (and a community attorney).

I could moderate the comments, and then revise the tiddlers to put out revised versions of the production wiki. It sounds like a lot of steps and may prove too complicated. I will have to get a workflow in order to not forget steps.

Ideally, we all build consensus amongst owners (many of the needed changes will require 100% unanimous consent, and we have yet to get 100% participation in any meeting). This may be easier now with the advent of Zoom...

1) Does anyone have a plugin that provides a "register" or "login" for access to a wiki? (like Zoom uses for access to a recording)

2) I am sure that Continuous Integration solutions are the ultimate answer, but that is beyond my skillset (for now) and I would like to get this project up and running within a couple weeks (max).

3) Should I have made the repository "Public"? (or does it matter, since I am the only one who will likely be working on it at the gitHub level).

4) Does it matter if I use relative or canonical links to images?

5) Do you know any example wiki's I can learn from or find ideas?

6) Convert to Spanish with a button? (just one tiddler at a time - ultimately the document we will create needs to be in Spanish)

Jeffrey

[Charlie Veniot]

G'day Jeffrey,

Not much I can help you with, but I did want to at least throw a curve-ball at you re getting comments from your TiddlyWiki viewers.

What if you setup your TiddlyWiki to capture user comments via some other collaboration tool that you can embed in your TiddlyWiki Tiddlers ?

Just for prototyping $hit$ and giggle$, I've setup a quick Google Spreadsheet to capture info via a Google Form, and I embedded the Google Form in a "template" tiddler.

That template tiddler takes care of putting the current tiddler's title into the first field of the form by dynamically creating the link to that Google Form with the first field pre-populated.

Then, any tiddler you want to enable for viewer comments, you could setup something very basic like I did:  transclude the tiddler in question via the Google Form template to get the current tiddler's title into the Google Forms link.

Check out the result in this sample tiddler I've added to my hosted TiddlyWiki instance.  

I didn't do anything too fancy there.  Just proof of concept !

Cheers !

[TiddlyTweeter]

JWHoneycutt opined...

I am interested in a limited set of end users being able to comment, for me to moderate and revise the tiddlers.   

 cj.v...@gmail.com replied...

What if you setup your TiddlyWiki to capture user comments via some other collaboration tool that you can embed in your TiddlyWiki Tiddlers ?  

Right! 

Any tool users would: Twitter, Telegram, Disqus etc.

The issue is that TW is not default on-line server based. That is its skill. SOMETIMES one needs add interaction. BUT whether its just an embed of an existing service or more sweat is about the purpose. 

IF you can do it through framing an extant tool then why not? If you need more then happy coding.

TT 

[Hans Wobbe]

@ cj.v

I works! Indeed!!

Now to think about how to make effective use of this.

Thanks for sharing.

Hans

[Charlie Veniot]

I just had a thought for no-fuss-no-muss/no-frills getting comments/feedback on Tiddlers:  email !!!

<a href="mailto:m...@myemailprovider.com?subject=tiddler-title">Send a comment/feedback about this tiddler.</a>

So modify the template tiddler to do this instead of that Google Forms stuff (replacing that "m...@myemailprovider.com" with the email address where comments should go):

<$list filter="[all[current]split[ ]join[%20]] +[addprefix[mailto:m...@myemailprovider.com?subject=]]">

<a href={{!!title}}  target="_blank">Send a comment/feedback about this tiddler.</a>

</$list>

[ludwa6]

Hey @Charlie: the gForms/gSheet solution was kinda cool... But this email method is simple & slick enough, i think it could actually work in production! 

But: i'm not quite clear where to stick that little code-block you've shared, to make this "comment mailto: feature appear on every tiddler. 

Would it be one of those many $:/config/EditTemplateFields/Visibility/..." tiddlers i see in list of "Shadows," perhaps

/walt

[Charlie Veniot]

G'day g'day,

Please find further below and example of what you need to do:  first, the code, then a screenshot (me having applied that code to tiddlywiki.com)

Cheers and best regards !!!

<hr style="border-width:4px;">

<center>

<$list filter="[all[current]split[ ]join[%20]] +[addprefix[mailto:m...@myemailprovider.com?subject=]]">

<a href={{!!title}}  target="_blank">Send a comment/feedback about this tiddler.</a>

</$list>

</center>

[ludwa6]

This is great, @charlie; i *almost* got it working... Only problem being, instead of this new comment link appearing just once at bottom of any given tiddler, as it does in your screenshot, it repeats itself many times in a vertical column that appears to cascade endlessly down the tiddler space.

I've copied your code verbatim (only w/ my own email address swapped-in for the dummy address) onto a new tiddler that i named "Comment Link", tagged with "$:/tags/ViewTemplate" as you have done.  The tiddler's content type is "text/vnd.tiddlywiki".  Can you see any place in here where i might have got something wrong? 

8<------(snip)------>8

<hr style="border-width:4px;">
<center>
<$list filter="[all[current]split[ ]join[%20]] +

[addprefix[mailto: waltzemail@waltzemailhost?subject=]]">

<a href={{!!title}} target="_blank">Send a comment/feedback about this tiddler.</a>


</$list>
</center>

8<------(snip)------>8

[coda coder]

Hi Charlie

On Wednesday, February 3, 2021 at 9:09:18 PM UTC-6 cj.v...@gmail.com wrote:

I just had a thought for no-fuss-no-muss/no-frills getting comments/feedback on Tiddlers:  email !!!

It would be better to cover the case where the tiddler title is one word. Something like...

<a href={{{[all[current]split[ ]join[%20]else<currentTiddler>] +[addprefix[mailto:fr...@example.com?subject=]]}}}
  target="_blank">Send a comment/feedback about <<currentTiddler>>.</a>

[Charlie Veniot]

Silly question here:  Why?

Without the "else", the transclusion works just fine.  If there is nothing to split by "space", then there is nothing to join by "%20".

I'm thinking the else just complicates things, no?  (Don't mind me: although usually verbose, I try to make programming code as uncluttered as I can.)

Along the same vein, me being overly anal and totally subjective preference:  I prefer "Send a comment/feedback about {{!!title}}".  That said, you have an excellent idea including the tiddler name in the link's display-text; very useful for any long tiddler for which the title is off screen.

[ludwa6]

Thanks @codacoder: in fact i was testing this on a one-word tiddler (as many of mine are; i use CamelCase a lot)... So i swapped that part of Charlie's code for your variation, and now it works like a champ! 

/walt

[Charlie Veniot]

I'm trying to figure out how the two different kind of links behave differently with CamelCase, and I'm not seeing any difference.

What am I missing here?

[coda coder]

Your split/join works on spaces. With a tiddler called MyTiddler, there aren't any spaces.

The "one-liner" {{{ [...] }}} is just my preference - safe to ignore.

[coda coder]

I should have added at the end, "I think". I'm a seasoned TW hacker, not an expert.

[Charlie Veniot]

Bear with me:  I'm just generally seasoned, yet not particularly spicy?

Before I forget:  it took me a bit to realize you had compacted everything down into one line.  Big "deer in the headlights moment" over here that dragged way too long.

I'm still not grasping your filter, though.  Why are you setting things up to care whether or not there are spaces?  The results of both filters are visually equal.  Does your "else" make the filter execute faster, and/or prevent some potential bug I'm unaware of?