Community Survey Results

In August we completed the TiddlyWiki User Survey for 2025. This brief, anonymous survey was designed to give us insight into the needs of TiddlyWiki users.

The results of this survey now inform the future developments, helping us focus on what would make TiddlyWiki better for you, both as software and as a community. Here are a few key observations from the survey results:

• About half of the participants described themselves as programmers. A solid fifth of the userbase has written custom JavaScript for their wiki!

• Use is often personal, with just 1⁄3 sharing their wiki to the WWW or an intranet.

• Most of the main use cases are as a knowledge base, note-taking and journaling. However, half the participants also included uses for task and project management (including CRM).

• Participants overwhelmingly had a positive impression of TiddlyWiki, the key things people appreciate are the flexibility, privacy and security that it offers.

• Key areas for improvement are: issues with documentation and tutorials (as well as ease of use in general), the out-of-the-box experience, giving more consideration to cross-device syncing, and better support for Markdown.

More observations and the full discussion on the results of the survey are available here on talk.tiddlywiki.org

Interview with Saq Imtaz - Release Manager for Release 5.4.0

I sat down with Saq Imtaz - the Release Manager for then next upcoming release and for almost an hour I was really impressed by this amazing volunteer to the community. Highlights from that discussion included:

• Saq, fascinating journey from a trained medical doctor, to non-profit work in education in the sub-Sahara that lead to TiddlyWiki Classic and then a Masters in UX Design

• Currently there is very good progress on Release v5.4.0 with work halfway complete on the critical backlog and lots of push requests (PRs) merged. The plan is to target a release in January or February 2026. Regular releases are being planned so that the milestone releases introduce new features more often.

• Saq had really positive things to say about the community and some key individuals contributing to Release v5.4.0

• We discussed the policy around backwards compatibility and how TiddlyWiki can move forward.

• Finally we discussed how Saq himself uses TiddlyWiki, from his own plugins, and note taking on fine wines and teas, to some reporting tools for social workers in Central Asia.

The full transcript is available here

TW5-Graph

TW5-Graph is a TiddlyWiki plugin which allows for the creation of elaborate graphs with a wide range of customisable functionality.

It is the spiritual successor to TiddlyMap which has served the community well for years. TW5-Graph is a redesign of the idea from the ground up. Instead of being graphing plugin for TiddlyWiki, it’s a framework to allow for graphing and charting libraries to integrate.

With TW5-Graph you can:

• Quickly create and edit graphs through a simple point-and-click GUI

• Use wikitext widgets to create customised graphs and template to exactly match your needs

• Easily create dynamic graphs to represent changing state or individual tiddlers

There’s loads TW5-Graph can do for you. Check out its demo website here.

The plugin is a masterpiece by its creator Flibbles (aka sci-fi novelist Cameron Fisher), who had this to say:

TLDR: A Discussion on Artificial Intelligence

In July this year, I posted an entry to the banner competition for the v5.3.7 Release. Little did I know that my use of the AI tool, Sora, to produce that small artwork would reignite a controversy about the use of AI within the TiddlyWiki community. It wasn’t the first debate on the topic, nor likely the last. The community itself is adjusting to this technology and being very pragmatic about its use and potential misuse. Here are just a few points for and against AI that were discussed:

• It enables those without certain skills (e.g. drawing, coding) produce work that would be impossible or very difficult for them otherwise.

• AI is “a tool that people can master” to improve productivity and capabilities, and not necessarily replace human creativity.

• Without human review, AI-generated content risks being misleading, or low-quality and what’s more long winded and verbose. That’s problematic for content intended for education and sharing among a community.

• AI can mass produce content and without synthesis, editing or curating of content, it can become generic, mechanical, or formulaic and generally a waste of time for readers to sift through.

More of this summary (generated with the help of AI) is available here.

In the end the suggestion is to add to the code of conduct: not to post the raw output of AI generated content. There are situations where AI-derived content is acceptable (eg providing a link to a chat for reference). But the valuable contributions to the community are those that people have made themselves, either from scratch or from AI tools as input.

Next Edition

• We interview Elise Springer, Associate Professor of Philosophy at Wesleyan University.. and explore how TiddlyWiki serves her work.

• There will be a showcase from talk.tiddlywiki.org of how features in TiddlyWiki are being used in creative ways.

why should I read something that you cannot even be bothered to write for yourself?

This article was written with the help of AI. However, as per our community policy, it is not the raw output, but rather a revision of the key observations that AI made of three very long discussions on talk.tiddlywiki.org. Such is the controversy of using AI as the community adjusts to this technology and attempts to be pragmatic about its use and potential misuse. Here then is a look of where we are today:

Pros / Potential Benefits

• Productivity / accessibility / lowering barrier to entry

  Many on the discussions see AI as “a tool that people can master” and can help people who otherwise lack certain skills (e.g. design, painting, coding) produce output that would be impossible or very difficult for them manually.

• Expanded creative freedom / experimentation

  For people who enjoy tinkering or are curious, AI lowers the barrier enough so they can play with art, code or design. AI allows experimentation without much overhead, to explore visual ideas without needing deep expertise, or iterate rapidly on designs.

• AI output with human oversight, editing and validation can be valuable.

  Though voice of skepticism is strong, there is recognition that LLM output can be valuable, especially as a starting point or brainstorm. There is a need for careful critical use and not blind trust, as several warn that just because something feels articulate does not mean it’s reliable. However, together AI and people can create useful content.

Cons / Risks / Downsides

• Quality concerns & accuracy / “slop”

  Several commenters emphasize that AI tools are not truly “intelligent” but rather eloquent pattern-matching systems trained to generate plausible results. Those results are often prone to “AI hallucinations” which are false but plausible suggestions lacking the real domain knowledge and expertise.

• Potential to undercut human contributors / discourage craftsmanship

  Without genuine human touch, content can lack nuance, emotional depth or connection. Instead it feels generic or formulaic, potentially reducing the uniqueness or personal voice that humans bring.

• Concern over corporatisation and power imbalance

  The original post notes that AI development is largely driven by “very powerful Internet Corporations,” which raises concerns about privacy, centralization, marketing hype, and corporate influence over what becomes “standard.”

• Ethics, transparency, and editorial responsibility

  People assert that if AI is used (for ideas, drafts, code, etc.), it should be acknowledged. The “slop” from AI should not be published verbatim without review. Always label what came from AI vs what’s your own words/code.

• Waste of readers’ time, polluting forum content.

  As one commenter said: why should someone read stuff you couldn’t be bothered to write yourself? Instead we should prioritise readability and value to other community members, aiming for concise, meaningful contributions rather than verbose AI output.

• Intelligence as process, not object

  One contributor challenges the usual framing of “natural vs artificial intelligence.” Instead of seeing “intelligence” as a discrete thing you can pack into a machine, they propose thinking of intelligence as a relational, dynamic process. This values AI as another voice in the forum of discussion and one that needs to relate to that forum.

If you want to dive even deeper into the discussions on AI you can follow these links and re-ignite some more debate:

• Discussion about AI created banner - from June 2025

• AI Generated Content on talk.tiddlywiki.org - from July 2024

• Regarding ‘Artificial Intelligence’ (AI) … #1 from April 2023

You’re the first project manager for a TiddlyWiki release - which is new for our community. What does the role mean in that context ?

I mean I’d say its not new in other open source communities, it is for us. TiddlyWiki has always been primarily Jeremy’s doing work at his own pace and his own schedule but welcoming contributions from others. And it’s been sort of discussed for a long time that you know in order to make them more efficient and remove bottlenecks, we should try to move to a different structure and way of doing things, where it takes some of the load off of Jeremy actually, so he spending less of his time with sort of maintenance and actually able to focus on other things. Not sure if quite gotten there yet, but this was meant as a step in that direction, so I think he was earlier this year that we moved the GitHub repository from being under Jeremy name to being under the TiddlyWiki organisation. So instead of jeremy/TiddlyWiki5 it became TiddlyWiki/TiddlyWiki5, and one of the reasons, well primary driver for doing that was exactly that, that having it owned by an organisation allows us to assign responsibilities to different people for different roles.

Its also the first time using GitHub’s Project dashboard - which shows us that Release 5.4 has 89 changes, 41 of which are done - Does that reflect the status of the release ?

I would look at that project plan a little bit differently in the sense that it is not necessarily intended that we get through everything on that list. Anything that potentially could be worked on has been added to that list, after which it becomes a case of who’s willing to work on something, we are basically entirely volunteer driven. So Jeremy sort of has his plateful already with a few large PRs that he started close to a year ago now that basically hasn’t the bandwidth to take on anything else. So how much of the other things we get done in time for 5.4 really depends on who else is willing to work on things.

Well, what we have done within that project plan as if you click over to the tab at the top called “Prioritized backlog”, those are the things that we sort of feel like our key features for 5.4. That absolutely need to get done, and the first four of those are all Jeremy. And since he’s more than halfway through all of them, they’re also not in the state right now where it’s easy for someone else to step in and contribute. So those are sort of the things that we think of a sort of being the cornerstones with the 5.4 release and everything else is a bonus and we’d like to get as many of them done as possible. But at the end it depends on what people want to work on.

From that point of view, I would say that we’re making very good progress on 5.4. The amount of things we have merged, I think is pretty impressive. However the exception of maybe one PR that has been merged from linonetwo that has to do with laying the groundwork for supporting WYSIWIG editing, and only the groundwork mind you. The other four big ones from Jeremy that I think are the key features are still in progress.

And you know part of the challenge, I think we’re Jeremy there is just finding the time to work on them because reviewing other peoples PR’s, providing feedback, merging them, that takes a lot of time. So its often difficult to find the time to work on the things that are actually assigned to you. I’ve been struggling a bit with the same where I feel like this is maybe the release I’ve put the most of my personal time into, but maybe with the fewest amount of direct changes to the code, because I don’t have the time to work on it. All the time I can commit to TiddlyWiki up being spent on the project management part of it.

So, it’s a shift also in terms of how we do things and different type of gratification as well. It’s nice to be able to help out in those role, but you miss out on that sense of actually being able to directly work on the things that you personally care about. So, it’s always a compromise in that sense.

It’s kinda mirrors what I do in my day job as well, where I wish I could do more hands on coding but I end up doing more management work, because as I’m reminded there is no-one else that can do that but there are many programmers. So I find myself doing the same thing now the TiddlyWiki -verse, which is Ok for now, but I’m hoping when we get ourselves into a better routine, I can also find a better balance there.

Another thing I think is worth mentioning in relation to the 5.4 timeline, and how far we are through the process, is that we’ve sort of made an adjustment along the way. Where instead of trying to be very ambitious with what we get done for 5.4 and it maybe being a release That’s like 12 to 18 months so away from what we first started talking about it. We are now actually hoping that early next year. This will be released so like January February time frame. And that is one of the reasons as well, we identified some key features we want to be present in 5.4, to get those out into the community so they can take advantage of them, but also allows community contributors to build upon them, and that way we shift our focus on a 5.5 Release. So the idea being to have these sort of milestone releases that introduce new features more often instead of making people wait a very long time for those features.

