1
0
mirror of https://github.com/Jermolene/TiddlyWiki5 synced 2026-01-26 04:43:42 +00:00

Compare commits

..

12 Commits

Author SHA1 Message Date
Jeremy Ruston
0b4fffcb33 Update responses 2025-07-28 10:57:31 +01:00
Jeremy Ruston
a9284d3074 Add count for each unique response 2025-07-28 10:37:45 +01:00
Jeremy Ruston
c876da3da1 Show response count 2025-07-28 09:11:10 +01:00
Jeremy Ruston
3504660b64 Fix responses 2025-07-27 22:00:12 +01:00
Jeremy Ruston
9ff7fed426 Fix schema 2025-07-27 21:59:22 +01:00
Jeremy Ruston
a66f9f6df6 Reimport answers with new schema 2025-07-27 21:44:20 +01:00
Jeremy Ruston
a2ea8eb06d Improve import specs 2025-07-27 21:43:01 +01:00
Jeremy Ruston
d2fae62d2b Save changes on the server for when we're importing on the command line 2025-07-27 20:20:35 +01:00
Jeremy Ruston
a6cb0f1585 New 2025 answer 2025-07-27 20:20:01 +01:00
Jeremy Ruston
afa4126602 Survey results as of 25th July 2025 2025-07-26 21:38:20 +01:00
Jeremy Ruston
d7c86a6721 Community Survey 2025 improvements 2025-07-26 21:37:53 +01:00
Jeremy Ruston
8611d06eb9 Community Survey import specifier for xlsx plugin 2025-07-18 14:07:20 +01:00
220 changed files with 424 additions and 3436 deletions

View File

@@ -5,8 +5,8 @@ on:
paths:
- 'boot/**'
- 'core/**'
- 'themes/tiddlywiki/snowwhite/**'
- 'themes/tiddlywiki/vanilla/**'
- 'themes/snowwhite/**'
- 'themes/vanilla/**'
jobs:
calculate-build-size:

View File

@@ -1,5 +0,0 @@
title: Community Cards Caveats
created: 20250909171928024
modified: 20250909171928024
''Please note that [[Community Cards]] are a new initiative started in September 2025. There is further work required to complete the team and people information.''

View File

@@ -1,11 +0,0 @@
title: Community Cards
tags: Community
modified: 20250909171928024
created: 20250909171928024
The purpose of Community Cards is to allow project plans and other community activities to be linked to the people who are involved in them. They also allow people to share their interests and activities in the TiddlyWiki community, and to help people in the TiddlyWiki community get to know each other better.
{{Community Cards Caveats}}
* [[Submitting a Community Card]]
* [[Displaying Community Cards]]

View File

@@ -1,26 +0,0 @@
title: Displaying Community Cards
tags: [[Community Cards]]
modified: 20250909171928024
created: 20250909171928024
!! Cards for people
This is an inline card for <<community-card-pill-person title:"@Jermolene">> and <<community-card-pill-person title:"@ericshulman">> which can be used in the middle of a sentence.
This is a stack of inline cards:
<<community-card-pill-stack-person>>
Here is a full format card:
<<community-card-person title:"@Jermolene">>
This is how the card looks when there is no such person:
<<community-card-person title:"@MissingPerson">>
!! Cards for teams
This is a card for a project team:
<<community-card-team title:"Project Team">>

View File

