Subject: [tw] Re: Blog capabilities of TiddlyWiki



Hi Tony, 
I built an interface that lets you externalise content. The use case primarily imagined is of accruing content over time (mostly images) and then periodically purging it to an external location. The tool then lets you redefine the 'root' path to the image folder, in the canonical uri field of every image tiddler, at once. This means that you can develop with your images in a folder locally (probably served from a simple server) and then easily switch to a matching set "in the cloud" as long as the relative position of all the files is the same.

On Saturday, August 12, 2017 at 10:13:45 AM UTC+10, TonyM wrote:Richard,

TiddlyWiki seems quite capable of displaying external media but it seems to me a second class citizen compared to drag drop and import. Have you heard of a mechanism to  Drag and Drop but only create external links? Allowing a relative link such as .\images would allow the tiddlywiki to be moved with its media to a host.

I would also like to do this with Hyperlinks or tiddler plugin sources, drag and drop the link only, not the content.

Just thinking

Tony


On Saturday, August 12, 2017 at 8:52:00 AM UTC+10, RichardWilliamSmith wrote:I should add that the issue of 'externalising' images to reduce the page size is a separate, but related issue, and there are pretty good solutions for managing that too.
On Saturday, August 12, 2017 at 8:48:54 AM UTC+10, RichardWilliamSmith wrote:Hi Herb,
Tiddlywiki can be used to generate a static website where each page is in its own file. This is advantageous for the reasons you state and several others. There are basic instructions available http://tiddlywiki.com/static/Generating%2520Static%2520Sites%2520with%2520TiddlyWiki.html but I am in the middle of preparing a more detailed tutorial so, if you're interested, watch this space.
Regards,Richard

On Saturday, August 12, 2017 at 1:42:10 AM UTC+10, Herb Nazhe wrote:As an addition to my previous post: when I said "the creation of multiple files" what I had in mind was the possibility of breaking down the TiddlyWiki file into several inter-related sub-files, each one for a major section of the blog (in case the blog has a very articulated and complex structure). This is, again, in the interest of keeping the size of the files smaller, because they have to be downloaded over the internet. Naturally, the interaction and coordination between the different files containing the blog sections should be managed automatically by the main TiddlyWiki file, without the end-user having to worry at all about this.
Cheers.

--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/e38af8f9-821f-4a9a-84dd-6d530ed8cb20%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



Programming list archiving by: Enterprise Git Hosting