So keeping the community interests with future directions is a key consideration in the project planning ?

And that reasoning was precisely is why one of the prioritised that was assigned to me last week was to simplify the upgrade process for simplified TiddlyWikis, because if the idea is that we want to push out major changes more frequently than we want people to be able to operate as easily as possible. So it’s you know, that’s often something that comes up. So I think there are other things that Jeremy and I would rather I work on that would be more, you know, enjoyable from a programmer’s perspective, but it feels like from a community point of view this is what makes sense right now. So that balance is sort of something we always think about.

And you know a lot of the innovation that happens in TiddlyWiki actually comes from community contributors whether they’re directly contributing to the core or building plugins. So getting some of these new features out there, even though they are fundamental features that people who just open a new version of TiddlyWiki might not notice, allows people in the community to build on them. So rather than wait 18 months until that process can start the features that are ready should be shipped out as soon as we possibly can and that is part of the thinking here.

You mentioned your day job, and in your bio it says “UX designer, developer, doctor, non-profit educational sector jack of all trades, photographer and other things I often forget” - What actually is your job ?

Oh goodness, I work as a consultant, I run a small consulting company that works with IT development for non-profits in under-served parts of the world.

So under-served parts the world have a large potential to benefit from the use of IT. But the challenges are very different in terms of infrastructure, in terms of budget, in terms of social concerns that you have to take into account. And that’s where open source software has been a blessing and that’s actually what was my original driver to essentially become a self-taught programmer many many years ago. Via TiddlyWiki actually in the classic days. So this is like maybe 2007 or something because it allows you that possibility of customising things for specific demographics and their needs that is not really possible with commercial software at least not with the kind of budgets that we work under.

My original background was that I was trained as a medical doctor, and never really practised for long before pivoting towards working in the non-profit sector mostly in education and mostly in sub-Saharan Africa. Setting up schools, boarding schools that would transition to community owned at some point in time, and that was where the idea that we could do things more efficiently by leveraging IT came about. There were no solutions available that you could just pick up and use. I was having a hard time getting people to buy into my vision of how this could be done. So that’s where I ended up essentially teaching myself how to program and prototyping tools based upon TiddlyWiki Classic, that went far enough to show people, OK this is actually viable.

So, that’s how the shift happened towards programming and a good five six years after I’d already been doing that while working, I went back to school on the side, and also got a Master’s in UX Design. And again my focus in UX Design was, to be fair, more user-centred design than UX Design because with UX Design we think more about computer interfaces versus end user-centred design we think about all products and services as well. And again my focus there actually tends to be more on marginalised communities, and their needs because it tend to be different.

To give you a very obvious example, so you know one of the first apps that I worked on after that was for guiding women through pregnancy, but tailored for population with the extremely low literacy. So that meant very visually heavy designs and it meant things like text to audio and this is now over 10 years ago when these things were not so common.

The last release 5.3.7 had 22 contributors - Do you know how many are working on this release ?

No, I mean, I would have to sit down and count. What I can tell you is that as of last two years or so, especially we’ve been very very fortunate with our Chinese community members really stepping up in terms of contributions. Linonetwo has been a present, you know, a constant throughout the last two years working on some pretty challenging things and having the patience to see them through, because when you work on really fundamental things it goes through heavy review, heavy revision. It takes time. So the PR of his, that was merged, that lays the groundwork for WYSIWIG editing was probably in progress for like a year and a half and a lot of people would get frustrated and give up, but you know we tend to be very conservative with TiddlyWiki because of our backwards compatibility commitment.

So having the persistence and patients to work with us and see that through has been phenomenal. Another community member who goes by the GitHub handle Leilei332 is another Chinese community member has been phenomenal for this release in terms of both the amount of work they’ve done, but also taking on work that I would call grudge work. It’s not fun things. You know updating deprecated code marking it out where it needs to be replaced. It’s work that needs to be done, but it’s never enjoyable. It doesn’t give you that thrill of satisfaction, you know, working on a new feature does. He’s also been working heavily on accessibility, which I really appreciate and I know Jeremy does as well. Again the kind of work that isn’t, you know, most programmers who contribute to open source projects and do it to scratch a personal itch. They want to be able to build something, and there’s a missing feature or, you know, there’s something that personally interests them. So finding someone that’s working willing to work on these things, that really need to be worked on but maybe aren’t as glamorous, is fantastic, and it’s been high quality work as well. Which isn’t to, you know, diminish the work of any other contributors, but in terms of people who have really stood out for me in this release cycle I wanted to point them out.

Clearly there are some great contributors then to this release - but you don’t mention much of a collaboration process ? Is that fair to say ?

For the most part I think that’s accurate. I mean, I think it’s pretty normal for open source communities to work that way. If we may be had an approach where we were creating issues far in advance of things we want to work on let’s say. We’re already doing that for 5.5. Maybe then we would end up with a more collaborative approach for people would see that and maybe work on it. But at the same time a challenge tends to be that, you know, most of those features that we would possibly create issues for tend to be very fundamental changes for TiddlyWiki and getting them right so that you aren’t stepping on other subsystems or creating a clash that is going to be difficult to resolve later requires a very deep knowledge of the entire code base, which there’s not a lot of people that necessarily have.

So sometimes there’s also this feeling that okay, perhaps, we need to sort of get that process started ourselves in terms of starting a PR or starting work on the code and then if somebody else wants to contribute or take over, that’s great because you’ve sort of marked out what needs to be done. Which doesn’t mean we aren’t open to new ideas within that, but it’s often helpful because otherwise sometimes you end up with really large contributions from people, you know, that has taken a lot of effort and might be really high quality work, but can’t be merged because fundamentally there’s some sort of clash with the way we work in TiddlyWiki and it’s going to cause problems either with other subsystems or down the line.

So to avoid that duplication of effort, we do usually encourage people that if they want to work on something larger, create an issue for us. Let’s discuss it. And you know, go ahead and work on it

In terms of collaboration, it’s outside the 5.4 scope, but I think the work that Arlen22 is doing on MWS is a great example of collaborating with Jeremy on that. And I think now it’s a bit more Arlen22’s taking the lead, but Jeremy still guiding, but Jeremy had done the original prototype that Harlan rewrote, so I think that’s a good example of a collaborative approach. It does happen, but it isn’t the rule. I would say, it is more so that people contribute.

What challenges have you faced with this release ?

I mean there are always challenges, but nothing that I would say is you know dramatically different from working in any other kind of project. You have to always make sure that you provide feedback to people in a timely manner and part of what I need to do is mark out the tickets and issues that require a feedback and then Jeremy and I have pretty regular calls, and we’ll go through them together to make sure that we actually do provide feedback to people. Because that allows them to take the next step, you know, if we need to refine something about their contribution or changed direction than they need to know sooner rather than later.

Sometimes. You know you can have community members that get a bit impatient, which again is a completely human thing. I’ve been on the other side of this even within TiddlyWiki itself and it happens. And I think that there are things that we could do to make that easier for people to understand. So for example, Jeremy and I speak about once a week. He sometimes does take the time to go through the project plan and merge PR as on his own. If they don’t whatever doesn’t get caught we try to talk about and that weekly review, but that does mean that there might be a week’s wait until you know your PR gets attention, or if one of us is a way on vacation or something, and that’s going to be a longer wait. Another thing is that we tend to try to keep the way we work in GitHub relatively simple, and that’s to facilitate contributors who aren’t necessarily very Git savvy. So for example after a new release, for a few weeks, we won’t merge any PR’s. And we do that intentionally in case we find a critical bug that forces us to push out a bug fix release then we don’t want any other new changes in there. And there are ways we could do that with a different branch and still make it work, but we try to keep that process simpler for others. So for that code freeze, I feel like, if we were to communicate and actually put a date on it at the same time the release happens it may help people understand as well. Okay. There’s a code freeze right now. I’m going to have to wait for my PR to get merged.

For 5.4. There was an additional delay, because you know we made a pretty fundamental policy change, which is in terms of the JavaScript dialect that we support. Which we updated to ES2017. So that means covering browsers from about the last 10 years or so. But that required that we actually put into place some additional tests and scripts in the repository so that we don’t accidentally commit code newer than that. Because, for a lot of us who have been working with TiddlyWiki for a very long time, it’s muscle memory. We remember what old ancient dialect of JavaScript we have to use in TiddlyWiki. But once you say you can use something newer then its hard to remember where the border is right. So that was an additional delay, because it’s something we hadn’t done before so we had to get that in place, so that also meant that the merging a PR is was delayed.

Another learning for us was that we hadn’t set up the project plan for 5.4 during this waiting period so PR is that maybe were ready for consideration or merging there was no way to track them, and therefore some PR’s were only picked up recently or people had to remind us that, hey, this this one’s actually ready. Even though we try to review everything that’s open. Which is why a project plan for 5.5 is already there now. So as soon as we release 5.4 in that situation, we can just start adding them to the 5.5 plan, and it makes it easier for us to track or anything that we say in 5.4. Hey we’re not working on this now. We’re going to do in 5.5. We can automatically assign it to 5.5 and keep track of it there.

You’ve mentioned Release 5.5 is in planning - Is there an intention to move to a 5.5 release sooner ?

It’s not set in stone. The idea is basically that since we decided to timebox 5.4 meaning which means instead of waiting to finish a set of features, we said we’ll do as many of them as we can let’s say by early spring right and release that. After that, we start working on the next set of big features, which will be 5.5 and again we’d hope that it’s not going to be any later than like, let’s say, late next year all things allowing. I mean unless something drastic happens. In the meantime if there are contributions that should be pushed out or bug fix releases required. We might have A 5.4.1+ , but the idea is that we will start planning for a 5.5 right away and it might be that we set up another project plan for 5.4.1 if we decide that there are things that need to go out faster.

Right, but 5.4 was about some necessary breaks in backward compatibility, will 5.5 also focus on those sort of changes ?

No the expectation would be the same. I mean there are things that potentially would require a breaking backwards compatibility that probably can’t happen within this timeframe and if we manage to avoid those backwards compatibility breaks, and it might be a huge feature release, but it wouldn’t get the 5.5 tag. There hasn’t been any decision to change that naming convention.

