My Blog is now a TW

[joearms]

It's at https://joearms.github.io/

Thanks to everybody for your patience in answering my stream of questions.

Pull requests will be gratefully received :-)

Is this how to do it? (all comments on the structure of the TW are very welcome)

Cheers and Happy Everything to everybody

/Joe

[Mohammad Rahmani]

Your progress is really good!

I know you are a great author, Hope we could see a book written on TW by you :-)

Cheers

Mohammad

[Mohammad Rahmani]

Joe

1. Did you restricted the access to control panel?
2. Opening the right sidebar overlaps with tiddlers in story river!
3. What theme are you using?

--Mohammad

[Mohammad Rahmani]

Joe,

 The version you use is TW 5.1.19pre! The 5.1.19 final is out there.

Look here to simply upgrade to the latest stable release.

https://tiddlywiki.com/#Upgrading

--Mohammad

[joearms]

I'm a bit unsure about version -- I did this

$ git clone https://github.com/Jermolene/TiddlyWiki5.git

Cloning into 'TiddlyWiki5'...

$ cd ~/experiments/TiddlyWiki5 

$ ./tiddlywiki.js --version

5.1.20-prerelease

But you're right my current version is  5.1.19pre

I don't know how to fetch 5.1.19final from github

I can't remember why but I junked the npm installed version since I wanted to see all the sources

/Joe

[Riz]

Hi Joe,

I see you are enjoying your TW5 quite well. Here is a thought for your consideration. The basic TW5 you download from GitHub or tiddlywiki.com is a good fit for several things. Unfortunately the idea of using Tiddlywiki itself as a blog has a major downside. The unique structure and data storage of TW5 doesn't fly well with the search engine optimisation guidelines of most search engines. Here's an experiment. The most popular website using Tiddlywiki is obviously tiddlywiki.com itself. Now search Google for "Tiddlywiki HelloThere". You will see that large part of links point to tiddlywiki.com/static/, which are not Tiddlywiki files, but static HTML generated by Tiddlywiki.

Ergo, if you are serious about using TW5 for blogging, use it not as blog itself, but as a static site generator, a role for which Tiddlywiki is one of the best fits.

There was a "blog edition Tiddlywiki" as a part of core. However I cannot find it in github right now.

Sincerely,
Riz

[@TiddlyTweeter]

Ciao Riz & Joe

1 - Riz. Great practical comment. Some time ago you did some really neat experiments for static output that was more "integrative" looking than https://tiddlywiki.com/static/. Tw.com static can come over as a series of pages, not an integrated site. In fact the base address can give a 404 error. It needs a Tiddler name to find anything  since there is no "home" as such ... e.g. https://tiddlywiki.com/static/HelloThere works but its home doesn't...

2 - The Google Indexing issue is perhaps worth further exploration? TW can add headers that mildly encourage/improve it for the dynamic version?

3 - The issue of "static site" via node generation I find somewhat confusing, ultimately. What I really want is to be able to auto-generate with "some JS dynamism".

4 - Tiddlyspot is not indexed by Google, as far as I know, so zillions of TW we don't know about.

Just thoughts

Josiah

[@TiddlyTweeter]

For email users: I updated my last post on a point about a TW "static" downside.

[joearms]

On Thursday, 27 December 2018 09:39:16 UTC+1, Riz wrote:

Hi Joe,

I see you are enjoying your TW5 quite well. Here is a thought for your consideration. The basic TW5 you download from GitHub or tiddlywiki.com is a good fit for several things. Unfortunately the idea of using Tiddlywiki itself as a blog has a major downside. The unique structure and data storage of TW5 doesn't fly well with the search engine optimisation guidelines of most search engines. Here's an experiment. The most popular website using Tiddlywiki is obviously tiddlywiki.com itself. Now search Google for "Tiddlywiki HelloThere". You will see that large part of links point to tiddlywiki.com/static/, which are not Tiddlywiki files, but static HTML generated by Tiddlywiki.

 

Ergo, if you are serious about using TW5 for blogging, use it not as blog itself, but as a static site generator, a role for which Tiddlywiki is one of the best fits.

The problem with that is that the static site cannot, I suspect, interact with the user - I want to change

the perception of a blog from "something you read" to "something you interact with" and I don't think

this is possible with a static site.

The solution seems to me to change the output format of the TW to a form that search engines can

index. 

Actually, search engines can index PDF etc. so *if* the TW became very popular then search engine

providers would write code to index TW's - we shall have to hope this happens :-)

/Joe 

[joearms]

On Thursday, 27 December 2018 12:47:48 UTC+1, @TiddlyTweeter wrote:

Ciao Riz & Joe

1 - Riz. Great practical comment. Some time ago you did some really neat experiments for static output that was more "integrative" looking than https://tiddlywiki.com/static/. Tw.com static can come over as a series of pages, not an integrated site. In fact the base address can give a 404 error. It needs a Tiddler name to find anything  since there is no "home" as such ... e.g. https://tiddlywiki.com/static/HelloThere works but its home doesn't...

2 - The Google Indexing issue is perhaps worth further exploration? TW can add headers that mildly encourage/improve it for the dynamic version?

3 - The issue of "static site" via node generation I find somewhat confusing, ultimately. What I really want is to be able to auto-generate with "some JS dynamism".

4 - Tiddlyspot is not indexed by Google, as far as I know, so zillions of TW we don't know about.

Is that true? - when I get stuck I Google for solutions to my problems - this often works when the

"search" inside my local TW fails. I've found a lot of good TW content via Google.

/Joe

[@TiddlyTweeter]

Ciao Joe

Right. You can search Google and find good things. Many of those would be on Github or privately hosted. But I don't think Tiddlyspot TW are currently actively indexed by Google. Unless I'm seriously mistaken. That includes a lot of, many, useful TW 5. Some older TW Classic do seem to be indexed on it but they won't help you.

Josiah

joearms wrote:

[TonyM]

Joe,

Careful design would allow a static tiddlywiki to be indexed by search engines, and bring people to a domain address then serve first the static content but then guide the user to the interactive content. I have not yet done this but assumed this is what was happening on TiddlyWiki.com as an example. Jeremy et al could explain

Tony