tiddlywiki 5.3.7 → 5.4.0

package/editions/tw5.com/tiddlers/Concatenating variables to create a URL.tid

@@ -0,0 +1,13 @@
+created: 20251021142733998
+modified: 20251021142733998
+tags: 
+title: Concatenating variables to create a URL
+type: text/vnd.tiddlywiki
+
+!! Concatenating strings and variables to create a URL
+
+<$macrocall $name=wikitext-example src="""<$let hash={{{ [<currentTiddler>encodeuricomponent[]] }}}>
+<a href=`http://tiddlywiki.com/#$(hash)$`>this tiddler on tiddlywiki.com</a>
+</$let>"""/>
+
+See: [[Substituted Attribute Values]]

package/editions/tw5.com/tiddlers/Core CSS Variables.tid

@@ -0,0 +1,11 @@
+created: 20251108075028089
+modified: 20260130070027124
+tags: Reference
+title: Core CSS Variables
+type: text/vnd.tiddlywiki
+
+<<.from-version 5.4.0>> Tiddlywiki CSS variable definitions starts with `--tp-*` and `--tpc-*`. They are mainly used to [[Write stylesheets in vanilla CSS|Writing stylesheets in vanilla CSS]]. These prefixes ''are reserved'' for Tiddlywiki, so it should not be used for user defined CSS variables. It is also not recommended to override these core CSS variables.
+
+Core CSS variables are defined in [[$:/core/stylesheets/custom-properties]].
+
+<<list-links "[tag[Core CSS Variables]]" class:"multi-columns">>

package/editions/tw5.com/tiddlers/Deprecated Core Classes.tid