On the topic of backwards compatibility, and this is up in the air because I proposed a Jeremy last week, and I need to make an issue for it so the community can discuss it and I haven’t had the time yet. I am proposing that we change our backwards compatibility policy. So you know in the past our policy has been that we try to make sure that any code written for TiddlyWiki whether it’s Wikitext, whether it’s JavaScript continues to work. Yes it did. And I’m suggesting that we change that and revise it to a commitment to trying to make sure that Wikitext works as it previously does, but there can be changes on the JavaScript front, which we will announce in advance. Give people enough lead time to upgrade their plugins and the idea there being that, it is really the end users who would struggle when Wikitext stops working as it does. Developers who write JavaScript plugins are more used to having to update their code. If we’re having to get them to update their plugin once every two years, that’s still far less frequent than any other open source project I know of that’s active. And then we would, you know, provide guidance on what the changes need to be. There is also the intention after 5.4 to try to set up a community plugin library, which has been talked about, to death, but we have an idea for how to get a minimal version of that up and running. Which would help us also be able to better understand what plugins are going to break when we change something on the JavaScript end.

And part of that is also that you know the break and JavaScript backwards compatibility already happens. And often we don’t manage to catch it because it’s just so difficult because what we haven’t done in the title Wiki core is mapped out a specific set of functions that are supposed to be publicly used by developers. Instead you can use anything, but very often we need to refactor and change those methods to be able to have new functionality. So those brakes happen anyway unintentionally. So rather than have these accidental breaks that we then have to rush and try to fix somehow and adds a lot of complexity. The idea is no let’s do it in an intentional controlled manner where necessary with enough lead time warning to everyone.

Lastly - You mention end users. What do you use TiddlyWiki for as a end user ?

Oh - You know I was very active in the community during the TiddlyWiki classic days and during that time most of my TiddlyWiki usage will actually all of it was not for myself. I didn’t use it myself at all. It was used entirely in educational context. I was creating tools for some of the schools, I was working with. I was working with a few professors in different universities prototyping different ways for providing slides and classroom and lecture notes to students and this was all public back in the TiddlyWiki classic days. The nice thing about TiddlyWiki 5 is that I actually had stepped away from TiddlyWiki for some years and I came back. And it was driven actually by my own personal needs to start off with so. The wiki that I use every single day is a note taking wiki. It doesn’t look anything like that normal TiddlyWiki interface. I did a demo of it, with a video with Jeremy some years ago, and I can send you a screenshot later if you’d like, but it’s actually a replicates an app on macOS called Notional Velocity. There are clones of it for windows, as well. So you have a text box. You can type into it to search, for a no title if it doesn’t exist, you can hit enter to create it and just start typing right away. So that is something that is constantly open somewhere on my desktop every single day and I use it every single day.

I maintain a few additions for a few groups of friend. So some of my interests include both natural wine, and also high-end Chinese tea , which is meant to be aged. So I maintain two additions that are for tasting notes and I have a small group of friends that uses both of them. It has its own update mechanism, so I can push out updates, and they get the new features and you can see each other’s notes. So that’s been quite enjoyable to actually make something for yourself that way.

I work with a few social workers in Central Asia right now, for whom I’ve made some reporting tools. These are people who I work with on a professional capacity, but the TiddlyWiki tools I made for them were on a volunteer basis. So it’s just I saw an opportunity to help out. There’s no budget, okay I’ll just go ahead and do it. So it allows them to take case notes while they’re in the field, and then be able to synchronize them back to a central server when they’re back at the office because they don’t always have field connectivity. So and, you know, TiddlyWiki is a great fit for that because of the fact that it’s truly offline first. There are very few tools that really are able to work just on your device with no internet connectivity. All other tools that even say they’re offline first, seem to almost have the offline feature just added on and it doesn’t work as smoothly, so that’s another use case.

So things like that, and I have I operate this site on GitHub that I call my Plugins Sandbox and everything on there is labelled experimental where I’ve been publishing components, a lot of the components, of this stuff and that’s because I don’t really have the time to be able to publish them as plugins with proper documentation, provide support, but the hope is that if I just put out what I can in terms of components will be helpful to someone.

There has been a great deal going on in the world of TiddlyWiki since our last newsletter. Today we have released a new version of TiddlyWiki, and we are inviting the community to complete our 2025 Community Survey. We also have some exciting future plans to share, and an important appeal for your help.

You will find a warm welcome for your thoughts and questions at the TiddlyWiki forum.

New Version Released on 7th July 2025

There are 29 important bug fixes in v5.3.7, and a handful of new or updated features. The highlights include:

• Updates to the Chinese, French, German, Greek and Japanese translations

• CodeMirror plugin updated to v5.65.19

• New hidden setting for the default type for missing tiddlers

• New control panel setting to specify the default tiddler info tab

• Support for images in AVIF format

You can upgrade your existing single file wikis here:

https://tiddlywiki.com/upgrade.html

For Node.js users, the new version is available on npm at https://www.npmjs.com/package/tiddlywiki

As usual, please exercise caution when upgrading, and take care to keep backup copies of everything important.

Our thanks to everyone who contributed to this release.

Community Survey

The core developers work hard year by year to continuously improve TiddlyWiki. Part of the satisfaction is that we are not just building software for ourselves, we’re serving the needs of a wider community of users.

That begs the question of how we can understand the needs of these other users. We do it in an informal way through every interaction with users on the forum, or on GitHub, but once in a while it can be useful to do take a more formal approach, such as a survey.

Please take our new TiddlyWiki User Survey

So, we would like to invite you to participate in the TiddlyWiki User Survey 2025. This brief, anonymous survey is designed to give us insight into the needs of TiddlyWiki users, with a mix of structured and freeform questions.

The results of this survey will help inform future developments, helping us focus on what would make TiddlyWiki better for you, both as software and as a community. Even longer-term, it will help us refine the future vision of the project, ensuring it is based on the needs of our community.

The survey will remain open until Monday, 11th August. Shortly afterwards, we will aggregate and share the findings.

Take the survey

Community Wiki Information Reporting

The most common way to get information about how people are using your software/website/app is to track their activities with cookies or other identifiers. It is standard across the industry that each time you click a link, or type into a text box, another little record is added to a central database, building up into a comprehensive picture of everything you do. There is an entire industry around aggregating and interpreting the information that is gathered.

TiddlyWiki is never, ever going to invade the privacy of our users in that way. A painful consequence of our stance is that we lack the sort of metrics that are commonplace in our industry, even something as simple as the number of unique visitors per month to the website - let alone things like the most popular plugins, or most common configuration choices.

To try to address this gap, today we are launching a new way for users to report high-level information about their wikis. Sharing the information is entirely voluntary, and intentionally entirely manual. The wiki information is presented as a plain text box whose content can be copied to the clipboard with one click.

We are asking users to run the tool and include the results in the survey (see above). The information that is gathered is also designed to be helpful when providing support to a user.

You can find the Wiki Information Tool here in the Control Panel under Info. You can also drag the tool to any other wiki (including older versions of TiddlyWiki).

The Great Viral TiddlyWiki Interview Project 2010

You may also be interested in “The Great Viral TiddlyWiki Interview Project” from 2010. This was in the TiddlyWiki Classic period, when I was starting to think about TiddlyWiki 5. We invited TiddlyWiki users to join the interview project with these words:

For many people that use it. there is a distinct discovery moment when TiddlyWiki explodes in their brain. For others, it is a challenge to get their heads around TiddlyWiki at all.

This project explores how people think about TiddlyWiki by collecting together responses to a set of questions about it.

You can explore the questions and responses on this new site. There is also a forum discussion.

Project 2036

From its beginnings in 2011, TiddlyWiki 5 had the tagline “a reboot of TiddlyWiki for the next 25 years”. Back then, I was keen to communicate my commitment to keeping TiddlyWiki going as long as I could. At that point, 25 years in the other direction was 1986; not much software from that era was still in common usage apart from Unix.

We’re now 11 years until we get to that 25-year mark. What with the passage of time and other developments, this is a good time to start talking about where we want TiddlyWiki to be by that point, and to consider the longer-term future of TiddlyWiki.

There is a longer forum post about Project 2036.

Into the Future with v5.4.0

Part of Project 2036 is that we are planning a new release of TiddlyWiki in the near future that judiciously and surgically makes some narrow, technical breaks in backwards compatibility in order to allow us to bring in some of the improvements that are currently held back by concerns about backwards compatibility.

Some of the features we are planning include:

• WYSIWYG editing

• True single tiddler mode

• Links to sections

• Visual refresh, with new icons, palettes, and layout improvements

• More powerful filters with multi-valued variables and comments

• Improvements to bidirectional text handling

• For developers, the adoption of a more modern version of JavaScript

Read the forum post announcing the plans for v5.4.0, and the project plan on GitHub.

MultiWikiServer

TiddlyWiki is growing up: the new MultiWikiServer is a more powerful and flexible server for TiddlyWiki.

MWS brings TiddlyWiki up to par with common web-based tools like WordPress or MediaWiki by supporting multiple wikis and multiple users at the same time. The architecture is based on combining “bags” of tiddlers according to a “recipe” to make an editable TiddlyWiki. This architecture allows code and data to be shared, combined, and reused. Extensive security capabilities give fine-grained access control that spans fully public to totally private.

MultiWikiServer is not part of v5.4.0, and is currently intended to work with both v5.3.x and v5.4.x versions of TiddlyWiki. It can be run locally on your own machine or hosted with a cloud service provider.

The most important change since MWS first started development in early 2024 is that Arlen Beiler has stepped up as project lead. Arlen is an experienced developer who has been contributing to TiddlyWiki for 15 years.

Arlen has made impressive progress working towards a v2.0 release of MWS. Find out more at the dedicated website mws.tiddlywiki.com and follow the development of MWS on GitHub.

Get Involved

TiddlyWiki is built, maintained, and supported entirely by volunteers from all over the world. We’ve got big plans for the future, and there is always a lot to do.

We need your help. You don’t need to be a software developer in order to contribute to the project. There are many other skills that are very valuable to us: writing and documentation, illustration, project management, product management, infrastructure operations, translation, and on, and on.

Another way that you can help is by supporting TiddlyWiki financially.

TiddlyWiki depends on you just as much as you depend on TiddlyWiki. You can show that you care by getting involved.

Best wishes

Jeremy.

The biggest news this issue is that there is a brand new release of TiddlyWiki available, version 5.3.6.

Highlights from the release note for v5.3.6 include:

• New translations (Chinese, Hong Kong) and updates to a few existing translations

• Updates to the Geospatial plugin

• Updates to the Markdown plugin

• Support for social media preview cards

• The export button gains the ability to be dragged from one TiddlyWiki to another bringing the entire result set with it

• A couple of updates to the Control Panel

• And a host of issues from earlier releases fixed

Try out the new release at https://tiddlywiki.com/.

Let us know in the comments your favourite new feature — and anything you feel should be a new feature in upcoming releases.

Sidebar Resizer

User BurningTreeC posted a demo of his upcoming feature proposal, a Sidebar Resizer for Tiddlywiki. This is not a plugin but rather a proposed addition to the TiddlyWiki core code.

You can try out the Sidebar Resizer in the preview build. Be sure to let us know what you think in the comments.

Experimental Highlighting WikiText Editor

