@charlie: clearly you speak as one who's been around this loop a good few times already, and your advice about engaging a "lead visionary" (custodian/ librarian/ evangelist) is right-on, IMHO.
Moreover: I think that work you shared in an earlier thread <https://intertwingularityslicendice.neocities.org/CJ_ORM.html> is an awe-inspiring display of mastery over a number of skill-sets that such a project lead would do very well to have, including Information Architecture, Relational Database Modelling, advanced TW5 interface design, etc. All that being said: what you've built there is (to invoke ESR's immortal metaphor) a Cathedral, not a Bazaar... And i wonder to what extent such an application might serve the needs of users in the context that Cedric describes. Bottom line: i think Charlie's closing point is really the clincher: whatever it is that users will actually find helpful (as indicated not by what they say up front, but what they actually do after the fact!) is what will carry the day. So it is that i've had to swallow the bitter pill of using Google Docs vs Wiki for collaborative documentation-building so many times already... (just thinking about it makes me wanna puke :-) /walt On Saturday, January 30, 2021 at 1:32:27 PM UTC work.ced...@gmail.com wrote: > I also would like to add that the backend developer wants to leave the > company and that I am new there so the solution that I am looking for > should be very easy to set up and use quickly. I hope that Tiddly will be > the right one. > > Le samedi 30 janvier 2021 à 14:28:54 UTC+1, C J a écrit : > >> Thank you for your answers! >> >> I am interested in the git synchronisation and the different >> aforementioned plugins and approaches. I do not know how to do the git sync >> and I would need an example. >> >> However, I would like to make it collaborative. Ludwa06 and Finn said >> that it is difficult for a team. >> I do not know GitHub pages. Is it free? We use a private GitLab business >> account so I am not sure that it would be the solution. >> >> If you could provide me with a recipe to use it like Finn with the >> implementation of Charlie and Sylvain's ideas I will try it on Monday. >> >> To be honest I will compare it to Notion, Bookstack and Tettra. Knowing >> that we are a very small company (14 employees including 4 full-time >> developers) I have to find a free solution while escaping from the messy >> situation where nobody knows how the guy who is just sitting next to you >> installs software, runs programs, writes his code and deploys it, etc. >> >> This situation has consequences: if someone is absent or leaves the >> company the onboarding is very hard. Last Monday I spend all my time trying >> to set up a program. Finally, on Tuesday its developer told me that he has >> a lot of steps to explain to me, that I have to follow to start the >> applications with many installations. >> >> This is my case and the reason for what I am looking for a private Wiki. >> >> Best Regards. >> Cedric >> >> Le samedi 30 janvier 2021 à 13:57:48 UTC+1, flanc...@gmail.com a écrit : >> >>> @ludwa6 does make a point, at least in my opinion. A wiki is most >>> definitely a powerful tool, and tiddlyWiki holds the potential to make a >>> great, modernized version of one. The issue with using tiddlyWiki as a >>> group or team wiki, in my experience, is implementing proper controls. For >>> example, in my collaborative tiddlyWiki at wiki.finnsoftware.net, I’ve >>> removed all traces of control panel, trash button, and anything to find >>> them, including advanced search to prevent users from modifying the “core >>> vitals” of the software. TiddlyWiki was made to be a personal notebook, and >>> hence has not had proper testing (or documentation) at a team level. Anyone >>> attempting to do this will surely face bugs and issues, and the main thing >>> needed to do all of this correctly is patience. >>> >>> The second point I will make is questioning to the extent at which >>> Cedric would like to use TiddlyWiki. It is one thing to make a tiddlyWiki >>> hosted on GitHub that displays your changes. It is quite another to make it >>> fully collaborative, even with all the amazing plugins available. I one >>> again would stress the importance of using GitHub Pages over a server to >>> Cedric if he seeks to make the wiki fully collaborative, as at least that >>> has a little bit of testing for this purpose. >>> >>> Regards, >>> Finn Lancaster >>> Software Developer finnsoftware.net >>> Implementing TiddlyWiki at wiki.finnsoftware.net >>> >>> On Sat, Jan 30, 2021 at 7:32 AM Hans Wobbe <hww...@gmail.com> wrote: >>> >>>> ludwa6: >>>> >>>> Thanks for you post. It resonated with me since its insights are >>>> consistent with me experience. I also appreciate the Rufus Pollack link >>>> >>>> Regards, >>>> Hans >>>> >>>> >>>> On Saturday, January 30, 2021 at 5:29:12 AM UTC-5 ludwa6 wrote: >>>> >>> The UseCase that Cedric has shared falls squarely in the middle of a >>>>> problem space that TW is very well-suited to solve, i think, and much as >>>>> i >>>>> resonate with the ideas shared by Finn and Charlie have shared, what i'm >>>>> really hungry for is a working example of some solution that solves a >>>>> UseCase as close as possible to that which the OP here describes. >>>>> >>>>> Reason i ask is: much as i love wiki for personal KM & productivity >>>>> management (have used different desktop wikis over many years, and >>>>> finally >>>>> settled on TW5 as the best solution for me), every time i have tried to >>>>> deploy it as a workgroup solution, it has failed to achieve sufficient >>>>> traction to warrant its continued maintenance. >>>>> >>>>> My theory of cause about this could be thought of as the flipside of >>>>> the very coin that makes wiki such a powerful tool for quickly building >>>>> an >>>>> extensive knowledge base, and a PERSONAL interface to same: it's fast, >>>>> it's >>>>> "InterTWingly," it can (if built on such sound architecture as TW5) >>>>> accommodate whatever computer language you might be partial to, etc. >>>>> Problem is, when it comes to the languages that stand at higher levels up >>>>> the KM stack -i.e. for naming and tagging and classifying knowledge- we >>>>> all >>>>> have different ideas. I guess that's what Rufus Pollock means, @charlie, >>>>> when he talks about the shift that we'll see >>>>> <https://blog.okfn.org/2007/04/30/what-do-we-mean-by-componentization-for-knowledge/> >>>>> >>>>> in the coming Componentization Revolution, when that 90:10 ratio of >>>>> Content:Interface will flip around to its mirror image. With granular >>>>> content everywhere, interface-building becomes the name of the game. >>>>> Question then becomes: how do we make of that interface-building game a >>>>> really good collaborative one? >>>>> >>>>> SO: seeing as how i'm no good at this, i'd like to know who really >>>>> is. To that end: can you please share here, any and all, links to >>>>> collaborative software documentation projects powered by TW5 that are >>>>> open >>>>> for us all to explore? (read-only, i mean: the only case of wiki open to >>>>> edits by all that actually works in practice is Wikipedia -and that only >>>>> by >>>>> virtue of its army of dedicated editors!) >>>>> >>>>> /walt >>>>> On Saturday, January 30, 2021 at 3:11:43 AM UTC Charlie Veniot wrote: >>>>> >>>>>> Bonjour Cedric et bienvenue à la TiddlyWikernité (fraternité >>>>>> TiddlyWiki? Pshiuuuuu ... boom.) >>>>>> >>>>>> I really can't see TiddlyWiki being anything but a great choice for >>>>>> just about anything. Even if you try it and decide it isn't right for >>>>>> the >>>>>> job, you still have "prototyping" value and likely have the benefit of >>>>>> having better figured out your needs/requirements. >>>>>> >>>>>> The beauty of TiddlyWiki, to me: it is like a blank canvas. Don't >>>>>> let yourself get stuck in the mud trying to figure out "structure." >>>>>> Avoid >>>>>> "structure block" (like writer's block), and just get to writing. Let >>>>>> structural needs sprout organically / incrementally / iteratively, and >>>>>> try >>>>>> to keep things easily adaptable with a "componentized" approach >>>>>> <https://blog.okfn.org/2007/04/30/what-do-we-mean-by-componentization-for-knowledge/> >>>>>> . >>>>>> >>>>>> It might take time to get everything juuuust right, but it will fit >>>>>> you and your crew perfectly. The option is a "canned" solution with >>>>>> prescriptive "whatever", and then you have to take time for you and your >>>>>> crew to adapt to the solution. (Yeah, I much prefer adapt a flexible >>>>>> solution to my quirky self.) >>>>>> >>>>>> Rock'n roll ! >>>>>> >>>>>> On Friday, January 29, 2021 at 5:41:09 AM UTC-4 work.ced...@gmail.com >>>>>> wrote: >>>>>> >>>>>>> Hi everybody. >>>>>>> >>>>>>> I am Cedric, a French Software developer and I start working in a >>>>>>> very small (4 people) team o software developers in a very small >>>>>>> company. >>>>>>> >>>>>>> Unfortunately the knowledge is neither organized either shared >>>>>>> between people who yet work in the same room and I want to start >>>>>>> documenting projects and applications while managing updates and >>>>>>> versions. >>>>>>> >>>>>>> Knowing that we already have a Jira to manage our project but we >>>>>>> cannot afford for a team plan I was looking for a free open source >>>>>>> wikimedia like or a home made blog using Wagtail when I discovered >>>>>>> Tiddly. >>>>>>> >>>>>>> Do you think that it can be an suitable tool for me? >>>>>>> >>>>>>> Best regards. >>>>>>> Cedric J. >>>>>>> >>>>>> -- >>>> >>> You received this message because you are subscribed to the Google >>>> Groups "TiddlyWiki" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to tiddlywiki+...@googlegroups.com. >>>> >>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/tiddlywiki/da6bc24d-6d48-4e17-a3e4-0e4b92d31f53n%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/tiddlywiki/da6bc24d-6d48-4e17-a3e4-0e4b92d31f53n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/1eb68252-8287-4baf-920e-0d8f13729c34n%40googlegroups.com.