@@ -0,0 +1,13 @@
+created: 20251015120940754
+modified: 20251101092833913
+tags: $:/deprecated [[Core Classes]]
+title: Deprecated Core Classes
+type: text/vnd.tiddlywiki
+
+<<.warning "It is not recommended to use these classes for styling. Though tiddlywiki might still support them, they may be in the process of being dropped, or may only be kept for compatibility purposes. Avoid using them, and update existing code if possible. Be aware that this feature may cease to work at any time.">>
+
+These [[Core Classes]] are considered deprecated. It is not recommend to use them for styling.
+
+* `tc-tagged-*` <<.deprecated-since 5.1.16>> Use [[Custom styles by data-tags]] instead.
+* `tc-reveal` <<.deprecated-since 5.3.8>> for styling purposes as it is subject to change.
+* `tc-language-(language code)` <<.deprecated-since 5.3.8>> Please use [[:lang()|https://developer.mozilla.org/en-US/docs/Web/CSS/:lang]] instead.

package/editions/tw5.com/tiddlers/Deprecated core macros.tid

@@ -0,0 +1,31 @@
+created: 20251101085817414
+modified: 20251101091035398
+tags: [[Core Macros]] Macros $:/deprecated
+title: Deprecated core macros
+type: text/vnd.tiddlywiki
+
+<<.warning "It is discouraged to use the following macros. Though tiddlywiki might still support them, they may be in the process of being dropped, or may only be kept for compatibility purposes. Avoid using it, and update existing code if possible. Be aware that these macros may cease to work at any time. ">>
+
+Most deprecated macros are defined in [[$:/core/macros/deprecated]]. It is discouraged to use them.
+
+! Stylesheet Macros
+
+<<.deprecated-since 5.4.0>> The following core [[macros|Macros]] used to made it easy to specify alternative browser-specific properties when constructing a [[stylesheet|Cascading Style Sheets]] tiddler. They are deprecated after 2017 baseline is supported in v5.4.0:
+
+; `<<box-shadow shadow>>`
+: for the `x-box-shadow` properties
+
+; `<<filter filter>>`
+: for the `x-filter` properties
+
+; `<<transition transition>>`
+: for the `x-transition` properties
+
+; `<<transform-origin origin>>`
+: for the `x-transition-origin` properties
+
+; `<<background-linear-gradient gradient>>`
+: for the `x-linear-gradient` values of the `background-image` property
+
+; `<<column-count columns>>`
+: for the `x-column-count` property

package/editions/tw5.com/tiddlers/TiddlyWiki Docs PR Maker.tid

@@ -1,11 +1,10 @@
 created: 20240313100515958
-modified: 20240313103959789
+modified: 20251023154747366
 tags: Editions
 title: TiddlyWiki Docs PR Maker
 
-''~TiddlyWiki Docs PR Maker'' is a special edition of tiddlywiki.com designed to help you contribute to and improve the documentation made by [[@saqimtiaz|https://github.com/saqimtiaz/]].
-
-https://saqimtiaz.github.io/tw5-docs-pr-maker/
+''~TiddlyWiki Docs PR Maker'' is a special edition of tiddlywiki.com designed to help you contribute to and improve the documentation.
+https://edit.tiddlywiki.com
 
 All changes made to the documentation can be very easily submitted to GitHub -- the pull request will be automatically made, hence the "PR Maker" name of the edition.
 

package/editions/tw5.com/tiddlers/Writing stylesheets in vanilla CSS.tid

@@ -0,0 +1,69 @@
+created: 20251108075645447
+modified: 20260201043953311
+title: Writing stylesheets in vanilla CSS
+type: text/vnd.tiddlywiki
+
+<<.from-version 5.4.0>> Before v5.4.0, theme developers have to mix wikitext syntax with CSS syntax when writing stylesheets to intergrate Tiddlywiki color palettes and theme settings. With the introduction of [[Core CSS Variables]] in v5.4.0, theme developers can intergrate most Tiddlywiki palettes with vanilla CSS.
+
+! Getting Tiddlywiki palette colors
+Tiddlywiki's custom properties for colors are prefixed `--tpc-`. Before v5.4.0, theme developers have to use the following wikitext to get a color value of a palette:
+
+```
+.tag {
+	background: <<colour tag-background>>;
+}
+```
+
+Since v5.4.0, theme developers can use the following CSS to get the palette color:
+
+```css
+.tag {
+	background: var(--tp-color-tag-background);
+}
+```
+
+! Getting and processing Tiddlywiki CSS settings
+See [[Core CSS Variables]] for the available CSS variables. Before v5.4.0, theme developers have to use macros with filters to get and process theme settings:
+
+```
+.tc-sidebar-header {
+	padding: 14px;
+	min-height: 32px;
+	margin-top: {{$:/themes/tiddlywiki/vanilla/metrics/storytop}};
+	transition:  min-height {{$:/config/AnimationDuration}}ms ease-in-out, padding-top {{$:/config/AnimationDuration}}ms ease-in-out, padding-bottom {{$:/config/AnimationDuration}}ms ease-in-out;
+}
+```
+
+Since v5.4.0, the theme settings are also available as the CSS variables, so theme developers can use the following code:
+
+```css
+.tc-sidebar-header {
+	padding: 14px;
+	min-height: 32px;
+	margin-top: var(--tp-story-top);
+	transition: min-height var(--tp-animation-duration) ease-in-out, padding-top var(--tp-animation-duration) ease-in-out, padding-bottom var(--tp-animation-duration) ease-in-out;
+}
+```
+
+! Limits
+CSS variables can only be used in rules, while wikitext can be used everywhere. See this example:
+
+Old way of using wikitext in media query definitions:
+
+```
+\define sidebarbreakpoint()
+<$text text={{$:/themes/tiddlywiki/vanilla/metrics/sidebarbreakpoint}}/>
+\end
+
+@media (min-width: <<sidebarbreakpoint>>) {
+	/* CSS rules */
+}
+```
+
+While using CSS variables in media quert definitions doesn't work at all:
+
+```css
+@media (min-width: var(--tp-sidebar-breakpoint)) {
+	/* Doesn't work */
+}
+```

package/editions/tw5.com/tiddlers/_tw_shared/doc-utilities/doc-macros.tid

@@ -36,13 +36,56 @@ type: text/vnd.tiddlywiki
 		</h2>
 		<table class="tc-view-field-table">
 			<tbody>
-				<$list filter="[all[current]fields[]sort[title]] -title" template="$:/core/ui/TiddlerFieldTemplate" variable="listItem"/>
+				<$list filter="[all[current]fields[]sort[title]] -title -text" template="$:/core/ui/TiddlerFieldTemplate" variable="listItem"/>
 			</tbody>
 		</table>
+		<$codeblock code={{{ [<currentTiddler>get[text]] }}}/>
 	</div>
 </$tiddler>
 \end
 
+\procedure .demo-tiddler(tidText)
+	\procedure create-tiddler-actions()
+		<$action-setmultiplefields $tiddler=<<title>> $fields="[<jsonTiddler>jsonindexes[0]sort[]]" $values="[<jsonTiddler>jsonindexes[0]sort[]] :map[<jsonTiddler>jsonget[0],<currentTiddler>]"/>
+	\end create-tiddler-actions
+	<$let
+		jsonTiddler={{{ [<tidText>deserialize[application/x-tiddler]] }}}
+		title={{{ [<jsonTiddler>jsonget[0],[title]] }}}
+	>
+		<div class="doc-tiddler-fields">
+			<h2>
+			<$link to=<<title>>>
+				<$text text=<<title>>/>
+			</$link>
+			</h2>
+			<table class="tc-view-field-table">
+				<tbody>
+					<$list filter="[<jsonTiddler>jsonindexes[0]sort[]] -title -text" variable="listItem">
+						<tr class="tc-view-field">
+							<td class="tc-view-field-name">
+								<$text text=<<listItem>>/>
+							</td>
+							<td class="tc-view-field-value">
+								<$text text={{{ [<jsonTiddler>jsonget[0],<listItem>] }}}/>
+							</td>
+						</tr>
+					</$list>
+				</tbody>
+			</table>
+			<$codeblock code={{{ [<jsonTiddler>jsonget[0],[text]] }}}/>
+			<div>
+				<%if [<title>has[title]] %>
+					The tiddler '<$link to=<<title>>><$text text=<<title>>/></$link>' already exists
+				<%else%>
+					<$button actions=<<create-tiddler-actions>> class="tc-btn-big-green">
+						Create this tiddler
+					</$button>
+				<%endif%>
+			</div>
+		</div>
+	</$let>
+\end
+
 \function .mtitle(_) [<_>] Macro +[join[ ]]
 \function .otitle(_) [<_>] Operator +[join[ ]]
 \function .vtitle(_) [<_>] Variable +[join[ ]]
@@ -197,15 +240,10 @@ 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)

package/editions/tw5.com/tiddlers/_tw_shared/doc-utilities/doc-styles.tid

@@ -240,7 +240,7 @@ a.doc-deprecated-version.tc-tiddlylink {
     vertical-align: text-bottom;
 }
 
-.doc-link-badge {
+html button.doc-link-badge, html a.doc-link-badge {
     text-decoration: none;
     background-color: #7eba4c;
     color: <<colour foreground>>;
@@ -250,10 +250,22 @@ a.doc-deprecated-version.tc-tiddlylink {
     font-size: 0.75em;
 }
 
-.doc-link-badge:hover {
+html button.doc-link-badge:hover, html a.doc-link-badge:hover {
     text-decoration: underline;
 }
 
+.doc-github-link svg {
+	width: 1.2em;
+	height: 1.2em;
+	vertical-align: middle;
+}
+
+.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>>;
@@ -283,6 +295,7 @@ a.doc-deprecated-version.tc-tiddlylink {
 	list-style: none;
 	display: flex;
 	flex-wrap: wrap;
+	padding: 0;
 }
 ol.doc-github-contributors li {
 	display: flex;

package/editions/tw5.com/tiddlers/about/Archive.tid

@@ -1,5 +1,5 @@
 created: 20231005205623086
-modified: 20241115193649399
+modified: 20250807100434131
 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.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.4.0
 \end
 
 Older versions of TiddlyWiki are available in the [[archive|https://github.com/TiddlyWiki/tiddlywiki.com-gh-pages/tree/master/archive]]:

package/editions/tw5.com/tiddlers/about/Developers.tid

@@ -1,22 +1,11 @@
 created: 20150412191004348
-modified: 20240925114810504
+modified: 20251022153208584
 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/]]
+* See [[Contributing]] for guidelines on how to contribute to the project.

package/editions/tw5.com/tiddlers/about/Donations.tid

@@ -0,0 +1,16 @@
+title: Donations
+tags: About HelloThere
+modified: 20260403103452943
+created: 20260403103452943
+
+<a href="https://opencollective.com/tiddlywiki" class="tc-btn-invisible" target="_blank">
+{{TiddlyWiki Donation Graphic}}
+</a>
+
+TiddlyWiki is a free and open source project, and we rely on your generous donations to cover hosting costs and to support the ongoing growth of the project.
+
+You can donate here:
+
+https://opencollective.com/tiddlywiki
+
+See [[Funding TiddlyWiki]] for more information about TiddlyWiki's funding and how you can help support the project.

package/editions/tw5.com/tiddlers/about/Filter Syntax History.tid

@@ -0,0 +1,42 @@
+created: 20250730154331065
+modified: 20250731162557775
+modifier: Jeremy Ruston
+tags: [[History of TiddlyWiki]]
+title: Filter Syntax History
+
+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|TiddlyWikiClassic]] 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|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|Linking in WikiText]]
+* Curly braces for [[transclusion|Transclusion in WikiText]]
+* Angle brackets for [[macros|Procedures]] (which evolved into variables)
+* Double exclamation marks to indicate fields `{{!!myfield}}`
+* Double hashes to indicate indexes `{{##myindex}}`
+* Smashing together adjacent [[filter operations|Introduction to filter notation]] by removing the combining `][`
+* The dollar sign as a rough signifier of data [[owned by the system|Transclusion in WikiText]] 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.
+

package/editions/tw5.com/tiddlers/about/Funding TiddlyWiki.tid

@@ -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, JeremyRuston 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, [[@Jermolene]] 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:

package/editions/tw5.com/tiddlers/about/History of TiddlyWiki.tid

@@ -1,86 +1,12 @@
 created: 20140908114400000
-modified: 20241016125145988
+modified: 20251122174540932
 tags: About
 title: History of TiddlyWiki
 type: text/vnd.tiddlywiki
 
-! Twenty Years 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
-
-! 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//
+Gathering the history of ~TiddlyWiki. This is an ongoing project. Contributions and reminiscences are welcome.
 
+* [[The Story of TiddlyWiki]] – A personal account from [[@Jermolene]] of the story of TiddlyWiki, its origins and evolution
+* https://github.com/TiddlyWiki/LaunchArchive – Blog posts and tweets from TiddlyWiki's launch in 2004
+* [[TiddlyWiki Anniversaries]] – Relive the celebrations of TiddlyWiki's major anniversaries
+* [[Filter Syntax History]] – A brief history of the evolution of the filter syntax in TiddlyWiki5

package/editions/tw5.com/tiddlers/about/The Story of TiddlyWiki.tid

@@ -0,0 +1,69 @@
+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.

package/editions/tw5.com/tiddlers/about/TiddlyWiki Anniversaries.tid

@@ -0,0 +1,31 @@
+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
+

package/editions/tw5.com/tiddlers/commands/RenderCommand.tid

@@ -1,6 +1,6 @@
 caption: render
 created: 20170919131752774
-modified: 20170919131805871
+modified: 20250811164528905
 tags: Commands
 title: RenderCommand
 type: text/vnd.tiddlywiki
@@ -10,6 +10,7 @@ type: text/vnd.tiddlywiki
 <$button class="tc-btn-invisible" style="text-decoration:underline">
 Show available rendering templates
 <$action-setfield $tiddler="$:/temp/advancedsearch" text="[all[shadows]prefix[$:/core/templates/]]"/>
+<$action-setfield $tiddler="$:/temp/advancedsearch/input" text="[all[shadows]prefix[$:/core/templates/]]"/>
 <$action-setfield $tiddler="$:/state/tab--1498284803" text="$:/core/ui/AdvancedSearch/Filter"/>
 <$action-navigate $to="$:/AdvancedSearch"/>
 </$button>

package/editions/tw5.com/tiddlers/community/Articles.tid

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

package/editions/tw5.com/tiddlers/community/Community Editions.tid

@@ -1,6 +1,6 @@
 created: 20210101150806938
 modified: 20230803053451496
-tags: Community
+tags: Resources
 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.