TiddlyWiki is very powerful but gives too much freedom to new users. I lost myself: A story and an idea

#41

Yes. I think the first step is to find important uses.

For instance, my periodic table wiki might do well in a look-what-you-can-do showcase, but would have no place in a list of editions-you-might-build-upon.

What I don’t know how to do here is to collect the data somewhat rigorously. Does Discourse have any polling/voting tools? I guess that’s for a later step, after an initial group discussion. But I think we will eventually need that as a way to separate the consensus from the loudest voices.

Yes, but maybe later? Let’s figure out what before worrying about how. We might end up with very different designs of we’re trying to present three editions than if we expect to handle thirty.

1 Like
#42

Yes

image

1 Like
#43

I created a new topic.
In this topic I invite a discussion about which editions are the most important and about how it would be best to proceed. I believe we can do both in one.

But anyway, if there’s something I should change, tell me (including the topic’s tags: I put “community projects” and “landing page”, but I don’t know if they’re right)

#44

While I love the TiddlyWiki in vanilla form, but for different use cases I have to install different plugins.

As other explained above, there are too many different applications, and for all of them TW is enough flexible to conform with!

As @TW_Tones explained, editions can help newcomers to get onboard more smoothly! So, may be we need to more focus on creating polished well configured editions.

I myself use TW for research and there are three editions for this. I use Mehregan which has the Zettelkasten features for scientific note-taking and I am very happy with that.

#45

I’m hoping that Tiddlyhost can be a useful place for new TiddlyWiki users to find “editions”.

At the moment it is uncurated - any Tiddlyhost user can put whatever they like there - but I could imagine a carefully curated list of editions, where the editions are carefully chosen by the community, and there’s some kind of plan to keep them updated and working as new versions of TiddlyWiki are released.

Wdyt?

Ps, this thread made me think of Provide a "download" option as well as "clone" when showing templates in the explore tab · Issue #323 · simonbaird/tiddlyhost · GitHub which would make that list more useful for people not already using Tiddlyhost.

5 Likes
#46

Fantastic idea! There can be a non-curated public library of whatever folks want to share, but also some kind of overview with helpful comments…

Maybe even a master “TW editions” wiki with tagging, other metadata, plus iframes to preview stuff?

1 Like
#47

No matter which edition you use, you need to spend time understanding it before you can find the workflow that suits you. Not just tiddlywiki, many things are like thisComplex or simple is relative. If you want to understand every function, then it is complex. If you just Only a few features are required so it’s simple for you, time will tell,

#48

This is how I wish Tiddlyhost worked right now, but would it be possible to extend it so that it does so for new accounts:

https://username.tiddlyhost.com/wikiname/

?

I would love to claim, say, the “community” username for this effort, and then to have

https://community.tiddlyhost.com/notetaking/
https://community.tiddlyhost.com/authornotes/
https://community.tiddlyhost.com/recipes/

etc.

Would this be a large change? Would it be something a competent programmer be to the code-base might be able to take on?

1 Like
#49

Yeah, this would be a big change. There’s a lot of code that assumes one domain name per site. I guess it’s doable, but I’m not sure I like the idea. I can see that it makes the naming tidier, but the additional complexity might not be worth it overall.

We could still provide a list of editions under a single username via the hub, e.g. Tiddlyhost . Also a tag could be used if different users maintain different editions.

1 Like
#50

I think the tiddlyhost hub and listing methods go a long way. Especialy since they can be used as templates. Just needs a little more promotion.

#51

I returned here because someone liked my reply and the following comes to mind,;

First, keep in mind an edition author can visit the published parent site for generating wikis and with the local storage plugin installed start using their own copy of the site

  • The last point below shows how we then take any edition to you create for inclusion in the published site

When creating the innerwiki editions force the user name to “source wiki / build” and provide a filter in advanced search for tiddlers with that user id. Now configure the innerwiki as desired, given the plugins and tiddlers installed from the parent wiki, now before closing the innerwiki export all customisations to a json file, and save the innerwiki for testing.

  • If happy with the configuration you can import the json of tiddlers into the parent to include when generating the edition in future to apply the tweaks and configuration.
  • Further to this once you have finalised the edition in the parent wiki have a custom export to export the whole edition to send to others and update the published parent wiki