User BuggyJ has shared an experimental pair of plugins that together provide syntax highlighting of wikitext within the TiddlyWiki editor:

MultiWikiServer News

Founder Jeremy Ruston published a new website to bring all the MWS documentation together in one bookmarkable place:

The idea is to make the MWS docs easily accessible without cluttering up the main [TiddlyWiki] site with material that will not be relevant to everyone.

TiddlyWiki Classic

TiddlyWiki Classic is still going strong. Version 2.10.2 has just been released with new features, bug fixes and UI improvements.

TiddlyWiki Classic maintainer Yakov Litvin has also recently published a collection of his own TWC plugins released in the last year.

In Memoriam

We are sad to report the passing of Udo Borkowski earlier this year. Udo was an enthusiastic early contributor to TiddlyWiki. His YourSearch plugin in particular became a staple for TiddlyWiki Classic users. Jeremy paid tribute to Udo and shared some memories in a GitHub thread with Yakov and Udo’s widow.

Happy 20th Birthday to TiddlyWiki

From the ICYMI department…

Did you know Jeremy Ruston and a joyous crowd of long-time TiddlyWiki fans celebrated TiddlyWiki’s 20th birthday, recently? If you missed it, you can catch up on any of the 3 long-running sessions right here.

It’s extraordinary to think that a primitave initial version of TiddlyWiki was first publicly released on September 20th 2004 to some acclaim. A community of fans rapidly formed around it. Over the years it has become much more ambitious and powerful but tries to remain true to the principles that set it apart in the beginning.

So, happy birthday, TiddlyWiki, and here’s to hoping there will be many more.

Grok TiddlyWiki reaches 2.0!

Soren Bjornstad’s popular TiddlyWiki tutorials site has been updated to the latest version of TiddlyWiki 5.3.5.

Here is Jeremy Ruston’s initial response to the announcement:

Congratulations @sobjornstad. Grok TiddlyWiki was already an outstanding piece of work and these improvements and updates really consolidate its position. The writing is authoritative and friendly and I think very effective.

Website: https://groktiddlywiki.com/read/

Announcement: https://talk.tiddlywiki.org/t/grok-tiddlywiki-2-0-is-live/10965

Streams Developments

From the You didn’t know it was a plugin department…

Many users have come to love and rely on Saq Imtiaz’s Streams plugin and cannot imagine using their TiddlyWiki without it. Even though it is many years on from its initial announcement, Streams is still in full sun — and, Saq implies, will be for many years to come…

Quoting from the Streams website:

Streams is a keyboard friendly way to write and easily divide your text into separate tiddlers while writing. Every time you want a new tiddler, just hit Enter. A new tiddler is created in the background and you can just continue writing.

Streams is, without doubt, creating its own ecosystem. Barely a week goes by before someone mentions it on talk.tiddlywiki. Recently, that someone was user lineonetwo. Taking Streams as a starting point, linonetwo created two new plugins using the Streams core code as a starting point:

First, linonetwo extracted “a Lightweight Outliner component” from the original Streams plugin.

Then, as though the Outliner wasn’t enough, linonetwo created the “Life Principles” plugin:

[It] allows you to record your life principles in the form of an outline, and engrave them in your brain like a mental steel stamp through spaced repetition technique, so that you can program yourself, learn from mistakes, and keep improving.

HowTo: Install TiddlyPWA on Glitch

User telumire posted a pair of video tutorials to help users intall Val Packett’s TiddlyPWA on Glitch. Note that there is no audio track, just video.

Musings & Insights

… a ticker-tape of utterances from the world of talk.tiddlywiki …

… User Mohammad offers a way to compose GMail from within your TiddlyWiki …

… Community members are discussing Robin Munn’s proposed new filter operator, braid — with quite some gusto …

… Elsewhere, user Dave Gifford asks, “What’s the oldest tiddler in my TiddlyWiki?” … we hope he will keep a note of the solution in his Daily BAD …

… Meanwhile, having emerged victorious from a battle with an image/svg+xml mime type, user Mohammad is now in search of a wikitext-only solution for link previews …

… And while user well-noted is offering up an Expanded ChatGPT Interface for TiddlyWiki, yours truly is insisting anything LLM-related is unwelcome inside his precious TW-space … yet, not to be dissuaded from his mission, well-noted wants to expand on it, asking for TiddlyWiki users to tender their own AI wishes …

… Back in the non-AI world, user XYZ wants his $:/TagManager to order tags by most/least-used — Eric Shulman provided a solution in short order …

… Sticking to the world of tags for a moment, user Vuk wants to “snatch tags” from arbitrary tiddlers, right at the point they’re being added to a target tiddler …

… User yedhukrishna fell foul of a CORS issue using tm-http-request but user buggyj managed to fix the problem …

… Founder Jeremy Ruston is working on a long-wished-for update to the colour macro and related palette management facilities. More details can be found over on GitHub …

… Lastly, over in server-land… Ever since its announcement, MultiWikiServer keeps / gaining / traction / …

… Wait! Just as we are preparing to publish this edition, The Banner Image Competion for TiddlyWiki v5.3.6 appears. As you would expect, we will feature the winning entry in a future edition, so pull out your digital pens, pencils and paintbrushes, and get cracking. You have until Sunday 10th November to rock the world with your artistic skills …

Farewell and good luck to Paul…

We would like to extend a huge thanks to Paul who started this newsletter in January 2023 and edited every issue until August 2023. We all wish him well in his future endeavours.

..And welcome to the new team

We have settled on a small team of editors working together to bring the TiddlyWiki Newsletter back into the light of day.

In that vein, if you feel you could bring something to the team and help out, please get in touch by leaving us a message here.

We hope you found this edition of the TiddlyWiki Newsletter fun and interesting. Let us know what you think in the Comments section below; about the newsletter as a whole and the topics included. And please let us know if there’s something you’d like to see more of/less of in future editions.

Thank you for reading!

Care to share?

Announcing the release of TiddlyWiki v5.3.1

I am delighted to announce the release of TiddlyWiki v5.3.1 at:

https://tiddlywiki.com/

This release comes relatively swiftly after v5.3.0, and is largely intended to fix a number of minor issues with that release:

