I am fine to move with the crowd. One reason I suggested tiddlywiki is
because there is already a lot of great content, for example I have gained
a lot from Tobibeer's https://tobibeer.github.io/tb5/#Welcome which has
being helpful in this phase of my learning. The content is out there, just
I also start developing the new "TiddlyWiki Manual" in my TiddlySpot wiki
(http://morosanuae.tiddlyspot.com/#TiddlyWiki%20Manual)
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from
Hi to all,
I've already started using the Arlen project on Wikibooks
(https://en.wikibooks.org/wiki/Wikibooks:WikiProject_TiddlyWiki) and even
made some modifications. I invite you all there!
Adrian.
--
You received this message because you are subscribed to the Google Groups
@TonyM a TiddlyWiki version was my idea initially but a I didn't want to
put all my efforts in it without a minimum community support/help. On the
other hand a TiiddlyWiki version would have all the obstacles/limitations
that the current GitHub version has, that makes collaboration very
Toward that end, I updated the page with the list you posted in your
original email. Here it is.
https://en.wikibooks.org/wiki/TiddlyWiki_for_Users
I have a feeling the reference might end up in a separate book.
We could call it the *TiddlyWiki Desk Reference*.
Someday, there will hopefully be
We could use Wikibooks as well if we wanted to. Plus they already are used
to doing things in the book sort of way. I started a couple books there a
few months ago, but I am not a writer. However I believe Wikibooks would
work perfect if we want to use MediaWiki. We can also have our own project
This requires deeper thought, perhaps with different "tracks" Newby, User,
Dev - but here is a quick one
- Overview should describe the feature and what id does in both simlple
and advanced uses
- Context - the various contexts in which this feature fits and can be
used eg
I can provide a free MediaWiki instance if you want, in a day or so, but my
preference was someone to build such a thing in tiddlyWiki itself.
Just ask if you want the mediaWiki instance and provide a user name and
email address (to AM [at] PSaT.com.au) if you want me to grant full update
@TonyM I don't know if I clearly understood what you said but maybe we have
a similar perspective. I imagine a documentation system that's dynamic not
static, with multiple views, capable to morph based on some user selected
criteria. That means, the ability to find knowledge in multiple ways:
Of special note is TiddlyWiki enables multiple views and collection of the
same content. We should be able to provide different structures that
support different user populations or degree of knowledge. A standard
tiddler with standard tabs with related tiddlers about each element we wish
to
Ciao Adrian
moros...@gmail.com wrote:
>
> It happens to me very often to forget the exact syntax or parameters order
> of a macro, so I need some kind of quick reference
>
On this I think you are absolutely, unequivocally, without doubt, right.
A series of Crib Sheets could be a Godsend.
In my proposal I'm not trying to cover only the newbies but all kind of
users, including myself. That's why I proposed two main sections: GUIDES
and REFERENCES. It happens to me very often to forget the exact syntax or
parameters order of a macro, so I need some kind of quick reference that is
Ciao Adrian, TonyM e tutti,
A footnote.
I think the approach can be developed empirically. What does a newbie need?
Talking for myself, back when I started, IF I had been pointed to a
resource (that effectively stands in for training) like Ton Gerner's
Customisation TW
Adrian et all,
There seems to me to be two issues, the structure of the documentation and
the knowledge within it. There are great resources out there that document
many details well, however they often suit a particular audience well, but
rarely for the newby (if it does its over simple). If
Hi Josiah and thanks a lot for your effort to give me a thorough answer.
I've waited an answer like that can offer me some kind of summary of the
problem because, honestly, I didn't know how/where to find it and my
searches didn't gave me satisfying results.
I don't want to be misunderstood. I
If you look back you will see on the main group a lot of discussion of how
to arrive at better "documentation". I have been heavily involved in some
of that. In the last few months there have been two major attempts to
supplement documentation via Reddit & StackExchange. The first is stalled.
16 matches
Mail list logo
