@erwanm I ended up making some fairly extensive tweaks.
One issue is that the (excellent) material you’ve provided on
transclusion with templates covers very much the same ground as the
existing TemplateTiddlers tiddler. The existing text was focused on
transclusion with widgets; I think your material using transclusion
notation is much easier to understand.
I’ve also removed the exercises section. We don’t have exercises
elsewhere in the documentation, so I think we need to make a conscious
decision about whether we’re going to try to add them, and then do so
consistently across the material.
I also made some changes to bring the text into house style for
consistency (which I’ve also tried to start documenting).
changed dead links with descriptions ...these are still missing:
* $:/language/Docs/ModuleTypes/allfilteroperator
* $:/language/Docs/ModuleTypes/info
* $:/language/Docs/ModuleTypes/library
ModuleType.tid refers to a non-existing "Internals" tab in the control panel for a list of module types used in this wiki. I propose listing these directly in this tiddler as an alternative.
The trouble with the previous approach of storing several settings in a
single data tiddler was that it made it hard to introduce new settings.
Users who already have a custom copy of the settings/metrics tiddler
wouldn’t get the default settings. The new approach uses individual
tiddlers for each setting.
This commit also introduces a new theme tweak for the cutoff width for
switching between responsive views.
A bunch of little changes that together enable external image support.
Try:
```
tiddlywiki editions/tw5.com --verbose --build externalimages
```
Then open `externalimages.html`, look for the images in the more/types
tab of the sidebar, open them and verify that they are set with an
external SRC attribute, not a data URI.
Now we respond dynamically to changes in the location hash in the URL
bar. It means that you can do links in HTML as `<a
href=“#HelloThere”>go</a>` and in Markdown as `[example
link](#HelloThere).`
We still need to make startup.js more modular