• Reverted adding the widget.destroy() method because of performance concerns (see implemented destroy() function by buggyj · Pull Request #7468 · Jermolene/TiddlyWiki5 · GitHub 1)

• fixed inefficiency when transcluding with the $output attribute set to text/plain that manifested itself as extremely slow export times

• fixed unwanted error message “Global assignment is not allowed within modules on node”

There are also some other improvements and bug fixes:

• improved ImportVariablesWidget and Pragma: \import to trim whitespace when parsing tiddlers

• extended WidgetMessage: tm-http-request to handle binary responses (demo)

• improved console reporting of JavaScript errors

• fixed table of contents indentation

• fixed bindStatus and bindProgress parameters of WidgetMessage: tm-http-request

• fixed attribute substitution to handle variables containing non-word characters

• fixed the pragmas introduced in v5.3.0 so that they can be indented with whitespace

• fixed size of tiddler icons

• fixed drag and drop from Chrome-like browsers to Firefox

• fixed listIndex mode of checkbox widgets

You can upgrade your existing single file wikis here:

https://tiddlywiki.com/upgrade.html

For Node.js users, the new version is available on npm at tiddlywiki - npm

As usual, please exercise caution when upgrading, and take care to keep backup copies of everything important.

My thanks to everyone who contributed to this release, from code contributions to feedback. We’re phenomenally lucky to have so many people willing to help, and it is much appreciated.

Any questions or comments are welcome here, or via GitHub.

Best wishes

Jeremy

Discussion here

Articles

Showcase: gavart.ist Digital Garden & Work Repository

User gavcloud updated their site and shared this video demo. The TiddlyWiki site is listed below.

Video here

Site here

Discussion here via Discord

Plugins

Nav - keyboard navigation plugin

once again, i found myself making a tool for my own personal use that i think is worth sharing with the community. so i present to you, nav - the keyboard navigation plugin! :compass:

dependencies: $:/plugins/felixhayashi/hotzone (found in the CPL or drag-and-droppable from the TiddlyMap demo site )

nav puts a “cursor” in the corner of the focused tiddler, which can be moved around by scrolling or with the keyboard shortcuts. they are based on putting your hand over the WASD keys with your thumb on alt:

• alt+W to move up, and alt+S to move down

• alt+A to close the focused tiddler (“swiping it away” as suggested by the default animation)

• alt+E to edit the focused tiddler

• alt+R or alt+H to go home (open the default tiddlers)

• alt+C to focus the sidebar search box (start typing to search)

I recommend also adding the following mappings for the default actions:

• alt+Q to cancel editing (cancel-edit-tiddler)

• alt+S to save a draft (save-tiddler)

all bindings remappable from the control panel. if you find moving to be sluggish, turn down the animation duration in Control Panel > Info > Basics to make it more responsive and snappy.

nav gives you a new keyboard-based way to move around the story river, allowing you to do much of your workflow from the keyboard when combined with the built-in keyboard shortcuts. it is also my first proper plugin. hope you find it useful!

- Scribs

Discussion here

Plugin here

Tips & Tricks

Sliding overflow (html) table with rotated header

User DaveGifford shared how to make the top row of headers diagonal, to allow the rest of the cells to be equal sized.

Site here

Discussion here

TiddlyWiki Newsletter

A bi-monthly newsletter of the most interesting and relevant news from the TiddlyWiki community

By Jeremy Ruston

TiddlyWiki v5.3.1 is preparing for release next week. We’re making a release relatively soon after v5.3.0 in order to correct a number of minor problems introduced in that release. You can help us by testing whether it works properly with your own plugins and customisations.

There are more details in the forum post.

Articles

Showcase: Kansas Railroad TiddlyWiki

Discussion here

Site here

Plugins

AsciiMath plugin for KaTeX

After recently posting about problems with the MathJax plugin after upgrading to TiddlyWiki 5.3.0, I was asked “why don’t you use KaTeX”?

The answer had been “it doesn’t support AsciiMath”, but after visiting the KaTeX website I found an AsciiMath converter someone had written. A little work proved I could use it to switch from MathJax to KaTeX.

I have now repackaged that converter into a TiddlyWiki plugin.

- Andrew

Discussion here

Plugin here

Keywords - increase tiddler findability

Are you one of those people that has ever not found something?

Aha! this is for exactly people like you!

KEYWORDS …lets you add keywords to locate tiddlers in standard search. This is not the same thing as “tags”; keywords can be anything, they are not directly visible and you can even add them to otherwise hard-to-find shadow tiddlers as keywords don’t overwrite or otherwise affect the tiddler.

Check it out.

- twMat

Discussion here

Plugin here

TiddlyPWA: Secure offline storage and cross-device synchronization solution

Hello everyone,

so a year ago I’ve tried TiddlyWiki again, didn’t like any existing storage/hosting solutions and started making my own. Now, it’s finally ready to be announced to the public!

Introducing TiddlyPWA

Basically, :notebook_with_decorative_cover: TiddlyPWA turns TiddlyWiki5 into an offline-first Progressive Web App with encrypted local persistent storage and efficient synchronization with a server that can easily be hosted for free.

It’s TiddlyWiki turned into a modern notes app, with the modern user experience you’d expect from that, without sacrificing anything that makes TiddlyWiki great: you can easily install plugins and themes, upgrade the TW core, and so on – when hosting the app wiki on the sync server, saving it is a one click operation.

- Val Packett

Discussion here

Plugin here

Tips & Tricks

Embedded vs External

How to "do" the canonical_uri

1. Create a new tiddler. You can name it whatever you like. For the purpose of this example, lets call it A Little More

2. Edit this new tiddler.

3. At the bottom of the tiddler, set Type: to application/pdf

4. Add a new field called _canonical_uri field, with the field value set to file:///D:\Music\CHARTS\A-E_SONG-Titles\A Little More.pdf

5. Save the changes

6. Now that the tiddler has been created, you can link to the pdf by using [[A Little More]] and you can transclude (show) the pdf by using {{A Little More}}

- Intrinsical

Discussion here

Those Pesky Brackets

As there are plenty of recurring “what’s up with all these brackets!!! Single brackets? Double brackets! TRIPLE BRACKedsfdsfsffddsbagel‽” threads lately so I wanted to give explanations another way in case they can be of any help.

The basics are mostly done (I needed something to do last week, in between many hours of sleep, while I was holed up with Covid).

I’ll add more bits to it as I think of them, but I think there’s enough to help a beginner out.

- Brian Radspinner

Discussion here

Site here

Showcase: Philosopher Life

Discussion here

Archive copy current as of 27 Dec 2022 here

Plugins

Tiddler-counter & Linked-Tiddlers

Discussion here

On Github here

Demo Tiddlywiki here

Tids-to-Table : Generate tables from filters

Proudly unleashing:

Tids-to-Table

This replaces both list-rows and the much earlier list-table-draggable.

Tids-to-Table is simple to use, basically you type <<table>> and you get a little setup form where you fill in the tiddler filter and other settings. The output is a table based on the tiddlers from the filter.

This uses the dynamic power of filters and templates and the fundamentals of html so really complex tables can be generated. This is way more powerful than wikitext pipe | tables and way more efficient than building static html tables. Try it out, I’m pretty sure you’ll like it.

-twMat

Discussion here

Plugin here

Tips & Tricks

TOC or Tree that uses filters instead of tags

Something I think would be really helpful is the ability to pass filter notation to the tree macro or the toc macros.

Something like <<tree filter:"[creator[JohnDoe]]">> (or similar but using the toc macros) which would create a tree of all tiddlers made by JohnDoe, so that you can still follow the same title format as the core tiddlers which won’t break things like custom config tiddlers, and not need to worry about tagging them, and for some tiddlers finding a different method to find them since you can’t tag them (journal config tiddlers for example)

How could the core tree (or toc) macro be modified to use this over requiring a tag?

- Justin_H

Discussion here

Download Solution by Mark_S here

Wilk-tweaks, my collection of TW tweaks, settings, styles, and palettes

I’d like to share my small collection of TiddlyWiki tweaks, settings, styles, palettes etc. that I use across my wikis. These are mostly small modifications that would not make much sense as plugins, but they took enough time to make/adjust/find that I want to keep them for future reference and share. There is a short explanation or simple usage example for each of them.

-vilc

Discussion here

Collection here

Announcing the release of TiddlyWiki v5.3.0

I’m delighted to announce the release of TiddlyWiki v5.3.0 at:

https://tiddlywiki.com/

The jump in version number is because the new parameterised transclusion and related features in this release are the culmination of thinking and experimenting that began around 7 years ago. These are far reaching improvements that allow authors to write clearer, more concise wikitext that is more powerful than ever before. They also fix some of the mistakes in the original design of TiddlyWiki 5. The real challenge has been to deliver these improvements without compromising on our commitment to backwards compatibility.

At its simplest, parameterised transclusion is the ability to pass parameters in a transclusion, separating them with a single vertical bar:

{{MyUtility|red|22px}}

Those parameters can be accessed within the tiddler “MyUtility” with the following declaration:

\parameters (colour:"green",size: "20px")
...

The work to implement parameterised transclusion also provides some other significant features:

• Custom widgets in wikitext

• Custom, parameterised named functions

• Procedures – these are essentially what macros should have been; they work in exactly the same way except that parameters are exposed as simple variables (without the double underscores) and no textual substitution takes place

The major features of the new release are:

• A new syntax for widget/html attributes that allows textual substitution of variable and filters

• Support for sending HTTP requests, opening up exciting possibilities to call web APIs and load content dynamically

• Updated Google Analytics plugin compatible with the new version

• New :then[...] filter run prefix

• New thisTiddler variable for transcluded tiddlers to access their own title

• More improvements to the browser storage plugin, making it more flexible and robust

• Many bug fixes

• Finally, CamelCase linking is now turned off by default

You can upgrade your existing single file wikis here:

https://tiddlywiki.com/upgrade.html

For Node.js users, the new version is available on npm at tiddlywiki - npm

As usual, please exercise caution when upgrading, and take care to keep backup copies of everything important.

My thanks to everyone who contributed to this release, from code contributions to feedback. We’re phenomenally lucky to have so many people willing to help, and it is much appreciated.

Any questions or comments are welcome here, or via GitHub.

Best wishes

Jeremy

Discussion here

Plugins

Feather Icon Set for TiddlyWiki

Discussion here

Icons hosted here

Presenting: OverWrite - modify shadow tiddlers freely

As you know, you are normally advised against overwriting shadow tiddlers because if an update modifies the shadow, then the overwrite may no longer perform as expected - possibly even doing very nasty things.

The OverWrite plugin targets this problem by alerting you when overwritten shadows have been modified in plugin updates, so that you can investigate the overwrites and approve, modify or delete them.

This is a pretty big deal as you can now feel a lot freer to modify both plugins and the TW core!

- twMat

Discussion here

Plugin here

Re-presenting: list-rows ~ formatted data in draggable rows

list-rows ~ lists data from filtered tiddlers, formatted into rearrangable table rows.

This macro takes inspiration from the macros list-links, list-tagged-draggable and list-links-draggable. They’re neat but all too limited, basically listing titles in bullet lists. The list-rows macro is more useful:

• you set a filter for which tiddlers to list

• the output is a table, each row corresponding to a tiddler

• each row structuredly displays tiddler data via a template

- twMat

Discussion here

Plugin here

Tips & Tricks

An alternative to reveal widgets and detail elements

Nothing revolutionary here. Just the result of some goofing around with CSS.

Give it a spin at TiddlyWiki.com.

<style>
.ch1 div {display:none;}
.ch1:hover {background-color:#F5F5F5;border:1px solid gray;}
.ch1:hover div {display:block;}
</style>

<$list filter="[tag[Articles]]">
<div class="ch1">
{{!!title}}<br>
<div style="max-height:100px;overflow:auto;">
<$transclude mode="block">
</div>
</div>
</$list>

- Charlie Venoit

Discussion here

Floating Images HowTo

Instructions and Discussion here

Macro here

Showcase: Liverpool & Manchester Railway Company Timeline

@vrsimility@vrsimility.masto.host

In case anyone's interested I've put a copy of the timeline #TiddlyWiki for the #LiverpoolAndManchesterRailway at

https://lmr200.tiddlyhost.com/

There's now a second timeline, viz excerpts from the Gore Street Directory potted history of #Liverpool 1822-30.

The timelines are accessed via the tabs on the extreme right labelled TL1 and TL2. They are zoomable and items shown are clickable to show further info.

Very much a work-in-progress. Best used with desktop.

Discussion here

Plugins

DelphesNotes a TiddlyWiki starter edition updated

Dear TW community,

I have made a major update to DelphesNotes a TiddlyWiki starter edition.

DelphesNotes packages several plugins on top of a TiddlyWiki empty edition : top menu, sidebar tools (favorites, table of contents, configuration tools, …), breadcrumbs, easy access to third patrty plugins libraries, basic help, …

DelphesNotes can be downloaded here:

https://delphes-notes.tiddlyhost.com/

You can also directly create a new TiddlyHost site using this edition from TiddlyHost template hub: https://tiddlyhost.com/sites/new?clone=delphes-notes

-Eskha

Discussion with full list of Updates here

Emoji Picker: Convenient and Efficient Emoji Selector

Emoji Picker is a plugin that offers TiddlyWiki users a convenient and efficient emoji selector. Whether you’re editing notes, writing articles, or engaging in communication with others, using emojis can enhance expressions and enrich content. The Emoji Picker plugin allows you to easily copy emoji symbols, providing an intuitive interface and simple operation.

- oeyoews

Plugin here

Discussion here

Note from Discussion

I’d like to add that if you are on Windows you can open the system emoji picker with [WIN+.] as well. - Scribs

Static Page Button

This plugin is only for TiddlyWiki running on Node.js server.

Suppose you have a TiddlyWiki site named https://my-tw-garden.com/ , on which you have tiddlers like “my-hobbies”, “my-favorite-movies”.

Sometimes you don’t want to share your homepage to friends, as it loads much longer than a static page, so you decide to share https://my-tw-garden.com/my-hobbies to others, instead of

https://my-tw-garden.com/#my-hobbies

But how do you get the static page URL quickly? Here comes the Static Page Button plugin. It will generate a button below the body of every non-system tiddler, when clicking the button you will get a static page of that tiddler.

If you want to switch back to interactive StoryRiver view from static page view, there is also a button below the body of that static page, clicking on it will bring you back to StoryRiver view.

I created this plugin with the help of Gatha Studio, Thanks @Mohammad for creating Gatha (I’m also using Utility / Favorites / Timeline plugin from Mohammad). And I also want to thank @linonetwo for his insistence that I convert this feature for my own use into a TiddlyWiki plugin, otherwise I would not know the making process in Gatha is so simple and straightforward.

Since it’s the first time I create TiddlyWiki plugin, it may contain bugs and other issues. If you are interested in this plugin, just install it on your Node.js TiddlyWiki site and have a try. I’d like to hear your feedbacks :blush:

- pimgeek

Download Plugin here

Discussion here

Tiddly2PDF Release

Tiddly2PDF is a plugin that allows for seamless conversion from wikis to fully customized PDFs. It is designed to allow wikis serving as documentation or journals to be exported into a more standard document format.

This is my first plugin, so I hope I didn’t mess anything up too badly :slight_smile:

This is the v0.1.1 release, otherwise known as very early alpha. The basic functionality all works, but expect some bugs. Currently, issues when formatting templates and configs can cause js errors if filled out wrong.

I hope some people end up testing it out, as I would love to get some feedback, feature requests, and bug reports for me to use to improve the plugin.

Warning: Sadly due to the libraries the plugin runs on the total size ends up being 2MB, and there is not much I can do to shrink it.

Version 0.1.2 is now out.

New Features include:

• Shrinked down to 1.5MB (I had to add some fonts back to get everything working)

• File names are now selectable

• Custom Fonts can now be uploaded and used. (This was the big thing)

• Minor bug fixes and opened an issue to get one resolved.

What next? The ability to have multiple docs and to be able to select different templates and settings for individual tiddlers. Additionally, lots more vars for the templates to choose from.

- GameDungeon

Github: GitHub - GameDungeon/Tiddly2PDF

Docs: Tiddly2PDF Docs

Download: Releases · GameDungeon/Tiddly2PDF · GitHub

Discussion here

Gavcloud is giving a TiddlyWiki Workshop

Excited to share that I will be giving a #TiddlyWiki workshop at

https://offline.place

in Berlin on 13/6 alongside @liaizon who will give a workshop following mine on the #fediverse

i’m very much looking forward to this and for the opportunity to present materials on #digitalgarden #pkm #personalwiki #wiki

more details to follow in the replies

- gavcloud

Source here

V5.3.0: Custom widgets and filter operator names must now contain a period

I’ve made a small change to the v5.3.0 prerelease which is not fully backwards compatible with previous versions of the prerelease.

The names of custom widgets and filter operator must now contain a period. (Custom widget names continue to also require a dollar sign as the first character).

For example:

\widget $my.custom.widget()
...
\end

<$my.custom.widget>
...
</$my.custom.widget>

And:

\function my.custom.function(a)
...
\end

<$text text={{{ [my.custom.function[22]] }}}/>

Previously, custom widget names had to start with a double dollar sign, and custom filter operator names had to start with a period.

This change is intended to makes things more consistent. See the discussion on GitHub for details.

- Jeremy

Discussion here and here on Github

Plugins

Speaker Notes for the Reveal.js Plugin

I recently did a short talk for a large (1000+ -member) audience. Although it was in a Powerpoint-heavy environment, I did mine in a TW, using the Reveal.js plugin.

I love using that plugin; it lets me embed presentations inside my documentation wiki, allowing me to step out of the presentation to show other TW content; it’s quite useful. But one feature from the Reveal.js tool was not ported to TW: speaker notes. My guess is that it is, at a minimum, very difficult to port, and quite possibly impossible.

But I created something that gets part of the way there; it worked well for my talk. Perhaps others would find it useful. It a simple-to-use, simple-to-maintain set of speaker notes. It doesn’t offer Reveal’s useful slideshow controls from the same UI, so those I manage from a separate screen. But it does the rest of what I want speaker notes to do.

My presentations are created out of simple calls to the plugin’s <$presentation ...> widget, choosing as slides all tiddlers tagged with the presentation tiddler’s title. In fact a presentation tiddler has a body consisting just of

<<presentation>>

and a list field to order the slides.

A slide is just a single tiddler, tagged with the name of the presentation. And the speaker notes for that slide is simply another tiddler whose title is that slide’s title with “ - notes” appended.

The notes for the presentation is a similarly short call to a macro:

<<speaker-notes "My Presentation">>

where “My Presentation” is simply the title of the presentation tiddler.

This renders the notes to the left, the slide to the right. There is an edit icon for the notes, which launches that particular note in edit mode. The titles of the slides serve the same purpose. It looks like this:

You can try this live by downloading this:

SpeakerNotes.json (1.1 MB)

and then dropping it onto an empty edition. The only interesting parts, once you include the reveal plugin, are the macros in $:/_/my/SpeakerNotes/macros and a trivial stylesheet, $:/_/my/SpeakerNotes/styles.

If this is useful enough to develop into a full plug-in, please let me know.

- Scott Sauyet

Discussion here

TiddlyPDF Plugin Design Discussion

I recently started developing the plugin, TiddlyPDF, which allows you to export tiddlers as a pdf.

The main goal is to be able to export a TiddlyWiki into a notebook-like format, or even exporting a wiki into a business report or whatever. I’m currently at the point where I have an MVP, and some basic functionality like the basic conversion, and CSS-akin styling.

I’m making this post for two reasons, one is to gauge interest in this plugin, and the other is to talk about design from a user’s perspective.

I want to know how you would use this, and how the interface would have to work to allow you it to its fullest potential.

- GameDungeon

Discussion here

Leave a comment

Share TiddlyWiki Newsletter

Volunteer needed to maintain the Catalan translation of TiddlyWiki

Many thanks to Paco Rivière who is stepping down after 8 years of steady contributions to the Catalan translation plugin for TiddlyWiki.

It would be great to hear from anyone who might be able to take over. Making updates to translations doesn’t require any knowledge of GitHub; I or another core developer can make the PR given a single file TiddlyWiki of the changes made with the translators edition.

- Jeremy

Discussion here

Plugins

Tiddler Editor Text Resizer

Just for the giggles to figure out how I would go about it.

Download the attached and drag into TiddlyWiki.com for import of the tiddlers.

- Charlie Veniot

Discussion here

Json file to download and import

Tips & Tricks

Tiddler Ribbon Using Pure CSS & Simple Macro

A customizable ribbon for your special tiddlers.

Demo

• download tiddler-ribbon-tips-tricks.json (2.2 KB)

• drag and drop into https://tiddlywiki.com

• open one example

How it works?

• In any tiddler you like to add ribbon call folded-ribbon macro

• The macro uses three parameters: a text to display, a class to determine the side of tiddler to be displayed, and a style to control the background color, text color and folded part height!

Credits: Temani Afif

- Mohammad

Discussion here

Leave a comment

Share TiddlyWiki Newsletter

Early Testing for v5.3.0-prerelease

The upcoming v5.3.0 release of TiddlyWiki introduces some significant improvements and new features related to some of TiddlyWiki’s most fundamental components: macros, widgets, operators and transclusion. v5.3.0 also contains several other bug fixes and improvements. All the changes are intended to be backwards compatible.

This is a good time to test the new release and give feedback. The currently planned schedule is to freeze further changes on June 12th, followed by the final release on June 26th. That means that there is time to act on feedback, but it’s helpful to get it as soon as possible.

https://tiddlywiki.com/prerelease

There are several ways you can help:

• Visit the prerelease on the web, explore the release note and try out the new features. Let us know if the release note or documentation is not clear

• Use the prerelease upgrader at https://tiddlywiki.com/prerelease/upgrade.html to make a test upgrade of your own single file wiki and try out your usual workflows

• If using Node.js, download the prerelease from GitHub - Jermolene/TiddlyWiki5: A self-contained JavaScript wiki for the browser, Node.js, AWS Lambda etc. and try it with your own data and plugins

Any feedback is welcome here, or on GitHub.

Please wait until the official release before updating your day-to-day wikis, and remember the first rule of TiddlyWiki: to make sure to take (and verify) backups before doing anything risky.

Best wishes

Jeremy

Discussion here

Plugins

I'm Reading - A tool to track & stimulate your reading

If you already have a “book TW” then this probably integrates pretty well; it just requires the book tids to be tagged Book. That’s it, but there are also some optional features for “genre tags” and an author field.

I can personally attest that this plugin works in the real world: I read in a real book for 30 minutes yesterday! My head is still spinning. Man, this is a good.

- twMat

Plugin & Documentation here

Discussion here

Make quick and easy todo lists, kanban and more with the ButtonListMacro

I have made a handful of macros for my own use and figured they might be helpful to others. while this is not actually a plugin (it’s just one tiddler), it seemed close enough. so i packed it up and brought them for you here!

Introducing ButtonListMacro (actually 4 macros now), a quick tool to make todo lists, workflow tracking, kanban, or anything else that consists of lists with buttons to move things between them. it’s pretty simple, but hopefully someone else finds it useful :slight_smile:

There is support for one button (before each list item – like a checkbox) or two (one on each side of the list item). each button removes the tag that the item is listed with and replaces it with another one. icons can be easily added by putting the name of an image tiddler as the macro parameter.

Both one-button and two-button layouts have tabled variants that have a nice header.

syntax(es):

<<buttonlist listTag clickTag iconTiddler>>
<<buttonlist2 listTag clickTag iconTiddler clicktag2 iconTiddler2>>
<<buttonlisttable listTag clickTag iconTiddler>>
<<buttonlisttable2 listTag clickTag iconTiddler clicktag2 iconTiddler2>>

The attached tiddler contains the macros as well as a description, syntax reference, and a demo todo list showing how multiple ButtonListMacros can come together to make a nice workflow tracker.

enjoy!

- scribs

ButtonListMacro.tid <— Includes Documentation

Discussion here

Monthly Report App: A TiddlyWiki TimeSheet

Hi everyone,

I am a caregiver. My clients may be in a retirement home or still in their own home, I have to count the time spent with each one of them and report (monthly) my daily hours (the cumulated time of all my appointments). I also have to provide an other daily total for Sundays and/or holydays. If I have to do something out the client’s home, I have to indicate the distance too.

As many of you may know, computing hours is not that easy, that’s where this app come handy: you only have to tell the app the beginning and the end time of your appointment.

- FRDV

How to use it:

This app comes in 2 languages: English and French. You can change the working language with a click on a button. This is done under the Parameters tab.

Should you click on the button labeled Français fr-FR the app will be in French. Click again on English en-GB, it’s in English.

The TW language setting if also changed while changing the app language (good or bad thing? maybe an option is needed).

Now you have to create a town, click Clients, then New Town. Enter the town name and its zip code, a button that allow you to confirm the creation of the town will appear, click on it!

Now click the New client tab. Enter the desired values in at least 3 input zones (name, address, town) and a button will appear to create the client.

You are free to add some other data immediately in the other fields, you will be able to edit the client’s data in the Registered Clients tabs later.

• Click now the Services tab, then New service.

• Select the day (for Sundays and holydays you still have to check the checkbox)

• Select the client,

• Enter the beginning hour of your appointment

• Enter the ending hour of your appointment

• Indicate the kilometers done (if needed)

• Click the button that appeared, the new service is added!

• Click now the Monthly report tab, select the year and month : you have your monthly report!

Plugin Site here

Discussion here

TiddlyWiki Wikitext Cheatsheet Plugin

The Wikitext Cheatsheet Plugin allows you to lookup the most common wikitext syntax.

• Creates a new editor toolbar button F1 , that activates a cheat-sheet modal

• Creates a new sidebar button that activates a cheat-sheet modal

The modal is scrollable and most “code examples” can be copied to the clipboard with 1 click.

- pmario

The ControlPanel → Keyboard Shortcuts - show-cheatsheet configuration can be used to change the default keyboard shortcut setting used in “edit-mode”.

Plugin Site here

Discussion here

TW5-CSEncryption: Client-Side Encryption for TiddlyWiki5 on Node.js

Encryption has finally come to the server!

Configure a master password for TiddlyWiki5 on Node.js, and automatically encrypt tiddlers once it leaves the browser.

This plugin is currently in public beta, and I would love to hear everyone’s feedback and suggestions!

Document: TW5-CSEncryption — Client-Side Encryption for TiddlyWiki5 on Node.js

Source code: FSpark/TW5-CSEncryption: Client-Side Encryption for TiddlyWiki5 on Node.js

Discussion here

Volantis Edition: A Repack of Volant for TiddlyWiki 5.2.7

Mentat by Adam Sherwood is a great piece of work. It is a special edition with multi columns story river where tiddlers have wings to fly :wink: and are draggable and resizable.

Here is a repack of Volant plugin to work with TiddlyWiki 5.2.7. The edition is called Volantis (by original developer)

Features

• Draggable/Resizable tiddlers

• Dock to window edge [Volant-Rapid]

• Work with other kookma plugins, Link-to-Tab and Relinks [other third part plugins are not tested]

• Work with official TiddlyWiki plugins

Important Warning:

• Volantis edition overwrites two core tiddlers

  • $:/core/ui/EditTemplate

  • $:/core/ui/ViewTemplate

- Mohammad

TiddlyHost Demo: My Volantis — TW edition with flying tiddlers (tiddlyhost.com)

TiddlyHost Template to simply clone for yourself: Tiddlyhost

Discussion here

Leave a comment

Share TiddlyWiki Newsletter

Curating Editions on TiddlyWiki.com

What are TiddlyWiki editions and why are they useful?

TiddlyWiki is distributed in several distinct editions that are tuned for specific purposes.

An edition consists of the TiddlyWiki core components along with plugins, documentation and sample content to get you up and running as quickly as possible.

You can mix and match the components of these editions, to make a unique solution for your particular application.

- https://tiddlywiki.com/#Edition

On the forum we are inviting users to nominate third party editions for listing on tiddlywiki.com. Please see discussion here.

The example that prompted the discussion was “TiddlyWiki Xp” by Keaton Lao:

It aggregates the best third party plugins for TiddlyWiki and adds some very powerful extensions of its own:

Articles

Is TiddlyWiki written in itself?

“Tiddlywiki is written in itself […] the entire user interface of TiddlyWiki […] is all constructed out of wiki text primitives”

The most important philosophy of TiddlyWiki is that the purpose of recording information is to re-use it, and TW proposes that the best way to optimise information for reuse is to cut it up into the smallest semantic units. One can then use links, lists and tags to weave the fragments together into multiple overlapping narratives.

The observation about TiddlyWiki being written in itself relates to some secondary principles:

• that the individual needs of users are all different, and so it is not respectful to try to impose the same user interface on every user that users are not generally in a position to know up front what their ideal user interface looks like that the most efficient way for users to figure out precisely what they need is by iteratively modifying the user interface themselves

We address these needs by making wikitext powerful enough to be able to implement TiddlyWiki’s entire user interface.

To address your specific questions:

If I understand correctly, this means that TiddlyWiki is based on a “small” set of text primitives, that could be implemented in any underlying user interface language (for example Elm, or emacs lisp)

That’s right. As others have pointed out, the target platform of TiddlyWiki is the browser, and so even if TiddlyWiki were to be rewritten in a different language it would still need a web browser (or an emulation of one)

Are there any different backend for implementing these primitives other than HTML+Javascript?

The only available implementation of the TiddlyWiki primitives is currently JavaScript, targeting HTML.

Another example of an interesting backend could be Jupyter Notebook, maybe bringing together the wiki-style documentation with the Data Science exploratory data analysis.

I am not familiar with the internals of Jupyter Notebook, but given the fact that it manifests itself as an interactive web page it must include JavaScript in its implementation. If that’s true, then the simplest path to integration might be to integrate the existing JS implemention of TiddlyWiki.

- Jeremy Ruston

Full Discussion here

TiddlyWiki in SecondLife

Just wanted to give some kudos to the developers for a job well done.

I was playing SecondLife 6 which allows the ability to load web pages as a texture on 3D models. Typically these are static HTML files being served but I started to wonder if instead it could be a TiddlyWiki. One of the issues is that the web views lag far behind the green field browsers and the user agent is not your typical user agent so most server based pages break with more modern JS and User Agent sniffing.

But with TiddlyWiki it works perfectly, I tried both the main site tiddlywiki.com and my personal blog site tritarget.org both which are pretty hefty single page TW documents. I was elated that they just worked out right.

Again, Thank you so much for developing a product that is so useful and also so flexible that it can be used in so many ways. It truly is the very definition of what the Web was originally all about.

Discussion here

Plugins

Gitgraph in TiddlyWiki

I created a new plugin tw-gitgraph to show git-graph in tiddlywiki

tw-gitgraph is a wrapper for gitgraph.js to display gitgraph figure in TiddlyWiki.

Demo and codes can be found here:

• Demo: https://tw-gitgraph.bangyou.me

• Code: GitHub - byzheng/tw-gitgraph: gitgraph.js for tiddlywiki

- Bangyou Zheng

Discussion here

URL Import Gadget

Creates a drop zone in edit mode for links and automatically adds a wikitext title.

by Charlie Venoit

Discussion here

Video here

Files here

Yaisog's TimeTracker

This is a work-in-progress demo site for Yaisog's TimeTracker / Calendar.

It was originally conceived as a time-tracking tool for the current day, with weekly or monthly summaries for the time spent on various projects.

With a little love (from someone else) this could be extended into a calendar thingy. I currently have no intention to develop it in this direction, as I have no use for another calendar tool.

Discussion here

Plugin & Demo here

Tips & Tricks

Filter Maker and Power Search

Click on the “hammer-and-screwdriver” icon.

To select from a droplist of saved custom filters and pre-defined shadow filters, click on the “Filters” heading. Or, manually enter any custom filter syntax directly into the text input control.

Once a filter syntax has been created, entered or selected, it will show a list of matching tiddler titles, which can then be further filtered by searching selected fields for matching text or a regexp pattern.

There is a heading above the list of tiddlers that shows the number and total size of matching tiddlers. Clicking that heading will show a more detailed summary that includes “last change”, “newest created”, “oldest created”, “smallest” and “largest”.

This list of matching tiddlers can also be sorted by title, size, created date, or modified date in ascending or descending order.

In the top-right of the TiddlyTools/Search/Filters interface, there are “bulk action” buttons that allow you to tag, clone, export or delete the matching tiddler titles.

- Eric Shulman

Discussion here

Site here

Notes from the Editor

If you have any comments, feedback, suggestions, etc. please use the comment button below. This newsletter is for you, and we’d love to hear your thoughts.

Announcing the release of TiddlyWiki v5.2.7

TiddlyWiki v5.2.7 has just been released to:

https://tiddlywiki.com/

This is a bug fix release to fix a single bug that was introduced in the prior v5.2.6 release.

You can upgrade your existing single file wikis here:

https://tiddlywiki.com/upgrade.html

For Node.js users, the new version is available on npm at tiddlywiki - npm

As usual, please exercise caution when upgrading, and take care to keep backup copies of everything important.

I’d like to thank everyone who has contributed to this release.

Any questions or comments are welcome here, or via GitHub.

Articles

3 Steps to building your own personal Knowledge Management System

We'll explore personal knowledge management in this article, learning what it means, who can benefit from it, and what it offers. Discover how to create a personal knowledge management system and grow your own knowledge base.

Article here

Discussion here

Plugins

Extra Filter Operators Updated: Release 1.2

As part of working on an unannounced project I wanted a search mechanism that has more functionality than you can squeeze from vanilla TW. I didn’t like the idea of shipping those with the plugin and so the idea was born to share them.

As it usually happens with my ideas, what was one simple filter turned into 4 complex filters that should cover all your searching needs together with new and exceptional documentation, unit tests guaranteeing no regressions and powerful live example.

There are four filter operators available as of now:

susearch – search that’s slightly more powerful than the good-old search; among others it can strip away wikitext to avoid false positives caused by the structure.

susearch-sort – sort the results in an intelligent way that for the most part should feel just right and natural.

susearch-mark – for highlighting the matches.

focus-on – for extracting a part of the input, specifically designed for partial previews of the matched text.

Documentation · Demo · Install: Extra Operators

Discussion here

hiveBroker for TiddlyWiki Classic

hiveBroker can be your starting point for all your classic TiddlyWiki's.

TiddlyWiki classic is traditionally used in a browser like Firefox or Chrome or in TiddlyDesktop.

TiddlyDesktop provides a more application like look and feel, it runs on NW.js an is suited for TiddlyWiki classic and TiddlyWiki 5.

Over the years saving a TiddlyWiki in a browser became more and more difficult and I started looking for something else.

My starting point was that I only wanted to use classic TiddlyWiki's, on NW.js or Electron , with a very open architecture.

First I wrote a very basic saver to use TiddlyWiki classic with NW.js. From a running TiddlyWiki classic on NW.js you can open another TiddlyWiki classic in a new window. The same as one would use tabs in a browser.

Because I use several classic TiddlyWiki's I needed something to organize, categorize and find them with ease.

The hiveBroker-Plugin.js makes this possible, this plugin can generate a tiddler with file information in it for all folders/files in selected folders on your drive. The generated tiddlers have buttons to do basic things like delete, rename, copy and start your classic TiddlyWiki. From the tiddlers a dashboard is generated that shows you bagdes for all classic TiddlyWiki's or files that you selected, by extension, badge color, tags and sorted by number of clicks.

Available here

Discussion here

TiddlyWiki v5.2.6 Released Today

The new version of TiddlyWiki v5.2.6 has been released today and is available at https://tiddlywiki.com/.

Some highlights of the new features and improvements – see the release note for the full list of changes:

• A new improved Markdown plugin with extended syntax and simpler tiddler links

• Better handling of loss of network connectivity with the client-server configuration

• New diff-match-patch primitives for computing the similarity of strings, and making and applying patches that represent the differences between two different texts

• Fixed the Share plugin

• Fixed pasting text into the CodeMirror editor

• And last but not least, a revised "save wiki" icon that is intended to be more accessible for users without colour vision

You can upgrade your existing single file wikis here:

https://tiddlywiki.com/upgrade.html

For Node.js users, the new version is available on npm

As usual, please exercise caution when upgrading, and take care to keep backup copies of everything important.

Articles

TiddlyWiki 5 Core Icon Development

Over in the thread about the v5.2.6 prerelease there has been some interesting discussion about the improvements to the “save wiki” icon.

I thought it might be interesting to share my workbook of the TW5 icons. I’ve been using a drawing app for the Mac called Sketch since 2011. It lets me keep all the icons laid out on a canvas, with an overlay to indicate the areas to be exported as image files. (Sketch is not as popular as it was, and I don’t use it for anything besides the TW icons, so I wouldn’t recommend it nowadays).

Here’s the main area, which shows the finished versions of most of the core icons, along with a number of icons for side projects and some ideas that haven’t (yet) come to fruition:

Here’s the graveyard area where I put ideas that didn’t seem to work. Amongst other things, it shows how many attempts it took to come up with a control panel icon that I liked!

- Jeremy

Discussion here

Plugins

Advanced Search in Fields Plugin Updated: Release 0.9.0

• [NEW] Updated to Tiddlywiki 5.2.5

• [NEW] Icon for toggling plain/table view of result

• [FIXED] Extra space issues with UI

• [FIXED] Options and selected fields settings now are stored in config tiddlers to be saved between sessions

by Mohammad

Discussion here

Demo: Advanced Search in Fields — search in fields
Code: GitHub - kookma/TW-Search: Advanced search in fields using regular expression and tabular output

Favorites Plugin Updated: Release 4.8.2

• [NEW] Updated to Tiddlywiki 5.2.5

• [FIXED] Drag and drop of items with short titles. Now the droppable tag is div.

• [FIXED] Wrong variable parameter in $:/plugins/kookma/favorites/macros/drag-n-drop.

by Mohammad

Discussion here

Demo: Favorites 4.6.8— create flat and structured lists of favorite items
Code: GitHub - kookma/TW-Favorites: Favorites creates flat and structured lists of favorite items

Refnote Plugin Updated: Release 1.8.6

• Mar 9th, 2023

• [NEW] Updated to Tiddlywiki 5.2.5

• [FIXED] Cited in now supports both ref and cite macros.

by Mohammad

Discussion here

"Refnotes is a reference manager tool that allows you to maintain a “personal library” of references, citations, footnotes and abbreviations in Tiddlywiki."

Demo: https://kookma.github.io/TW-Refnotes
Code: https://github.com/kookma/TW-Refnotes

Shiraz Plugin Updated: Release 2.7.5

Shiraz and one of its children (Shiraz Formatter) have got new updates.

• [NEW] Dynamic table tags template has a new variable sv-exlude-tags to exclude specified tags from displaying in table

• [NEW] Documents updated, new examples to quick table were added

• [FIXED] Small typos in variable parameter in some code tiddlers. Thanks to Elise Springer.

• [FIXED] The background color of mono macro now supports dark palettes.

by Mohammad

Discussion here

"Shiraz is a small framework of stylesheets, templates and macros to create stylish contents in Tiddlywiki. Shiraz has customized elements like alerts, cards, panels, images, static tables, dynamic tables, quick table, badges, texts, etc. Shiraz uses some modified CSS classes from Bootstrap 4.3.1."

Demo: https://kookma.github.io/TW-Shiraz/
Github: https://github.com/kookma/TW-Shiraz

Tiddler Commander Plugin Updated: Release 2.1.6

• [FIXED] Space and icon issue in page control. See Spaces in buttons need to be dealt with · Issue #32 · kookma/TW-Commander · GitHub reported by keatonlao (Keaton Lao) · GitHub

• [FIXED] Log and alert background color supports palette in use

• [FIXED] Field rename support TW 5.2.0 mixed case name and spaces in field name

• [FIXED] SNR setting is now stored in config tiddler instead of state tiddler. This allows to have permanent config and do not lose them between sessions.

by Mohammad

Discussion here

Demo: Commander Plugin 2.1.6 — bulk operations on tiddlers
Code: GitHub - kookma/TW-Commander: A tiddler toolkit for Tiddlywiki 5. Batch operations on bulk of tiddlers. Create, delete, add fields, tags, search and replace and inspect tiddlers.

Utility Plugin Updated: Release 2.6.1

• [NEW] The .lorem macro supports number of words

• [NEW] The wikitext-macro supports embeded macro (macro embeded in host tiddler).

• [NEW] The wikitext-macro name has been changed. This is not backward compatible.

• [FIXED] Space in page control button (view-fields)

• [FIXED] The snippets for wikitext-example modified and corresponding tiddlers were renamed

• [FIXED] The wikitext-macro supports dark palettes

• [FIXED] The reveal-code does not show duplicate code for tiddlers has code-body field set to yes.

WARNING The wikitext-example and wikitext-example-without-html macros are not backward compatible. See examples and details before upgrading!

by Mohammad

Discussion here

"The utility plugin objective is to provide set of tools for authors. These tools includes simple transclusions, show raw contents of tiddlers, reader mode, wikitext macros, show fields in view mode, linkify, code, docit, and much more!"

Demo: Utility 2.6.1 — utility kit for authors and developers Code: GitHub - kookma/TW-Utility: Utility macros, buttons, and styles for documentation and development

Tips & Tricks

How To: Talk TiddlyWiki RSS Feeds

Every category at Talk has an rss feed. eg: https://talk.tiddlywiki.org/c/announcements/20 If you add .rss like so: https://talk.tiddlywiki.org/c/announcements/20.rss you'll be able to load the feed. Basically every URL in discourse has an rss feed.

-pmario

Discussion here

Development Roadmap

Today we have frozen the new features for the upcoming TiddlyWiki version v5.2.6, scheduled for release on 20th March 2023. You can see the prerelease at https://tiddlywiki.com/prerelease. We would appreciate help testing it to check whether everything works with your existing customizations and plugins. You can use the online (but downloadable) updgrader to test it, but of course we do not recommend running the new version in production until it is released. Feedback is welcomed in the discussion group, GitHub, or via Twitter.

As ever, the first rule of TiddlyWiki applies: make sure you have backed up your data!

400 Subscribers on Substack

We hit 400 subscribers to the newsletter on Feb 26th and are currently at 430!

Articles

Using ChatGPT & TiddlyWiki

The short version: Users are experiencing a wide variety of results. Caution should be used as most are finding the answers provided by ChatGPT highly unreliable.

Ongoing Discussions here & here

Successes

• Bookmarklet to convert TW Talk tiddler json download links into share site urls

I've been looking for the perfect note taking app for the past 10 years. I listed all my requirements to ChatGPT and it recommended #TiddlyWiki. My thoughts and life have never been so organized before. Thank you for this gift! - Miladiouss

Others having less than Success

• Don't believe ChatGPT - we do NOT offer a "phone lookup" service

Discussions

“Be Rad” Custom Layout

While still very much a work-in-progress, my on-going customization feels complete enough to post about again. Since all the major UI elements are very dependant on an alternative layout, I can’t currently release anything as plugins, so I’ll just call this an edition.

by Brian Radspinneer

Explore the Be Rad Edition here

Plugins

Subsume Plugin Updated

"...so that it takes the caption field of a subsumed tiddler into account, and displays that in the details summary element rather than the tiddler title."

Thank you @Scribs for the recommended update to the Subsume Plugin, and to @EricShulman for the tweak to make it work correctly.

by Dave Gifford

Update Discussion here

Plugin here

SuperTag Plugin: Auto-generate a field editor

Auto generate input form on a tiddler by simply adding a SuperTag to it. Create a SuperTag by compositing existing TraitTags.

by Lin Onetwo

Discussion here

Demo site

Github

Tips & Tricks

Subscribe to the TiddlyWiki Newsletter via RSS Feed

If you prefer to receive this newsletter via RSS feed here is the link https://tiddlywiki.substack.com/feed

You can get the Feedbro RSS reader here

RSS (RDF Site Summary or Really Simple Syndication) is a web feed that allows users and applications to access updates to websites in a standardized, computer-readable format. Subscribing to RSS feeds can allow a user to keep track of many different websites in a single news aggregator, which constantly monitor sites for new content, removing the need for the user to manually check them. News aggregators (or "RSS readers") can be built into a browser, installed on a desktop computer, or installed on a mobile device.

- Source Wikipedia

TiddlyWiki Icon Submitted to Simple Icons

oeyoews has submitted a SVG of the TiddlyWiki logo via Github PR to Simple Icons for inclusion on their website. It is still pending approval.

Simple Icons provides free SVG icons for popular brands.

Discussion here

Articles

Showcase: Periodic Table

Discussion here & here

Plugins

Directory List to TiddlyWiki

I made a script that scans a folder & displays the file/folder names in @TiddlyWiki. This makes it easy to browse & search, and share your file listings with friends. Source & example output here. - @trumad

Original Post here

Output Example here

Giscus Plugin for TiddlyWiki

Announcing Giscus for TiddlyWiki. Comments inside the wiki are welcomed 🤗❤️. Come try it out. - Abraham

A commenting system for TiddlyWiki powered by Github discussions via Giscus app.

Tips & Tricks

How To Compare the Content of a Shadow Tiddler With the Content of an Overwritten Shadow

Mario Pietsch provided a detailed step-by-step walk-through. Article & discussions at the title link above.

Stroll updated to TW 5.2.5

I updated Stroll, and its empty file, to TW version 5.2.5.

If you have Stroll, do to the TiddlyWiki upgrade Wizard (https://tiddlywiki.com/upgrade.html) and upgrade your file if you haven’t already. Save a backup before doing so, just to be safe.

Then go to https://giffmex.org/stroll/stroll.html#Updating%20Stroll , and drag the tag pill "$:/giffmex/stroll" to your file. This is so that one or two overwritten system tiddlers stay overwritten. The upgrade process “un-overwrites” them, so dragging the pill “re-overwrites” them.

Dave Gifford

Discussion here

Articles

Creating educational materials with TiddlyWiki

We hope that this work will help teachers to create professional quality materials and their teaching work is facilitated.

Juan José de Haro

Article Source

Translated by MS Edge

TiddlyWiki Information Videos in Chinese

TiddlyWiki builds your digital second brain

Ep054 Build a personal public digital garden with TiddlyWiki to simulate Andy notes website by pimgeek

Li Guang Interval repeating card notes: a new choice - TiddlyMemo

Links shared by Lin Onetwo

Link titles translated by MS Edge

Promotional Video Discussion here

Plugins

Accordian Macro

by Scott Sauyet

Discussion here

Post-it Notes in a Tiddler Body

Thomas Chuffart made it by combining tips from Eric Shulman on Viewtemplates here and Mohammad Rahmani's on RGB with Alpha Channel here.

Tips & Tricks

How to create an Editor Toolbar button copies the full "text" field to the clipboard

<$action-sendmessage $message="tm-copy-to-clipboard" $param={{{ [<targetTiddler>get[text]] }}}/>

Solution by Mario Pietsch

Discussion here

Open-Source UI elements - made with CSS and HTML

This site collects together pure HTML+CSS implementations of buttons, checkboxes, loaders and other basic UI elements. They are straightforward to reuse in TiddlyWiki but no doubt there is scope to make a plugin that encapsulates the implementations neatly for reuse.

- Jeremy Ruston

Discussion here

Use example by Anthony Muscio here

Using Stylesheets in the official documentation