Riz, Lots of good and important ideas. You possibly know this but if you edit tiddlers in tiddlywiki.com you will get a link to the GitHub version. It is possible there to submit document changes. Perhaps you could submit some of the less controversial changes, and await some feed back on the more involved changes?
I would like to add more examples to the documentation and fill a few gaps, the only complexity is there a pile of macros on tiddlywiki.com to support easy coding of the documentation, each time I edit I need to work these "standards" out again. There seems to be no documentation guidelines, tips and documentation macro references. Personally I contribute a lot, to changes in tiddlywiki core but only through discussion and issues, or tiddlywiki.com documentation changes. I have not quite worked out how to submit changes to the core because I need to fork the repository, I am still not sure if I have to fork again after my last was a long time ago. Unfortunately it appears you are only recognised in a tiddlywiki release if you made code changes through github, not that I need this, just it would be nice. I currently have a change to propose which needs changes in most button tiddlers, I have no idea if there is an easier way than changing all tiddlers, individually in Github. I understand there is a plugin first approach, but I also have a few changes I would like to see and they over lap a little, so not sure how to proceed. Regards Tony On Saturday, 2 May 2020 07:47:57 UTC+10, Riz wrote: > > Sorry about the other post. It seems google groups is messing with me > today. > > > So, I made some changes to documentation changes and pushed them already. > Some others, I felt like I would need to consult the community. > > Few things are very much in need of updates. > > Major Points > > 1. Despite tiddlyfox disappearing entirely from Firefox addon store, it is > still documented as one of the main saving mechanisms for Tiddlywiki. > > https://tiddlywiki.com/#GettingStarted%20-%20Firefox > https://tiddlywiki.com/#GettingStarted%20-%20Android > > Other saving methods are definitely documented. However the space and > prominence given to TiddlyFox gives a false idea that it is somehow still > relevant. > > Please note: I have edited and pushed changes regarding Termux and > replaced AndTidwiki with Tiddloid. I felt like TiddlyFox warrants more > discussion and approval owing to its community nature. > > 2. What is the actual point of "Getting started" tiddlers? All but the > main getting started tiddlers are way outdated and provides false > information. I already pointed out the "Getting started Firefox" and > "Getting started Android" issues. Now look at "Getting started - Chrome" > > https://tiddlywiki.com/#GettingStarted%20-%20Chrome > > The first sentence says only HTML fallback mechanism works in Chrome. This > is false info and other saver mechanisms are documented in TW5 itself. > > The only "Getting started" Tiddler that makes a reasonable sense is > "Getting started Node JS". Delete the rest so that there is one source of > truth to maintain. > > 3. There should be a feature comparison table between the multitude of > saving options available. Throwing tons of options at a user will work > better if the user knows what is the difference between them. > > > 4. Most of the examples of filters in TW5 uses "sort". sortan is more > advanced and natural with respect to non-technical users. However it is > hard to find because user have to specifically search for it. So much so > that even experienced TW5 users forgot about its existence. I suggest we > change all filter examples from sort to sortan. > > Need for reorganisation > > 5. I know "Getting started" is one of the default tiddlers. However in the > TOC organization, it appears in "Working with Tiddlywiki". For a newbie who > accidentally closed the Getting started tiddler, one of the first places he > will look in will be Table of contents. I say we retag the "Getting > started" with HelloThere and push it to the top. > > 6. Is there a definite criteria for matters to be tagged. This is my > understanding from the main site > > - HelloThere introduces and explains the philosophical aspects of > tiddlywiki > - "Working with Tiddlywiki" explains basic tasks. > - "Learning" explains more advanced tasks > - Customisation should ideally involve things you can do regarding styles, > things you can achieve with CSS, color palettes. > > Points below is based on this understanding. > > 7. "Working with Tiddlywiki" should come before "Learning"? Because it is > much more basic. > > > 8. "Philosophy of tiddlers" should be under "HelloThere" with all other > explanations - not under learning > > 9. https://tiddlywiki.com/#TaskManagementExampleDraggableTemplate does > not require "Learning" tag > > 10. Suggested title changes > "How to hide the author's and other fields with CSS" to "How to hide > author/date/other parts of viewtemplate with CSS" > "Simple ways to write protect tiddlers" to "How to write protect > tiddlers" > > 11. Export tiddlers, Adopt a title policy - these two should be under > "Working with Tiddlywiki" because these are basic things and one of the > first things people might look for. > > 12. "How to Customize TiddlyDesktop" should be under Customisation > > 13. https://tiddlywiki.com/#Scalability is a claim. There should be links > to specific instances of such Wikis IMO. > > 14. There is a need for rearranging Learning and Working with Tiddlywiki. > Things like "Task Management example" and is variations should be together > and they should also link to community resources that implemented complex > task management systems. > > > > -- 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/c03fcf58-207b-4331-80ca-817b6b4b98be%40googlegroups.com.
