"Nah... not for me" - Why?

#154

To add some real-life feedback/reasons people start trying TW, here is the podcast episode which led me to discover TW myself.

Here they start talking about wikis in general. (they mention https://wiki.js.org/ (apparently beautiful in their words) and https://www.bookstackapp.com/), with reasons why they started researching selfhosted wiki solutions:

Here is the timestamped segment they start talking about TW:

There is a follow-up episode where the host says he stopped using it (not sure if he mentions why), I’ll try to find it as well.

Edit: Next episode where they do a more detailed TW review:

Still looking for the episode where they dropped it.

Edit2: Found their own wiki talking about TW pros and cons here:

https://wiki.selfhosted.show/self-hosted-apps/wikis/

Edit3: Obsidian / Joplin / Notion review:

:mag_right:FOUND it (and that reminds as well - images - I struggle with those still as well, actually I host them on imgur (I know not nice, but keeps the wiki smaller)):

2 Likes
Beyond empty.html a standard edition
Beyond empty.html a standard edition
#155

I know it’s a popular past-time, but I’ve tried to quickly create a user-friendly starter template:

https://starter.tiddlyhost.com/

The getting started tiddler has to be short, easily visually scannable and get you started within a couple of minutes with options to dive deeper.

2 Likes
#156

@Andy_Filan very much Like I was thinking about. Some notes not necessarily specific to your example;

  • Save as a local file and use (default save mechanisum) before
  • Mentioning “Lot’s of Extensions and Plugins” is importiant but to put it first suggest the core is weak and needs them. Perhaps start with highly usable as is.
    • Here I think we do need to introduce a standard edition as many of the issues here would be addressed.

Here is a minimal example except it includes relink My TiddlyWiki — standard starter edition

  • Suggestions welcome

[Edited] To discuss this edition Beyond empty.html a standard edition

1 Like
#157

What is the wizard? Something to write later, or some other resource?

Just had my eye visit. I like your white on black them. Hmm. Could use a dark discord theme.

#158

Happy for anyone to modify it and to collaborate:

https://starter.tiddlyhost.com/

Edit: Mario – removed credentials here and sent new PWD in private to Andy.

Don’t worry, these are all one-off passwords/email aliases.

Regarding:

Save as a local file and use (default save mechanisum) before

Steal this starter template
and Selfhosting (advanced)

Actually it’s more difficult to have a local html file because saving/editing doesn’t work w/o additional work, so using tiddlyhost is quicker and better UX (if I’m not mistaken). Of course this would be then covered later in the Self-hosted section or somewhere else.

#159

Yeah, I wrote the content in ~30 min, so definitely a lot of room for improvement, but I’d keep this template as simple as possible (since it’s recommended to be copied).

IMO there shouldn’t be more than 10-20 tiddlers which can be deleted by the users later if needed.

We can link to the official TW site for a deep-dive.

In general humans are not good at scanning anything that has more than 6 items (e.g. 6 bullet points, six images, 6 words, 6 emojis) so a good practice is to keep everything nice and compact, on point.

Yes, give the user options to explore further, but the basics should be very easily digestible.

BTW: I can help to adhere to some documentation / content writing & strategy best practices - I’m starting a new role as Head of Documentation soon so it will be good exercise. Not sure if you’d be interested.

Beyond empty.html a standard edition
#160

It looks good Andy, a huge improvement if adopted. Please feel free to use and edit any content I’ve uploaded if that helps.

1 Like
Beyond empty.html a standard edition
#161

So I started a discussion for a standard edition

@Andy_Filan Andy if you can apply my proposed changes please do, I would hope to include something like you propose in a standard edition, with a method to remove it and other customisations if desired.

#162

Thanks! I’ve copied over some content (tags, new tiddlers - will still do some cleanup), again, trying to keep it concise. :slight_smile: People are lazy, so they don’t read what they don’t have to (which doesn’t help them to achieve their goal to get started).

1 Like
#163

I think that misses the problem – most people who read about TiddlyWiki for the first time are not reading it to get started, they’re reading it to judge if the tool is right for them without wasting too much time and effort. If we don’t approach this problem from this angle then the introduction will be aimed not at potential new users but at those who’re already interested.

3 Likes
#164

People are also lazy when evaluating tools. The quicker you convince them your tool is worth trying, the bigger the advantage against the competition.

They are definitely 3 goals:

  1. To convince people to try TW
  2. To get them started ASAP
  3. Keep users using TW

Usually only people who try to get their own TW setup will stick with it. So #2 is very much connected to #1. If the experience of setting up their own TW instance is cumbersome, they won’t read or try more. And I’m not saying not to give people the option to explore more.

image

The template (let’s say getting started template) is a top of the funnel resource linking to the actual TW docs. Maybe there will be even a persona specific layer below the docs, but that’s just another possibility in the future.

So this top-of-the-funnel part needs to be to-the-point. Concise. Goal-oriented. I tried to come up with those goals here:

1 Like
#165

I think you may be missing my point or we’re calling the same thing with two different names. I am trying to look at this like a company selling a product and aiming to get best conversion rates. If your starting point is “How do we convince people to try X?” you automatically exclude the majority of people who don’t know what X is, so you need to start at the very beginning.

How to ensure new visitors understand our product? My comparative analysis partially covered that – when you visit Notion’s or Nimbus Note’s or Evernote’s or Wordpress you get certain sense of what the tool is designed to maximize conversion, though in their cases they have the benefit of being much well known and people having already some kind of understanding what the tool is about.

Which is why I don’t agree that “Getting Started” is the first step. I also still claim that not throwing the user immediately into the tool is a better option. With a page optimized for conversion you actually get people invested into the tool before they click the big “Try for Free” button; at least that’s how I understand the motivation of big players for designing their websites the way they do (and they have an actual monetary incentive to optimize those things).

(And just so there is no misunderstand I very much agree all steps need to be optimized and I think your Starter template is a step in the right direction, I just want to point out that for every person that even tries TW, there are most likely many who never try it in the first place because they can’t quickly grasp what the tool is about, and that’s not something a better Getting Started page solves)

3 Likes
#166

Derailing elephant - comparative analysis of TW front page

This is beautiful, kudos!

Which is why I don’t agree that “Getting Started” is the first step.

Agree here as well, the home page needs serious work. And I think your comparative analysis covers mostly the website. My comments/work are only regarding the template. If we open the discussion about the website, then to correct my amazing (lol) funnel, it would look something like this:

image

I didn’t know (apologies if I missed it) that having a new landing page/website is on the table. And although I do love TW, I think it should be a proper website IMO which is better suited to create CTAs and track conversions.

And again, the analysis is amazing work, now we just need to take actions :slight_smile: After quickly scanning it, I’m going to read it now.

Edit: Read it and completely agree - I’m not sure why that thread died? Ideally there should be some follow-up actions, maybe a poll to discuss what to replace the current landing page with, what are best-selling points for TW etc…

#167

I don’t really know what’s on the table, I am just a small contributor, at least at this point. I think if TW is ever to stop being niche tool a bigger overhaul and some hard thinking is needed to determine who and how to market it best for.
I love all the ideas for even small changes but I am a little skeptical about the overall effect they’ll have on making it more accessible to people who aren’t already invested into TW at least the tiniest bit. That is, improving the textual content of the front-page or getting a better starter will surely help people who already know they want to try it or have the time to invest, but will do little for what could be a lot of people who don’t even understand what TW is yet.
But this leads to a question “what’s the target audience of TW?” which I am not sure the community has quite figured out yet, which is another important at deciding next steps. Because perhaps TW is meant to have a very limited audience and it’s fine if it reaches a niche group of specialists who love it for what it is. There are a lot of commercial (with free option) alternatives that might be better suited for casual users who just want something that works.

1 Like
Derailing the Nah - What is TW?
#168
  • To me the answer to this is first and foremost “those who would benefit from using it”.

However on further reflection we do need to consider not being all things to all people, why?, because although at the moment its a virtuous circle, eg new users inspire experienced users, who help the new users get involved.

  • I know it seems somewhat paradoxical that we are talking about how do we get TiddlyWiki to be adopted by more people, then I question if we really want every one to see us?
  • At the very least I think we could look at the funnel and make sure we direct the different users and needs appropriately, so we do not “make a rod for our own backs”. We need to ensure no single demographic dominates, we do not attract too many “high needs” users, or technically demanding users, so we can maintain the virtuous circle we currently have.
  • One way may be to try and include users and organisations who may contribute time, skills and even money without strings attached. That is “proactively target particular audiences”, even if we do so through more than one channel, and be able to dial the channels up and down if we face difficulties.

What do we perceive as is our Mission, our Vision, our purpose, our “raison d’etre” for TiddlyWiki? @jeremyruston

  • And more importantly what do we consider as our future?
  • One answer I have is;

To promote accessibility and democratic access to software. The means of control and production of software to every person, as to their need.

2 Likes
#169

The time-saver for everyone, would be if they recognized that TW is not a multi-user note-sharing system. If people are looking for something like that, it’s going to be a heart-breaker. If people need a collaborative tool for sharing info in an office, they should probably look elsewhere.

And yes, some people have managed to sort of wedge the square peg into the round hole, but it’s not easy and it’s not part of the core functionality.

Derailing the Nah - What is TW?
#170

To not derail this too much, I’ve created a separate thread: Derailing the Nah - What is TW?

#171

I don’t know about marketing, but I can say that the whole notion of a wiki has always been off-putting to me because although I could see the utility of a website that has no back-end, it always seemed like sites like these were too rigidly-structured around atomic elements to really express the full beauty of the web, which is based on the construct of pages, which are able to offer more opportunities to combine ideas than a series of small chunks of information presented in boxes.

I wonder if formally introducing a middle level of content grouping to TW would broaden its appeal. I have felt the need for this kind of grouping and have started working with a “page” concept in my wiki (see the fourth sidebar tab), wherein I make use of the enlist filter to curate little collections of content.

This makes me quite happy. I suppose it breaks the rule that everything must be a tiddler. I think of it as multi-phasing the river.

Also I think more emphasis on visual design might be helpful, and maybe that cat could gain a doggie companion. :slight_smile:

1 Like
#172

Indeed, TiddlyWiki 5 has always emphasised the single file configuration which is definitely not suitable for multi-user note-sharing. But the wrinkle is that the Node.js configuration can be perfectly successful as a multi-user note-sharing system.

I work with a couple of companies that run the Node.js configuration of TiddlyWiki exposed to the the Internet with basic authentication of SSL.

Deploying TiddlyWiki in this way is basically the same as deploying any other standard Node.js application, and so while it requires some technical skills, those skills are not specific to TiddlyWiki.

So I think ideally the home page needs to communicate the full range of capabilities of the platform, lest TiddlyWiki be overlooked by people who are looking for more than the constraints of the single file configuration.

1 Like
Derailing the Nah - What is TW?
#173

TW can do anything, but you can’t do anything with it!

It only contains the content of your entire wiki in one HTML file, but when you actually use it, you will find that the edited content cannot be saved directly! You need to install a sleeve over it…

It’s a website that doesn’t need a database, but when you want to deploy it on the web, you’ll find that even basic user authentication needs to be solved by yourself! There is no installation package you are used to…

It is highly customizable, provided you first learn macros, widgets that are harder to understand than JS, and even adding a menu item, you must first understand the MenuBar plugin…

Of course this all has a solution in the end, and it’s a piece of cake for programmers, the problem is that people just want to find a handy tool to get the job done, not spend a lot of effort researching a tool.

The TW is a whimsical toy for those who are fascinated by the tool itself, and as a production tool it is mutilated and unfriendly.

1 Like