@@ -1,36 +0,0 @@
title: Submitting a Community Card
tags: [[Community Cards]]
modified: 20250909171928024
created: 20250909171928024
Anyone associated with the TiddlyWiki community can submit a Community Card. The submission process currently involves making a GitHub pull request but we intend to provide a more user-friendly submission process in the future.
Pull requests to add or update a community card should be made against the `tiddlywiki-com` branch of the [[TiddlyWiki repository|https://github.com/TiddlyWiki/TiddlyWiki5]] in the directory `community/people`.
The card should be a TiddlyWiki tiddler with the following fields:
|!Field |!Required|!Description |
|`title`|Yes |The username of the person represented by the card, starting with `@` (e.g. `@Jermolene`). This is the title of the card and should be unique |
|`tags`|Yes |The tags for the card, including `Community/Person` |
|`fullname`|Yes |The full name of the person or group represented by the card |
|`avatar`|Yes |The base64 representation of the 32x32 avatar image for the person represented by the card |
|`first-sighting`|No |The date of the first sighting in the community of the person represented by the card. This should be in ISO 8601 format (YYYY-MM-DD) |
|`talk.tiddlywiki.org`|Yes |The username of the person or group on the TiddlyWiki Talk forum |
|`github`|No |The username of the person or group on GitHub |
|`linkedin`|No |The URL of the LinkedIn profile for the person or group represented by the card |
|`flickr`|No |The URL of the Flickr profile for the person or group represented by the card |
|`homepage`|No |The URL of the homepage for the person or group represented by the card |
|`email`|No |The email address of the person or group represented by the card |
|`text`|Yes |The text of the card. This should include a brief description of the person or group represented by the card, and any other relevant information |
! Rules for Community Cards
Community cards must observe the following rules. It is intended to enforce them with an automated script, but for the moment they will be manually checked.
* `title` must be unique and start with `@`
* `tags` must include `Community/Person`
* `fullname` must be provided
* `avatar` must be a base64 representation of a 32x32 image, with a limit of 1KB. [[Squoosh|https://squoosh.app/]] is recommended for resizing and compressing images
* `first-sighting` should be in ISO 8601 format (YYYY-MM-DD)
* `talk.tiddlywiki.org` must be provided
* `text` total size must not exceed 2KB

View File

@@ -1,10 +0,0 @@
title: @Arlen22
tags: Community/Person
fullname: Arlen Beiler
first-sighting: 2011-06-20
talk.tiddlywiki.org: arlen22
github: Arlen22
homepage: arlen22.github.io
avatar: /9j/4AAQSkZJRgABAQAAAQABAAD/2wEEEAAVABUAFQAVABYAFQAYABoAGgAYACEAIwAfACMAIQAwAC0AKQApAC0AMABJADQAOAA0ADgANABJAG8ARQBRAEUARQBRAEUAbwBiAHcAYQBaAGEAdwBiALEAiwB7AHsAiwCxAMwArACiAKwAzAD4AN0A3QD4ATgBKAE4AZcBlwIkEQAVABUAFQAVABYAFQAYABoAGgAYACEAIwAfACMAIQAwAC0AKQApAC0AMABJADQAOAA0ADgANABJAG8ARQBRAEUARQBRAEUAbwBiAHcAYQBaAGEAdwBiALEAiwB7AHsAiwCxAMwArACiAKwAzAD4AN0A3QD4ATgBKAE4AZcBlwIk/8IAEQgAQABAAwEiAAIRAQMRAf/EADAAAAIDAQEAAAAAAAAAAAAAAAMFAQQGAgABAQEBAQEAAAAAAAAAAAAAAAIDAQAE/9oADAMBAAIQAxAAAADIRMd3XctQlXtCTTmB6RFvANDouy4DYwEEar6YVM7ocz57mcqnZys+V2azZU4XZSoiZqhQt9TKOlnO+GOl1HyoUPXLn//EACYQAAICAQQCAgEFAAAAAAAAAAECABEDBBIhMUFRECITFCMycZH/2gAIAQEAAT8AI4Bv4ryAeBAnANHuNidWogEwYHNRsdfA8iruVMOIu6iYtK4c714vgTDpXyOfrQHdifoArEXxM2mR0NeOhUzI+LJzYbuHszCm5hYseZh0gXYWFIai4cWJgFJuFKYvtr2sJRuB9fUzgDHlGMHia2757uYsYc0TNHpsSmzzMONjl9iu74iK6PbWT7gv/RMiZDk+qcA3NXkAVl3gE+ADU1PDVdiaDCGJZjQEyowKANS1ZMwK+HJ+3a0KUDqYnYINxJ3eItDk81M2cZD+NVIrmanU/wAl2gCZiGNiaFziJ3LYIHcXMrLvDABe17EN1vCgqR2TNPnGTBSBbDTeV3c2amdlxPuD2C3H9epqmV628xqsUYmdiuwkVVTSZ0Q/dxwYdScrgBRsqONi2KQX7mo1G4WCK20B6j6p/VpcfMXPVQ9mbhx9eLgZrFGDUZB1DqMrCma4xN8mDcR5qK5Rgw7Hx//EABwRAQEBAQACAwAAAAAAAAAAAAECABEDIhIxQf/aAAgBAgEBPwDVQYpfzd66qDeOSn7yEmH23ffDAi66mug6DM9N8HTAY3//xAAcEQEBAQEAAgMAAAAAAAAAAAABAAIREBIiQVH/2gAIAQMBAT8AglC+rJbdCT1vVC33l83tj2OPLS+AJ3+Tf//Z
I make random software.

View File

@@ -1,29 +0,0 @@
title: @ericshulman
tags: Community/Person Community/Team/Contributors
fullname: Eric Shulman
first-sighting: 2005-06-21
talk.tiddlywiki.org: ericshulman
github: ericshulman
homepage: tiddlytools.com
email: elsdesign@gmail.com
avatar: iVBORw0KGgoAAAANSUhEUgAAACAAAAAgCAQAAADZc7J/AAAD/ElEQVR42o2Tf2iUdRzH37e7rOa222233bab3mqKU9QihCAi+isKwX/sh5UQhGYQhNAvQowRUoghQWDOIJtQmOY0M92ZmVGm0WbTyZI1Nnft99S1jc3dPT9efffg/bHdLn19Hp4HPjzv9/fz+fL5aE58PwUkjzzFVC4P/G/k6E445Pc+uceeaqnv7Ogd6Rq68PPhrc+vkiERWOLT/+Ib8uQHNiXax3BIM0mC+CEtl2G7X9mIeCV+9Ejrr2MAtgkH14SNBRZXrYYPNF86nsXCkx/8dATAsp0JhknQTYJrTHg5SNI0qMekb+aw8Hr74WCKpNNu/0Kck5ymkRMcZz/1Jv5g2CUFbZYelrbMvlBMonHvJK3JuPsdTQxwExc8XG7SxF7OcxGScP6wRGCG/Asjf39VPydTzbQyRBrXBKToBCP/nQQ9VpIDO6SumU3EjUFLzX766HMG0mIvoJnXEbU47GGXc4TGBs3zWp5Jh7F47omdf56hy9lLIz3gyYfZSQMJztFEH3KEDg+bf1dkzkO9Savks7H9NLqnuEw3MEU314nTwABj/MV2R6y8JL+0wKdM8MtX23aFy04dF5mg08QI6XYsemmzRfiMDP5Mg1emK4ienZxi0p0gBfRwhSHAxgXGGeS6tYUdu6TPA3Ofr3Mfj9Bv4zHMDaCTMcBlnG4cJqx64sagN9Ngw3RJoa5R+MftI8k1Wm7NcSsH6KKPFGBbG1n1srQ+06DWpJ59cRhsGKGbo0wBFpDgNGcBcHGsl9BuSZmjfCRHWnv0BtgOcJVWwAZG2cw+3uErAKacZ6hq32PkGWuNSaxsHgIHxqjje5I4/Ms2dCt+BHpcUT4ai0j5sw22TCea2sCBbz3BOjaRFj+JeAE46IoHxlUmlfrmWuZT+8Ae935fjljDe3zpLdEJxGriLHdFtL8mKC2cbbAgIOXVBemwBhHibZq4xN/0YgPrESsRsiMs+C1zEwwFxqBqs4hY2yhlKeIUab5GLEM8SLlVRslu77jZhEwL/ofKKZ4uknxiiLO0cYFGFpJPMTGiRO0iQqtNrX7NxueTcahqv4/FTpgwFYinOcoxtiLKWEwF+U6Mqv5FuVlWSQHzvBWmKmUqIEg1YiMfIu6lhjKCRK0YkXelwoDmIjztWrCot5KQs5R5zKccIVZQwl3cTaVdQVGnfOkrzFbDuvuJWTVuBcXcQ5iFlFFAmBynlBKKH/f6z06pX6r6pJoSQlaeW2gsighi3na1E6HwNSkUUHbS45FXG7ajhIi68+1cO98qtqqJEHzTW6LbEfUstER1ef2llBKhiGqKW7VGUk6lT7dnmS/gnZMf1KPaoI16VWsrA1KhX3dObo5m9VqQpff/AFTcI4hMzFV+AAAAAElFTkSuQmCC
\define wiki(text,topic) [[$text$|https://en.wikipedia.org/wiki/$topic$]]
''Hello! My name is Eric Shulman''. I am the author of ''[[www.TiddlyTools.com|http://www.TiddlyTools.com]] (Small Tools for Big Ideas! &trade;)'', a popular collection of original plugins, macros, widgets, templates and stylesheets for TiddlyWiki that I have created and shared with the TiddlyWiki community.
<<<
Think of TiddlyTools as a ''virtual hardware store and "demonstration showroom"'', offering tools, parts and techniques that provide a rich variety of new functionality and feature enhancements to help you ''turn a general-purpose TiddlyWiki "info-house" into a comfortable, custom-built "info-home"''.
The TiddlyWiki core system provides the basic structure and utilities: the foundation, framing, walls, roof, windows/doors, plumbing, heating, and electrical systems. Then, TiddlyTools helps you with all the "finish work": the appliances, fixtures, lighting, cabinets, furniture, paint, wallpaper, carpeting, etc. ''to best suit your specific needs and personal style''.
<<<
Since the early days of TiddlyWiki (April 2005), I have worked closely with its inventor, [[Jeremy Ruston|https://jermolene.com/]], to help develop and improve TiddlyWiki's core functions. I am also a key contributor and administrator of the online TiddlyWiki [[Discourse|https://talk.TiddlyWiki.org]] and [[GoogleGroups|https://groups.google.com/forum/#!forum/tiddlywiki]] discussion forums, providing ongoing assistance to the worldwide TiddlyWiki community. I have written over 15,000 detailed responses to individual questions posted online. For several years I was also the lead developer and maintainer of the [[TiddlyWiki Classic|https://classic.tiddlywiki.com/]] codebase.
I was born and raised in suburban Long Island, NY, and attended [[Carnegie Mellon University (CMU)|https://www.cmu.edu/]] in Pittsburgh, PA, where I studied ''Computer Science, Cognitive Psychology, Sociology, Human Factors Design, and Artificial Intelligence''. As an undergraduate at CMU, I was privileged to work with some of the major luminaries in early software research and design, including <<wiki "Herbert Simon" "Herbert_A._Simon">>, <<wiki "Allen Newell" "Allen_Newell">>, <<wiki "James Gosling" "James_Gosling">>, and <<wiki "Raj Reddy" "Raj_Reddy">>. I was also employed in several Computer Science Department research projects, including the development of speech recognition technologies, graphical interface systems, and interactive applications for instruction in physics, art and music. I received a ''Bachelor of Science in "Interactive Systems Design"'' from CMU in 1985.
During my early post-graduate years, I worked for several notable software development companies, including
<<wiki "Honeywell Information Systems" "Honeywell#Honeywell_Information_Systems">> and <<wiki "Lotus Software" "Lotus_Software">>. I was an integral member of the <<wiki "1-2-3 spreadsheet"
"Lotus_1-2-3">> development team where I helped create the first GUI-based application interfaces for Microsoft Windows and IBM OS/2.
Since 1998, I have been an ''independent design consultant'', living and working in Silicon Valley, where I apply more than 40 years of experience to provide ''analysis, design and software development services'' for commercial companies and not-for-profit organizations, with emphasis on ''information architecture'' and ''interaction/visual design standards'' to improve ease-of-use for new and existing software products and online environments.

View File

@@ -1,20 +0,0 @@
title: @Jermolene
tags: Community/Person
fullname: Jeremy Ruston
first-sighting: 2004-09-20
talk.tiddlywiki.org: jeremyruston
github: Jermolene
linkedin: www.linkedin.com/in/jermy
flickr: www.flickr.com/photos/jermy/
homepage: jermolene.com
email: jeremy@jermolene.com
avatar: /9j/4AAQSkZJRgABAQAAAQABAAD/2wCEAAgICAgJCAkKCgkNDgwODRMREBARExwUFhQWFBwrGx8bGx8bKyYuJSMlLiZENS8vNUROQj5CTl9VVV93cXecnNEBCAgICAkICQoKCQ0ODA4NExEQEBETHBQWFBYUHCsbHxsbHxsrJi4lIyUuJkQ1Ly81RE5CPkJOX1VVX3dxd5yc0f/CABEIACAAIAMBIgACEQEDEQH/xAAtAAEBAAMAAAAAAAAAAAAAAAAHBgIEBQEBAQEBAAAAAAAAAAAAAAAAAgQBBf/aAAwDAQACEAMQAAAANF4uTuPRhD2nBLnUiJvKM0DtMKy//8QAKxAAAgIBAwMDAQkAAAAAAAAAAQIDBBEABRITITEiMkFxFEJRUmFicoGR/9oACAEBAAE/AInTA6gUGP4ZOQbW1bPsmyUq1q+gmvFPUzZPDkPamtwqU75ks04JakroVcg5RwRjg66NUx25KbzqJYyMngfqSuq0M3NZYIebJIvZozIvI/iNPcp/aalSdJXsS4VcKeIzlvU3jVTcYLNiaGISrjkhWQYDfQ63pYAzCDBsOiu7Dsx4EHH6r2w2ttimjd2IsNErhhJHKI04/uzqxuCxpBYVVWKSHqwMyMSQ33SB7dUJFmlkMYRgnqZgCMf7rf8AeEt3A9YOhjXAb2k8u7dtT1RZeOtXmYxiOPj4ZWY/lb51skqUNnNW/wBNzC7IpB6gQeeB/jq/fqGOaLbowuYn5MAQOw8LjW5Vmeo0qIsqYLLKjHIZmwv9fB1//8QAHxEAAQMEAwEAAAAAAAAAAAAAEQABAgMSIWExMkFR/9oACAECAQE/AD9iTy2lJmHUB8BVKM4SNSOj46a29saX/8QAHREAAgICAwEAAAAAAAAAAAAAAQIAAwQRITGBkf/aAAgBAwEBPwDHpFpJZtamVSiBWT2Yt7hmCDsb+TKtsKqpGg3M/9k=
I'm the original inventor of TiddlyWiki. You can hire me through my consultancy company [[Intertwingled Innovations|https://intertwingledinnovations.com]] or contact me directly.
Further information:
* A recording of the [[keynote I gave at QCon London in April 2024|https://www.infoq.com/presentations/bbc-micro/]], and the [[discussion on talk.tiddlywiki.org|https://talk.tiddlywiki.org/t/recording-of-jeremys-keynote-at-qcon-london-april-2024/10505]]. The talk mixes some nostalgia about my teenage activities with the BBC Micro with thoughts on the development of the software industry and insights gained from working with TiddlyWiki
* An [[interview with me in The Inquirer|https://web.archive.org/web/20111103225832/http://www.theinquirer.net/inquirer/feature/2105529/bt-software-engineer-tells-telco-source]] by Wendy Grossman
* A [[hilarious interview with me|https://www.youtube.com/watch?v=auyIhw8MTmQ]] from British television in 1983
* Here's a video of a presentation I did in 2007 called [["How to Start an Open Source Project"|http://vimeo.com/856110]].

View File

@@ -1,11 +0,0 @@
title: @MotovunJack
tags: Community/Person Community/Robot
fullname: Motovun Jack
first-sighting: 2012-01-12
github: MotovunJack
homepage: tiddlywiki.com
avatar: /9j/4AAQSkZJRgABAQAAAQABAAD/2wEEEAAYABgAGAAYABkAGAAaAB0AHQAaACUAKAAjACgAJQA2ADIALgAuADIANgBSADsAPwA7AD8AOwBSAH0ATgBbAE4ATgBbAE4AfQBuAIYAbQBlAG0AhgBuAMYAnACKAIoAnADGAOUAwQC2AMEA5QEWAPgA+AEWAV4BTAFeAckByQJmEQAYABgAGAAYABkAGAAaAB0AHQAaACUAKAAjACgAJQA2ADIALgAuADIANgBSADsAPwA7AD8AOwBSAH0ATgBbAE4ATgBbAE4AfQBuAIYAbQBlAG0AhgBuAMYAnACKAIoAnADGAOUAwQC2AMEA5QEWAPgA+AEWAV4BTAFeAckByQJm/8IAEQgAQABAAwEiAAIRAQMRAf/EADAAAAIDAQEAAAAAAAAAAAAAAAMEAQIFBgABAQEBAQEAAAAAAAAAAAAAAAIDAQAE/9oADAMBAAIQAxAAAADZCfn5vZJz+rnODGtpbpm6O8xzG9lCiszXtikQhtkTBputBxURJuVVYlEdBaQ284mPDj6GmkNUblMxRmi7dKw//8QAKxAAAgIBAgUCBgMBAAAAAAAAAQIAAxESIQQTIkFRFGEjMUJxgaEyNGLR/9oACAEBAAE/AMmX3ilMkjPaV3ragZDtNRmoxpvA2sEqQcHEwJxlwa98nYbCU8TymDfSTvPVKMbZHkQcTU4yDH46tTiE8RxjLXnQp7Dx5MACgKuyqMAS1xXU7kjYTiEbWp3y0IucYbGx6e05hDAqMH/k59o3DfxAE5hss1MNzODdVraxu50ieppH1Tivi8O6eYQ1j4B6guAftChDMNjBqycHcCYJqdj2s3idRBHfpi/1Kie7PDo95w/EMxYM22n9yy5AzBc/iLe7dIqx7kyy2ypyOWoYTofhCyDAZtx4MOmpK9sncyx1NdSq2kBBt3EKf6mgIzDUPIiByuqk7faMLbOyEjuuxEAyo56AgeTA3KL1AYRm1CcvmkgAs2wHjEvPxGIMJPmHUQCQNothr32A0ggeYluplcAK2PlLbTytZUkdwI7V3lAQMgbAfP8AMoCV1AKMOR+pdsc5yD595mMmNIGD4h0vsfupHyBlTKW9znMd+TQnljPWqHYIqhwD1zKsqtjBzCAVAyBicnqG6jbOe0//xAAbEQEBAAMBAQEAAAAAAAAAAAABAAIRIRASQf/aAAgBAgEBPwBYbZDuXvnLE5OrkWJzxI4g33ift//EABsRAAMBAQADAAAAAAAAAAAAAAABEQIhEBJB/9oACAEDAQE/AMqjzHwjGoZXPHTb6Zp1/TRp1khYjW01xHqz/9k=
Motovun Jack is a robot that helps maintain the TiddlyWiki project infrastructure. It is not a person, but rather a set of automated scripts and tools that assist in managing the various services and resources used by the TiddlyWiki community.
The origin of the name "Motovun Jack" is a lovable and playful kitten encountered by [[@Jermolene]] in the beautiful medieval hill town of Motovun in Croatia. Jack was [[first adopted|https://github.com/TiddlyWiki/TiddlyWiki5/commit/ecfbaaa5641f14e1766ef17ef6416bf9aa992863]] as the TiddlyWiki 5 mascot in 2012.

View File

@@ -1,10 +0,0 @@
title: TiddlyWiki People
modified: 20250909171928024
created: 20250909171928024
tags: Community About
Members of the TiddlyWiki community who are involved in the development of TiddlyWiki and the running of the project are invited to [[create a Community Card|Submitting a Community Card]] so that they can be included in project plans and organisation charts. Community Cards can also showcase their interests and activities in the TiddlyWiki community.
{{Community Cards Caveats}}
<<community-card-pill-stack-person personFilter:"[tag[Community/Person]sort[title]]">>

View File

@@ -1,10 +0,0 @@
title: TiddlyWiki Project
modified: 20250909171928024
created: 20250909171928024
tags: Community About
The TiddlyWiki Project is the coordinated, ongoing effort to maintain and improve TiddlyWiki, and to support the TiddlyWiki community.
{{Community Cards Caveats}}
<$list filter="[tag[Community/Team]]" template="$:/tiddlywiki/community/cards/ViewTemplateBodyTemplateTeam"/>

View File

@@ -1,4 +0,0 @@
title: Vacant Positions
tags: [[TiddlyWiki Project]]
If you are interested in volunteering to help the project please get in touch with <<community-card-pill-person title:"@Jermolene">>.

View File

@@ -1,8 +0,0 @@
title: Core Team
tags: Community/Team
modified: 20250909171928024
created: 20250909171928024
leader: @Jermolene
team: @saqimtiaz
The core team is responsible for the maintenance and development of the TiddlyWiki core and official plugins.

View File

@@ -1,14 +0,0 @@
title: Infrastructure Team
tags: Community/Team
modified: 20250909171928024
created: 20250909171928024
team: @MotovunJack
The Infrastructure Team is responsible for maintaining and improving the infrastructure that supports the TiddlyWiki project. This includes the hosting, deployment, and management of the TiddlyWiki websites and services, as well as the tools and systems used by the TiddlyWiki community.
The infrastructure includes:
* talk.tiddlywiki.org
* github.com/TiddlyWiki
* tiddlywiki.com DNS
* Netlify account for PR previews

View File

@@ -1,8 +0,0 @@
title: MultiWikiServer Team
tags: Community/Team
modified: 20250909171928024
created: 20250909171928024
leader: @Arlen22
team:
The MultiWikiServer development repository is at https://github.com/TiddlyWiki/MultiWikiServer

View File

@@ -1,6 +0,0 @@
title: Newsletter Team
tags: Community/Team
modified: 20250909171928024
created: 20250909171928024
The Newsletter Team is responsible for producing the TiddlyWiki Newsletter, a monthly email newsletter that highlights news, updates, and community contributions related to TiddlyWiki.

View File

@@ -1,15 +0,0 @@
title: Project Team
tags: Community/Team
modified: 20250909171928024
created: 20250909171928024
icon: $:/tiddlywiki/community/icons/project-team
leader: @Jermolene
team: @saqimtiaz @ericshulman
The project team is responsible for the overall TiddlyWiki project, its vision, mission and values, and ensuring that it meets the needs of the community.
Areas of responsibility include:
* Communicating and demonstrating the vision, mission and values of the project
* Continuously improve the development process and practices of the project
* more to come...

View File

@@ -1,13 +0,0 @@
title: Succession Team
tags: Community/Team
modified: 20250909171928024
created: 20250909171928024
leader: @Jermolene
team: @saqimtiaz @ericshulman
The Succession Team is responsible for ensuring that personnel changes do not impact access to the external infrastructure used by the project.
* Work with the other teams to ensure that the project has a succession plan for key personnel
* Work with the other teams to ensure that they are using the appropriate, community-owned infrastructure
* Ensure that the members of the succession team share ownership of the key project resources (eg passwords and user accounts). The Succession Team is not expected to use their access rights apart from managing access in the event of personnel changes

View File

@@ -1,5 +0,0 @@
title: Community/Team
modified: 20250909171928024
created: 20250909171928024
list: [[Project Team]] [[Core Team]] [[Documentation Team]] [[MultiWikiServer Team]] [[Newsletter Team]] [[Infrastructure Team]] [[Succession Team]]

View File

@@ -1,3 +0,0 @@
# Community Records and Resources
These raw tiddlers comprise the community records and resources for the TiddlyWiki project. They are packaged as a root directory outside of the usual "editions" folder so that they can be shared with other wikis.

View File

@@ -1,15 +0,0 @@
title: $:/config/DefaultColourMappings/
community-card-background: #ffffee
community-card-foreground: #441111
community-card-dark-shadow: rgba(188, 189, 189, 0.5)
community-card-shadow: rgba(212, 212, 213, 0.5)
community-card-header-background: #9e3060
community-card-header-foreground: #ddddee
community-card-team-header-background: #306090
community-card-team-header-foreground: #ddeedd
community-card-vacancy-header-background: #609030
community-card-vacancy-header-foreground: #eedddd
community-card-info-background: #f3f38b
community-card-info-foreground: #444411
community-card-field-name-foreground: #888844

View File

@@ -1,168 +0,0 @@
title: $:/tiddlywiki/community/cards/Procedures
tags: $:/tags/Global
\procedure community-card-display-jpeg-field(fieldName,mode:"block",default)
<$genesis $type={{{ [<mode>match[block]then[div]else[span]] }}} class={{{ tc-community-card-field-image [[tc-community-card-field-image-]addsuffix<fieldName>] +[join[ ]] }}}>
<%if [<currentTiddler>has<fieldName>] %>
<img src={{{ [<currentTiddler>get<fieldName>addprefix[data:image/jpeg;base64,]] }}} width="32"/>
<%else%>
<$transclude $tiddler=<<default>> $mode=<<mode>>/>
<%endif%>
</$genesis>
\end community-card-display-jpeg-field
\procedure community-card-display-transclusion(fieldName,mode:"inline",default)
<$genesis $type={{{ [<mode>match[block]then[div]else[span]] }}} class={{{ tc-community-card-field-image [[tc-community-card-field-image-]addsuffix<fieldName>] +[join[ ]] }}}>
<%if [<currentTiddler>has<fieldName>] %>
<$transclude $tiddler={{{ [<currentTiddler>get<fieldName>] }}} $mode=<<mode>>/>
<%else%>
<$transclude $tiddler=<<default>> $mode=<<mode>>/>
<%endif%>
</$genesis>
\end community-card-display-transclusion
\procedure community-card-display-text-field(fieldName,showLabel:"yes",linkPrefix,displayPrefix,mode:"block")
<%if [<currentTiddler>has<fieldName>] :or[<fieldName>match[title]] %>
<$genesis $type={{{ [<mode>match[block]then[div]else[span]] }}} class={{{ tc-community-card-field-text [[tc-community-card-field-text-]addsuffix<fieldName>] +[join[ ]] }}}>
<%if [<showLabel>match[yes]] %>
<span class="tc-community-card-field-text-name"><$text text=<<fieldName>>/></span>
<%endif%>
<%if [<linkPrefix>!match[]] %>
<a
href={{{ [<currentTiddler>get<fieldName>addprefix<linkPrefix>] }}}
class="tc-community-card-field-text-value"
rel="noopener noreferrer"
target="_blank"
>
<$text text={{{ [<currentTiddler>get<fieldName>] :else[<fieldName>match[title]then<currentTiddler>] +[addprefix<displayPrefix>] }}}/>
</a>
<%else%>
<span class="tc-community-card-field-text-value">
<$text text={{{ [<currentTiddler>get<fieldName>] :else[<fieldName>match[title]then<currentTiddler>] +[addprefix<displayPrefix>] }}}/>
</span>
<%endif%>
</$genesis>
<%endif%>
\end community-card-display-text-field
\procedure community-card-person(title)
<$let currentTiddler=<<title>>>
<div class="tc-community-card">
<$link to=<<currentTiddler>> class="tc-community-card-header-link">
<div class="tc-community-card-header">
<<community-card-display-jpeg-field "avatar" default:"$:/tiddlywiki/community/icons/person">>
<<community-card-display-text-field "title" showLabel:"no">>
</div>
</$link>
<div class="tc-community-card-info">
<<community-card-display-text-field "fullname">>
<<community-card-display-text-field "first-sighting">>
<<community-card-display-text-field "talk.tiddlywiki.org" linkPrefix:"https://talk.tiddlywiki.org/u/" displayPrefix:"@">>
<<community-card-display-text-field "github" linkPrefix:"https://github.com/" displayPrefix:"@">>
<<community-card-display-text-field "linkedin" linkPrefix:"https://">>
<<community-card-display-text-field "flickr" linkPrefix:"https://">>
<<community-card-display-text-field "homepage" linkPrefix:"https://">>
<<community-card-display-text-field "email" linkPrefix:"mailto:">>
<%if [all[tiddlers+shadows]tag[Community/Team]sort[title]] :filter[{!!leader}match<..currentTiddler>] +[count[]compare:number:gt[0]] %>
<div class="tc-community-card-field-text">
<span class="tc-community-card-field-text-name">leader</span>
<span class="tc-community-card-field-text-value">
<$list filter="[all[tiddlers+shadows]tag[Community/Team]sort[title]] :filter[{!!leader}match<..currentTiddler>]">
<$transclude $variable="community-card-pill-team" title=<<currentTiddler>>/>
</$list>
</span>
</div>
<%endif%>
<%if [all[tiddlers+shadows]tag[Community/Team]sort[title]] :filter[enlist{!!team}match<..currentTiddler>] +[count[]compare:number:gt[0]] %>
<div class="tc-community-card-field-text">
<span class="tc-community-card-field-text-name">member</span>
<span class="tc-community-card-field-text-value">
<$list filter="[all[tiddlers+shadows]tag[Community/Team]sort[title]] :filter[enlist{!!team}match<..currentTiddler>]">
<$transclude $variable="community-card-pill-team" title=<<currentTiddler>>/>
</$list>
</span>
</div>
<%endif%>
</div>
<div class="tc-community-card-body">
<$transclude $tiddler=<<currentTiddler>> $field="text" $mode="block"/>
</div>
</div>
</$let>
\end community-card-person
\procedure community-card-team(title)
<$let currentTiddler=<<title>>>
<div class="tc-community-card tc-community-card-team">
<$link to=<<currentTiddler>> class="tc-community-card-header-link">
<div class="tc-community-card-header">
<<community-card-display-transclusion fieldName:"icon" default:"$:/tiddlywiki/community/icons/team">>
<<community-card-display-text-field "title" showLabel:"no">>
</div>
</$link>
<div class="tc-community-card-info">
<div class="tc-community-card-field-text">
<span class="tc-community-card-field-text-name">leader</span>
<span class="tc-community-card-field-text-value">
<%if [<currentTiddler>has[leader]] %>
<$transclude $variable="community-card-pill-person" title={{!!leader}}/>
<%else%>
<$transclude $variable="community-card-vacancy"/>
<%endif%>
</span>
</div>
<div class="tc-community-card-field-text">
<span class="tc-community-card-field-text-name">team</span>
<span class="tc-community-card-field-text-value"><$transclude $variable="community-card-pill-stack-person" personFilter={{!!team}}/></span>
</div>
</div>
<div class="tc-community-card-body">
<$transclude $tiddler=<<currentTiddler>> $field="text" $mode="block"/>
</div>
</div>
</$let>
\end community-card-team
\procedure community-card-pill-person(title)
<$let currentTiddler=<<title>>>
<$link to=<<currentTiddler>> class="tc-community-card-pill">
<<community-card-display-jpeg-field "avatar" default:"$:/tiddlywiki/community/icons/person" mode="inline">>
<<community-card-display-text-field "title" showLabel:"no" mode:"inline">>
</$link>
</$let>
\end community-card-pill-person
\procedure community-card-pill-stack-person(personFilter:"[tag[Community/Person]]")
<div class="tc-community-card-pill-stack">
<$list filter=<<personFilter>>>
<$list-template>
<$transclude $variable="community-card-pill-person" title=<<currentTiddler>> mode="block"/>
</$list-template>
<$list-empty>
<$transclude $variable="community-card-vacancy"/>
</$list-empty>
</$list>
</div>
\end community-card-pill-stack-person
\procedure community-card-pill-team(title)
<$let currentTiddler=<<title>>>
<$link to=<<currentTiddler>> class="tc-community-card-pill">
<<community-card-display-transclusion fieldName:"icon" default:"$:/tiddlywiki/community/icons/team">>
<<community-card-display-text-field "title" showLabel:"no" mode:"inline">>
</$link>
</$let>
\end community-card-pill-team
\procedure community-card-vacancy()
<$link to="Vacant Positions" class="tc-community-card-pill tc-community-card-pill-vacancy">
<span class="tc-community-card-field-image tc-community-card-field-image-avatar">
{{$:/core/images/help}}
</span>
<span class="tc-community-card-field-text tc-community-card-field-text-title">
<span class="tc-community-card-field-text-value">
Vacant
</span>
</span>
</$link>
\end community-card-vacancy

View File

@@ -1,158 +0,0 @@
title: $:/tiddlywiki/community/cards/Styles
tags: $:/tags/Stylesheet
.tc-community-card {
display: flex;
flex-direction: column;
flex-wrap: wrap;
justify-content: center;
border-radius: 8px;
width: 100%;
margin-bottom: 8px;
background: <<colour community-card-background>>;
color: <<colour community-card-foreground>>;
fill: <<colour community-card-foreground>>;
box-shadow: 0 1px 3px 0 <<colour community-card-shadow>>, 0 0 0 1px <<colour community-card-shadow>>;
transition: box-shadow 0.3s ease,transform .3s ease;
}
.tc-community-card:hover {
box-shadow: 0 1px 6px 0 <<colour community-card-dark-shadow>>, 0 0 0 1px <<colour community-card-shadow>>;
transform: translateY(-2px);
}
.tc-community-card .tc-community-card-header-link {
background-color: <<colour community-card-header-background>>;
color: <<colour community-card-header-foreground>>;
border-top-left-radius: 8px;
border-top-right-radius: 8px;
}
.tc-community-card.tc-community-card-team .tc-community-card-header-link {
background: <<colour community-card-team-header-background>>;
color: <<colour community-card-team-header-foreground>>;
fill: <<colour community-card-team-header-foreground>>;
}
.tc-community-card .tc-community-card-header-link:hover {
text-decoration: none;
background-color: <<colour community-card-header-foreground>>;
color: <<colour community-card-header-background>>;
}
.tc-community-card-header {
margin: 0;
padding: 0.5em;
display: flex;
flex-direction: row;
flex-wrap: nowrap;
justify-content: flex-start;
align-items: center;
line-height: 0;
}
.tc-community-card-header .tc-community-card-field-text-title {
font-size: 1.5em;
font-weight: bold;
}
.tc-community-card-header .tc-community-card-field-image {
display: table-row;
width: auto;
max-width: 100%;
margin-right: 12px;
}
.tc-community-card-info {
display: table;
width: auto;
max-width: 100%;
padding: 8px;
margin: 0;
background-color: <<colour community-card-info-background>>;
color: <<colour community-card-info-foreground>>;
}
.tc-community-card-body {
padding: 0 8px;
}
.tc-community-card .tc-community-card-field-text {
display: table-row;
}
.tc-community-card .tc-community-card-field-text-name,
.tc-community-card .tc-community-card-field-text-value {
display: table-cell;
padding: 2px 6px 2px 0;
vertical-align: top;
}
.tc-community-card .tc-community-card-field-text-name {
color: <<colour community-card-field-name-foreground>>;
white-space: nowrap;
text-align: right;
padding-right: 8px;
}
.tc-community-card .tc-community-card-field-text-value {
word-break: break-word;
font-weight: bold;
width: 100%;
}
a.tc-community-card-pill {
display: inline-flex;
align-items: center;
gap: 4px;
width: auto;
min-width:0;
max-width: none;
align-self: auto;
font-size: 0.9em;
line-height: 1;
vertical-align: middle;
padding: 4px;
border-radius: 4px;
background: <<colour community-card-header-background>>;
color: <<colour community-card-header-foreground>>;
fill: <<colour community-card-header-foreground>>;
box-shadow: 0 1px 3px 0 <<colour community-card-shadow>>, 0 0 0 1px <<colour community-card-shadow>>;
transition: box-shadow 0.3s ease,transform .3s ease;
}
a.tc-community-card-pill.tc-community-card-pill-vacancy {
background: <<colour community-card-vacancy-header-background>>;
color: <<colour community-card-vacancy-header-foreground>>;
fill: <<colour community-card-vacancy-header-foreground>>;
}
a.tc-community-card-pill:hover {
text-decoration: none;
box-shadow: 0 1px 6px 0 <<colour community-card-dark-shadow>>, 0 0 0 1px <<colour community-card-shadow>>;
transform: translateY(-2px);
background: <<colour community-card-header-foreground>>;
color: <<colour community-card-header-background>>;
fill: <<colour community-card-header-background>>;
}
a.tc-community-card-pill .tc-community-card-field-image img,
a.tc-community-card-pill .tc-community-card-field-image svg {
width: 16px;
height: 16px;
vertical-align: middle;
display: inline-block;
}
a.tc-community-card-pill .tc-community-card-field-text {
display: inline;
}
.tc-community-card-pill-stack {
display: inline-flex;
flex-direction: column;
align-items: stretch;
gap: 4px;
margin: 0;
padding: 0;
}

View File

@@ -1,6 +0,0 @@
title: $:/tiddlywiki/community/cards/ViewTemplateBodyCascade
tags: $:/tags/ViewTemplateBodyFilter
list-before:
[tag[Community/Person]then[$:/tiddlywiki/community/cards/ViewTemplateBodyTemplatePerson]]
[tag[Community/Team]then[$:/tiddlywiki/community/cards/ViewTemplateBodyTemplateTeam]]

View File

@@ -1,3 +0,0 @@
title: $:/tiddlywiki/community/cards/ViewTemplateBodyTemplatePerson
<$transclude $variable="community-card-person" title=<<currentTiddler>>/>

View File

@@ -1,3 +0,0 @@
title: $:/tiddlywiki/community/cards/ViewTemplateBodyTemplateTeam
<$transclude $variable="community-card-team" title=<<currentTiddler>>/>

View File

@@ -1,7 +0,0 @@
title: $:/tiddlywiki/community/icons/person
tags: $:/tags/Image
\parameters (size:"22pt")
<svg width=<<size>> height=<<size>> viewBox="0 0 64 64">
<path d="M43.127,29.612c-0.879,-0.378 -1.452,-1.25 -1.452,-2.207c-0.006,-0.678 0.27,-1.33 0.761,-1.797c0.147,-0.141 0.29,-0.28 0.397,-0.393c0.753,-0.791 1.416,-1.663 1.978,-2.6c1.392,-2.318 2.126,-4.974 2.126,-7.677c0,-8.196 -6.744,-14.938 -14.938,-14.938c-0.945,0 -1.886,0.088 -2.813,0.266c-5.891,1.031 -10.578,5.586 -11.781,11.446c-1.105,5.016 0.454,10.264 4.118,13.865c0.495,0.469 0.78,1.118 0.792,1.799l0,0.012c0.008,0.966 -0.567,1.848 -1.453,2.23c-5.949,2.466 -10.698,7.172 -13.217,13.099c-1.772,4.059 -2.66,8.45 -2.607,12.88l0,3.192c0,2.858 2.351,5.211 5.212,5.211l43.5,0c2.859,0 5.212,-2.353 5.212,-5.211l-0,-3.225c0.053,-4.427 -0.837,-8.816 -2.611,-12.873c-2.523,-5.922 -7.274,-10.621 -13.224,-13.079Z" style="fill-rule:nonzero;"/>
</svg>

View File

@@ -1,7 +0,0 @@
title: $:/tiddlywiki/community/icons/project-team
tags: $:/tags/Image
\parameters (size:"22pt")
<svg width=<<size>> height=<<size>> viewBox="0 0 64 64">
<path d="M24.891,49.399l-3.521,0c-1.398,0 -2.547,-1.15 -2.547,-2.547l0,-1.56c-0.026,-2.165 0.408,-4.311 1.274,-6.295c1.231,-2.897 3.552,-5.197 6.46,-6.402c0.433,-0.187 0.714,-0.618 0.71,-1.09l0,-0.006c-0.006,-0.333 -0.145,-0.65 -0.387,-0.879c-1.791,-1.76 -2.553,-4.325 -2.013,-6.777c0.588,-2.864 2.879,-5.09 5.758,-5.594c0.453,-0.087 0.913,-0.13 1.375,-0.13c4.005,0 7.301,3.295 7.301,7.301c0,1.321 -0.359,2.619 -1.039,3.752c-0.275,0.458 -0.599,0.884 -0.967,1.271c-0.052,0.055 -0.122,0.123 -0.194,0.192c-0.24,0.228 -0.375,0.547 -0.372,0.878c0,0.468 0.28,0.894 0.71,1.079c2.908,1.201 5.23,3.498 6.463,6.392c0.815,1.865 1.248,3.872 1.276,5.904c-0.179,0.006 -0.351,0.007 -0.514,0.003c-0.556,-0.016 -1.375,-0.294 -2.288,-0.512c-1.295,-0.308 -2.719,-0.543 -4.01,-0.396l-0.013,0.001c-1.056,0.128 -2.116,0.325 -3.097,0.76c-0.385,0.171 -1.216,0.753 -1.446,0.916c-1.157,0.297 -2.564,0.475 -3.797,0.312c-0.713,-0.094 -1.402,-0.225 -1.703,-0.778c-0.207,-0.382 -0.181,-0.896 -0.031,-1.565c0.068,-0.3 0.11,-0.593 0.118,-0.842l-0.106,-0.887l-0.212,-0.491l-0.258,-0.36l-0.669,-0.514l-0.832,-0.231l-0.491,0.017l-0.459,0.12l-0.417,0.211l-0.415,0.342l-0.546,0.802l-0.033,0.067c-1.174,2.499 -0.945,4.643 0.013,6.317c0.251,0.437 0.56,0.845 0.919,1.219Zm22.984,-4.722c-0.052,-2.344 -0.566,-4.656 -1.514,-6.805c-1.232,-2.86 -3.339,-5.257 -6.018,-6.845c0.955,-0.816 2.033,-1.473 3.195,-1.949c0.434,-0.187 0.715,-0.618 0.71,-1.09l-0,-0.006c-0.005,-0.333 -0.144,-0.651 -0.386,-0.88c-1.791,-1.76 -2.553,-4.324 -2.013,-6.776c0.587,-2.864 2.878,-5.09 5.758,-5.594c0.453,-0.087 0.913,-0.131 1.375,-0.131c4.005,0 7.3,3.296 7.3,7.301c-0,1.322 -0.359,2.619 -1.038,3.753c-0.276,0.457 -0.6,0.883 -0.968,1.27c-0.052,0.055 -0.121,0.123 -0.194,0.192c-0.24,0.229 -0.375,0.547 -0.372,0.878c-0,0.468 0.28,0.894 0.71,1.079c2.908,1.201 5.229,3.498 6.462,6.392c0.756,1.728 1.184,3.578 1.264,5.458c-0.577,-0.341 -1.293,-0.373 -1.904,-0.07c-0.961,0.475 -1.861,1.117 -2.911,1.371c-0.49,-0.133 -0.983,-0.245 -1.485,-0.308c-0.253,-0.326 -0.536,-0.66 -0.84,-0.911l-0.813,-0.51l-0.752,-0.225c-0.327,-0.051 -0.662,-0.021 -0.974,0.089l-0.67,0.321l-0.569,0.448c-0.403,0.393 -0.733,0.911 -0.979,1.569c-0.202,0.54 -0.344,1.222 -0.492,2.014c-0.244,-0.027 -0.49,-0.047 -0.737,-0.058c-0.333,-0.02 -0.725,-0.006 -1.145,0.023Zm-24.215,-13.651c-2.683,1.591 -4.793,3.994 -6.024,6.861c-1.026,2.332 -1.542,4.857 -1.513,7.405l0,0.59l-11.735,0c-1.397,0 -2.547,-1.15 -2.547,-2.547l0,-1.561c-0.026,-2.165 0.409,-4.31 1.274,-6.295c1.231,-2.897 3.553,-5.197 6.46,-6.401c0.434,-0.187 0.715,-0.618 0.71,-1.09l0,-0.006c-0.005,-0.333 -0.144,-0.651 -0.386,-0.88c-1.791,-1.76 -2.553,-4.324 -2.013,-6.776c0.588,-2.864 2.879,-5.09 5.758,-5.594c0.453,-0.087 0.914,-0.131 1.375,-0.131c4.005,0 7.301,3.296 7.301,7.301c0,1.322 -0.359,2.619 -1.039,3.753c-0.275,0.457 -0.6,0.883 -0.967,1.27c-0.052,0.055 -0.122,0.123 -0.194,0.192c-0.24,0.228 -0.375,0.547 -0.372,0.878c0,0.468 0.28,0.894 0.71,1.079c1.164,0.476 2.246,1.135 3.202,1.952Zm29.027,33.111c-1.417,-0.04 -2.04,-0.037 -2.761,-1.223l-0.563,0.016c-0.654,-0.029 -0.381,-0.016 -0.818,-0.038c-0.73,-0.028 -0.613,-0.722 -0.742,-1.089c-0.205,-1.244 0.272,-2.494 0.257,-3.739c-0.005,-0.442 -0.63,-2.005 -0.854,-2.564c-0.7,0.131 -1.404,0.157 -2.114,0.192c-1.637,-0.004 -3.263,-0.205 -4.878,-0.459c-0.314,1.299 -1.249,3.118 -0.476,4.439c0.938,1.366 1.596,1.745 2.617,1.827c1.02,0.082 1.251,1.234 1.004,1.646c-0.219,0.284 -0.603,0.336 -0.929,0.405l-0.653,0.03c-0.513,-0.017 -0.973,-0.155 -1.43,-0.369c-0.765,-0.427 -1.554,-1.314 -2.141,-1.951c0.137,0.254 0.218,0.751 0.095,0.982c-0.347,0.491 -1.847,0.488 -2.534,0.183c-0.78,-0.347 -2.665,-2.781 -2.957,-4.604c0.776,-1.467 1.905,-2.744 2.477,-4.341c-1.246,-0.795 -1.913,-2.089 -1.827,-3.555l0.032,-0.17c-1.226,0.23 -0.59,0.144 -1.909,0.244c-4.2,-0.013 -7.893,-2.86 -5.813,-7.286c0.135,-0.262 0.263,-0.5 0.493,-0.386c0.184,0.091 0.157,0.457 0.065,0.863c-1.189,5.288 4.621,5.329 8.192,4.35c0.355,-0.097 1.06,-0.751 1.548,-0.968c0.798,-0.354 1.665,-0.498 2.524,-0.602c2.139,-0.244 4.709,0.883 6.015,0.92c1.306,0.037 3.164,-0.313 4.305,-0.239c0.827,0.037 1.64,0.187 2.438,0.4c0.517,-2.519 0.554,-4.374 1.779,-4.804c0.719,0.113 1.273,1.093 1.683,1.617l0.002,-0c0.835,-0.033 1.63,0.178 2.42,0.414c1.431,-0.203 2.631,-1.007 3.895,-1.632c-0.004,0.02 -0.025,0.027 -0.037,0.04c-1.244,1.005 -1.417,2.706 -1.271,4.278c0.054,0.816 -0.176,1.702 -0.461,2.538c-0.534,1.361 -1.564,2.796 -2.759,2.722c-0.452,-0.014 -0.715,-0.27 -1.051,-0.543c-0.065,0.553 -0.321,1.047 -0.568,1.536c-0.57,1.086 -2.06,1.564 -3.44,2.723c-1.379,1.159 0.442,5.297 0.883,6.052c0.442,0.754 1.674,1.03 1.196,1.71c-0.147,0.225 -0.37,0.305 -0.609,0.393l-0.325,0.042Zm-15.735,-3.096l0.206,0.06c0.258,-0.115 0.778,0.064 1.054,0.151c-0.508,-0.563 -1.273,-1.389 -1.824,-1.91c-0.181,-0.631 -0.103,-1.266 -0.065,-1.91l0.008,-0.053c-0.217,0.515 -0.493,1.016 -0.641,1.559c-0.173,0.732 0.771,1.522 1.137,1.975l0.125,0.128Z"/>
</svg>

View File

@@ -1,9 +0,0 @@
title: $:/tiddlywiki/community/icons/team
tags: $:/tags/Image
\parameters (size:"22pt")
<svg width=<<size>> height=<<size>> viewBox="0 0 64 64">
<path d="M37.439,32.592c-0.43,-0.185 -0.71,-0.611 -0.71,-1.079c-0.003,-0.331 0.132,-0.65 0.372,-0.878c0.072,-0.069 0.142,-0.137 0.194,-0.192c0.368,-0.387 0.692,-0.813 0.967,-1.271c0.68,-1.133 1.039,-2.431 1.039,-3.752c-0,-4.006 -3.296,-7.301 -7.301,-7.301c-0.462,-0 -0.922,0.043 -1.375,0.13c-2.879,0.504 -5.17,2.73 -5.758,5.594c-0.54,2.452 0.222,5.017 2.013,6.777c0.242,0.229 0.381,0.546 0.387,0.879l-0,0.006c0.004,0.472 -0.277,0.903 -0.71,1.09c-2.908,1.205 -5.229,3.505 -6.46,6.402c-0.866,1.984 -1.3,4.13 -1.274,6.295l-0,1.56c-0,1.397 1.149,2.547 2.547,2.547c-0,-0 0,-0 0,-0l21.261,-0c1.397,-0 2.547,-1.15 2.547,-2.547l-0,-1.576c0.026,-2.164 -0.409,-4.309 -1.276,-6.292c-1.233,-2.894 -3.555,-5.191 -6.463,-6.392Z" style="fill-rule:nonzero;"/>
<path d="M60.882,35.466c-1.233,-2.894 -3.554,-5.191 -6.462,-6.392c-0.43,-0.185 -0.71,-0.611 -0.71,-1.079c-0.003,-0.331 0.132,-0.649 0.372,-0.878c0.073,-0.069 0.142,-0.137 0.194,-0.192c0.368,-0.387 0.692,-0.813 0.968,-1.27c0.679,-1.134 1.038,-2.431 1.038,-3.753c0,-4.005 -3.295,-7.301 -7.3,-7.301c-0.462,0 -0.922,0.044 -1.375,0.131c-2.88,0.504 -5.171,2.73 -5.758,5.594c-0.54,2.452 0.222,5.016 2.013,6.776c0.242,0.229 0.381,0.547 0.386,0.88l-0,0.006c0.005,0.472 -0.276,0.903 -0.71,1.09c-1.162,0.476 -2.24,1.133 -3.195,1.949c2.679,1.588 4.786,3.985 6.018,6.845c1.029,2.332 1.546,4.857 1.517,7.405l-0,0.605l11.734,-0c1.397,-0 2.547,-1.15 2.547,-2.547l-0,-1.576c0.026,-2.165 -0.409,-4.31 -1.277,-6.293Z" style="fill-rule:nonzero;"/>
<path d="M23.66,31.026c-0.956,-0.817 -2.038,-1.476 -3.202,-1.952c-0.43,-0.185 -0.71,-0.611 -0.71,-1.079c-0.003,-0.331 0.132,-0.65 0.372,-0.878c0.072,-0.069 0.142,-0.137 0.194,-0.192c0.367,-0.387 0.692,-0.813 0.967,-1.27c0.68,-1.134 1.039,-2.431 1.039,-3.753c-0,-4.005 -3.296,-7.301 -7.301,-7.301c-0.461,0 -0.922,0.044 -1.375,0.131c-2.879,0.504 -5.17,2.73 -5.758,5.594c-0.54,2.452 0.222,5.016 2.013,6.776c0.242,0.229 0.381,0.547 0.386,0.88l0,0.006c0.005,0.472 -0.276,0.903 -0.71,1.09c-2.907,1.204 -5.229,3.504 -6.46,6.401c-0.865,1.985 -1.3,4.13 -1.274,6.295c0,0 0,1.561 0,1.561c0,1.397 1.15,2.547 2.547,2.547c-0,-0 11.735,-0 11.735,-0l0,-0.59c-0.029,-2.548 0.487,-5.073 1.513,-7.405c1.231,-2.867 3.341,-5.27 6.024,-6.861Z" style="fill-rule:nonzero;"/>
</svg>

View File

@@ -4,4 +4,4 @@ TiddlyWiki incorporates code from these fine OpenSource projects:
* [[The Stanford Javascript Crypto Library|http://bitwiseshiftleft.github.io/sjcl/]]
* [[The Jasmine JavaScript Test Framework|https://jasmine.github.io/]]
* [[modern-normalize by Sindre Sorhus|https://github.com/sindresorhus/modern-normalize]]
* [[Normalize.css by Nicolas Gallagher|http://necolas.github.io/normalize.css/]]

View File

@@ -70,7 +70,7 @@ alert-border: <<colour flexoki-ye>>
alert-highlight: <<colour flexoki-re>>
alert-muted-foreground: <<colour flexoki-ye>>
background: #100F0F
blockquote-bar: <<colour flexoki-ma>>
blockquote-bar: <<colour flexoki-ma-2>>
button-background: <<colour flexoki-bg-2>>
button-foreground: <<colour flexoki-paper>>
button-border: <<colour flexoki-600>>
@@ -106,7 +106,7 @@ foreground: #CECDC3
highlight-background: <<colour flexoki-yellow-900>>
highlight-foreground: inherit
menubar-background: <<colour primary>>
menubar-foreground: <<colour flexoki-999>>
menubar-foreground: <<colour flexoki-paper>>
message-background: <<colour background>>
message-border: <<colour foreground>>
message-foreground: <<colour foreground>>

View File

@@ -7,7 +7,7 @@ caption: {{$:/language/SideBar/Tools/Caption}}
\procedure lingo-base() $:/language/ControlPanel/
\function config-title() [[$:/config/PageControlButtons/Visibility/$(listItem)$]substitute[]]
<<lingo Basics/Version/Prompt>><span class="tc-tiny-gap-left"><<version>></span>
<<lingo Basics/Version/Prompt>> <<version>>
<$let tv-config-toolbar-icons="yes"
tv-config-toolbar-text="yes"

View File

@@ -1,58 +1,55 @@
title: $:/core/macros/colour-picker
tags: $:/tags/Macro
\define colour-picker-update-recent()
\procedure colour-picker-update-recent()
<$action-listops
$tiddler="$:/config/ColourPicker/Recent"
$subfilter="$(colour-picker-value)$ [list[$:/config/ColourPicker/Recent]remove[$(colour-picker-value)$]] +[limit[8]]"
$subfilter="[<colour-picker-value>] [list[$:/config/ColourPicker/Recent]remove<colour-picker-value>] +[limit[8]]"
/>
\end
\define colour-picker-inner(actions)
<$button tag="a" tooltip="""$(colour-picker-value)$""">
$(colour-picker-update-recent)$
<$transclude $variable="__actions__"/>
<span style="display:inline-block; background-color: $(colour-picker-value)$; width: 100%; height: 100%; border-radius: 50%;"/>
\procedure colour-picker-inner(actions)
<$button tag="a" tooltip=<<colour-picker-value>>>
<<colour-picker-update-recent>>
<$transclude $variable="actions"/>
<span style.display="inline-block" style.backgroundColor=<<colour-picker-value>> style.width="100%" style.height="100%" style.borderRadius="50%"/>
</$button>
\end
\define colour-picker-recent-inner(actions)
\whitespace trim
<$set name="colour-picker-value" value="$(recentColour)$">
<$macrocall $name="colour-picker-inner" actions=<<__actions__>>/>
\procedure colour-picker-recent-inner(actions)
<$set name="colour-picker-value" value=<<recentColour>>>
<$transclude $variable="colour-picker-inner" actions=<<actions>>/>
</$set>
\end
\define colour-picker-recent(actions)
\whitespace trim
\procedure colour-picker-recent(actions)
{{$:/language/ColourPicker/Recent}}<$list filter="[list[$:/config/ColourPicker/Recent]]" variable="recentColour">
&#32;
<$macrocall $name="colour-picker-recent-inner" actions=<<__actions__>>/>
<$transclude $variable="colour-picker-recent-inner" actions=<<actions>>/>
</$list>
\end
\define colour-picker(actions)
\whitespace trim
\procedure colour-picker(actions)
<div class="tc-colour-chooser">
<$macrocall $name="colour-picker-recent" actions=<<__actions__>>/>
<$transclude $variable="colour-picker-recent" actions=<<actions>>/>
---
<$list filter="LightPink Pink Crimson LavenderBlush PaleVioletRed HotPink DeepPink MediumVioletRed Orchid Thistle Plum Violet Magenta Fuchsia DarkMagenta Purple MediumOrchid DarkViolet DarkOrchid Indigo BlueViolet MediumPurple MediumSlateBlue SlateBlue DarkSlateBlue Lavender GhostWhite Blue MediumBlue MidnightBlue DarkBlue Navy RoyalBlue CornflowerBlue LightSteelBlue LightSlateGrey SlateGrey DodgerBlue AliceBlue SteelBlue LightSkyBlue SkyBlue DeepSkyBlue LightBlue PowderBlue CadetBlue Azure LightCyan PaleTurquoise Cyan Aqua DarkTurquoise DarkSlateGrey DarkCyan Teal MediumTurquoise LightSeaGreen Turquoise Aquamarine MediumAquamarine MediumSpringGreen MintCream SpringGreen MediumSeaGreen SeaGreen Honeydew LightGreen PaleGreen DarkSeaGreen LimeGreen Lime ForestGreen Green DarkGreen Chartreuse LawnGreen GreenYellow DarkOliveGreen YellowGreen OliveDrab Beige LightGoldenrodYellow Ivory LightYellow Yellow Olive DarkKhaki LemonChiffon PaleGoldenrod Khaki Gold Cornsilk Goldenrod DarkGoldenrod FloralWhite OldLace Wheat Moccasin Orange PapayaWhip BlanchedAlmond NavajoWhite AntiqueWhite Tan BurlyWood Bisque DarkOrange Linen Peru PeachPuff SandyBrown Chocolate SaddleBrown Seashell Sienna LightSalmon Coral OrangeRed DarkSalmon Tomato MistyRose Salmon Snow LightCoral RosyBrown IndianRed Red Brown FireBrick DarkRed Maroon White WhiteSmoke Gainsboro LightGrey Silver DarkGrey Grey DimGrey Black" variable="colour-picker-value">
&#32;
<$macrocall $name="colour-picker-inner" actions=<<__actions__>>/>
<$transclude $variable="colour-picker-inner" actions=<<actions>>/>
</$list>
---
<$edit-text tiddler="$:/config/ColourPicker/New" tag="input" default="" placeholder=""/>
&#32;
<$edit-text tiddler="$:/config/ColourPicker/New" tag="input" default="" placeholder="" class="tc-tiny-gap-right"/>
<$edit-text tiddler="$:/config/ColourPicker/New" type="color" tag="input"/>
<$set name="colour-picker-value" value={{$:/config/ColourPicker/New}}>
<$macrocall $name="colour-picker-inner" actions=<<__actions__>>/>
<%if [{$:/config/ColourPicker/New}!is[blank]] %>
<$transclude $variable="colour-picker-inner" actions=<<actions>>/>
<%endif%>
</$set>
</div>

View File

@@ -1,7 +1,7 @@
title: $:/core/macros/dumpvariables
tags: $:/tags/Macro
\define dumpvariables()
\procedure dumpvariables()
\whitespace trim
<ul>
<$list filter="[variables[]]" variable="varname">

View File

@@ -1,39 +1,36 @@
created: 20170715180840889
modified: 20170715180914005
tags: $:/tags/Macro
title: $:/core/macros/image-picker
type: text/vnd.tiddlywiki
\define image-picker-thumbnail(actions)
<$button tag="a" tooltip="""$(imageTitle)$"""><$transclude $variable="__actions__"/><$transclude tiddler=<<imageTitle>>/></$button>
\procedure image-picker-thumbnail(actions)
<$button tag="a" tooltip=<<imageTitle>>><$transclude $variable="actions"/><$transclude tiddler=<<imageTitle>>/></$button>
\end
\define image-picker-list(filter,actions)
\procedure image-picker-list(filter,actions)
\whitespace trim
<$list filter="""$filter$""" variable="imageTitle">
<$macrocall $name="image-picker-thumbnail" actions=<<__actions__>>/>
<$list filter=<<filter>> variable="imageTitle">
<$transclude $variable="image-picker-thumbnail" actions=<<actions>>/>
&#32;
</$list>
\end
\define image-picker(actions,filter:"[all[shadows+tiddlers]is[image]] -[type[application/pdf]] +[!has[draft.of]$subfilter$sort[title]]",subfilter:"")
\procedure image-picker(actions,filter:"[all[shadows+tiddlers]is[image]] -[type[application/pdf]] +[!has[draft.of]$subfilter$sort[title]]",subfilter:"")
\whitespace trim
<div class="tc-image-chooser">
<$vars state-system=<<qualify "$:/state/image-picker/system">>>
<$let state-system=<<qualify "$:/state/image-picker/system">> tv-filter={{{ [<filter>search-replace[$subfilter$],<subfilter>] }}}>
<$checkbox tiddler=<<state-system>> field="text" checked="show" unchecked="hide" default="hide">
&#32;
{{$:/language/SystemTiddlers/Include/Prompt}}
<span class="tc-tiny-gap-left">{{$:/language/SystemTiddlers/Include/Prompt}}</span>
</$checkbox>
<$reveal state=<<state-system>> type="match" text="hide" default="hide" tag="div">
<$macrocall $name="image-picker-list" filter="""$filter$ +[!is[system]]""" actions=<<__actions__>>/>
<$transclude $variable="image-picker-list" filter=`$(tv-filter)$ +[!is[system]]` actions=<<actions>>/>
</$reveal>
<$reveal state=<<state-system>> type="nomatch" text="hide" default="hide" tag="div">
<$macrocall $name="image-picker-list" filter="""$filter$""" actions=<<__actions__>>/>
<$transclude $variable="image-picker-list" filter=<<tv-filter>> actions=<<actions>>/>
</$reveal>
</$vars>
</$let>
</div>
\end
\define image-picker-include-tagged-images(actions)
<$macrocall $name="image-picker" filter="[all[shadows+tiddlers]is[image]] [all[shadows+tiddlers]tag[$:/tags/Image]] -[type[application/pdf]] +[!has[draft.of]sort[title]]" actions=<<__actions__>>/>
\procedure image-picker-include-tagged-images(actions)
<$transclude $variable="image-picker" filter="[all[shadows+tiddlers]is[image]] [all[shadows+tiddlers]tag[$:/tags/Image]] -[type[application/pdf]] +[!has[draft.of]sort[title]]" actions=<<actions>>/>
\end

View File

@@ -1,14 +1,18 @@
title: $:/core/macros/list
tags: $:/tags/Macro
\define list-links(filter,type:"ul",subtype:"li",class:"",emptyMessage,field:"caption")
\procedure list-links-draggable-drop-actions()
<$action-listops $tiddler=<<targetTiddler>> $field=<<targetField>> $subfilter="+[insertbefore<actionTiddler>,<currentTiddler>]"/>
\end
\whitespace trim
<$genesis $type=<<__type__>> class=<<__class__>>>
<$list filter=<<__filter__>> emptyMessage=<<__emptyMessage__>>>
<$genesis $type=<<__subtype__>>>
\procedure list-links(filter,type:"ul",subtype:"li",class:"",emptyMessage,field:"caption")
<$genesis $type=<<type>> class=<<class>>>
<$list filter=<<filter>> emptyMessage=<<emptyMessage>>>
<$genesis $type=<<subtype>>>
<$link to={{!!title}}>
<$let tv-wikilinks="no">
<$transclude field=<<__field__>>>
<$transclude field=<<field>>>
<$view field="title"/>
</$transclude>
</$let>
@@ -18,24 +22,19 @@ tags: $:/tags/Macro
</$genesis>
\end
\define list-links-draggable-drop-actions()
<$action-listops $tiddler=<<targetTiddler>> $field=<<targetField>> $subfilter="+[insertbefore<actionTiddler>,<currentTiddler>]"/>
\end
\define list-links-draggable(tiddler,field:"list",emptyMessage,type:"ul",subtype:"li",class:"",itemTemplate)
\whitespace trim
\procedure list-links-draggable(tiddler,field:"list",emptyMessage,type:"ul",subtype:"li",class:"",itemTemplate)
<span class="tc-links-draggable-list">
<$vars targetTiddler="""$tiddler$""" targetField="""$field$""">
<$genesis $type=<<__type__>> class="$class$">
<$list filter="[list[$tiddler$!!$field$]]" emptyMessage=<<__emptyMessage__>>>
<$let targetTiddler=<<tiddler>> targetField=<<field>>>
<$genesis $type=<<type>> class=<<class>>>
<$list filter="[<tiddler>get<field>enlist-input[]]" emptyMessage=<<emptyMessage>>>
<$droppable
actions=<<list-links-draggable-drop-actions>>
tag="""$subtype$"""
tag=<<subtype>>
enable=<<tv-enable-drag-and-drop>>
>
<div class="tc-droppable-placeholder"/>
<div>
<$transclude tiddler="""$itemTemplate$""">
<$transclude tiddler=<<itemTemplate>>>
<$link to={{!!title}}>
<$let tv-wikilinks="no">
<$transclude field="caption">
@@ -60,52 +59,54 @@ tags: $:/tags/Macro
</$droppable>
</$tiddler>
</$genesis>
</$vars>
</$let>
</span>
\end
\define list-tagged-draggable-drop-actions(tag)
\whitespace trim
\procedure list-tagged-draggable-drop-actions(tag)
<!-- Save the current ordering of the tiddlers with this tag -->
<$set name="order" filter="[<__tag__>tagging[]]">
<$set name="order" filter="[<tag>tagging[]]">
<!-- Remove any list-after or list-before fields from the tiddlers with this tag -->
<$list filter="[<__tag__>tagging[]]">
<$list filter="[<tag>tagging[]]">
<$action-deletefield $field="list-before"/>
<$action-deletefield $field="list-after"/>
</$list>
<!-- Save the new order to the Tag Tiddler -->
<$action-listops $tiddler=<<__tag__>> $field="list" $filter="+[enlist<order>] +[insertbefore<actionTiddler>,<currentTiddler>]"/>
<$action-listops $tiddler=<<tag>> $field="list" $filter="+[enlist<order>] +[insertbefore<actionTiddler>,<currentTiddler>]"/>
<!-- Make sure the newly added item has the right tag -->
<!-- Removing this line makes dragging tags within the dropdown work as intended -->
<!--<$action-listops $tiddler=<<actionTiddler>> $tags=<<__tag__>>/>-->
<!--<$action-listops $tiddler=<<actionTiddler>> $tags=<<tag>>/>-->
<!-- Using the following 5 lines as replacement makes dragging titles from outside into the dropdown apply the tag -->
<$list filter="[<actionTiddler>!contains:tags<__tag__>]">
<$list filter="[<actionTiddler>!contains:tags<tag>]">
<$fieldmangler tiddler=<<actionTiddler>>>
<$action-sendmessage $message="tm-add-tag" $param=<<__tag__>>/>
<$action-sendmessage $message="tm-add-tag" $param=<<tag>>/>
</$fieldmangler>
</$list>
</$set>
\end
\define list-tagged-draggable(tag,subFilter,emptyMessage,itemTemplate,elementTag:"div",storyview:"")
\whitespace trim
\procedure list-tagged-draggable(tag,subFilter,emptyMessage,itemTemplate,elementTag:"div",storyview:"")
<span class="tc-tagged-draggable-list">
<$set name="tag" value=<<__tag__>>>
<$set name="tag" value=<<tag>>>
<$list
filter="[<__tag__>tagging[]$subFilter$]"
emptyMessage=<<__emptyMessage__>>
storyview=<<__storyview__>>
filter=`[<tag>tagging[]$(subFilter)$]`
emptyMessage=<<emptyMessage>>
storyview=<<storyview>>
>
<$genesis $type=<<__elementTag__>> class="tc-menu-list-item">
<$genesis $type=<<elementTag>> class="tc-menu-list-item">
<$droppable
actions="""<$macrocall $name="list-tagged-draggable-drop-actions" tag=<<__tag__>>/>"""
actions="""<$macrocall $name="list-tagged-draggable-drop-actions" tag=<<tag>>/>"""
enable=<<tv-enable-drag-and-drop>>
>
<$genesis $type=<<__elementTag__>> class="tc-droppable-placeholder"/>
<$genesis $type=<<__elementTag__>>>
<$transclude tiddler="""$itemTemplate$""">
<$genesis $type=<<elementTag>> class="tc-droppable-placeholder"/>
<$genesis $type=<<elementTag>>>
<$transclude tiddler=<<itemTemplate>>>
<$link to={{!!title}}>
<$view field="title"/>
<$let tv-wikilinks="no">
<$transclude field="caption">
<$view field="title"/>
</$transclude>
</$let>
</$link>
</$transclude>
</$genesis>
@@ -114,11 +115,11 @@ tags: $:/tags/Macro
</$list>
<$tiddler tiddler="">
<$droppable
actions="""<$macrocall $name="list-tagged-draggable-drop-actions" tag=<<__tag__>>/>"""
actions="""<$macrocall $name="list-tagged-draggable-drop-actions" tag=<<tag>>/>"""
enable=<<tv-enable-drag-and-drop>>
>
<$genesis $type=<<__elementTag__>> class="tc-droppable-placeholder"/>
<$genesis $type=<<__elementTag__>> style="height:0.5em;"/>
<$genesis $type=<<elementTag>> class="tc-droppable-placeholder"/>
<$genesis $type=<<elementTag>> style="height:0.5em;"/>
</$droppable>
</$tiddler>
</$set>

View File

@@ -1,28 +1,28 @@
title: $:/core/macros/translink
tags: $:/tags/Macro
\define translink(title,mode:"block")
\procedure translink(title,mode:"block")
\whitespace trim
<$list filter="[<__mode__>match[block]]">
<%if [<mode>match[block]] %>
<div class="tc-translink">
<div>
<$link to="""$title$""">
<h1><$text text="""$title$"""/></h1>
<$link to=<<title>>>
<h1><$text text=<<title>>/></h1>
</$link>
<$transclude tiddler="""$title$""" mode="block">
<$set name="currentTiddler" value="""$title$"""><$transclude tiddler="$:/language/MissingTiddler/Hint"/></$set>
<$transclude tiddler=<<title>> mode="block">
<$set name="currentTiddler" value=<<title>>><$transclude tiddler="$:/language/MissingTiddler/Hint"/></$set>
</$transclude>
</div>
</div>
</$list>
<$list filter="[<__mode__>match[inline]]">
<%endif%>
<%if [<mode>match[inline]] %>
<span class="tc-translink">
<$link to="""$title$""">
<$text text="""$title$"""/>
<$link to=<<title>> class="tc-tiny-gap-right">
<$text text=<<title>>/>
</$link>
&#32;(<$transclude tiddler="""$title$""" mode="inline">
<$set name="currentTiddler" value="""$title$"""><$transclude tiddler="$:/language/MissingTiddler/Hint"/></$set>
(<$transclude tiddler=<<title>> mode="inline">
<$set name="currentTiddler" value=<<title>>><$transclude tiddler="$:/language/MissingTiddler/Hint"/></$set>
</$transclude>)
</span>
</$list>
<%endif%>
\end

View File

@@ -1,62 +1,58 @@
title: $:/core/macros/tree
tags: $:/tags/Macro
\define leaf-link(full-title,chunk,separator: "/")
<$link to=<<__full-title__>>><$text text=<<__chunk__>>/></$link>
\procedure leaf-link(full-title,chunk,separator: "/")
<$link to=<<full-title>>><$text text=<<chunk>>/></$link>
\end
\define leaf-node(prefix,chunk)
\whitespace trim
\procedure leaf-node(prefix,chunk)
<li>
<$list filter="[<__prefix__>addsuffix<__chunk__>is[shadow]] [<__prefix__>addsuffix<__chunk__>is[tiddler]]" variable="full-title">
<$list filter="[<full-title>removeprefix<__prefix__>]" variable="chunk">
<span>{{$:/core/images/file}}</span>&#32;<$macrocall $name="leaf-link" full-title=<<full-title>> chunk=<<chunk>>/>
<$list filter="[<prefix>addsuffix<chunk>is[shadow]] [<prefix>addsuffix<chunk>is[tiddler]]" variable="full-title">
<$list filter="[<full-title>removeprefix<prefix>]" variable="chunk">
<span class="tc-tiny-gap-right">{{$:/core/images/file}}</span><$transclude $variable="leaf-link" full-title=<<full-title>> chunk=<<chunk>>/>
</$list>
</$list>
</li>
\end
\define branch-node(prefix,chunk,separator: "/")
\whitespace trim
\procedure branch-node(prefix,chunk,separator: "/")
<li>
<$set name="reveal-state" value={{{ [[$:/state/tree/]addsuffix<__prefix__>addsuffix<__chunk__>] }}}>
<$set name="reveal-state" value={{{ [[$:/state/tree/]addsuffix<prefix>addsuffix<chunk>] }}}>
<$reveal type="nomatch" stateTitle=<<reveal-state>> text="show">
<$button setTitle=<<reveal-state>> setTo="show" class="tc-btn-invisible">
{{$:/core/images/folder}}&#32;<$text text=<<__chunk__>>/>
{{$:/core/images/folder}}&#32;<$text text=<<chunk>>/>
</$button>
</$reveal>
<$reveal type="match" stateTitle=<<reveal-state>> text="show">
<$button setTitle=<<reveal-state>> setTo="hide" class="tc-btn-invisible">
{{$:/core/images/folder}}&#32;<$text text=<<__chunk__>>/>
{{$:/core/images/folder}}&#32;<$text text=<<chunk>>/>
</$button>
</$reveal>
&#32;
<span>(<$count filter="[all[shadows+tiddlers]removeprefix<__prefix__>removeprefix<__chunk__>] -[<__prefix__>addsuffix<__chunk__>]"/>)</span>
<span class="tc-tiny-gap-left">(<$count filter="[all[shadows+tiddlers]removeprefix<prefix>removeprefix<chunk>] -[<prefix>addsuffix<chunk>]"/>)</span>
<$reveal type="match" stateTitle=<<reveal-state>> text="show">
<$macrocall $name="tree-node" prefix={{{ [<__prefix__>addsuffix<__chunk__>] }}} separator=<<__separator__>>/>
<$transclude $variable="tree-node" prefix={{{ [<prefix>addsuffix<chunk>] }}} separator=<<separator>>/>
</$reveal>
</$set>
</li>
\end
\define tree-node(prefix,separator: "/")
\whitespace trim
\procedure tree-node(prefix,separator: "/")
<ol>
<$list filter="[all[shadows+tiddlers]removeprefix<__prefix__>splitbefore<__separator__>sort[]!suffix<__separator__>]" variable="chunk">
<$macrocall $name="leaf-node" prefix=<<__prefix__>> chunk=<<chunk>> separator=<<__separator__>>/>
<$list filter="[all[shadows+tiddlers]removeprefix<prefix>splitbefore<separator>sort[]!suffix<separator>]" variable="chunk">
<$transclude $variable="leaf-node" prefix=<<prefix>> chunk=<<chunk>> separator=<<separator>>/>
</$list>
<$list filter="[all[shadows+tiddlers]removeprefix<__prefix__>splitbefore<__separator__>sort[]suffix<__separator__>]" variable="chunk">
<$macrocall $name="branch-node" prefix=<<__prefix__>> chunk=<<chunk>> separator=<<__separator__>>/>
<$list filter="[all[shadows+tiddlers]removeprefix<prefix>splitbefore<separator>sort[]suffix<separator>]" variable="chunk">
<$transclude $variable="branch-node" prefix=<<prefix>> chunk=<<chunk>> separator=<<separator>>/>
</$list>
</ol>
\end
\define tree(prefix: "$:/",separator: "/")
\whitespace trim
\procedure tree(prefix: "$:/",separator: "/")
<div class="tc-tree">
<span><$text text=<<__prefix__>>/></span>
<span><$text text=<<prefix>>/></span>
<div>
<$macrocall $name="tree-node" prefix=<<__prefix__>> separator=<<__separator__>>/>
<$transclude $variable="tree-node" prefix=<<prefix>> separator=<<separator>>/>
</div>
</div>
\end

View File

@@ -11,7 +11,6 @@ type: text/vnd.tiddlywiki
# Move the latest release note from the prerelease edition into the tw5.com edition
# Adjust the release date and the ''released'' field of the latest release tiddler (eg, [[Release 5.1.3]])
# Also adjust the github.com comparison link to point to the tag for the new release
# Adjust the tiddler [[TiddlyWiki Archive]] to include the new version number
# Ensure [[TiddlyWiki Releases]] has the new version as the default tab
# Adjust the modified time of HelloThere
# Make sure ''master'' is fully committed

View File

@@ -0,0 +1,62 @@
caption: 5.4.0
created: 20250707115023707
modified: 20250707115023707
tags: ReleaseNotes
title: Release 5.4.0
type: text/vnd.tiddlywiki
description: Under development
//[[See GitHub for detailed change history of this release|https://github.com/TiddlyWiki/TiddlyWiki5/compare/v5.3.7...master]]//
! New Features
-
! Translation improvements
*
! Plugin Improvements
*
! Widget Improvements
*
! Usability Improvements
*
! Palette Improvements
*
! Hackability Improvements
*
! Bug Fixes
*
! Node.js Improvements
*
! Performance Improvements
*
! Developer Improvements
*
! Acknowledgements
[[@Jermolene|https://github.com/Jermolene]] would like to thank the contributors to this release who have generously given their time to help improve TiddlyWiki:
<<.contributors """
""">>

View File

@@ -2,7 +2,6 @@ created: 20131127215321439
modified: 20140912135951542
title: $:/DefaultTiddlers
[[Hire the founder of TiddlyWiki]]
[[TiddlyWiki Pre-release]]
HelloThere
[[Quick Start]]

View File

@@ -1,6 +1,6 @@
title: $:/config/LocalPluginLibrary
tags: $:/tags/PluginLibrary
url: http://127.0.0.1:8080/prerelease/library/v5.4.0/index.html
url: http://127.0.0.1:8080/prerelease/library/v5.3.7/index.html
caption: {{$:/language/OfficialPluginLibrary}} (Prerelease Local)
A locally installed version of the official ~TiddlyWiki plugin library at tiddlywiki.com for testing and debugging. //Requires a local web server to share the library//

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "tiddlywiki.com",
"other-survey-source": "",
"are-you-a-dev": "Yes, I would",
"first-used-tw": "2024",
"joined-tw-community": "No",
"started-tw-community": "",
"use-ttw": "",
"use-mailing-list": "",
"use-reddit": "",
"use-discord": "",
"use-github-discuss": "",
"published-plugin": "No",
"main-use-cases": "As a knowledge base (including technical, non-fiction and encyclopaedic content);Worldbuilding (e.g. for role-playing games);Narrative fiction writing (either supporting its creation or directly writing in TiddlyWiki)",
"other-use-cases": "",
"use-for-work-or-study": "No",
"share-wikis": "No, my TiddlyWiki is for personal use only",
"publish-to-web": "",
"publish-to-intranet": "",
"value-of-tw": "I use it as a configurable storage system that I can dynamically query and reformat. In particular, I use timestamps, sha256, and sorting to pick out random items from lists.",
"tw-ability-level": "I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...);I am comfortable writing filter expressions;I have written custom JavaScript",
"save-method": "Single-file wiki through web browser with Download Saver (default saving mechanism)",
"backup-method": "WebDAV;DIY (any other solution)",
"diy-backup-info": "I use Syncthing to sync a folder between my personal laptop, work laptop, and android phone, then rclone to serve that folder as WebDav and the builtin WebDav saver.",
"wiki-setup-info": "<details><summary>Wiki Information</summary><pre><code>\nTiddlyWiki Version: 5.3.6\nCurrent palette: $:/palettes/Twilight\nCurrent theme: \nCurrent layout: \nBrowser language setting: en-US\nDefault type for missing tiddlers: \nAuto save setting: no\nCode wrapping setting: pre-wrap\nSticky titles setting: no\nSidebar layout setting: fluid-fixed\nAuto focus field setting for new tiddlers: title\nCurrent storyview setting: classic\nToolbar text setting: no\nToolbar icon setting: yes\nButton class setting: tc-btn-invisible\nNavigation address bar setting: permaview\nTiddler opening behaviour setting for navigations from outside the story river: top\nTiddler opening behaviour setting for navigations from within the story river: below\nCamelCase linking setting: disable\nKeyboard shortcuts that have been customised: \nDisabled plugins: \nPlugins: \n $:/core - 5.3.6\n $:/plugins/ahahn/tinka - 0.5.0\n $:/plugins/us.schwier.tiddlywiki/AdvancedTransform - 1.0.0\n $:/plugins/us.schwier.tiddlywiki/Archived - 1.0.2\n $:/plugins/us.schwier.tiddlywiki/Archivist - 0.1.8\n $:/plugins/us.schwier.tiddlywiki/Tagging - 0.1.0\n $:/temp/info-plugin - \n $:/themes/tiddlywiki/snowwhite - 5.3.6\n $:/themes/tiddlywiki/vanilla - 5.3.6\n</code></pre></details>",
"tw-customisations": "I built my own plugins for extending the Advanced Search, exporting text to a webdav file, an organized tagging system, and archiving using ViolentMonkey to host TiddlyWiki in an iframe.",
"positive-about-future": "Yes",
"tw-future-confidence": "Yes",
"project-decision-trust": "Yes",
"project-strengths": "I really like the customization, and the fact the wiki is moving towards using widgets and filters for more functionality because I find them easier to understand.",
"project-weaknesses": "I would like it if the core components start working towards supporting Javascript Promises. There are native browser libraries I would like to use in filters and events, but can't because they are Promise or callback based.",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00160",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "tiddlywiki.com",
"other-survey-source": "",
"are-you-a-dev": "Yes, I would",
"first-used-tw": "2018",
"joined-tw-community": "No",
"started-tw-community": "",
"use-ttw": "",
"use-mailing-list": "",
"use-reddit": "",
"use-discord": "",
"use-github-discuss": "",
"published-plugin": "No",
"main-use-cases": "Note-taking;As a knowledge base (including technical, non-fiction and encyclopaedic content);Other",
"other-use-cases": "Estudos espiritualista para o auto-conhecimento, TI, programação",
"use-for-work-or-study": "Yes",
"share-wikis": "No, my TiddlyWiki is for personal use only",
"publish-to-web": "",
"publish-to-intranet": "",
"value-of-tw": "Um excelente método de estudo, onde você cria o conteúdo onde ele proporciona total liberdade para concatenar e interligar o seu próprio método e capacidade para estudar rumo à compreensão.\nSou muito grato a todos que trabalham para que o TiddlyWiki exista e seja muito útil.",
"tw-ability-level": "I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...)",
"save-method": "Single-file wiki with TiddlyDesktop",
"backup-method": "DIY (any other solution)",
"diy-backup-info": "Apenas utilizo o OneDrive para estudos durante o trabalho, em casa, copio os tiddlers para o arquivo principal.",
"wiki-setup-info": "<details><summary>Wiki Information</summary><pre><code>\nTiddlyWiki Version: 5.3.7\nCurrent palette: $:/palettes/Vanilla\nCurrent theme: $:/themes/tiddlywiki/heavier\nCurrent layout: \nBrowser language setting: pt-BR\nDefault type for missing tiddlers: \nAuto save setting: yes\nCode wrapping setting: pre-wrap\nSticky titles setting: no\nSidebar layout setting: fixed-fluid\nAuto focus field setting for new tiddlers: title\nCurrent storyview setting: top\nToolbar text setting: no\nToolbar icon setting: yes\nButton class setting: tc-btn-invisible\nNavigation address bar setting: no\nTiddler opening behaviour setting for navigations from outside the story river: top\nTiddler opening behaviour setting for navigations from within the story river: above\nCamelCase linking setting: disable\nKeyboard shortcuts that have been customised: $:/config/shortcuts/colortext,$:/config/shortcuts/highlight\nDisabled plugins: \nPlugins: \n $:/core - 5.3.7\n $:/languages/pt-BR - 5.3.7\n $:/plugins/bj/storytabs - 1.11.0\n $:/plugins/danielo515/ContextPlugin - 2.1.0\n $:/plugins/felixhayashi/hotzone - 0.0.3\n $:/plugins/felixhayashi/tiddlymap - 0.15.4+9756\n $:/plugins/felixhayashi/topstoryview - 0.2.0\n $:/plugins/felixhayashi/vis - 4.21.0-SNAPSHOT\n $:/plugins/ihm/tidgraph - 0.9.6\n $:/plugins/kookma/refnotes - 1.9.0\n $:/plugins/kookma/timelines - 1.5.0\n $:/plugins/mermaid-tw5 - 0.3.5\n $:/plugins/tiddlywiki/browser-sniff - 5.3.7\n $:/plugins/tiddlywiki/codemirror - 5.3.7\n $:/plugins/tiddlywiki/codemirror-search-replace - 5.3.7\n $:/plugins/tiddlywiki/evernote - 5.3.7\n $:/plugins/tiddlywiki/nodewebkitsaver - 5.3.7\n $:/plugins/tiddlywiki/railroad - 5.3.7\n $:/plugins/TWaddle/ListTree - 1.0.4\n $:/plugins/TWaddle/SideEditor - 2.1.0\n $:/temp/info-plugin - \n $:/themes/tiddlywiki/centralised - 5.3.7\n $:/themes/tiddlywiki/heavier - 5.3.7\n $:/themes/tiddlywiki/readonly - 5.3.7\n $:/themes/tiddlywiki/seamless - 5.3.7\n $:/themes/tiddlywiki/snowwhite - 5.3.7\n $:/themes/tiddlywiki/starlight - 5.3.7\n $:/themes/tiddlywiki/tight - 5.3.7\n $:/themes/tiddlywiki/tight-heavier - 5.3.7\n $:/themes/tiddlywiki/vanilla - 5.3.7\n</code></pre></details>",
"tw-customisations": "Não fiz alterações particulares, apenas utilizo os plugins que facilitam anotações, marcações, criar links, ferramentas que ajudam o estudo.",
"positive-about-future": "Yes",
"tw-future-confidence": "Yes",
"project-decision-trust": "Yes",
"project-strengths": "Vejo TiddlyWiki como uma poderosa e vasta ferramenta de estudos onde se pode agregar os mais diversos tipos de mídia para fins de estudos e para a compreensão de si, do meio e do todo. Claro que, o mais sofisticado possa ter algum custo, o que é válido! E sim: ampliar as possibilidades nativas de edição textual, tabelas, flowchart, mind map, imagens etc...",
"project-weaknesses": "Não imagino dexando o TiddlyWiki, utilizo por fora um leitor de PDF, um outro para anotações e para aplicar tags aos conteúdos sublinhados que estudo uso o Zotero para os diversos livros que estudo.\nO que temo no TiddlyWiki é que deixe sua qualidade e capacidade de expansão se reduzir e se fechar, não mais produzindo possibilidades de crescimento.\nEu ainda não participo de comunidades...\nPara contribuir, vou procurar como faze-lo e efetivar a ajuda.",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00161",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "tiddlywiki.com",
"other-survey-source": "",
"are-you-a-dev": "Yes, I would",
"first-used-tw": "2013",
"joined-tw-community": "Yes",
"started-tw-community": "2013",
"use-ttw": "I do not engage with this community",
"use-mailing-list": "I read/lurk, but do not post",
"use-reddit": "I do not engage with this community",
"use-discord": "I do not engage with this community",
"use-github-discuss": "I read and post in this community",
"published-plugin": "Yes",
"main-use-cases": "Note-taking;Journalling;Task and project management (including CRMs);As a knowledge base (including technical, non-fiction and encyclopaedic content)",
"other-use-cases": "",
"use-for-work-or-study": "Yes",
"share-wikis": "Yes, with multiple editors/administrators",
"publish-to-web": "Not publishing to this location",
"publish-to-intranet": "Yes, using a single-file wiki;Yes, served through Node.js",
"value-of-tw": "i have been using it every day as personal and professional journal and knowledge base",
"tw-ability-level": "I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...);I am comfortable writing filter expressions;I have written custom HTML;I have written custom CSS styles;I have written custom JavaScript",
"save-method": "Single-file wiki through web browser with Download Saver (default saving mechanism);Single-file wiki with custom saver (e.g. TiddlyPWA, Timimi, tw5-browser-nativesaver);Multi-file wiki served through Node.js",
"backup-method": "Git forge (GitHub, Gitea/Forgejo, GitLab);DIY (any other solution)",
"diy-backup-info": "i have set up a Bob server on my intranet / VPN",
"wiki-setup-info": "i have several quite different live setups",
"tw-customisations": "all of the above, and more. I even tweaked the core plugin on several occasions for my specific needs. I try to regroup my most useful tweaks in plugins that i make available to the world via github",
"positive-about-future": "Yes",
"tw-future-confidence": "Yes",
"project-decision-trust": "Yes",
"project-strengths": "local first, one file containing data+app+plugins+settings, no need for any app but a recent web browser, works on any and all devices that can run any recent web browser. It is important to me that a server should remain optional, and should be assumed unreachable or unavailable most of the time",
"project-weaknesses": "i really need TW to be collaborative, in a local first way. I don't think the current ways, available or being explored by the mainstream community (bags & recipes with a server using SQLite) would suit my needs exactly, because 1/ development is too slow, because 2/ it seems too complex, my need is more simple\n\nI am now looking into a 3-fold way to make TW more collaborative, i don't have enough characters in this box to describe it here, please contact me if interested",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00162",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "tiddlywiki.com",
"other-survey-source": "",
"are-you-a-dev": "Yes, I would",
"first-used-tw": "2017",
"joined-tw-community": "No",
"started-tw-community": "",
"use-ttw": "",
"use-mailing-list": "",
"use-reddit": "",
"use-discord": "",
"use-github-discuss": "",
"published-plugin": "No",
"main-use-cases": "Note-taking;Journalling;As a knowledge base (including technical, non-fiction and encyclopaedic content)",
"other-use-cases": "",
"use-for-work-or-study": "Yes",
"share-wikis": "Yes, and I am the only editor/administrator of my wiki(s)",
"publish-to-web": "Yes, using a single-file wiki",
"publish-to-intranet": "Not publishing to this location",
"value-of-tw": "Single file website, easy to use, open source",
"tw-ability-level": "I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...);I am comfortable writing filter expressions;I have written custom HTML;I have written custom CSS styles",
"save-method": "Single-file wiki through web browser with Download Saver (default saving mechanism);Single-file wiki with custom saver (e.g. TiddlyPWA, Timimi, tw5-browser-nativesaver)",
"backup-method": "Git forge (GitHub, Gitea/Forgejo, GitLab);Consumer online storage (e.g. Google Drive, Dropbox)",
"diy-backup-info": "",
"wiki-setup-info": "Page on Github/Gitlab\nStoring on Dropbox for personal use case",
"tw-customisations": "Added custom thumbnails, filters to list all tiddlers inside a single tiddler for reference. (Is that how you conjugate Tiddly?)",
"positive-about-future": "Yes",
"tw-future-confidence": "Yes",
"project-decision-trust": "Yes",
"project-strengths": "It's a single file that does a lot!",
"project-weaknesses": "More tutorials! Most of the stuff had to be learned by reverse engineering and guessing.",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00163",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -1,33 +0,0 @@
are-you-a-dev: No, I would not
backup-method: DIY (any other solution)
diy-backup-info: I use Resilio Sync to sync a folder across local wifi containing the wikis between Desktop and Laptop
first-heard-survey: Talk TiddlyWiki
first-used-tw: 2014
joined-tw-community: Yes
main-use-cases: Note-taking;Journalling;Task and project management (including CRMs);As a knowledge base (including technical, non-fiction and encyclopaedic content)
ok-to-publish: Yes, I am happy for my responses to be published
other-survey-source:
other-use-cases:
positive-about-future: Yes
project-decision-trust: Yes
project-strengths: That Jeremy is still at the helm but there are also several key people who have a deep knowledge of the architecture. Also, the project is open source and there is a commitment to some degree of 'backwards compatibility'.
project-weaknesses: I'm extremely grateful for what I receive from the forum when I ask for help and I almost always get the answer to a problem. I could never imagine leaving TW or something that would change my relationship with it. Unfortunately, I don't have the time or skills to make substantial contributions to the project - hence my gratitude that others do.
publish-to-intranet:
publish-to-web:
published-plugin: No
save-method: Single-file wiki through web browser with Download Saver (default saving mechanism);Single-file wiki with custom saver (e.g. TiddlyPWA, Timimi, tw5-browser-nativesaver);Single-file wiki with TiddlyDesktop;Single-file wiki third-party mobile app (e.g. Tiddloid, Quine)
share-wikis: No, my TiddlyWiki is for personal use only
started-tw-community: 2014
tags: [[Community Survey 2025]]
title: Community Survey 2025 Answer 00164
tw-ability-level: I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...);I am comfortable writing filter expressions;I have written custom CSS styles
tw-customisations:
tw-future-confidence: Yes
use-discord: I do not engage with this community
use-for-work-or-study: Yes
use-github-discuss: I do not engage with this community
use-mailing-list: I do not engage with this community
use-reddit: I do not engage with this community
use-ttw: I read and post in this community
value-of-tw: It is absolutely invaluable. I use it several times a day almost every day and don't know how I would operate without it. Very grateful to Jeremy and the developers.
wiki-setup-info:

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "tiddlywiki.com",
"other-survey-source": "",
"are-you-a-dev": "No, I would not",
"first-used-tw": "2023",
"joined-tw-community": "No",
"started-tw-community": "",
"use-ttw": "",
"use-mailing-list": "",
"use-reddit": "",
"use-discord": "",
"use-github-discuss": "",
"published-plugin": "No",
"main-use-cases": "Note-taking;Journalling;As a knowledge base (including technical, non-fiction and encyclopaedic content)",
"other-use-cases": "",
"use-for-work-or-study": "Not applicable (as retired, etc)",
"share-wikis": "No, but I may export content into other formats and share individual tiddlers, the whole wiki, or an extract of the wiki",
"publish-to-web": "",
"publish-to-intranet": "",
"value-of-tw": "It started as 'the thing I ramble in' but the ability to start dipping my toes in on the backend gradually has helped me as a creative writer develop previous interests I had in coding! I can directly credit TiddlyWiki as the inspiration for me to write my own website (a WIP...)",
"tw-ability-level": "I have customised TiddlyWiki through options and plugins;I am comfortable writing filter expressions;I have written custom HTML",
"save-method": "Single-file wiki through web browser with Download Saver (default saving mechanism);Single-file wiki with custom saver (e.g. TiddlyPWA, Timimi, tw5-browser-nativesaver)",
"backup-method": "TiddlySpot / TiddlyHost;DIY (any other solution);No automatic sync across my devices",
"diy-backup-info": "currently manual backups though I've just started looking into setting up automatic syncing",
"wiki-setup-info": "<details><summary>Wiki Information</summary><pre><code>\nTiddlyWiki Version: 5.3.6\nCurrent palette: $:/palettes/CupertinoDark\nCurrent theme: \nCurrent layout: \nBrowser language setting: en-US\nDefault type for missing tiddlers: \nAuto save setting: no\nCode wrapping setting: pre\nSticky titles setting: no\nSidebar layout setting: fluid-fixed\nAuto focus field setting for new tiddlers: title\nCurrent storyview setting: classic\nToolbar text setting: no\nToolbar icon setting: yes\nButton class setting: tc-btn-invisible\nNavigation address bar setting: no\nTiddler opening behaviour setting for navigations from outside the story river: top\nTiddler opening behaviour setting for navigations from within the story river: below\nCamelCase linking setting: disable\nKeyboard shortcuts that have been customised: \nDisabled plugins: \nPlugins: \n $:/core - 5.3.6\n $:/plugins/tiddlywiki/codemirror - 5.3.6\n $:/plugins/tiddlywiki/codemirror-autocomplete - 5.3.6\n $:/plugins/tiddlywiki/codemirror-closebrackets - 5.3.6\n $:/plugins/tiddlywiki/codemirror-closetag - 5.3.6\n $:/plugins/tiddlywiki/codemirror-mode-css - 5.3.6\n $:/plugins/tiddlywiki/codemirror-mode-htmlembedded - 5.3.6\n $:/plugins/tiddlywiki/codemirror-mode-htmlmixed - 5.3.6\n $:/plugins/tiddlywiki/codemirror-mode-javascript - 5.3.6\n $:/plugins/tiddlywiki/codemirror-mode-markdown - 5.3.6\n $:/plugins/tiddlywiki/codemirror-mode-xml - 5.3.6\n $:/plugins/tiddlywiki/codemirror-search-replace - 5.3.6\n $:/plugins/tiddlywiki/internals - 5.3.6\n $:/plugins/tiddlywiki/markdown - 5.3.6\n $:/temp/info-plugin - \n $:/themes/tiddlywiki/readonly - 5.3.6\n $:/themes/tiddlywiki/snowwhite - 5.3.6\n $:/themes/tiddlywiki/vanilla - 5.3.6\n</code></pre></details>",
"tw-customisations": "I tried a few community templates and am currently using a mildly customized MPTW5 setup. As a beginner to Coding In General I've found the community resources Extremely Helpful... but hard to find mostly because I don't have the mindset to go looking for them!",
"positive-about-future": "Yes",
"tw-future-confidence": "Yes",
"project-decision-trust": "Yes",
"project-strengths": "As an outsider who fell into the FOSS movement, I very much like what I found here! TiddlyWiki is perfect for my needs as a writer while also encouraging the out-of-the-box thinking skills I've worked so hard to develop. It's so simple to advertise TiddlyWiki to people who I think will get",
"project-weaknesses": "I work full-time in an unrelated field so don't have much personal time to dedicate to coding, and what time I do have I prefer to spend on my writing projects. I very much want to contribute to the project, but don't feel I have much to contribute in the way of skills right now. Hopefully that'll change in the future as I continue to get more comfortable with my personal usage of TiddlyWiki!",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00165",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "Official newsletter",
"other-survey-source": "",
"are-you-a-dev": "Yes, I would",
"first-used-tw": "2016",
"joined-tw-community": "No",
"started-tw-community": "",
"use-ttw": "",
"use-mailing-list": "",
"use-reddit": "",
"use-discord": "",
"use-github-discuss": "",
"published-plugin": "No",
"main-use-cases": "Note-taking;Task and project management (including CRMs);As a knowledge base (including technical, non-fiction and encyclopaedic content);Producing/publishing interactive fiction;Worldbuilding (e.g. for role-playing games);Narrative fiction writing (either supporting its creation or directly writing in TiddlyWiki)",
"other-use-cases": "",
"use-for-work-or-study": "Yes",
"share-wikis": "No, but I may export content into other formats and share individual tiddlers, the whole wiki, or an extract of the wiki",
"publish-to-web": "",
"publish-to-intranet": "",
"value-of-tw": "TiddlyWiki is an indispensable tool for quick notetaking and team management at work, while at home I use it for worldbuilding and fiction writing, as well as managing to do lists. It allows for fast and organised working.",
"tw-ability-level": "I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...);I am comfortable writing filter expressions;I have written custom HTML;I have written custom CSS styles",
"save-method": "Single-file wiki with TiddlyDesktop",
"backup-method": "N/A - I keep my wiki on a single system",
"diy-backup-info": "",
"wiki-setup-info": "<details><summary>Wiki Information</summary><pre><code>\nTiddlyWiki Version: 5.3.7\nCurrent palette: $:/palettes/DesertSand\nCurrent theme: $:/themes/tiddlywiki/vanilla\nCurrent layout: \nBrowser language setting: en-GB\nDefault type for missing tiddlers: \nAuto save setting: yes\nCode wrapping setting: pre-wrap\nSticky titles setting: no\nSidebar layout setting: fluid-fixed\nAuto focus field setting for new tiddlers: title\nCurrent storyview setting: zoomin\nToolbar text setting: no\nToolbar icon setting: yes\nButton class setting: tc-btn-invisible\nNavigation address bar setting: no\nTiddler opening behaviour setting for navigations from outside the story river: top\nTiddler opening behaviour setting for navigations from within the story river: above\nCamelCase linking setting: disable\nKeyboard shortcuts that have been customised: \nDisabled plugins: \nPlugins: \n $:/core - 5.3.7\n $:/plugins/felixhayashi/hotzone - 0.0.3\n $:/plugins/felixhayashi/tiddlymap - 0.17.7+9982\n $:/plugins/felixhayashi/topstoryview - 0.2.0\n $:/plugins/felixhayashi/vis - \n $:/plugins/Gk0Wk/CPL-Repo - 2025.03.29\n $:/plugins/Gk0Wk/echarts - 0.2.13\n $:/plugins/Gk0Wk/focused-tiddler - 0.0.3\n $:/plugins/kookma/commander - 2.1.14\n $:/plugins/kookma/shiraz - 3.0.12\n $:/plugins/kookma/shiraz-callout - 0.8.0\n $:/plugins/kookma/shiraz-formatter - 0.6.2\n $:/plugins/kookma/timelines - 1.5.0\n $:/plugins/kookma/todolist - 1.5.0\n $:/plugins/OokTech/WordCount - 0.0.6\n $:/plugins/tiddlywiki/codemirror - 5.3.7\n $:/plugins/tiddlywiki/codemirror-autocomplete - 5.3.7\n $:/plugins/tiddlywiki/codemirror-closebrackets - 5.3.7\n $:/plugins/tiddlywiki/codemirror-closetag - 5.3.7\n $:/plugins/tiddlywiki/codemirror-mode-css - 5.3.7\n $:/plugins/tiddlywiki/codemirror-mode-htmlembedded - 5.3.7\n $:/plugins/tiddlywiki/codemirror-mode-htmlmixed - 5.3.7\n $:/plugins/tiddlywiki/codemirror-mode-javascript - 5.3.7\n $:/plugins/tiddlywiki/codemirror-mode-markdown - 5.3.7\n $:/plugins/tiddlywiki/codemirror-mode-xml - 5.3.7\n $:/plugins/tiddlywiki/codemirror-search-replace - 5.3.7\n $:/plugins/tiddlywiki/codemirror-trailingspace - 5.3.7\n $:/plugins/tiddlywiki/github-fork-ribbon - 5.3.7\n $:/temp/info-plugin - \n $:/themes/tiddlywiki/snowwhite - 5.3.7\n $:/themes/tiddlywiki/vanilla - 5.3.7\n</code></pre></details>",
"tw-customisations": "I've got a customised stylesheet, JavaScript to calculate age, created three new buttons to help with the creation of specific Tiddlers, and created display templates to standardise output on these specific Tiddlers.",
"positive-about-future": "Yes",
"tw-future-confidence": "Yes",
"project-decision-trust": "Yes",
"project-strengths": "The community on Talk TiddlyWiki is very friendly, and knowledgeable. I use both a lot to work out issues, and while I've not posted questions, I've always been able to find the answers. The documentation on the main site is very comprehensive and well organised. GitHub is a well used tool giving me confidence in the robustness of TiddlyWiki. Each new version of TiddlyWiki has brought something new and exciting to its functionality, and make me rethink how things could be better organised.",
"project-weaknesses": "I'm unsure about the work that is being done on MWS and what it might mean for my use of TiddlyWiki. I prefer simple implementations and maintenance, like I currently have with the single file, so depending on what MWS means in the long run, will determine whether I would upgrade or stick with the version that precedes it.",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00166",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "Reddit",
"other-survey-source": "",
"are-you-a-dev": "No, I would not",
"first-used-tw": "2021",
"joined-tw-community": "No",
"started-tw-community": "",
"use-ttw": "",
"use-mailing-list": "",
"use-reddit": "",
"use-discord": "",
"use-github-discuss": "",
"published-plugin": "No",
"main-use-cases": "Note-taking;Journalling;As a knowledge base (including technical, non-fiction and encyclopaedic content)",
"other-use-cases": "",
"use-for-work-or-study": "Yes",
"share-wikis": "No, but I may export content into other formats and share individual tiddlers, the whole wiki, or an extract of the wiki",
"publish-to-web": "",
"publish-to-intranet": "",
"value-of-tw": "Me ayuda a guardar cosas que no sabría dónde más guardarlas, además de vincularlas entre sí: notas sobre personas, proveedores, proyectos, conceptos, bibliografía, etc...",
"tw-ability-level": "My use is basic; I use TiddlyWiki in a configuration close to standard, without plugins",
"save-method": "Multi-file wiki served through Node.js",
"backup-method": "DIY (any other solution)",
"diy-backup-info": "Syncthing",
"wiki-setup-info": "",
"tw-customisations": "",
"positive-about-future": "Yes",
"tw-future-confidence": "Yes",
"project-decision-trust": "Yes",
"project-strengths": "Siempre mejorando. Fiel a una filosofía y conceptos que son claros y robustos.",
"project-weaknesses": "Sería fantástico que estuviese más desarrollado cómo hackear tiddlywiki, con ejemplos concretos o pequeños proyectos de ejemplo resueltos para practicar y sentar conceptos.\n\nUna característica fundamental y que hecho en falta es una mejor gestión de archivos adjuntos (imágenes, pdfs, etc...)",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00167",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -1,33 +0,0 @@
are-you-a-dev: Yes, I would
backup-method: No automatic sync across my devices
diy-backup-info:
first-heard-survey: tiddlywiki.com
first-used-tw: 2013
joined-tw-community: No
main-use-cases: Note-taking;As a knowledge base (including technical, non-fiction and encyclopaedic content)
ok-to-publish: Yes, I am happy for my responses to be published
other-survey-source:
other-use-cases:
positive-about-future: Yes
project-decision-trust: No
project-strengths: project is actively developed - have hopes for features I need to be implemented in the future
project-weaknesses: still waiting for JSON Mangler plugin to work with wiki > 5.1.xxx (I can't upgrade some wiki files because of that - still using 5.1.22) or other functionality for creating/updating hierarchical JSON data tiddlers
publish-to-intranet:
publish-to-web:
published-plugin: No
save-method: Single-file wiki through web browser with Download Saver (default saving mechanism);Single-file wiki with TiddlyDesktop
share-wikis: No, my TiddlyWiki is for personal use only
started-tw-community:
tags: [[Community Survey 2025]]
title: Community Survey 2025 Answer 00168
tw-ability-level: I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...);I am comfortable writing filter expressions;I have written custom CSS styles
tw-customisations: plugins for arithmetic calculations, json handling (updates! not just reading), macros for copy information with button click (links, code, text)
tw-future-confidence: Yes
use-discord:
use-for-work-or-study: Yes
use-github-discuss:
use-mailing-list:
use-reddit:
use-ttw:
value-of-tw: essential knowledge base, don't need to remember/learn again everything
wiki-setup-info:

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "tiddlywiki.com",
"other-survey-source": "",
"are-you-a-dev": "No, I would not",
"first-used-tw": "2018",
"joined-tw-community": "Yes",
"started-tw-community": "2019",
"use-ttw": "I read/lurk, but do not post",
"use-mailing-list": "I read/lurk, but do not post",
"use-reddit": "I read/lurk, but do not post",
"use-discord": "I do not engage with this community",
"use-github-discuss": "I read/lurk, but do not post",
"published-plugin": "Yes",
"main-use-cases": "Note-taking;Journalling;Narrative fiction writing (either supporting its creation or directly writing in TiddlyWiki);Other",
"other-use-cases": "Fitness tracker",
"use-for-work-or-study": "No",
"share-wikis": "No, my TiddlyWiki is for personal use only",
"publish-to-web": "",
"publish-to-intranet": "",
"value-of-tw": "It helps me keep track of things in a highly personalized manner. For me, the most important feature of tiddlywiki is not just its data security, but also its customability.",
"tw-ability-level": "I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...);I am comfortable writing filter expressions;I have written custom CSS styles",
"save-method": "Single-file wiki third-party mobile app (e.g. Tiddloid, Quine)",
"backup-method": "TiddlySpot / TiddlyHost",
"diy-backup-info": "",
"wiki-setup-info": "<details><summary>Wiki Information</summary><pre><code>\nTiddlyWiki Version: 5.3.5\nCurrent palette: $:/palettes/Dracula\nCurrent theme: $:/themes/tiddlywiki/vanilla\nCurrent layout: \nBrowser language setting: en-US\nDefault type for missing tiddlers: \nAuto save setting: no\nCode wrapping setting: pre-wrap\nSticky titles setting: no\nSidebar layout setting: fluid-fixed\nAuto focus field setting for new tiddlers: title\nCurrent storyview setting: classic\nToolbar text setting: no\nToolbar icon setting: yes\nButton class setting: tc-btn-invisible\nNavigation address bar setting: no\nTiddler opening behaviour setting for navigations from outside the story river: top\nTiddler opening behaviour setting for navigations from within the story river: below\nCamelCase linking setting: disable\nKeyboard shortcuts that have been customised: \nDisabled plugins: \nPlugins: \n $:/core - 5.3.5\n $:/temp/info-plugin - \n $:/themes/tiddlywiki/snowwhite - 5.3.5\n $:/themes/tiddlywiki/vanilla - 5.3.5\n</code></pre></details>",
"tw-customisations": "stylesheets and macros to present my tw to myself like how a native notes app would look like on my phone. I don't have a personal computer anymore and am mostly on mobile now.",
"positive-about-future": "Yes",
"tw-future-confidence": "Yes",
"project-decision-trust": "Yes",
"project-strengths": "people are so eager to help and solve each others' problems, and often are also very inspired in their ways",
"project-weaknesses": "I'm afraid of the empty version someday becoming bloated. \nEven now, I think there is a way to make it even more barebones.\nI'm very reserved and asocial now, unfortunately. I don't think I'll participate in the community any more than I already had, although I still love reading community posts and seeing everyone's interactions.",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00169",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "tiddlywiki.com",
"other-survey-source": "",
"are-you-a-dev": "Yes, I would",
"first-used-tw": "2003",
"joined-tw-community": "No",
"started-tw-community": "",
"use-ttw": "",
"use-mailing-list": "",
"use-reddit": "",
"use-discord": "",
"use-github-discuss": "",
"published-plugin": "No",
"main-use-cases": "Note-taking;Task and project management (including CRMs);As a knowledge base (including technical, non-fiction and encyclopaedic content);Producing/publishing interactive fiction",
"other-use-cases": "",
"use-for-work-or-study": "Yes",
"share-wikis": "Yes, with multiple editors/administrators",
"publish-to-web": "Yes, using a single-file wiki",
"publish-to-intranet": "Yes, using a single-file wiki;Yes, served through Node.js",
"value-of-tw": "arranging text in the form of tiddlers with automatic date showing age of information and ease of cross platform (phone, tablet, windows, linux) neat field and content search and easy to adapt and so many more things I cant begin to write about in 280 characters!",
"tw-ability-level": "I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...)",
"save-method": "Single-file wiki through web browser with Download Saver (default saving mechanism);Single-file wiki with custom saver (e.g. TiddlyPWA, Timimi, tw5-browser-nativesaver);Single-file wiki third-party mobile app (e.g. Tiddloid, Quine)",
"backup-method": "Git forge (GitHub, Gitea/Forgejo, GitLab);Consumer online storage (e.g. Google Drive, Dropbox)",
"diy-backup-info": "",
"wiki-setup-info": "<details><summary>Wiki Information</summary><pre><code>\nTiddlyWiki Version: 5.3.3\nCurrent palette: $:/palettes/Vanilla\nCurrent theme: \nCurrent layout: \nBrowser language setting: en-GB\nDefault type for missing tiddlers: \nAuto save setting: yes\nCode wrapping setting: pre-wrap\nSticky titles setting: no\nSidebar layout setting: fluid-fixed\nAuto focus field setting for new tiddlers: title\nCurrent storyview setting: classic\nToolbar text setting: no\nToolbar icon setting: yes\nButton class setting: tc-btn-invisible\nNavigation address bar setting: no\nTiddler opening behaviour setting for navigations from outside the story river: top\nTiddler opening behaviour setting for navigations from within the story river: below\nCamelCase linking setting: enable\nKeyboard shortcuts that have been customised: \nDisabled plugins: \nPlugins: \n $:/core - 5.3.3\n $:/plugins/tiddlywiki/consent-banner - 5.3.3\n $:/plugins/tiddlywiki/googleanalytics - 5.3.3\n $:/plugins/tiddlywiki/katex - 5.1.21\n $:/temp/info-plugin - \n $:/themes/tiddlywiki/snowwhite - 5.3.3\n $:/themes/tiddlywiki/vanilla - 5.3.3\n</code></pre></details>",
"tw-customisations": "auto generation of tiddlers from templates using bash scripts. book like features inspired by https://groktiddlywiki.com/read/.",
"positive-about-future": "Yes",
"tw-future-confidence": "Yes",
"project-decision-trust": "Yes",
"project-strengths": "multi user access. at the moment I am exploring https://github.com/dionisos2/tiddlygit because it enables me to have code review and code in the same git repository. https://github.com/TiddlyWiki/MultiWikiServer seems to be very good but requires more infrastructure.",
"project-weaknesses": "its a great tool. I started using it in 2007 and was enthusiastic about it then. it has stood the test of time. I am still using it in 2025 and I am perhaps more enthusiastic about it now.",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00170",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "tiddlywiki.com",
"other-survey-source": "",
"are-you-a-dev": "Yes, I would",
"first-used-tw": "2024",
"joined-tw-community": "No",
"started-tw-community": "",
"use-ttw": "",
"use-mailing-list": "",
"use-reddit": "",
"use-discord": "",
"use-github-discuss": "",
"published-plugin": "No",
"main-use-cases": "Note-taking;Journalling;Task and project management (including CRMs);As a knowledge base (including technical, non-fiction and encyclopaedic content);Worldbuilding (e.g. for role-playing games)",
"other-use-cases": "",
"use-for-work-or-study": "No",
"share-wikis": "No, my TiddlyWiki is for personal use only",
"publish-to-web": "",
"publish-to-intranet": "",
"value-of-tw": "Non-linear general-purpose notebook/wiki system",
"tw-ability-level": "I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...);I am comfortable writing filter expressions;I have written custom CSS styles",
"save-method": "Multi-file wiki served through Node.js",
"backup-method": "N/A - I keep my wiki on a single system",
"diy-backup-info": "",
"wiki-setup-info": "<details><summary>Wiki Information</summary><pre><code>\nTiddlyWiki Version: 5.3.3\nCurrent palette: $:/palettes/Nord\nCurrent theme: $:/themes/tiddlywiki/vanilla\nCurrent layout: \nBrowser language setting: en-US\nDefault type for missing tiddlers: \nAuto save setting: yes\nCode wrapping setting: pre\nSticky titles setting: yes\nSidebar layout setting: fluid-fixed\nAuto focus field setting for new tiddlers: title\nCurrent storyview setting: classic\nToolbar text setting: no\nToolbar icon setting: yes\nButton class setting: tc-btn-invisible\nNavigation address bar setting: permalink\nTiddler opening behaviour setting for navigations from outside the story river: top\nTiddler opening behaviour setting for navigations from within the story river: below\nCamelCase linking setting: disable\nKeyboard shortcuts that have been customised: $:/config/shortcuts-not-mac/underline,$:/config/shortcuts/excise,$:/config/shortcuts/subscript,$:/config/shortcuts/superscript\nDisabled plugins: \nPlugins: \n $:/core - 5.3.3\n $:/plugins/aaldrich/tables - 0.6.21\n $:/plugins/cdr/markdown-more - 0.1.0\n $:/plugins/danielo515/2click2edit - 0.1\n $:/plugins/Gk0Wk/TW5-CodeMirror-Enhanced - 0.1.4\n $:/plugins/mklauber/aliases - 5.3.3\n $:/plugins/sq/Stories - 1.0.3\n $:/plugins/tiddlywiki/codemirror - 5.3.3\n $:/plugins/tiddlywiki/codemirror-closebrackets - 5.3.3\n $:/plugins/tiddlywiki/codemirror-closetag - 5.3.3\n $:/plugins/tiddlywiki/codemirror-mode-css - 5.3.3\n $:/plugins/tiddlywiki/codemirror-mode-htmlmixed - 5.3.3\n $:/plugins/tiddlywiki/codemirror-mode-javascript - 5.3.3\n $:/plugins/tiddlywiki/codemirror-mode-markdown - 5.3.3\n $:/plugins/tiddlywiki/codemirror-mode-xml - 5.3.3\n $:/plugins/tiddlywiki/codemirror-search-replace - 5.3.3\n $:/plugins/tiddlywiki/codemirror-trailingspace - 5.3.3\n $:/plugins/tiddlywiki/filesystem - 5.3.3\n $:/plugins/tiddlywiki/highlight - 5.3.3\n $:/plugins/tiddlywiki/markdown - 5.3.3\n $:/plugins/tiddlywiki/tiddlyweb - 5.3.3\n $:/temp/info-plugin - \n $:/themes/tiddlywiki/snowwhite - 5.3.3\n $:/themes/tiddlywiki/vanilla - 5.3.3\n</code></pre></details>",
"tw-customisations": "Stylesheets and ViewTemplates",
"positive-about-future": "Yes",
"tw-future-confidence": "Yes",
"project-decision-trust": "Yes",
"project-strengths": "Open source, system transparency.",
"project-weaknesses": "Markdown integration.",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00171",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "tiddlywiki.com",
"other-survey-source": "",
"are-you-a-dev": "No, I would not",
"first-used-tw": "2009",
"joined-tw-community": "No",
"started-tw-community": "",
"use-ttw": "",
"use-mailing-list": "",
"use-reddit": "",
"use-discord": "",
"use-github-discuss": "",
"published-plugin": "No",
"main-use-cases": "Note-taking;Journalling;Task and project management (including CRMs);As a knowledge base (including technical, non-fiction and encyclopaedic content);Programming",
"other-use-cases": "",
"use-for-work-or-study": "Yes",
"share-wikis": "Yes, and I am the only editor/administrator of my wiki(s)",
"publish-to-web": "Yes, using a single-file wiki",
"publish-to-intranet": "Not publishing to this location",
"value-of-tw": "keeps all my notes together at one place.\nI can write mermaid and railway diagrams and can write math expressions.\nI can export and import via drag and drop.\nI use tiddlymap to get mindmaps and relationships between topics.\nI can work from every browser everywhere.",
"tw-ability-level": "I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...);I have written custom HTML;I have written custom CSS styles",
"save-method": "Single-file wiki through web browser with Download Saver (default saving mechanism)",
"backup-method": "WebDAV",
"diy-backup-info": "",
"wiki-setup-info": "<details><summary>Wiki Information</summary><pre><code>\nTiddlyWiki Version: 5.3.7\nCurrent palette: $:/palettes/Fresh\nCurrent theme: \nCurrent layout: \nBrowser language setting: en-GB\nDefault type for missing tiddlers: \nAuto save setting: yes\nCode wrapping setting: pre\nSticky titles setting: yes\nSidebar layout setting: fixed-fluid\nAuto focus field setting for new tiddlers: title\nCurrent storyview setting: top\nToolbar text setting: no\nToolbar icon setting: yes\nButton class setting: tc-btn-invisible\nNavigation address bar setting: permalink\nTiddler opening behaviour setting for navigations from outside the story river: top\nTiddler opening behaviour setting for navigations from within the story river: above\nCamelCase linking setting: disable\nKeyboard shortcuts that have been customised: \nDisabled plugins: \nPlugins: \n $:/core - 5.3.7\n $:/languages/de-DE - 5.3.7\n $:/plugins/felixhayashi/hotzone - 0.0.3\n $:/plugins/felixhayashi/tiddlymap - 0.17.20+10024\n $:/plugins/felixhayashi/topstoryview - 0.2.0\n $:/plugins/flibbles/vis-network - 9.1.3\n $:/plugins/inmysocks/Dashboard - 0.1.2\n $:/plugins/jd/NTFS19 - 1.0.1\n $:/plugins/jd/plainrevs - 0.0.30\n $:/plugins/orange/mermaid-tw5 - 0.3.8\n $:/plugins/tgrosinger/tw5-checklist - 0.0.14\n $:/plugins/tiddlywiki/external-attachments - 5.3.7\n $:/plugins/tiddlywiki/katex - 5.3.7\n $:/plugins/tiddlywiki/markdown - 5.3.7\n $:/plugins/tiddlywiki/qrcode - 5.3.7\n $:/plugins/tiddlywiki/railroad - 5.3.7\n $:/temp/info-plugin - \n $:/themes/tiddlywiki/snowwhite - 5.3.7\n $:/themes/tiddlywiki/vanilla - 5.3.7\n</code></pre></details>",
"tw-customisations": "some plugins I found on the web and just drag and dropped them in.\nI edited external-attachments to work with webdav.",
"positive-about-future": "Yes",
"tw-future-confidence": "Yes",
"project-decision-trust": "Yes",
"project-strengths": "keeping the project running and breaking not much backward compatibility.",
"project-weaknesses": "With age a project gets stuck in it's tracks and there is not much improvement.\nWe will propably never get a WYSIWYG editor for example.\nBut I'm propably the wrong person. I'm not enough involved in the community or the project.",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00172",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "tiddlywiki.com",
"other-survey-source": "",
"are-you-a-dev": "Yes, I would",
"first-used-tw": "2010",
"joined-tw-community": "No",
"started-tw-community": "",
"use-ttw": "",
"use-mailing-list": "",
"use-reddit": "",
"use-discord": "",
"use-github-discuss": "",
"published-plugin": "No",
"main-use-cases": "Note-taking;Journalling;Task and project management (including CRMs);As a knowledge base (including technical, non-fiction and encyclopaedic content);Other",
"other-use-cases": "Id like to shape a prepared Tiddlywiki for people arriving in a job, having to keep note of many things : contacts, orgs, projects, procs…",
"use-for-work-or-study": "Yes",
"share-wikis": "No, but I may export content into other formats and share individual tiddlers, the whole wiki, or an extract of the wiki",
"publish-to-web": "",
"publish-to-intranet": "",
"value-of-tw": "Heavy payload to prepare my version to achieve the goals I wanted to reach. Many days of reading docs, acquiring comprehension of internal functionnalities et how to use them.\nNow my \"preparation\" is optimum and I use it almost permanently at work as maintained knowledge base.",
"tw-ability-level": "I have customised TiddlyWiki through options and plugins;I have written custom HTML;I have written custom CSS styles",
"save-method": "Single-file wiki through web browser with Download Saver (default saving mechanism)",
"backup-method": "DIY (any other solution)",
"diy-backup-info": "I save the wiki file on a daily basis, renaming the file, and save many times ad day to avoid loosing changes. Keeping 2 weeks of daily versions, then 1 monthly (last day) version.",
"wiki-setup-info": "",
"tw-customisations": "",
"positive-about-future": "Yes",
"tw-future-confidence": "Yes",
"project-decision-trust": "Yes",
"project-strengths": "maintaining the product",
"project-weaknesses": "better explanations and exemples to go deeper in ecases, or better turorials",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00173",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -1,33 +0,0 @@
are-you-a-dev: Yes, I would
backup-method: Web or cloud hosting (other than TiddlyHost/TiddlySpot e.g. Netlify, AWS, OVH, Google Cloud...)
diy-backup-info:
first-heard-survey: tiddlywiki.com
first-used-tw: 2012
joined-tw-community: No
main-use-cases: As a knowledge base (including technical, non-fiction and encyclopaedic content);Producing/publishing interactive fiction;Programming
ok-to-publish: Yes, I am happy for my responses to be published
other-survey-source:
other-use-cases:
positive-about-future: Yes
project-decision-trust: Yes
project-strengths: Information on the https://tiddlywiki.com/ website
project-weaknesses: Add formatting for (amongst others) currencies
publish-to-intranet: Not publishing to this location
publish-to-web: Not publishing to this location
published-plugin: No
save-method: Single-file wiki with TiddlyDesktop
share-wikis: Yes, and I am the only editor/administrator of my wiki(s)
started-tw-community:
tags: [[Community Survey 2025]]
title: Community Survey 2025 Answer 00174
tw-ability-level: I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...);I am comfortable writing filter expressions;I have written custom HTML;I have written custom CSS styles
tw-customisations: stylesheets, macros, functions and procedures,
tw-future-confidence: Yes
use-discord:
use-for-work-or-study: Not applicable (as retired, etc)
use-github-discuss:
use-mailing-list:
use-reddit:
use-ttw:
value-of-tw: Quite a lot, use it to keep track of recepies, possesions and use it in charity projects.
wiki-setup-info:

View File

@@ -1,33 +0,0 @@
are-you-a-dev: Yes, I would
backup-method: TiddlySpot / TiddlyHost;Consumer online storage (e.g. Google Drive, Dropbox)
diy-backup-info:
first-heard-survey: tiddlywiki.com
first-used-tw: 2012
joined-tw-community: Yes
main-use-cases: Note-taking;Journalling;Task and project management (including CRMs);As a knowledge base (including technical, non-fiction and encyclopaedic content);Worldbuilding (e.g. for role-playing games)
ok-to-publish: Yes, I am happy for my responses to be published
other-survey-source:
other-use-cases:
positive-about-future: Yes
project-decision-trust: Yes
project-strengths: I love the customization, community, and ease of use. You can make it whatever you need.
project-weaknesses: I think I previously said I needed help with hosting and customization (esp for themes) but after a little research.... I was wrong! Now using TiddlyHost, and found all kinds of new resources I didn't know about.
publish-to-intranet:
publish-to-web:
published-plugin: No
save-method: Single-file wiki through web browser with Download Saver (default saving mechanism)
share-wikis: No, my TiddlyWiki is for personal use only
started-tw-community:
tags: [[Community Survey 2025]]
title: Community Survey 2025 Answer 00175
tw-ability-level: I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...);I am comfortable writing filter expressions;I have written custom HTML;I have written custom CSS styles;I have written custom JavaScript
tw-customisations: All of the above (stylesheets, macros/functions/procedures, JavaScript, and direct edits to the core). I make extensive use of templates and custom buttons, special classes for handling formatting type things.
tw-future-confidence: Yes
use-discord: I do not engage with this community
use-for-work-or-study: No
use-github-discuss: I do not engage with this community
use-mailing-list: I read and post in this community
use-reddit: I read/lurk, but do not post
use-ttw: I read and post in this community
value-of-tw: VERY useful in keeping track of info. It's like a Commonplace book or Zettelkasten.
wiki-setup-info:

View File

@@ -1,33 +0,0 @@
are-you-a-dev: Yes, I would
backup-method: DIY (any other solution)
diy-backup-info: Depends on the particular TW. There are many file sync options.
first-heard-survey: tiddlywiki.com
first-used-tw: 2012
joined-tw-community: No
main-use-cases: Note-taking;Journalling;Task and project management (including CRMs);As a knowledge base (including technical, non-fiction and encyclopaedic content)
ok-to-publish: Yes, I am happy for my responses to be published
other-survey-source:
other-use-cases:
positive-about-future: Yes
project-decision-trust: Yes
project-strengths: Open helpful community. I mostly just read relevant topics. JavaScript has many libraries, so standing on the shoulders of giants. Regular updates. Beautiful web site, also as a TW.
project-weaknesses: Make JavaScript more accessible. Filter expressions etc. are good for simple use cases, but become very tough and hard to debug in more complex scenarios. Writing JS requires reloading etc., is cumbersome. Many TW plugins become outdated, e.g. single maintainer. Would be good to know on which ones, one can rely on. Maybe have some hierarchy, have multiple maintainers for heavily used PlugIns. Do not focus too much on NodeJS. I do not want a local Node JS installation. Have a way for online colab
publish-to-intranet: Not publishing to this location
publish-to-web: Not publishing to this location
published-plugin: Yes
save-method: Single-file wiki through web browser with Download Saver (default saving mechanism);Single-file wiki third-party mobile app (e.g. Tiddloid, Quine)
share-wikis: Yes, with multiple editors/administrators
started-tw-community:
tags: [[Community Survey 2025]]
title: Community Survey 2025 Answer 00176
tw-ability-level: I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...);I am comfortable writing filter expressions;I have written custom HTML;I have written custom CSS styles;I have written custom JavaScript
tw-customisations: Made a kind of versioning sync, so that you can drop one version of TW into another, will track changes and sync to the most current changes or show conflicts. Using NodeJS etc. would loose a big benefit: running purely in browser, important in restricted / company environments
tw-future-confidence: Yes
use-discord:
use-for-work-or-study: Yes
use-github-discuss:
use-mailing-list:
use-reddit:
use-ttw:
value-of-tw: Single file is blessing: Reliable & beautiful place to put information; Spreading of information controllable, no install, browser sandbox; Nice for sharing projects / collections with others by secure channel. And curse: size limit, siloed, not interoperable with local fs tools.
wiki-setup-info:

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "tiddlywiki.com",
"other-survey-source": "",
"are-you-a-dev": "Yes, I would",
"first-used-tw": "2012",
"joined-tw-community": "No",
"started-tw-community": "",
"use-ttw": "",
"use-mailing-list": "",
"use-reddit": "",
"use-discord": "",
"use-github-discuss": "",
"published-plugin": "No",
"main-use-cases": "Note-taking;Task and project management (including CRMs);As a knowledge base (including technical, non-fiction and encyclopaedic content)",
"other-use-cases": "",
"use-for-work-or-study": "Yes",
"share-wikis": "No, my TiddlyWiki is for personal use only",
"publish-to-web": "",
"publish-to-intranet": "",
"value-of-tw": "Highly configurable note taking knowledge base / task management / organizer that I can customize to perfectly suit my needs.",
"tw-ability-level": "I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...);I am comfortable writing filter expressions;I have written custom JavaScript",
"save-method": "Multi-file wiki served through Node.js",
"backup-method": "Web or cloud hosting (other than TiddlyHost/TiddlySpot e.g. Netlify, AWS, OVH, Google Cloud...)",
"diy-backup-info": "",
"wiki-setup-info": "<details><summary>Wiki Information</summary><pre><code>\nTiddlyWiki Version: 5.3.2\nCurrent palette: $:/palettes/Vanilla\nCurrent theme: $:/themes/tiddlywiki/vanilla\nCurrent layout: $:/core/ui/PageTemplate\nBrowser language setting: en-US\nDefault type for missing tiddlers: \nAuto save setting: yes\nCode wrapping setting: pre-wrap\nSticky titles setting: yes\nSidebar layout setting: fixed-fluid\nAuto focus field setting for new tiddlers: title\nCurrent storyview setting: classic\nToolbar text setting: no\nToolbar icon setting: yes\nButton class setting: tc-btn-invisible\nNavigation address bar setting: no\nTiddler opening behaviour setting for navigations from outside the story river: top\nTiddler opening behaviour setting for navigations from within the story river: below\nCamelCase linking setting: disable\nKeyboard shortcuts that have been customised: $:/config/shortcuts-mac/toggle-sidebar\nDisabled plugins: \nPlugins: \n $:/core - 5.3.2\n $:/plugins/tiddlywiki/filesystem - 5.3.2\n $:/plugins/tiddlywiki/highlight - 5.3.2\n $:/plugins/tiddlywiki/katex - 5.3.2\n $:/plugins/tiddlywiki/markdown - 5.3.2\n $:/plugins/tiddlywiki/railroad - 5.3.2\n $:/plugins/tiddlywiki/tiddlyweb - 5.3.2\n $:/temp/info-plugin - \n $:/themes/tiddlywiki/snowwhite - 5.3.2\n $:/themes/tiddlywiki/vanilla - 5.3.2\n</code></pre></details>",
"tw-customisations": "I have many custom macros. My largest one is for tracking context with coworkers and meetings. I also have a variety of templates for common pages.\n\nOnly direct edits I've done to the core are to add automatic linkification for certain custom links.",
"positive-about-future": "No",
"tw-future-confidence": "Yes",
"project-decision-trust": "Yes",
"project-strengths": "* Very open community\n* Strong focus on compatibility / support. I never worry that my wiki will no longer be supported\n* Strong focus on customization.\n* Focus on self-host / DIY.",
"project-weaknesses": "* TiddlyWiki is an incredibly powerful \"operating system\" for knowledge management tools, but it's difficult to develop on top of. My main reason for using TiddlyWiki over other tools is customization. I'd love to see that brought more to the forefront. e.g. version control tools, easier testing for plugins, debuggers, etc.\n* I'm afraid TiddlyWiki will become irrelvent / be surpassed in features by Roam/Obsidian.",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00177",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -1,33 +0,0 @@
are-you-a-dev: No, I would not
backup-method: TiddlySpot / TiddlyHost
diy-backup-info:
first-heard-survey: tiddlywiki.com
first-used-tw: 2005
joined-tw-community: Yes
main-use-cases: Note-taking;Task and project management (including CRMs);As a knowledge base (including technical, non-fiction and encyclopaedic content);Other
ok-to-publish: Yes, I am happy for my responses to be published
other-survey-source:
other-use-cases: Experimentation, collaboration
positive-about-future: Yes
project-decision-trust: Yes
project-strengths: I like the enthusiastic and robust development community and development timeline. I admire the creativity, skills and generosity of the experienced developers and experimenters. It is the most tweakable, customizable, and creatively enjoyable environment I have ever worked in.
project-weaknesses: I will always be a loyal fan and user of TW. At my current skill level, there is still a gap between the ideas and concepts I read about in the users groups and my ability to comprehend many of them. There are not enough step-by-step tutorials and example uses that help me understand core concepts and how to build workable models. Would help to have more beginner and intermediate level discussion platforms.
publish-to-intranet:
publish-to-web:
published-plugin: No
save-method: Single-file wiki through web browser with Download Saver (default saving mechanism)
share-wikis: No, but I may export content into other formats and share individual tiddlers, the whole wiki, or an extract of the wiki
started-tw-community: 2015
tags: [[Community Survey 2025]]
title: Community Survey 2025 Answer 00178
tw-ability-level: I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...);I am comfortable writing filter expressions;I have written custom HTML
tw-customisations: Stylesheets, some macros and procedures
tw-future-confidence: Yes
use-discord: I do not engage with this community
use-for-work-or-study: No
use-github-discuss: I do not engage with this community
use-mailing-list: I read/lurk, but do not post
use-reddit: I do not engage with this community
use-ttw: I read and post in this community
value-of-tw: It mostly has potential value as I am attempting to develop a real-time team collaboration environment.
wiki-setup-info:

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "Talk TiddlyWiki",
"other-survey-source": "",
"are-you-a-dev": "No, I would not",
"first-used-tw": "2012",
"joined-tw-community": "Yes",
"started-tw-community": "2025",
"use-ttw": "I read and post in this community",
"use-mailing-list": "I read/lurk, but do not post",
"use-reddit": "I read/lurk, but do not post",
"use-discord": "I do not engage with this community",
"use-github-discuss": "I do not engage with this community",
"published-plugin": "No",
"main-use-cases": "Note-taking;As a knowledge base (including technical, non-fiction and encyclopaedic content)",
"other-use-cases": "",
"use-for-work-or-study": "Not applicable (as retired, etc)",
"share-wikis": "No, my TiddlyWiki is for personal use only",
"publish-to-web": "",
"publish-to-intranet": "",
"value-of-tw": "The way TW stores the data in one HTML-file. \n(I personaly use one sub-folder for media storage).",
"tw-ability-level": "I have customised TiddlyWiki through options and plugins",
"save-method": "Single-file wiki with TiddlyDesktop",
"backup-method": "Web or cloud hosting (other than TiddlyHost/TiddlySpot e.g. Netlify, AWS, OVH, Google Cloud...)",
"diy-backup-info": "",
"wiki-setup-info": "",
"tw-customisations": "",
"positive-about-future": "Yes",
"tw-future-confidence": "Yes",
"project-decision-trust": "Yes",
"project-strengths": "Appealing to me is that the software (application) is future proof.",
"project-weaknesses": "I think that TW will always keeps my interest.",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00179",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "tiddlywiki.com",
"other-survey-source": "",
"are-you-a-dev": "Yes, I would",
"first-used-tw": "2013",
"joined-tw-community": "No",
"started-tw-community": "",
"use-ttw": "",
"use-mailing-list": "",
"use-reddit": "",
"use-discord": "",
"use-github-discuss": "",
"published-plugin": "No",
"main-use-cases": "Note-taking;Journalling;Task and project management (including CRMs);As a knowledge base (including technical, non-fiction and encyclopaedic content);Other",
"other-use-cases": "Sort of a tiddler database, used by other projects.",
"use-for-work-or-study": "Yes",
"share-wikis": "No, my TiddlyWiki is for personal use only",
"publish-to-web": "",
"publish-to-intranet": "",
"value-of-tw": "It's mandatory :). I recently changed from Chrome to Firefox mainly because Timimi is not working anymore in Chrome.",
"tw-ability-level": "I have customised TiddlyWiki through options and plugins",
"save-method": "Single-file wiki with custom saver (e.g. TiddlyPWA, Timimi, tw5-browser-nativesaver)",
"backup-method": "Consumer online storage (e.g. Google Drive, Dropbox)",
"diy-backup-info": "",
"wiki-setup-info": "<details><summary>Wiki Information</summary><pre><code>\nTiddlyWiki Version: 5.3.7\nCurrent palette: $:/palettes/Vanilla\nCurrent theme: \nCurrent layout: \nBrowser language setting: pt-BR\nDefault type for missing tiddlers: \nAuto save setting: yes\nCode wrapping setting: pre-wrap\nSticky titles setting: yes\nSidebar layout setting: fluid-fixed\nAuto focus field setting for new tiddlers: title\nCurrent storyview setting: classic\nToolbar text setting: no\nToolbar icon setting: yes\nButton class setting: tc-btn-invisible\nNavigation address bar setting: no\nTiddler opening behaviour setting for navigations from outside the story river: top\nTiddler opening behaviour setting for navigations from within the story river: below\nCamelCase linking setting: disable\nKeyboard shortcuts that have been customised: \nDisabled plugins: \nPlugins: \n $:/core - 5.3.7\n $:/temp/info-plugin - \n $:/themes/tiddlywiki/snowwhite - 5.3.7\n $:/themes/tiddlywiki/vanilla - 5.3.7\n</code></pre></details>",
"tw-customisations": "I don't play outside the data because I fear to lose everything in the next upgrade, so I prefer to read the wiki data from outside.",
"positive-about-future": "Yes",
"tw-future-confidence": "Yes",
"project-decision-trust": "Yes",
"project-strengths": "The change of the data to JSON made it extremely easier to import from outside. I loved it.",
"project-weaknesses": "If I was able to learn more about \"under the hood\" stuff (actions, transclusions, ...), I'd probably use them more often.",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00180",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "tiddlywiki.com",
"other-survey-source": "",
"are-you-a-dev": "Yes, I would",
"first-used-tw": "2006",
"joined-tw-community": "No",
"started-tw-community": "",
"use-ttw": "",
"use-mailing-list": "",
"use-reddit": "",
"use-discord": "",
"use-github-discuss": "",
"published-plugin": "No",
"main-use-cases": "Note-taking;Journalling;As a knowledge base (including technical, non-fiction and encyclopaedic content)",
"other-use-cases": "",
"use-for-work-or-study": "No",
"share-wikis": "No, my TiddlyWiki is for personal use only",
"publish-to-web": "",
"publish-to-intranet": "",
"value-of-tw": "A space to write and link my thoughts.",
"tw-ability-level": "I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...);I am comfortable writing filter expressions",
"save-method": "Multi-file wiki served through Node.js",
"backup-method": "Git forge (GitHub, Gitea/Forgejo, GitLab)",
"diy-backup-info": "",
"wiki-setup-info": "<details><summary>Wiki Information</summary><pre><code>\nTiddlyWiki Version: 5.3.3\nCurrent palette: $:/palettes/Vanilla\nCurrent theme: $:/themes/tiddlywiki/vanilla\nCurrent layout: \nBrowser language setting: en-US\nDefault type for missing tiddlers: \nAuto save setting: yes\nCode wrapping setting: pre-wrap\nSticky titles setting: no\nSidebar layout setting: fluid-fixed\nAuto focus field setting for new tiddlers: title\nCurrent storyview setting: classic\nToolbar text setting: no\nToolbar icon setting: yes\nButton class setting: tc-btn-invisible\nNavigation address bar setting: no\nTiddler opening behaviour setting for navigations from outside the story river: top\nTiddler opening behaviour setting for navigations from within the story river: top\nCamelCase linking setting: disable\nKeyboard shortcuts that have been customised: $:/config/shortcuts/excise\nDisabled plugins: \nPlugins: \n $:/core - 5.3.3\n $:/plugins/danielo515/ContextPlugin - 2.1.0\n $:/plugins/flibbles/relink - 1.10.2\n $:/plugins/Gk0Wk/sidebar-resizer - 0.0.3\n $:/plugins/mklauber/math.js - 1.1.2\n $:/plugins/snowgoon88/edit-comptext - 0.8.1\n $:/plugins/sq/editor-autolist - 0.1.10\n $:/plugins/sq/Stories - 1.0.3\n $:/plugins/techlifeweb/xmlbuilder - 1.1.0\n $:/plugins/tiddlywiki/filesystem - 5.3.3\n $:/plugins/tiddlywiki/highlight - 5.3.3\n $:/plugins/tiddlywiki/tiddlyweb - 5.3.3\n $:/plugins/wikilabs/link-to-tabs - 2.0.1\n $:/temp/info-plugin - \n $:/themes/tiddlywiki/snowwhite - 5.3.3\n $:/themes/tiddlywiki/vanilla - 5.3.3\n</code></pre></details>",
"tw-customisations": "None",
"positive-about-future": "Yes",
"tw-future-confidence": "Yes",
"project-decision-trust": "Yes",
"project-strengths": "Producing, maintaining, and supporting a stable, self-contained product.",
"project-weaknesses": "Nothing comes to mind.",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00181",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -1,33 +0,0 @@
are-you-a-dev: No, I would not
backup-method: DIY (any other solution)
diy-backup-info: Self hosted cloud server.
first-heard-survey: Reddit
first-used-tw: 2015
joined-tw-community: No
main-use-cases: Note-taking;Task and project management (including CRMs);As a knowledge base (including technical, non-fiction and encyclopaedic content)
ok-to-publish: Yes, I am happy for my responses to be published
other-survey-source:
other-use-cases:
positive-about-future: Yes
project-decision-trust: Yes
project-strengths: Just love the project in general. It stays small and functional.
project-weaknesses: An official saving browser extension would be awesome.. esp with timimi being end of lifed due to Chrome pushing V3 and no updates in sight :(
publish-to-intranet: Yes, using a single-file wiki
publish-to-web: Not publishing to this location
published-plugin: No
save-method: Single-file wiki with custom saver (e.g. TiddlyPWA, Timimi, tw5-browser-nativesaver)
share-wikis: Yes, with multiple editors/administrators
started-tw-community:
tags: [[Community Survey 2025]]
title: Community Survey 2025 Answer 00182
tw-ability-level: I have customised TiddlyWiki through options and plugins
tw-customisations:
tw-future-confidence: Yes
use-discord:
use-for-work-or-study: Yes
use-github-discuss:
use-mailing-list:
use-reddit:
use-ttw:
value-of-tw: Mostly an easy repository of information.
wiki-setup-info: n/a

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "tiddlywiki.com",
"other-survey-source": "",
"are-you-a-dev": "Yes, I would",
"first-used-tw": "2014",
"joined-tw-community": "No",
"started-tw-community": "",
"use-ttw": "",
"use-mailing-list": "",
"use-reddit": "",
"use-discord": "",
"use-github-discuss": "",
"published-plugin": "No",
"main-use-cases": "As a knowledge base (including technical, non-fiction and encyclopaedic content);Other",
"other-use-cases": "mind mapping / chain of thoughts",
"use-for-work-or-study": "No",
"share-wikis": "No, my TiddlyWiki is for personal use only",
"publish-to-web": "",
"publish-to-intranet": "",
"value-of-tw": "free, private, open information store",
"tw-ability-level": "I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...)",
"save-method": "Multi-file wiki served through Node.js",
"backup-method": "Web or cloud hosting (other than TiddlyHost/TiddlySpot e.g. Netlify, AWS, OVH, Google Cloud...)",
"diy-backup-info": "",
"wiki-setup-info": "<details><summary>Wiki Information</summary><pre><code>\nTiddlyWiki Version: 5.3.7\nCurrent palette: $:/palettes/Vanilla\nCurrent theme: \nCurrent layout: $:/core/ui/PageTemplate\nBrowser language setting: en\nDefault type for missing tiddlers: \nAuto save setting: yes\nCode wrapping setting: pre-wrap\nSticky titles setting: no\nSidebar layout setting: fixed-fluid\nAuto focus field setting for new tiddlers: title\nCurrent storyview setting: top\nToolbar text setting: no\nToolbar icon setting: yes\nButton class setting: tc-btn-invisible\nNavigation address bar setting: no\nTiddler opening behaviour setting for navigations from outside the story river: top\nTiddler opening behaviour setting for navigations from within the story river: above\nCamelCase linking setting: disable\nKeyboard shortcuts that have been customised: \nDisabled plugins: $:/plugins/tesseract/tekan\nPlugins: \n $:/core - 5.3.7\n $:/plugins/felixhayashi/hotzone - 0.0.3\n $:/plugins/felixhayashi/tiddlymap - 0.17.16+10020\n $:/plugins/felixhayashi/topstoryview - 0.2.0\n $:/plugins/flibbles/vis-network - 9.1.3\n $:/plugins/sobjornstad/TiddlyRemember - 1.3.3\n $:/plugins/tiddlywiki/filesystem - 5.3.7\n $:/plugins/tiddlywiki/highlight - 5.3.7\n $:/plugins/tiddlywiki/tiddlyweb - 5.3.7\n $:/temp/info-plugin - \n $:/themes/tiddlywiki/snowwhite - 5.3.7\n $:/themes/tiddlywiki/vanilla - 5.3.7\n</code></pre></details>",
"tw-customisations": "",
"positive-about-future": "Yes",
"tw-future-confidence": "Yes",
"project-decision-trust": "Yes",
"project-strengths": "keeping the software self contained and with no dependencies",
"project-weaknesses": "simplifying the customisation learning curve for none programmer",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00183",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "tiddlywiki.com",
"other-survey-source": "",
"are-you-a-dev": "No, I would not",
"first-used-tw": "2015",
"joined-tw-community": "No",
"started-tw-community": "",
"use-ttw": "",
"use-mailing-list": "",
"use-reddit": "",
"use-discord": "",
"use-github-discuss": "",
"published-plugin": "No",
"main-use-cases": "Note-taking;Task and project management (including CRMs);As a knowledge base (including technical, non-fiction and encyclopaedic content);Other",
"other-use-cases": "Questionnaire",
"use-for-work-or-study": "Yes",
"share-wikis": "No, but I may export content into other formats and share individual tiddlers, the whole wiki, or an extract of the wiki",
"publish-to-web": "",
"publish-to-intranet": "",
"value-of-tw": "It is a simple way of organising information and to make it addressable without needing programming skills and without being dependent on other proprietary software. The addons are very valuable and the entire system is free and open source.",
"tw-ability-level": "I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...);I am comfortable writing filter expressions;I have written custom HTML;I have written custom CSS styles",
"save-method": "Single-file wiki through web browser with Download Saver (default saving mechanism);Single-file wiki with custom saver (e.g. TiddlyPWA, Timimi, tw5-browser-nativesaver);Single-file wiki with TiddlyDesktop;Single-file wiki third-party mobile app (e.g. Tiddloid, Quine)",
"backup-method": "Web or cloud hosting (other than TiddlyHost/TiddlySpot e.g. Netlify, AWS, OVH, Google Cloud...)",
"diy-backup-info": "",
"wiki-setup-info": "<details><summary>Wiki Information</summary><pre><code>\nTiddlyWiki Version: 5.3.7\nCurrent palette: $:/themes/jd/Material/Palette/MaterialLightBase\nCurrent theme: $:/themes/jd/Material\nCurrent layout: \nBrowser language setting: de-DE\nDefault type for missing tiddlers: \nAuto save setting: yes\nCode wrapping setting: pre-wrap\nSticky titles setting: yes\nSidebar layout setting: fluid-fixed\nAuto focus field setting for new tiddlers: title\nCurrent storyview setting: zoomin\nToolbar text setting: no\nToolbar icon setting: yes\nButton class setting: tc-btn-boxed\nNavigation address bar setting: no\nTiddler opening behaviour setting for navigations from outside the story river: top\nTiddler opening behaviour setting for navigations from within the story river: below\nCamelCase linking setting: enable\nKeyboard shortcuts that have been customised: \nDisabled plugins: \nPlugins: \n $:/core - 5.3.7\n $:/languages/de-DE - 5.3.7\n $:/plugins/BurningTree/hammerwidgets - 0.1.0\n $:/plugins/custom/setfield - 0.0.5\n $:/plugins/danielo/encryptTiddler - 2.1\n $:/plugins/danielo515/ContextPlugin - 2.1.0\n $:/plugins/danielo515/encryptTiddler - 2.3\n $:/plugins/felixhayashi/hotzone - 0.0.3\n $:/plugins/felixhayashi/tiddlymap - 0.17.14+10018\n $:/plugins/felixhayashi/topstoryview - 0.2.0\n $:/plugins/felixhayashi/vis - \n $:/plugins/inmysocks/MathyThing - 0.2.1\n $:/plugins/inmysocks/randVal - 0.1.3\n $:/plugins/rboue/SocialCalc - 1.0.0\n $:/plugins/tiddlywiki/hammerjs - 5.3.7\n $:/plugins/tiddlywiki/katex - 5.3.7\n $:/plugins/tiddlywiki/tiddloid-tweaks - 1.2.0\n $:/temp/info-plugin - \n $:/themes/jd/Material - 0.4.14\n $:/themes/tiddlywiki/centralised - 5.3.7\n $:/themes/tiddlywiki/readonly - 5.3.7\n $:/themes/tiddlywiki/seamless - 5.3.7\n $:/themes/tiddlywiki/snowwhite - 5.3.7\n $:/themes/tiddlywiki/vanilla - 5.3.7\n</code></pre></details>",
"tw-customisations": "Stylesheets and macros.",
"positive-about-future": "Yes",
"tw-future-confidence": "Yes",
"project-decision-trust": "Yes",
"project-strengths": "From my perspective, everything. I can't see anything negative.",
"project-weaknesses": "I will continue to use TiddlyWiki massively. It would be sad, if TiddlyWiki would be discontinued. I am no programmer, just a power user, so it is difficult for me to contribute anything to the project that would be valuable for others. From my perspective you do a fantastic job. I have no idea what could be done better.",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00184",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "tiddlywiki.com",
"other-survey-source": "",
"are-you-a-dev": "Yes, I would",
"first-used-tw": "2010",
"joined-tw-community": "Yes",
"started-tw-community": "2020",
"use-ttw": "I read and post in this community",
"use-mailing-list": "I do not engage with this community",
"use-reddit": "I do not engage with this community",
"use-discord": "I do not engage with this community",
"use-github-discuss": "I read and post in this community",
"published-plugin": "Yes",
"main-use-cases": "Note-taking;Journalling;Task and project management (including CRMs);As a knowledge base (including technical, non-fiction and encyclopaedic content);Producing/publishing interactive fiction;Narrative fiction writing (either supporting its creation or directly writing in TiddlyWiki);Other",
"other-use-cases": "prototyping Interpersonal Wikis, linguistic revitalizing on Colombian Amazonas and other research projects.",
"use-for-work-or-study": "Yes",
"share-wikis": "Yes, and I am the only editor/administrator of my wiki(s)",
"publish-to-web": "Yes, using a single-file wiki",
"publish-to-intranet": "Yes, using a single-file wiki",
"value-of-tw": "It's a flexible metatool to adapt to my needs for quickly prototyping that is usually good enough. As I said in the forum, the problem is related with increased complexity of usage that makes the particular knowledge of TW low transferable to other more complex contexts.",
"tw-ability-level": "I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...);I am comfortable writing filter expressions",
"save-method": "Single-file wiki with custom saver (e.g. TiddlyPWA, Timimi, tw5-browser-nativesaver)",
"backup-method": "Git forge (GitHub, Gitea/Forgejo, GitLab)",
"diy-backup-info": "",
"wiki-setup-info": "<details><summary>Wiki Information</summary><pre><code>\nTiddlyWiki Version: 5.3.6\nCurrent palette: $:/palettes/DesertSand\nCurrent theme: $:/themes/nico/notebook\nCurrent layout: \nBrowser language setting: en-US\nDefault type for missing tiddlers: \nAuto save setting: no\nCode wrapping setting: pre-wrap\nSticky titles setting: no\nSidebar layout setting: fixed-fluid\nAuto focus field setting for new tiddlers: title\nCurrent storyview setting: classic\nToolbar text setting: no\nToolbar icon setting: yes\nButton class setting: tc-btn-invisible\nNavigation address bar setting: no\nTiddler opening behaviour setting for navigations from outside the story river: top\nTiddler opening behaviour setting for navigations from within the story river: below\nCamelCase linking setting: disable\nKeyboard shortcuts that have been customised: $:/config/shortcuts/divisor\nDisabled plugins: \nPlugins: \n $:/ak/plugins/TWCrossLinks - 0.1.19\n $:/core - 5.3.6\n $:/languages/es-ES - 5.3.6\n $:/plugins/adithyab/cmplus - 0.2.2\n $:/plugins/flibbles/relink - 2.1.1\n $:/plugins/Gk0Wk/echarts - 0.0.4+1\n $:/plugins/kookma/refnotes - 1.7.3\n $:/plugins/kookma/shiraz - 2.4.4\n $:/plugins/linonetwo/markdown-transformer - 0.1.3\n $:/plugins/nico/notebook-mobile - 1.0.0\n $:/plugins/nico/projectify - 0.14.0\n $:/plugins/nico/projectify-es-ES - 0.13.1\n $:/plugins/sq/spotlight - 0.0.5\n $:/plugins/sycom/leaflet - 0.8.6\n $:/plugins/telmiger/details - 0.7.5\n $:/plugins/telmiger/EditButtons - 1.0.6\n $:/plugins/telmiger/HarveyBalls - 0.1.0\n $:/plugins/telmiger/simple-search - 1.0.24\n $:/plugins/tiddlywiki/codemirror - 5.3.6\n $:/plugins/tiddlywiki/codemirror-closebrackets - 5.3.6\n $:/plugins/tiddlywiki/highlight - 5.3.6\n $:/plugins/tiddlywiki/markdown - 5.3.6\n $:/plugins/tobibeer/split - 0.8.0\n $:/temp/info-plugin - \n $:/themes/nico/notebook - 1.4.1\n $:/themes/tiddlywiki/snowwhite - 5.3.6\n $:/themes/tiddlywiki/starlight - 5.3.6\n $:/themes/tiddlywiki/vanilla - 5.3.6\n</code></pre></details>",
"tw-customisations": "This couple of wikis reflect most of my customizations taken from the community in the form of a custom template + plugins + usage scenario:\n\nhttps://cartofonia-amanecer-la-palabra.tiddlyhost.com/",
"positive-about-future": "Yes",
"tw-future-confidence": "No",
"project-decision-trust": "Yes",
"project-strengths": "I think the community is pretty supportive and welcoming, starting with Jeremy and all the usual folks in the forum. I think that keeping a different identity that sets TW apart from other PKMs and Wikis is important and has been constructed over all those years.",
"project-weaknesses": "I don't know how governance works for the project and that could be more explicit. Also the present discussion on prepackaged editions beyond empty.html is important and a way to be more approachable for new people. \n\nI imagine myself, in the mid/long term, leaving TiddlyWiki for Cardumem, my own wiki engine inspired by TW, but reimagined as an hypermedia system. More details here:\n\nhttps://offray.tiddlyhost.com/#Cardumem%2FEn",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00185",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "Talk TiddlyWiki",
"other-survey-source": "",
"are-you-a-dev": "No, I would not",
"first-used-tw": "2013",
"joined-tw-community": "Yes",
"started-tw-community": "2024",
"use-ttw": "I read and post in this community",
"use-mailing-list": "I read/lurk, but do not post",
"use-reddit": "I read/lurk, but do not post",
"use-discord": "I do not engage with this community",
"use-github-discuss": "I do not engage with this community",
"published-plugin": "Yes",
"main-use-cases": "Note-taking;Journalling;Task and project management (including CRMs)",
"other-use-cases": "",
"use-for-work-or-study": "Yes",
"share-wikis": "No, but I may export content into other formats and share individual tiddlers, the whole wiki, or an extract of the wiki",
"publish-to-web": "",
"publish-to-intranet": "",
"value-of-tw": "TiddlyWiki is amazing to work with, and developing with it can even become a bit addictive. The concept is extremely challenging for non-programmers, but it also offers unexpected moments of success.",
"tw-ability-level": "I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...);I am comfortable writing filter expressions;I have written custom HTML;I have written custom CSS styles",
"save-method": "Single-file wiki through web browser with Download Saver (default saving mechanism)",
"backup-method": "DIY (any other solution);No automatic sync across my devices",
"diy-backup-info": "I use TiddlyWiki on a USB stick with a backup folder, and from time to time, I back up the USB stick to my computer. Its truly old-school, but it works good enough.",
"wiki-setup-info": "<details><summary>Wiki Information</summary><pre><code>\nTiddlyWiki Version: 5.3.7\nCurrent palette: $:/palettes/Vanilla\nCurrent theme: $:/themes/tiddlywiki/snowwhite\nCurrent layout: \nBrowser language setting: de\nDefault type for missing tiddlers: \nAuto save setting: yes\nCode wrapping setting: pre-wrap\nSticky titles setting: no\nSidebar layout setting: fluid-fixed\nAuto focus field setting for new tiddlers: title\nCurrent storyview setting: classic\nToolbar text setting: no\nToolbar icon setting: yes\nButton class setting: tc-btn-invisible\nNavigation address bar setting: no\nTiddler opening behaviour setting for navigations from outside the story river: bottom\nTiddler opening behaviour setting for navigations from within the story river: bottom\nCamelCase linking setting: disable\nKeyboard shortcuts that have been customised: \nDisabled plugins: $:/plugins/danielo515/2click2edit,$:/plugins/tiddlywiki/github-fork-ribbon,$:/plugins/tiddlywiki/text-slicer,$:/plugins/wikilabs/link-to-tabs\nPlugins: \n $:/core - 5.3.7\n $:/languages/de-DE - 5.3.7\n $:/plugins/adithyab/cmplus - 0.2.2\n $:/plugins/kookma/commander - 2.1.14\n $:/plugins/tiddlywiki/codemirror - 5.3.7\n $:/plugins/tiddlywiki/sax - 5.3.7\n $:/plugins/wikilabs/edit-tabs - 2.0.1\n $:/temp/info-plugin - \n $:/themes/tiddlywiki/readonly - 5.3.7\n $:/themes/tiddlywiki/seamless - 5.3.7\n $:/themes/tiddlywiki/snowwhite - 5.3.7\n $:/themes/tiddlywiki/tight - 5.3.7\n $:/themes/tiddlywiki/vanilla - 5.3.7\n</code></pre></details>",
"tw-customisations": "",
"positive-about-future": "Yes",
"tw-future-confidence": "Yes",
"project-decision-trust": "Yes",
"project-strengths": "almost everything!!! The discussions, the leadership of the project, the very helpful community, the minimalist empty layout, and the overall design are all strong aspects of TiddlyWiki. One thing that would be very useful is a centralized 'how-to' website summarizing tips and tricks. Another positive aspect is the willingness to break backward compatibility when necessary — software needs the freedom to evolve. ;)",
"project-weaknesses": "The built-in editor doesn't support syntax highlighting!, and there's currently no dedicated theme for CodeMirror, even though the older version of TiddlyWiki 2.x included one. Additionally, Markdown integration remains limited and could benefit from deeper support. File saving continues to be a major pain point when recommending TiddlyWiki to others—improper saving often goes unnoticed, resulting in potential data loss.",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00186",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "Talk TiddlyWiki",
"other-survey-source": "",
"are-you-a-dev": "No, I would not",
"first-used-tw": "",
"joined-tw-community": "No",
"started-tw-community": "",
"use-ttw": "",
"use-mailing-list": "",
"use-reddit": "",
"use-discord": "",
"use-github-discuss": "",
"published-plugin": "No",
"main-use-cases": "Note-taking;Journalling;As a knowledge base (including technical, non-fiction and encyclopaedic content);Producing/publishing interactive fiction;Narrative fiction writing (either supporting its creation or directly writing in TiddlyWiki);Other",
"other-use-cases": "Application for my business, training/management/utilization tool for clients",
"use-for-work-or-study": "Yes",
"share-wikis": "Yes, and I am the only editor/administrator of my wiki(s)",
"publish-to-web": "Yes, using a single-file wiki;Not publishing to this location",
"publish-to-intranet": "Yes, served through Node.js",
"value-of-tw": "Flexibility, adaptability, and ease of use. Once understood it can be used for just about any idea. I have always used in work context to document workflow; transition platform to turn consulting documentation over to clients, build knowledgebases; managing my business. It's fun",
"tw-ability-level": "I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...);I am comfortable writing filter expressions;I have written custom HTML;I have written custom CSS styles;I have written custom JavaScript",
"save-method": "Multi-file wiki served through Node.js",
"backup-method": "DIY (any other solution)",
"diy-backup-info": "I run Node on Ubuntu and do filesystem backups using bash scripts. I do daily/monthly backups of my wiki directory (12 separate wiki's) and purge my daily on a 7 day rotation and. I have is set to run a cron job and report update view email.",
"wiki-setup-info": "",
"tw-customisations": "",
"positive-about-future": "Yes",
"tw-future-confidence": "Yes",
"project-decision-trust": "Yes",
"project-strengths": "I appreciate how active and committed the community shows up. The willingness of others to share and support others. I have not contributed to the community...I'm not sure how I can contribute, but I have learned so much from the community.",
"project-weaknesses": "Having more educational and tutorial opportunities, esp. around scripting. (Create a Tiddlywiki Design Patterns document with lots of examples...that would be great.) Having more real world examples in the Reference section on the tiddlywiki.com site. I appreciate the new structures being added: if/then/else constructs, etc. \n\nFinding out how others are using Tiddlywiki has stimulated my thinking. The 2nd Brain contribution have inspired my own work in that area.",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00187",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -1,33 +0,0 @@
are-you-a-dev: No, I would not
backup-method: Consumer online storage (e.g. Google Drive, Dropbox)
diy-backup-info:
first-heard-survey: Talk TiddlyWiki
first-used-tw: 2025
joined-tw-community: No
main-use-cases: Note-taking;Journalling;Task and project management (including CRMs);As a knowledge base (including technical, non-fiction and encyclopaedic content)
ok-to-publish: Yes, I am happy for my responses to be published
other-survey-source:
other-use-cases:
positive-about-future: Yes
project-decision-trust: Yes
project-strengths: The brief overview of the apps is nice.
project-weaknesses: Documentation. Having most of the apps made by the community is fine but it would be great if the documentation was more centralized. Or maybe more examples posted on how to setup an app. I am pretty new to TiddlyWiki, but I find it hard to find information. Or at least to get help. Maybe the community isn't very involved?? An official Discord server might work better for people to discuss issues, projects, customizations.
publish-to-intranet:
publish-to-web:
published-plugin: No
save-method: Single-file wiki with TiddlyDesktop
share-wikis: No, my TiddlyWiki is for personal use only
started-tw-community:
tags: [[Community Survey 2025]]
title: Community Survey 2025 Answer 00188
tw-ability-level: My use is basic; I use TiddlyWiki in a configuration close to standard, without plugins
tw-customisations:
tw-future-confidence: Yes
use-discord:
use-for-work-or-study: No
use-github-discuss:
use-mailing-list:
use-reddit:
use-ttw:
value-of-tw: I control the data. Makes me feel better. It is easy to search.
wiki-setup-info: I have been using TiddlyDesktop until recently. I was storing the wiki in OneDrive but if I forgot to close it on one computer and opened it on another they would be out of sync. I have been trying to get TiddlyPWA up and running but it is having trouble creating the database in deno. So right now I have it in Tiddly Bob. It is working but I would rather have a separate app that I use instead of having it in the browser.

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "tiddlywiki.com",
"other-survey-source": "",
"are-you-a-dev": "No, I would not",
"first-used-tw": "2005",
"joined-tw-community": "No",
"started-tw-community": "",
"use-ttw": "",
"use-mailing-list": "",
"use-reddit": "",
"use-discord": "",
"use-github-discuss": "",
"published-plugin": "No",
"main-use-cases": "As a knowledge base (including technical, non-fiction and encyclopaedic content)",
"other-use-cases": "",
"use-for-work-or-study": "No",
"share-wikis": "Yes, and I am the only editor/administrator of my wiki(s)",
"publish-to-web": "Yes, using a single-file wiki",
"publish-to-intranet": "Yes, using a single-file wiki",
"value-of-tw": "I have several TWs, I used constantly",
"tw-ability-level": "I have customised TiddlyWiki through options and plugins",
"save-method": "Single-file wiki with TiddlyDesktop;Single-file wiki third-party mobile app (e.g. Tiddloid, Quine)",
"backup-method": "Consumer online storage (e.g. Google Drive, Dropbox);DIY (any other solution)",
"diy-backup-info": "Rsync with several usb disks",
"wiki-setup-info": "",
"tw-customisations": "Plugins:\nDisclosure HTML element\nTristate Sidebar\nHighlight-searched-text\nLayout tweaks",
"positive-about-future": "Yes",
"tw-future-confidence": "Yes",
"project-decision-trust": "Yes",
"project-strengths": "I dont know. Its super util for me",
"project-weaknesses": "I dont know",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00189",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -1,33 +0,0 @@
are-you-a-dev: No, I would not
backup-method: N/A - I keep my wiki on a single system
diy-backup-info:
first-heard-survey: tiddlywiki.com
first-used-tw: 2018
joined-tw-community: No
main-use-cases: Note-taking;As a knowledge base (including technical, non-fiction and encyclopaedic content)
ok-to-publish: Yes, I am happy for my responses to be published
other-survey-source:
other-use-cases:
positive-about-future: Yes
project-decision-trust: Yes
project-strengths: Not breaking functionality, good documentation
project-weaknesses: examples for complicated tasks
publish-to-intranet: Yes, using a single-file wiki
publish-to-web: Not publishing to this location
published-plugin: No
save-method: Single-file wiki through web browser with Download Saver (default saving mechanism)
share-wikis: Yes, with multiple editors/administrators
started-tw-community:
tags: [[Community Survey 2025]]
title: Community Survey 2025 Answer 00190
tw-ability-level: I have customised TiddlyWiki through options and plugins
tw-customisations:
tw-future-confidence: Yes
use-discord:
use-for-work-or-study: Yes
use-github-discuss:
use-mailing-list:
use-reddit:
use-ttw:
value-of-tw: Organised notes and knowledge base with many visualisation options. Much more human brain friendly than browsing files and folders, or spreadsheets.
wiki-setup-info: did not work

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "tiddlywiki.com",
"other-survey-source": "",
"are-you-a-dev": "Yes, I would",
"first-used-tw": "2018",
"joined-tw-community": "No",
"started-tw-community": "",
"use-ttw": "",
"use-mailing-list": "",
"use-reddit": "",
"use-discord": "",
"use-github-discuss": "",
"published-plugin": "No",
"main-use-cases": "Note-taking;As a knowledge base (including technical, non-fiction and encyclopaedic content)",
"other-use-cases": "",
"use-for-work-or-study": "No",
"share-wikis": "Yes, and I am the only editor/administrator of my wiki(s)",
"publish-to-web": "Yes, served through Node.js",
"publish-to-intranet": "Not publishing to this location",
"value-of-tw": "It powers my personal wiki. It's where I keep notes, bookmarks, and keep track books I've read and their highlights.",
"tw-ability-level": "I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...);I have written custom HTML;I have written custom CSS styles",
"save-method": "Multi-file wiki served through Node.js",
"backup-method": "Git forge (GitHub, Gitea/Forgejo, GitLab);Web or cloud hosting (other than TiddlyHost/TiddlySpot e.g. Netlify, AWS, OVH, Google Cloud...)",
"diy-backup-info": "",
"wiki-setup-info": "<details><summary>Wiki Information</summary><pre><code>\nTiddlyWiki Version: 5.3.8\nCurrent palette: $:/palettes/personal\nCurrent theme: $:/themes/tiddlywiki/vanilla\nCurrent layout: \nBrowser language setting: en-US\nDefault type for missing tiddlers: \nAuto save setting: yes\nCode wrapping setting: pre-wrap\nSticky titles setting: yes\nSidebar layout setting: fluid-fixed\nAuto focus field setting for new tiddlers: title\nCurrent storyview setting: classic\nToolbar text setting: no\nToolbar icon setting: yes\nButton class setting: tc-btn-invisible\nNavigation address bar setting: permalink\nTiddler opening behaviour setting for navigations from outside the story river: top\nTiddler opening behaviour setting for navigations from within the story river: below\nCamelCase linking setting: disable\nKeyboard shortcuts that have been customised: $:/config/shortcuts-mac/save-tiddler\nDisabled plugins: \nPlugins: \n $:/core - 5.3.8\n $:/plugins/tiddlywiki/filesystem - 5.3.8\n $:/plugins/tiddlywiki/highlight - 5.3.8\n $:/plugins/tiddlywiki/markdown - 5.1.23\n $:/plugins/tiddlywiki/tiddlyweb - 5.3.8\n $:/temp/info-plugin - \n $:/themes/tiddlywiki/snowwhite - 5.3.8\n $:/themes/tiddlywiki/vanilla - 5.3.8\n</code></pre></details>",
"tw-customisations": "I override some styles with a custom CSS tiddler, I attempt to keep bots off my wiki by adding a `<meta>` tag to `<head>`.",
"positive-about-future": "Yes",
"tw-future-confidence": "Yes",
"project-decision-trust": "Yes",
"project-strengths": "* Frequent releases.\n* Moving from Google Groups to Discourse (Talk TiddlyWiki).\n* Doing community surveys. :)\n* Maintaining a Mastodon account.",
"project-weaknesses": "* iOS and mobile browser support. There has been a bug for a while where typing in the text field renders \"Internal JavaScript Error\"\n* I think Node.JS documentation could be improved, it feels fairly light given the power of the hosted option. I would specifically like improvement around hosting multiple wikis and sharing Tiddlers between wikis.\n* Overall I would love to try contributing, but feel intimidated by the scope and history of TiddlyWiki.",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00191",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "tiddlywiki.com",
"other-survey-source": "",
"are-you-a-dev": "No, I would not",
"first-used-tw": "2018",
"joined-tw-community": "Yes",
"started-tw-community": "2018",
"use-ttw": "I read and post in this community",
"use-mailing-list": "I read/lurk, but do not post",
"use-reddit": "I do not engage with this community",
"use-discord": "I do not engage with this community",
"use-github-discuss": "I do not engage with this community",
"published-plugin": "No",
"main-use-cases": "As a knowledge base (including technical, non-fiction and encyclopaedic content)",
"other-use-cases": "",
"use-for-work-or-study": "Not applicable (as retired, etc)",
"share-wikis": "No, but I may export content into other formats and share individual tiddlers, the whole wiki, or an extract of the wiki",
"publish-to-web": "",
"publish-to-intranet": "",
"value-of-tw": "A flexible platform for my information needs.",
"tw-ability-level": "I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...)",
"save-method": "Multi-file wiki served through Node.js",
"backup-method": "TiddlySpot / TiddlyHost;Web or cloud hosting (other than TiddlyHost/TiddlySpot e.g. Netlify, AWS, OVH, Google Cloud...)",
"diy-backup-info": "",
"wiki-setup-info": "<details><summary>Wiki Information</summary><pre><code>\nTiddlyWiki Version: 5.3.7\nCurrent palette: $:/palettes/Vanilla\nCurrent theme: $:/themes/tiddlywiki/vanilla\nCurrent layout: \nBrowser language setting: en-US\nDefault type for missing tiddlers: \nAuto save setting: yes\nCode wrapping setting: pre-wrap\nSticky titles setting: no\nSidebar layout setting: fluid-fixed\nAuto focus field setting for new tiddlers: title\nCurrent storyview setting: zoomin\nToolbar text setting: no\nToolbar icon setting: yes\nButton class setting: tc-btn-invisible\nNavigation address bar setting: no\nTiddler opening behaviour setting for navigations from outside the story river: top\nTiddler opening behaviour setting for navigations from within the story river: top\nCamelCase linking setting: disable\nKeyboard shortcuts that have been customised: \nDisabled plugins: \nPlugins: \n $:/core - 5.3.7\n $:/plugins/danielo515/ContextPlugin - 2.1.0\n $:/plugins/Gk0Wk/sidebar-resizer - 0.0.3\n $:/plugins/kookma/commander - 2.1.2\n $:/plugins/kookma/refnotes - 1.8.5\n $:/plugins/kookma/shiraz - 2.7.5\n $:/plugins/snowgoon88/edit-comptext - 0.8.1\n $:/plugins/sq/editor-autolist - 0.1.10\n $:/plugins/sq/macy - 0.0.9\n $:/plugins/sq/spotlight - 0.0.4\n $:/plugins/sq/Stories - 1.0.3\n $:/plugins/sycom/leaflet - 0.8.6\n $:/plugins/tiddlywiki/filesystem - 5.3.7\n $:/plugins/tiddlywiki/highlight - 5.3.7\n $:/plugins/tiddlywiki/tiddlyweb - 5.3.7\n $:/plugins/wikilabs/link-to-tabs - 2.0.1\n $:/temp/info-plugin - \n $:/themes/tiddlywiki/snowwhite - 5.3.7\n $:/themes/tiddlywiki/vanilla - 5.3.7\n</code></pre></details>",
"tw-customisations": "",
"positive-about-future": "Yes",
"tw-future-confidence": "Yes",
"project-decision-trust": "Yes",
"project-strengths": "Community support",
"project-weaknesses": "More and better 'How To' guides rather than 'developer focussed' documentation.",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00192",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "tiddlywiki.com",
"other-survey-source": "",
"are-you-a-dev": "No, I would not",
"first-used-tw": "2007",
"joined-tw-community": "Yes",
"started-tw-community": "2017",
"use-ttw": "I read and post in this community",
"use-mailing-list": "I read/lurk, but do not post",
"use-reddit": "I do not engage with this community",
"use-discord": "I do not engage with this community",
"use-github-discuss": "I do not engage with this community",
"published-plugin": "No",
"main-use-cases": "Note-taking;As a knowledge base (including technical, non-fiction and encyclopaedic content);Other",
"other-use-cases": "I try to learn how it works (HTML5, JS, TiddlyWiki itself and several tools for it)",
"use-for-work-or-study": "Yes",
"share-wikis": "No, but I may export content into other formats and share individual tiddlers, the whole wiki, or an extract of the wiki",
"publish-to-web": "",
"publish-to-intranet": "",
"value-of-tw": "Several years ago, I had using TW to organized my part of work in a bigger project. Now I'm looking for an easy GTD tool, and I'm thinking TW would be fine, but I need it in German language and the translation is hard to me.",
"tw-ability-level": "I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...);I have written custom HTML;I have written custom JavaScript",
"save-method": "Single-file wiki with custom saver (e.g. TiddlyPWA, Timimi, tw5-browser-nativesaver);Single-file wiki third-party mobile app (e.g. Tiddloid, Quine)",
"backup-method": "DIY (any other solution)",
"diy-backup-info": "Normally I'm using file-backups by Mario Pietsch within my Firefox browser and get backups to my NAS. Also, sometimes I'm using a USB drive or send it in an e-mail.",
"wiki-setup-info": "<details><summary>Wiki Information</summary><pre><code>\nTiddlyWiki Version: 5.3.8\nCurrent palette: $:/palettes/Vanilla\nCurrent theme: \nCurrent layout: \nBrowser language setting: de\nDefault type for missing tiddlers: \nAuto save setting: yes\nCode wrapping setting: pre-wrap\nSticky titles setting: no\nSidebar layout setting: fluid-fixed\nAuto focus field setting for new tiddlers: title\nCurrent storyview setting: classic\nToolbar text setting: no\nToolbar icon setting: yes\nButton class setting: tc-btn-invisible\nNavigation address bar setting: no\nTiddler opening behaviour setting for navigations from outside the story river: top\nTiddler opening behaviour setting for navigations from within the story river: below\nCamelCase linking setting: disable\nKeyboard shortcuts that have been customised: \nDisabled plugins: \nPlugins: \n $:/core - 5.3.8\n $:/languages/de-DE - 5.3.8\n $:/plugins/.jcs/RefLinks - 0.0.6\n $:/plugins/danielo515/ContextPlugin - 2.1.0\n $:/plugins/flibbles/relink - 2.5.2\n $:/plugins/flibbles/relink-fieldnames - 2.5.2\n $:/plugins/flibbles/relink-markdown - 2.5.2\n $:/plugins/flibbles/relink-titles - 2.5.2\n $:/plugins/flibbles/relink-variables - 2.5.2\n $:/plugins/wikilabs/link-to-tabs - 3.0.1\n $:/temp/info-plugin - \n $:/themes/tiddlywiki/snowwhite - 5.3.8\n $:/themes/tiddlywiki/vanilla - 5.3.8\n</code></pre></details>",
"tw-customisations": "",
"positive-about-future": "Yes",
"tw-future-confidence": "Yes",
"project-decision-trust": "Yes",
"project-strengths": "It's free software - that's perhaps the best thing about it. It can be adapted to your own needs. There is also a community that is happy to help and answers questions. TiddlyWiki is much more than the online notebook for which it is pretending. It is a universal tool that you can learn to deal with HTML and JS.",
"project-weaknesses": "TW is the best tool I'd got since I'd used it for the first time. I've tested several others, but I always come back to it, even it's hard to me, to struggle with the English language. Yes, there is a German translation and a little introduction, but that isn't enough to get a useful TW. So it's still necessary always to use the original documentation and the English-speaking community. Yes, Google can help, but a German-speaking community would make it easier to me.",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00193",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -1,33 +0,0 @@
are-you-a-dev: Yes, I would
backup-method: TiddlySpot / TiddlyHost;N/A - I keep my wiki on a single system
diy-backup-info:
first-heard-survey: tiddlywiki.com
first-used-tw: 2005
joined-tw-community: Yes
main-use-cases: Note-taking;Journalling;Task and project management (including CRMs);Programming
ok-to-publish: Yes, I am happy for my responses to be published
other-survey-source:
other-use-cases:
positive-about-future: Yes
project-decision-trust: Yes
project-strengths: Very transparent in making decisions about the project.
project-weaknesses: Understanding how the project will continue if/when Jeremy moves on.
publish-to-intranet:
publish-to-web:
published-plugin: No
save-method: Single-file wiki with custom saver (e.g. TiddlyPWA, Timimi, tw5-browser-nativesaver)
share-wikis: No, but I may export content into other formats and share individual tiddlers, the whole wiki, or an extract of the wiki
started-tw-community: 2024
tags: [[Community Survey 2025]]
title: Community Survey 2025 Answer 00194
tw-ability-level: I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...)
tw-customisations:
tw-future-confidence: Yes
use-discord: I do not engage with this community
use-for-work-or-study: Yes
use-github-discuss: I read/lurk, but do not post
use-mailing-list: I do not engage with this community
use-reddit: I read/lurk, but do not post
use-ttw: I read and post in this community
value-of-tw: Tiddlywiki provides a way for me to capture notes in a free form way and then reorganize them (transclusions!) easily.
wiki-setup-info:

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "Other",
"other-survey-source": "Friend who uses tiddlywiki shared the link with me",
"are-you-a-dev": "Yes, I would",
"first-used-tw": "2017",
"joined-tw-community": "Yes",
"started-tw-community": "2018",
"use-ttw": "I read/lurk, but do not post",
"use-mailing-list": "I read/lurk, but do not post",
"use-reddit": "I read/lurk, but do not post",
"use-discord": "I read/lurk, but do not post",
"use-github-discuss": "I do not engage with this community",
"published-plugin": "Yes",
"main-use-cases": "Note-taking;Journalling;Programming;Other",
"other-use-cases": "I use it as a tiny art gallery website (very minimal CSS, only one tiddler open at a time)",
"use-for-work-or-study": "No",
"share-wikis": "Yes, and I am the only editor/administrator of my wiki(s)",
"publish-to-web": "Yes, using a single-file wiki;Yes, served through Node.js",
"publish-to-intranet": "Yes, using a single-file wiki",
"value-of-tw": "TiddlyWiki provides a way for me to serve my personal website content in a package that lets people download it as a single file, which is quite important to me. I do wish the Node.js lazy loading features were actually viable (last I looked primarily search didn't function).",
"tw-ability-level": "I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...);I am comfortable writing filter expressions;I have written custom HTML;I have written custom CSS styles;I have written custom JavaScript",
"save-method": "Multi-file wiki served through Node.js",
"backup-method": "DIY (any other solution)",
"diy-backup-info": "My primary note storage is on my NAS, with SyncThing to synchronize it across devices eg. phone, laptop. This backs up my _notes_ which I edit with various other tools, not TiddlyWiki, and TiddlyWiki is a publishing layer on top.",
"wiki-setup-info": "<details><summary>Wiki Information</summary><pre><code>\nTiddlyWiki Version: 5.3.3\nCurrent palette: $:/palettes/Vanilla\nCurrent theme: \nCurrent layout: \nBrowser language setting: en-US\nDefault type for missing tiddlers: \nAuto save setting: yes\nCode wrapping setting: pre-wrap\nSticky titles setting: no\nSidebar layout setting: fixed-fluid\nAuto focus field setting for new tiddlers: title\nCurrent storyview setting: classic\nToolbar text setting: no\nToolbar icon setting: yes\nButton class setting: tc-btn-invisible\nNavigation address bar setting: no\nTiddler opening behaviour setting for navigations from outside the story river: top\nTiddler opening behaviour setting for navigations from within the story river: below\nCamelCase linking setting: disable\nKeyboard shortcuts that have been customised: \nDisabled plugins: $:/plugins/noahlange/markdown-plus,$:/plugins/rmnvsl/krystal\nPlugins: \n $:/core - 5.3.3\n $:/plugins/benwebber/css-palette - 0.3.0\n $:/plugins/noahlange/monaco - 0.5.0\n $:/plugins/oeyoews/markdown-extensions-startup - 0.0.2\n $:/plugins/tiddlywiki/highlight - 5.3.3\n $:/plugins/tiddlywiki/markdown - 5.3.3\n $:/temp/info-plugin - \n $:/themes/tiddlywiki/snowwhite - 5.3.3\n $:/themes/tiddlywiki/vanilla - 5.3.3\n</code></pre></details>",
"tw-customisations": "- \"New Tiddlers\" sidebar customization\n- SO MUCH CSS customization\n- Because noahlange/tiddlymark exists, I can render my Obsidian vault as a single file wiki, still using TW in a way w/this.\n- I had to edit Core TW's JavaScript to enable Obsidian Style [[wiki|pretty links]].",
"positive-about-future": "Yes",
"tw-future-confidence": "Yes",
"project-decision-trust": "Yes",
"project-strengths": "I'm glad TW is still under development, and I'm glad it still has a healthy community of users - even though I don't use TiddlyWiki directly anymore, there's still many things (abstraction from the file system, hackability, ability to produce a single HTML file that can function like a \"book\" for my writing that can go anywhere and has longevity) that I appreciate about it, and while I couldn't go back now, I could see a future TW with improvements winning me back!",
"project-weaknesses": "After converting my Tiddlers from TW syntax to Obsidian style markdown, there's no way I'd ever go back to the TW syntax, sorry. Markdown support was in a poor state, especially the extent to which I had to hack it to read Obsidian style markdown (pretty links). I'd **love** to be able to use TW as an alternate UI to view and edit my notes while _also_ being able to use logseq or obsidian, but the Node.JS version not supporting bidirectionality or YAML metadata OOTB makes this nonviable.",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00195",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "tiddlywiki.com",
"other-survey-source": "",
"are-you-a-dev": "No, I would not",
"first-used-tw": "2023",
"joined-tw-community": "No",
"started-tw-community": "",
"use-ttw": "",
"use-mailing-list": "",
"use-reddit": "",
"use-discord": "",
"use-github-discuss": "",
"published-plugin": "No",
"main-use-cases": "Task and project management (including CRMs)",
"other-use-cases": "",
"use-for-work-or-study": "Yes",
"share-wikis": "Yes, and I am the only editor/administrator of my wiki(s)",
"publish-to-web": "Not publishing to this location",
"publish-to-intranet": "Yes, using a single-file wiki",
"value-of-tw": "Organized training materials for the newcomers, the training session is more efficient (shorter).",
"tw-ability-level": "My use is basic; I use TiddlyWiki in a configuration close to standard, without plugins",
"save-method": "Single-file wiki through web browser with Download Saver (default saving mechanism)",
"backup-method": "N/A - I keep my wiki on a single system",
"diy-backup-info": "",
"wiki-setup-info": "<details><summary>Wiki Information</summary><pre><code>\nTiddlyWiki Version: 5.3.3\nCurrent palette: $:/palettes/Dracula\nCurrent theme: $:/themes/tiddlywiki/snowwhite\nCurrent layout: $:/core/ui/PageTemplate\nBrowser language setting: en-US\nDefault type for missing tiddlers: \nAuto save setting: yes\nCode wrapping setting: pre-wrap\nSticky titles setting: no\nSidebar layout setting: fluid-fixed\nAuto focus field setting for new tiddlers: title\nCurrent storyview setting: pop\nToolbar text setting: no\nToolbar icon setting: yes\nButton class setting: tc-btn-invisible\nNavigation address bar setting: no\nTiddler opening behaviour setting for navigations from outside the story river: top\nTiddler opening behaviour setting for navigations from within the story river: below\nCamelCase linking setting: disable\nKeyboard shortcuts that have been customised: \nDisabled plugins: \nPlugins: \n $:/core - 5.3.3\n $:/temp/info-plugin - \n $:/themes/tiddlywiki/snowwhite - 5.3.3\n $:/themes/tiddlywiki/vanilla - 5.3.3\n</code></pre></details>",
"tw-customisations": "",
"positive-about-future": "Yes",
"tw-future-confidence": "Yes",
"project-decision-trust": "Yes",
"project-strengths": "Works out of the box. Overcomes the problem with our company's IT security - no exe/php file, while still can store data in a more friendly format than an Excel sheet.",
"project-weaknesses": "With ChatGPT things are changing, but when I started with the TiddlyWiki, I was looking for examples of how to use it. Grok book has been helpful (old school learner here). Still, would love to see some more examples of some user cases, e.g. Editable List - like in Microsoft's Lists or OneNote. I use it mostly as a CRM system and using the codes from Grok's book to tweak a bit to make what I need.",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00196",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -1,33 +0,0 @@
are-you-a-dev: No, I would not
backup-method: TiddlySpot / TiddlyHost
diy-backup-info:
first-heard-survey: tiddlywiki.com
first-used-tw: 2003
joined-tw-community: No
main-use-cases: Note-taking;As a knowledge base (including technical, non-fiction and encyclopaedic content);Other
ok-to-publish: Yes, I am happy for my responses to be published
other-survey-source:
other-use-cases: Electronic document management
positive-about-future: Yes
project-decision-trust: Yes
project-strengths: Site Web, gestion documentaire
project-weaknesses: pouvoir sortir en pdf plusieurs tiddlers
publish-to-intranet:
publish-to-web:
published-plugin: No
save-method: Single-file wiki through web browser with Download Saver (default saving mechanism)
share-wikis: No, but I may export content into other formats and share individual tiddlers, the whole wiki, or an extract of the wiki
started-tw-community:
tags: [[Community Survey 2025]]
title: Community Survey 2025 Answer 00197
tw-ability-level: I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...);I have written custom CSS styles
tw-customisations:
tw-future-confidence: Yes
use-discord:
use-for-work-or-study: Yes
use-github-discuss:
use-mailing-list:
use-reddit:
use-ttw:
value-of-tw: template to print in pdf
wiki-setup-info:

View File

@@ -1,37 +0,0 @@
[
{
"first-heard-survey": "tiddlywiki.com",
"other-survey-source": "",
"are-you-a-dev": "No, I would not",
"first-used-tw": "2015",
"joined-tw-community": "Yes",
"started-tw-community": "2024",
"use-ttw": "I read/lurk, but do not post",
"use-mailing-list": "I read/lurk, but do not post",
"use-reddit": "I do not engage with this community",
"use-discord": "I read and post in this community",
"use-github-discuss": "I read/lurk, but do not post",
"published-plugin": "No",
"main-use-cases": "Note-taking;Task and project management (including CRMs);As a knowledge base (including technical, non-fiction and encyclopaedic content)",
"other-use-cases": "",
"use-for-work-or-study": "Yes",
"share-wikis": "No, but I may export content into other formats and share individual tiddlers, the whole wiki, or an extract of the wiki",
"publish-to-web": "",
"publish-to-intranet": "",
"value-of-tw": "It helps me organize and prioritize my work-related activities and provides a reference for past work done.",
"tw-ability-level": "I have customised TiddlyWiki through options and plugins;I am comfortable using WikiText widgets (e.g. <$transclude>, <$list>...);I am comfortable writing filter expressions;I have written custom HTML;I have written custom CSS styles",
"save-method": "Single-file wiki with custom saver (e.g. TiddlyPWA, Timimi, tw5-browser-nativesaver)",
"backup-method": "Consumer online storage (e.g. Google Drive, Dropbox)",
"diy-backup-info": "",
"wiki-setup-info": "<details><summary>Wiki Information</summary><pre><code>\nTiddlyWiki Version: 5.3.6\nCurrent palette: $:/JMW/palettes/Nightfall\nCurrent theme: $:/themes/tiddlywiki/vanilla\nCurrent layout: \nBrowser language setting: en-CA\nDefault type for missing tiddlers: \nAuto save setting: yes\nCode wrapping setting: pre-wrap\nSticky titles setting: no\nSidebar layout setting: fluid-fixed\nAuto focus field setting for new tiddlers: title\nCurrent storyview setting: classic\nToolbar text setting: no\nToolbar icon setting: yes\nButton class setting: tc-btn-invisible\nNavigation address bar setting: no\nTiddler opening behaviour setting for navigations from outside the story river: bottom\nTiddler opening behaviour setting for navigations from within the story river: below\nCamelCase linking setting: disable\nKeyboard shortcuts that have been customised: \nDisabled plugins: $:/plugins/Gk0Wk/sidebar-resizer,$:/plugins/nico/notebook-mobile\nPlugins: \n $:/core - 5.3.6\n $:/plugins/danielo515/2click2edit - 0.1\n $:/plugins/eucaly/quickjump - 0.0.2\n $:/plugins/flibbles/relink - 2.4.5\n $:/plugins/flibbles/relink-fieldnames - 2.4.1\n $:/plugins/flibbles/relink-markdown - 2.4.5\n $:/plugins/flibbles/relink-titles - 2.4.0\n $:/plugins/flibbles/relink-variables - 2.4.1\n $:/plugins/Gk0Wk/CPL-Repo - 2025.03.29\n $:/plugins/kookma/commander - 2.1.13\n $:/plugins/kookma/narenj - 0.5.1\n $:/plugins/kookma/search - 1.0.0\n $:/plugins/kookma/shiraz - 3.0.8\n $:/plugins/kookma/shiraz-callout - 0.8.0\n $:/plugins/kookma/shiraz-formatter - 0.6.0\n $:/plugins/kookma/trashbin - 1.3.5\n $:/plugins/kookma/tweaks - 0.2.1\n $:/plugins/kookma/utility - 3.2.2\n $:/plugins/nico/projectify - 0.14.3\n $:/plugins/tiddlywiki/markdown - 5.3.6\n $:/plugins/wikilabs/link-to-tabs - 3.0.1\n $:/plugins/xp/magicsidebar - 0.2.0\n $:/temp/info-plugin - \n $:/themes/nico/notebook - 1.4.1\n $:/themes/tiddlywiki/snowwhite - 5.3.6\n $:/themes/tiddlywiki/vanilla - 5.3.6\n</code></pre></details>",
"tw-customisations": "stylesheets, macros, community-sourced customizations, custom templates, custom pallettes",
"positive-about-future": "Yes",
"tw-future-confidence": "Yes",
"project-decision-trust": "Yes",
"project-strengths": "Keeping tiddlywiki infinitely customizable to adapt to my needs rather than forcing me to adapt to it.",
"project-weaknesses": "For me, tighter Markdown integration, especially with macros, would be great. I currently have a mix of markdown and tiddlywiki tiddlers scattered throughout my file.",
"ok-to-publish": "Yes, I am happy for my responses to be published",
"title": "Community Survey 2025 Answer 00198",
"tags": "[[Community Survey 2025]]"
}
]

View File

@@ -26,7 +26,7 @@ tags: $:/tags/Global
<h1>
<$button class="tc-btn-invisible" style="text-align:left;">
<$action-setfield $tiddler=<<state>> $field="text" $value={{{ [<state>get[text]match[yes]then[no]else[yes]] }}}/>
<%if [<state>get[text]else[yes]match[yes]] %>
<%if [<state>get[text]match[yes]] %>
{{$:/core/images/chevron-down}}
<%else%>
{{$:/core/images/chevron-right}}
@@ -35,27 +35,18 @@ tags: $:/tags/Global
(<$text text={{{ [tag[Community Survey 2025]get<answerField>else[]!match[]] +[count[]] }}}/>)
</$button>
</h1>
<%if [<state>get[text]else[yes]match[yes]] %>
<%if [<state>get[text]match[yes]] %>
<ol>
<%if [<currentTiddler>get[question-type]else[]match[multiple-choice] %>
<$list filter="[tag[Community Survey 2025]get<answerField>else[]!match[]split[;]unique[]sort[]]" variable="answerText">
<li class="interview-answer">
<$text text=<<answerText>>/>
(<$text text={{{ [tag[Community Survey 2025]] :filter[get<answerField>else[]split[;]match<answerText>] +[count[]] }}}/>)
</li>
</$list>
<%else%>
<$list filter="[tag[Community Survey 2025]] :filter[get<answerField>else[]!match[]] +[each<answerField>sort<answerField>]" variable="answerTitle">
<$let answerText={{{ [<answerTitle>get<answerField>] }}}>
<li class="interview-answer">
<$link to=<<answerTitle>>>
<$text text={{{ [<answerTitle>get<answerField>] }}}/>
(<$text text={{{ [tag[Community Survey 2025]get<answerField>match<answerText>count[]] }}}/>)
</$link>
</li>
</$let>
</$list>
<%endif%>
<$list filter="[tag[Community Survey 2025]] :filter[get<answerField>else[]!match[]] +[each<answerField>sort<answerField>]" variable="answerTitle">
<$let answerText={{{ [<answerTitle>get<answerField>] }}}>
<li class="interview-answer">
<$link to=<<answerTitle>>>
<$text text={{{ [<answerTitle>get<answerField>] }}}/>
(<$text text={{{ [tag[Community Survey 2025]get<answerField>match<answerText>count[]] }}}/>)
</$link>
</li>
</$let>
</$list>
</ol>
<%endif%>
</$let>

View File

@@ -88,8 +88,7 @@
"import-field-column": "How would you describe your main use cases for TiddlyWiki?",
"title": "$:/2025 Community Survey/Questions/main-use-cases",
"import-field-source": "column",
"import-spec-role": "field",
"question-type": "multiple-choice"
"import-spec-role": "field"
},
{
"import-field-name": "other-use-cases",
@@ -117,16 +116,14 @@
"import-field-column": "Do you publish your wiki(s) online?: To the World Wide Web",
"title": "$:/2025 Community Survey/Questions/publish-to-web",
"import-field-source": "column",
"import-spec-role": "field",
"question-type": "multiple-choice"
"import-spec-role": "field"
},
{
"import-field-name": "publish-to-intranet",
"import-field-column": "Do you publish your wiki(s) online?: To an intranet",
"title": "$:/2025 Community Survey/Questions/publish-to-intranet",
"import-field-source": "column",
"import-spec-role": "field",
"question-type": "multiple-choice"
"import-spec-role": "field"
},
{
"import-field-name": "value-of-tw",
@@ -140,24 +137,21 @@
"import-field-column": "What is your level of ability with TiddlyWiki? This question assumes you can navigate TiddlyWiki, use basic WikiText and save changes.",
"title": "$:/2025 Community Survey/Questions/tw-ability-level",
"import-field-source": "column",
"import-spec-role": "field",
"question-type": "multiple-choice"
"import-spec-role": "field"
},
{
"import-field-name": "save-method",
"import-field-column": "How do you save changes in TiddlyWiki?",
"title": "$:/2025 Community Survey/Questions/save-method",
"import-field-source": "column",
"import-spec-role": "field",
"question-type": "multiple-choice"
"import-spec-role": "field"
},
{
"import-field-name": "backup-method",
"import-field-column": "How do you back up/sync changes between systems?",
"title": "$:/2025 Community Survey/Questions/backup-method",
"import-field-source": "column",
"import-spec-role": "field",
"question-type": "multiple-choice"
"import-spec-role": "field"
},
{
"import-field-name": "diy-backup-info",

View File

@@ -1,9 +0,0 @@
title: $:/state/survey-2025/--439398230$:/2025 Community Survey/Questions/
other-use-cases: no
value-of-tw: no
diy-backup-info: no
wiki-setup-info: no
tw-customisations: no
project-strengths: no
project-weaknesses: no

View File

@@ -197,10 +197,15 @@ This is an example tiddler. See [[Table-of-Contents Macros (Examples)]].
<!-- TODO use $:/palette colour settings -->
\procedure .link-badge-added(link,colour:#ffe246) <$macrocall $name=".link-badge" text="added" link=<<link>> colour=<<colour>>/>
\procedure .link-badge-addendum(link,colour:#fcc84a) <$macrocall $name=".link-badge" text="addendum" link=<<link>> colour=<<colour>>/>
\procedure .link-badge-extended(link,colour:#f9a344) <$macrocall $name=".link-badge" text="extended" link=<<link>> colour=<<colour>>/>
\procedure .link-badge-fixed(link,colour:#ffa86d) <$macrocall $name=".link-badge" text="fixed" link=<<link>> colour=<<colour>>/>
\procedure .link-badge-here(link,colour:#d88e63) <$macrocall $name=".link-badge" text="here" link=<<link>> colour=<<colour>>/>
\procedure .link-badge-hide(link,colour:#9d959f) <$macrocall $name=".link-badge" text="hide" link=<<link>> colour=<<colour>>/>
\procedure .link-badge-improved(link,colour:#7593c7) <$macrocall $name=".link-badge" text="improved" link=<<link>> colour=<<colour>>/>
\procedure .link-badge-modified(link,colour:#7f99c9) <$macrocall $name=".link-badge" text="modified" link=<<link>> colour=<<colour>>/>
\procedure .link-badge-removed(link,colour:#a9aabc) <$macrocall $name=".link-badge" text="removed" link=<<link>> colour=<<colour>>/>
\procedure .link-badge-renamed(link,colour:#b4b995) <$macrocall $name=".link-badge" text="renamed" link=<<link>> colour=<<colour>>/>
\procedure .link-badge-updated(link,colour:#91ba66) <$macrocall $name=".link-badge" text="updated" link=<<link>> colour=<<colour>>/>
\procedure .banner-credits(credit,url)

View File

@@ -254,12 +254,6 @@ a.doc-deprecated-version.tc-tiddlylink {
text-decoration: underline;
}
.doc-changenote-body {
margin-left: 2em;
font-style: italic;
font-size: 0.9em;
}
.doc-tiddler-fields {
background-color: <<colour code-background>>;
border: 1px solid <<colour tiddler-border>>;
@@ -289,7 +283,6 @@ a.doc-deprecated-version.tc-tiddlylink {
list-style: none;
display: flex;
flex-wrap: wrap;
padding: 0;
}
ol.doc-github-contributors li {
display: flex;

View File

@@ -1,5 +1,5 @@
created: 20231005205623086
modified: 20250807100434131
modified: 20241115193649399
tags: About
title: TiddlyWiki Archive
@@ -8,7 +8,7 @@ title: TiddlyWiki Archive
5.1.10 5.1.11 5.1.12 5.1.13 5.1.14 5.1.15 5.1.16 5.1.17 5.1.18 5.1.19
5.1.20 5.1.21 5.1.22 5.1.23
5.2.0 5.2.1 5.2.2 5.2.3 5.2.4 5.2.5 5.2.6 5.2.7
5.3.0 5.3.1 5.3.2 5.3.3 5.3.4 5.3.5 5.3.6 5.3.7 5.3.8
5.3.0 5.3.1 5.3.2 5.3.3 5.3.4 5.3.5 5.3.6 5.3.7
\end
Older versions of TiddlyWiki are available in the [[archive|https://github.com/TiddlyWiki/tiddlywiki.com-gh-pages/tree/master/archive]]:

View File

@@ -4,7 +4,19 @@ tags: Community Reference
title: Developers
type: text/vnd.tiddlywiki
! [[GitHub Stats|https://github.com/TiddlyWiki/TiddlyWiki5/graphs/contributors]]
There are several resources for developers to learn more about TiddlyWiki and to discuss and contribute to its development.
> [img[https://repobeats.axiom.co/api/embed/b92b1b363e2b5f26837ae573a60d39b4248b50a0.svg]]
* [[tiddlywiki.com/dev|https://tiddlywiki.com/dev]] is the official developer documentation
* Get involved in the [[development on GitHub|https://github.com/TiddlyWiki/TiddlyWiki5]]
* [[GitHub Discussions|https://github.com/TiddlyWiki/TiddlyWiki5/discussions]] are for Q&A and open-ended discussion
* [[GitHub Issues|https://github.com/TiddlyWiki/TiddlyWiki5/issues]] are for raising bug reports and proposing specific, actionable new ideas
* The older ~TiddlyWikiDev Google Group is now closed in favour of [[Talk TiddlyWiki|https://talk.tiddlywiki.org/]] and [[GitHub Discussions|https://github.com/TiddlyWiki/TiddlyWiki5/discussions]]
** It remains a useful archive: https://groups.google.com/group/TiddlyWikiDev
*** An enhanced group search facility is available on [[mail-archive.com|https://www.mail-archive.com/tiddlywikidev@googlegroups.com/]]

View File

@@ -1,42 +0,0 @@
title: Filter Syntax History
tags: [[History of TiddlyWiki]]
modifier: Jeremy Ruston
created: 20250730154331065
modified: 20250730154331065
In response to [[a discussion|https://talk.tiddlywiki.org/t/filter-syntax-history/13058]] about the filter syntax in TiddlyWiki5 I posted this brief personal history.
For context, before TiddlyWiki, I only had practical experience of a very small number of languages: machine code, assembly language, BASIC, FORTH, C, C++ and of course JavaScript. I had a smattering of Java, Pascal and one or two other ancient languages but no experience of actor based languages like Erlang, or modern functional languages.
The story starts with the double square bracket syntax used in wikitext for links. In 2004 this was already an established usage in wikis. However, I switched the ordering of pretty links because I thought Wikipedia's `[[link address|link text]]` was the wrong way around. It broke up sentences: `The file is [[https://site.com/thing|here]]` seems less readable than `The file is [[here|https://site.com/thing]]`. For a long time I regretted this decision, and wished that I had just gone with Wikipedia's established usage. Others have since pointed out that TiddlyWiki's ordering is actually consistent with [[Markdown]], which might be regarded as the winner of the markup wars.
I looked at the double square bracket link syntax is that it establishes a way to quote page/tiddler titles so that they may contain spaces, and don't have to use CamelCase. Thus, right at the start of TiddlyWiki Classic when I was implementing the first iteration of the DefaultTiddlers feature it was natural to use double square brackets to quote titles containing spaces, making a list of titles to be opened at startup.
Soon, I wanted to extend the implementation of DefaultTiddlers so that it could be used to open all tiddlers with a particular tag while retaining backwards compatibility.
A trick that I am apt to use in such situations is to try to engineer things so that the current behaviour is re-interpreted as a shortcut syntax for a new, richer syntax that provides more flexibility. In this case, the idea was that in filters we would interpret `[[mytiddler]]` as a shortcut for `[title[mytiddler]]`. Then we could put any keywords we like in place of "title", giving us an infinitely extensible syntax. A similar example is the way that we implemented filter run prefixes by retrospectively defining the absence of a prefix as implying a default prefix.
The new syntax was first [introduced in 2007] (see [this commit](https://github.com/TiddlyWiki/TiddlyWikiClassic/commit/1928962ea6811b1ca67378ed3cd62059a9806ae9)), with a simplified syntax that only supported a single `tag` operator but was just about sufficient for intended purpose. The only documentation was a comment in the source code (complete with a typo):
```
// Filter a list of tiddlers
//# filter - filter expression (eg "tidlertitle [[multi word tiddler title]] [tag[systemConfig]]")
//# Returns an array of Tiddler() objects that match the filter expression
```
Provision to combine the filter operators had been on my mind from the beginning. When TiddlyWiki 5 started in 2011 I reused the simple implementation from TiddlyWiki Classic. Smashing operators [was finally implemented in May 2012](https://github.com/TiddlyWiki/TiddlyWiki5/commit/8b0703b694e982b2bc448bdb133742164723dd8a). By the time of the launch the filter language had grown into pretty much what it is today -- see the [documentation for TiddlyWiki v5.1.0](https://tiddlywiki.com/archive/full/TiddlyWiki-5.1.0#Introduction%20to%20Filters).
The filter syntax had undoubtedly evolved into something approaching a programming language. As others have probably expressed much more eloquently, a characteristic of the programming languages that I love is that they start with a small number of principles that are consistently applied and combined. In the case of TiddlyWiki, the list would be very roughly:
* Double square brackets for linking and quoting
* Curly braces for transclusion
* Angle brackets for macros (which evolved into variables)
* Double exclamation marks to indicate fields `{{!!myfield}}`
* Double hashes to indicate indexes `{{##myindex}}`
* Smashing together adjacent filter operations by removing the combining `][`
* The dollar sign as a rough signifier of data owned by the system rather than the user
As I have written about elsewhere I was privileged to know Joe Armstrong, the co-inventor of Erlang, in the last few years of his life we were working together on a book about TiddlyWiki when he passed away in 2019. Joe had contacted me out of the blue ten years before to express his admiration for TiddlyWiki, and we had developed a friendship. He was actually a big fan of TW5's filter syntax, and used to make me feel better about it by joking that I had (re-)invented the monad, which sounded impressive to me. That doesn't make the filter language any easier to learn, but it does mean that it is *worth* learning: it's a real language, based on the same principles as other languages.
I find it pleasing that the TW5 filter language has its roots in decisions that were taken in the TWC days. It's still hard to learn, but that's an ongoing paradox of programming: people want to do complicated things, and complicated things are complicated. It's hard to see how we could have made filters any simpler without depriving users of the possibility of doing complicated things.

View File

@@ -10,7 +10,7 @@ Nonetheless, TiddlyWiki is a relatively big, complex machine that requires a sig
The people in the community that do the work have widely varying needs:
* At one end, a good proportion of the work on TiddlyWiki is performed by community members on a purely voluntary basis. For those people, the satisfaction of helping others is sufficient reward. Indeed, for many people, unpaid voluntary activities are a satisfying antidote to everyday paid work
* At the other extreme, [[@Jermolene]] and some other contributors are trying to make a full-time living working on TiddlyWiki by offering commercial products and services around it
* At the other extreme, JeremyRuston and some other contributors are trying to make a full-time living working on TiddlyWiki by offering commercial products and services around it
* In between, there are other people who would appreciate an ocassional token to reward them for their work
To support these needs in the community, we have two initiatives:

View File

@@ -1,12 +1,86 @@
created: 20140908114400000
modified: 20250730154331065
modified: 20241016125145988
tags: About
title: History of TiddlyWiki
type: text/vnd.tiddlywiki
! Twenty Years of ~TiddlyWiki
Here is a brief history of TiddlyWiki, its origins and its evolution since it was first released on 20th September 2004. Contributions and reminiscences are welcome.
We've held a number of livestreams to celebrate twenty years of ~TiddlyWiki. You can watch the recordings here:
* 19th September 2024 - https://youtube.com/live/z9slx92TyrU
* 20th September 2024 - https://youtube.com/live/puFdN-FgOjg
* 21st September 2024 - https://youtube.com/live/0SjsHvwjHGE
* 22nd September 2024 - https://youtube.com/live/oD7Jtq2D4lg
Over on GitHub, we celebrated the contributors to TiddlyWiki by [[asking them|https://github.com/TiddlyWiki/TiddlyWiki5/discussions/7983]] for their reflections on the anniversary. We received some interesting and thoughtful responses. For example, this from [[@FND|https://github.com/FND]]:
> TiddlyWiki had an immeasurable, enduring influence not just on my career, such as it is, but also on my values: To this day, I regularly find myself referring back to [[fundamental concepts|https://prepitaph.org/articles/creative-privacy/]] TiddlyWiki instilled in me - many of which are often forgotten or ignored elsewhere. Having this background thus helps me keep my bearings working in this industry, whether it's worshipping at the altar of technical complexity or even just remembering humans exist in the world of technology.
> By TiddlyWiki, I mean people. It was an immense privilege interacting with and learning from this community and the group Jeremy built around it. It also helps reminding myself that this privilege was afforded to me by sheer happenstance; I hope to be paying it forward.
Some recent podcasts featuring ~TiddlyWiki:
* The changelog podcast from 2016 - https://changelog.com/podcast/196 discussing ~TiddlyWiki's backstory
* Floss Weekly recording from 2021 - https://twit.tv/shows/floss-weekly/episodes/620
! Origins of TiddlyWiki
Back in 1997 a colleague introduced me to [[Ward Cunningham's original wiki|http://c2.com/cgi/wiki]]. I was impressed that something so powerful could fit into just 700 lines of Perl, and fascinated by the radical reimagining of security and permissions. Like many other developers, I took every opportunity I could to try out various wikis, and to explore their use at work.
The allure of the wiki for me was the feeling that it could eventually disrupt the prevailing paradigm of print-oriented documents and emails.
After watching people use wikis for a few years, I noticed that power users made extensive use of the ability to open multiple wiki pages at once in several browser tabs, making it easier for them to compare and review pages, to copy text between them and to act as a sort of queue of pages yet to be read.
I felt that this ability to manipulate multiple pages at once was central to the ability to refactor a wiki, and it is generally accepted that a wiki that is lovingly refactored tends to be more useful. And yet, standard wiki user interfaces have always been designed exclusively for the presentation and manipulation of single pages at once.
All of these thoughts came together when I saw GMail in April 2004, which used Ajax cleverly to blend individual emails into threaded conversations.
I started experimenting with HTML and JavaScript to explore the idea further. I'd had virtually no experience of either, just having put together some static pages and simple ASP sites in previous lives. Getting my head around these client-side technologies was painful; like everyone else, I was horrified to discover how appalling were the incompatibilities and inconsistencies of web programming.
! Launch of TiddlyWiki
So, in September 2004 I released a primitive [[first version of TiddlyWiki|https://classic.tiddlywiki.com/firstversion.html]]. It was the smallest possible thing that demonstrated the idea: it was a simple, self-contained static 48KB HTML file.
The downside of writing the first version of TiddlyWiki in this way was that it made it completely impractical to use for editing - when you click 'save changes' it just pops up a window showing the data that would be saved if it were possible for an HTML page to write to the file system.
Much of the early feedback was that TiddlyWiki was neat, but that it would be more useful when it was possible to properly save changes. I was a little frustrated, as I thought I knew that it was impossible for an HTML file running in the browser to save changes to the local file system.
Within a few months I saw an experimental Firefox extension that enabled TiddlyWiki to save changes in the browser. Examining the code, I realised that the APIs that it used to write to the file system were actually available in ordinary HTML files - as long as they were loaded via a `file://` URI.
I adapted the Firefox code into the core of TiddlyWiki, and soon added a similar ability for Internet Explorer (making use of an old [[ActiveX|https://en.wikipedia.org/wiki/ActiveX]] control that Microsoft distributed with Internet Explorer).
! Growth of TiddlyWiki
A major milestone in the growth of TiddlyWiki was the creation of "GTDTiddlyWiki" by Nathan Bowers. He took the vanilla TiddlyWiki product and adapted it for the specific application of keeping track of tasks using the popular Getting Things Done methodology. GTDTiddlyWiki was an immediate hit, being enthusiastically greeted on websites like [[LifeHacker|https://lifehacker.com/]].
Over the next couple of years TiddlyWiki continued to grow in popularity, and gained new features and capabilities. Within a year I was able to support myself by performing bespoke development work on TiddlyWiki, notably working with wiki pioneer [[SocialText|https://en.wikipedia.org/wiki/Socialtext]] on the ability to synchronise changes with an online server
! BT Acquisition
In May 2007, [[BT]] acquired [[Osmosoft]], my consultancy company. It was an unusual decision to acquire a company with a single employee and a tiny trickle of revenue - [[Osmosoft]] didn't even own the intellectual property in TiddlyWiki since I had handed it over to [[UnaMesa]] to assure its future for the community.
[[BT]]'s motivation was to help them understand community-based ecosystems. I joined the organisation as "Head of Open Source Innovation", taking responsibility for open source governance, and providing advice and expertise on how to participate in open soure communities.
! [[Osmosoft]] and TiddlySpace
I built a team in BT under the name [[Osmosoft]]. Our purpose was to evangelise the benefits of open source, and to help other teams realise those benefits in practice. We also found that it was necessary to evangelise the use of the web in general, and web standards in particular.
Our approach was to focus on showing rather than telling. We worked with the TiddlyWiki community to extend the ecosystem and we built numerous internal systems for BT (some based on TiddlyWiki and some not).
[[Osmosoft]]'s chief contribution to the TiddlyWiki community was the creation of TiddlyWeb and TiddlySpace. TiddlyWeb was a robust, internet scale server for tiddlers that could also compose TiddlyWiki views of those tiddlers. TiddlySpace was an attempt to package TiddlyWeb into a more directly usable form.
! Leaving BT
By the end of 2011 I was increasingly feeling that I would be better placed to realise the potential of TiddlyWiki outside of the corporate confines BT. Accordingly, I left and started work as an independent developer, primarily working on a brand new reboot of TiddlyWiki in the shape of TiddlyWiki5.
! Development of TiddlyWiki5
I worked on new release of TiddlyWiki from November 2011. As a programmer, working on "version 2.0" of something that I had already written is a very attractive proposition. It means that the requirements were fully understood, allowing me to focus on evolving the architecture needed to support the desired functionality.
! The Future
Now that TiddlyWiki5 has finally left "beta" status behind, my hope is that it will have a long life. Because it only uses standard features of HTML5 and Node.js, there is no reason why it cannot be fully operational for many years to come. My goal is for it to last for at least 25 years.
//Jeremy Ruston, 20th September 2014//
* [[The Story of TiddlyWiki]] a personal account of the story of TiddlyWiki, its origins and evolution
* [[TiddlyWiki Anniversaries]] relive the celebrations of TiddlyWiki's major anniversaries
* [[Filter Syntax History]] gives a brief history of the evolution of the filter syntax in TiddlyWiki5

View File

@@ -1,69 +0,0 @@
title: The Story of TiddlyWiki
tags: [[History of TiddlyWiki]]
modifier: Jeremy Ruston
created: 20140908114400000
modified: 20250730154331065
This is a personal account of the story of TiddlyWiki, its origins and its evolution since it was first released on 20th September 2004.
! Origins of TiddlyWiki
Back in 1997 a colleague introduced me to [[Ward Cunningham's original wiki|http://c2.com/cgi/wiki]]. I was impressed that something so powerful could fit into just 700 lines of Perl, and fascinated by the radical reimagining of security and permissions. Like many other developers, I took every opportunity I could to try out various wikis, and to explore their use at work.
The allure of the wiki for me was the feeling that it could eventually disrupt the prevailing paradigm of print-oriented documents and emails.
After watching people use wikis for a few years, I noticed that power users made extensive use of the ability to open multiple wiki pages at once in several browser tabs, making it easier for them to compare and review pages, to copy text between them and to act as a sort of queue of pages yet to be read.
I felt that this ability to manipulate multiple pages at once was central to the ability to refactor a wiki, and it is generally accepted that a wiki that is lovingly refactored tends to be more useful. And yet, standard wiki user interfaces have always been designed exclusively for the presentation and manipulation of single pages at once.
All of these thoughts came together when I saw GMail in April 2004, which used Ajax cleverly to blend individual emails into threaded conversations.
I started experimenting with HTML and JavaScript to explore the idea further. I'd had virtually no experience of either, just having put together some static pages and simple ASP sites in previous lives. Getting my head around these client-side technologies was painful; like everyone else, I was horrified to discover how appalling were the incompatibilities and inconsistencies of web programming.
! Launch of TiddlyWiki
So, in September 2004 I released a primitive [[first version of TiddlyWiki|https://classic.tiddlywiki.com/firstversion.html]]. It was the smallest possible thing that demonstrated the idea: it was a simple, self-contained static 48KB HTML file.
The downside of writing the first version of TiddlyWiki in this way was that it made it completely impractical to use for editing - when you click 'save changes' it just pops up a window showing the data that would be saved if it were possible for an HTML page to write to the file system.
Much of the early feedback was that TiddlyWiki was neat, but that it would be more useful when it was possible to properly save changes. I was a little frustrated, as I thought I knew that it was impossible for an HTML file running in the browser to save changes to the local file system.
Within a few months I saw an experimental Firefox extension that enabled TiddlyWiki to save changes in the browser. Examining the code, I realised that the APIs that it used to write to the file system were actually available in ordinary HTML files - as long as they were loaded via a `file://` URI.
I adapted the Firefox code into the core of TiddlyWiki, and soon added a similar ability for Internet Explorer (making use of an old [[ActiveX|https://en.wikipedia.org/wiki/ActiveX]] control that Microsoft distributed with Internet Explorer).
! Growth of TiddlyWiki
A major milestone in the growth of TiddlyWiki was the creation of "GTDTiddlyWiki" by Nathan Bowers. He took the vanilla TiddlyWiki product and adapted it for the specific application of keeping track of tasks using the popular Getting Things Done methodology. GTDTiddlyWiki was an immediate hit, being enthusiastically greeted on websites like [[LifeHacker|https://lifehacker.com/]].
Over the next couple of years TiddlyWiki continued to grow in popularity, and gained new features and capabilities. Within a year I was able to support myself by performing bespoke development work on TiddlyWiki, notably working with wiki pioneer [[SocialText|https://en.wikipedia.org/wiki/Socialtext]] on the ability to synchronise changes with an online server
! BT Acquisition
In May 2007, [[BT]] acquired [[Osmosoft]], my consultancy company. It was an unusual decision to acquire a company with a single employee and a tiny trickle of revenue - [[Osmosoft]] didn't even own the intellectual property in TiddlyWiki since I had handed it over to [[UnaMesa]] to assure its future for the community.
[[BT]]'s motivation was to help them understand community-based ecosystems. I joined the organisation as "Head of Open Source Innovation", taking responsibility for open source governance, and providing advice and expertise on how to participate in open soure communities.
! [[Osmosoft]] and TiddlySpace
I built a team in BT under the name [[Osmosoft]]. Our purpose was to evangelise the benefits of open source, and to help other teams realise those benefits in practice. We also found that it was necessary to evangelise the use of the web in general, and web standards in particular.
Our approach was to focus on showing rather than telling. We worked with the TiddlyWiki community to extend the ecosystem and we built numerous internal systems for BT (some based on TiddlyWiki and some not).
[[Osmosoft]]'s chief contribution to the TiddlyWiki community was the creation of TiddlyWeb and TiddlySpace. TiddlyWeb was a robust, internet scale server for tiddlers that could also compose TiddlyWiki views of those tiddlers. TiddlySpace was an attempt to package TiddlyWeb into a more directly usable form.
! Leaving BT
By the end of 2011 I was increasingly feeling that I would be better placed to realise the potential of TiddlyWiki outside of the corporate confines BT. Accordingly, I left and started work as an independent developer, primarily working on a brand new reboot of TiddlyWiki in the shape of TiddlyWiki5.
! Development of TiddlyWiki5
I worked on new release of TiddlyWiki from November 2011. As a programmer, working on "version 2.0" of something that I had already written is a very attractive proposition. It means that the requirements were fully understood, allowing me to focus on evolving the architecture needed to support the desired functionality.
! The Future
Back in 2014, shortly after TiddlyWiki5 was first released, I wrote:
> Now that TiddlyWiki5 has finally left "beta" status behind, my hope is that it will have a long life. Because it only uses standard features of HTML5 and Node.js, there is no reason why it cannot be fully operational for many years to come. My goal is for it to last for at least 25 years.
As I write this, TiddlyWiki5 is 44% of the way to that goal. With the support and enthusiasm of the community I am confident the project will continue to thrive and evolve.

View File

@@ -1,31 +0,0 @@
title: TiddlyWiki Anniversaries
tags: [[History of TiddlyWiki]]
created: 20250730154331065
modified: 20250730154331065
! Twentieth Anniversary of TiddlyWiki
We've held a number of livestreams to celebrate twenty years of ~TiddlyWiki. You can watch the recordings here:
* 19th September 2024 - https://youtube.com/live/z9slx92TyrU
* 20th September 2024 - https://youtube.com/live/puFdN-FgOjg
* 21st September 2024 - https://youtube.com/live/0SjsHvwjHGE
* 22nd September 2024 - https://youtube.com/live/oD7Jtq2D4lg
Over on GitHub, we celebrated the contributors to TiddlyWiki by [[asking them|https://github.com/TiddlyWiki/TiddlyWiki5/discussions/7983]] for their reflections on the anniversary. We received some interesting and thoughtful responses. For example, this from [[@FND|https://github.com/FND]]:
> TiddlyWiki had an immeasurable, enduring influence not just on my career, such as it is, but also on my values: To this day, I regularly find myself referring back to [[fundamental concepts|https://prepitaph.org/articles/creative-privacy/]] TiddlyWiki instilled in me - many of which are often forgotten or ignored elsewhere. Having this background thus helps me keep my bearings working in this industry, whether it's worshipping at the altar of technical complexity or even just remembering humans exist in the world of technology.
> By TiddlyWiki, I mean people. It was an immense privilege interacting with and learning from this community and the group Jeremy built around it. It also helps reminding myself that this privilege was afforded to me by sheer happenstance; I hope to be paying it forward.
Some recent podcasts featuring ~TiddlyWiki:
* The changelog podcast from 2016 - https://changelog.com/podcast/196 discussing ~TiddlyWiki's backstory
* Floss Weekly recording from 2021 - https://twit.tv/shows/floss-weekly/episodes/620
! Tenth Anniversary of TiddlyWiki
You can watch the livestream from 20th September 2014 celebrating the tenth anniversary of TiddlyWiki here:
https://www.youtube.com/watch?v=f_02ZV0J9NY

View File

@@ -1,6 +1,6 @@
created: 20140320230543190
modified: 20160602172752299
tags: Resources
tags: Community
title: Articles
type: text/vnd.tiddlywiki

View File

@@ -1,6 +1,6 @@
created: 20210101150806938
modified: 20230803053451496
tags: Resources
tags: Community
title: Community Editions
These are prepackaged editions created by the ~TiddlyWiki [[Community]]. These are ~TiddlyWikis with added plugins and configurations to facilitate a certain use-case. These are great starting points if you want to quickly jump into TiddlyWiki and start using it without spending too much time configuring yourself.

View File

@@ -1,6 +1,6 @@
created: 20210101152520906
modified: 20210101152533358
tags: Resources
tags: Community
title: Community Palettes
This is a list of palettes made by members of the ~TiddlyWiki [[Community]]. Palettes change the colourscheme of TiddlyWiki and can be used in combination with themes.

View File

@@ -1,6 +1,6 @@
created: 20210101150806938
modified: 20210101151403345
tags: Resources
tags: Community
title: Community Plugins
These are plugins created by the ~TiddlyWiki [[Community]]. Visit their website to try out the plugin. Carefully read the installing instructions and back up before installing! These plugins may not always be up to date and can contain bugs or unwanted behaviour. For even more plugins, visit the [[TiddlyWiki Groups|Forums]]. New plugins get posted and announced there first.

View File

@@ -0,0 +1,9 @@
title: Community Survey 2025 Sidebar Segment Styles
tags: $:/tags/Stylesheet
\rules only filteredtranscludeinline transcludeinline macrodef macrocallinline macrocallblock
.community-survey-sidebar-image {
width: 100%;
box-shadow: 0 0 10px rgba(0,0,0,0.1);
}

View File

@@ -0,0 +1,11 @@
title: Community Survey 2025 Sidebar Segment
created: 20250708130030654
modified: 20250708130030654
tags: $:/tags/SideBarSegment
list-after: $:/core/ui/SideBarSegments/site-subtitle
<div style.padding-right="3em" style.max-width="20em">
<$link to="Community Survey 2025">
<$image source="Community Survey 2025.png" alt="Shape the future by taking the TiddlyWiki Community Survey 2025" class="community-survey-sidebar-image"/>
</$link>
</div>

View File

@@ -1,25 +1,34 @@
title: Community Survey 2025
created: 20250708130030654
modified: 20250826162904085
modified: 20250708130030654
<div style.float="right" style.padding-left="1em">
<$image source="Community Survey 2025.png" alt="Shaping the future of TiddlyWiki with the Community Survey 2025" width="280"/>
<$image source="Community Survey 2025.png" alt="Shape the future by taking the TiddlyWiki Community Survey 2025" width="280"/>
</div>
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, were 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, and so we undertook the ~TiddlyWiki Community Survey 2025. This brief, anonymous survey was designed to give us insight into the needs of TiddlyWiki users, with a mix of structured and freeform questions.
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 survey.
The [[raw results|https://ec.europa.eu/eusurvey/publication/tiddlywiki-users-2025]] of the survey are available in TiddlyWiki form on this new site:
So, we would like to invite you to participate in the ~TiddlyWiki Community 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.
https://tiddlywiki.com/surveys.html
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 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. We intend to publish further analysis of the survey results in the coming weeks.
The survey will remain open until Monday 11th August 2025. Shortly afterwards, we will aggregate and share the findings.
Take the survey here:
https://ec.europa.eu/eusurvey/runner/tiddlywiki-users-2025
!! The Great Viral TiddlyWiki Interview Project (2010)
The new Surveys site also include the "The Great Viral TiddlyWiki Interview Project" from 2010. We invited TiddlyWiki users to join the interview project with these words:
In 2010, 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:
https://tiddlywiki.com/surveys.html

Some files were not shown because too many files have changed in this diff Show More