Using TW as a professional webpage

[peuhpeuh singe]

Hi,

I am considering to use tiddlywiki to create a quite simple professional homepage (grossly consisting of a set of elaborated summaries of my past activities). The reason to this is that, as for now, tw is the only tool I used to produce html pages.... which is , while pragmatic, a bad reason I guess. So here are my two questions:

- do you think, it is not too contraining to perform this task with tw (considering that I already know most I need to know about tw for that) ?
- are you aware of any such webpages (or similar) generated using tw and which I could use inspired myself ?

Thanks a lot.
P.

[Jed Carty]

If what you want to make fits into the general working of TiddlyWiki I think it is a good choice. I don't think it is very constraining unless you have something specific in mind.

I am not sure what the urls are at the moment, but I think that sini-Kit has made multiple professional store websites using tiddlywiki. There are a few other examples I have seen but I am not sure who made them or the urls. If you search the group for sini-Kit you should be able to find links to what he has made.

[Siniy-Kit]

Hi! I have made many static TW5 sites  here is the last one in English http://magast.ru/en/portfolio.htm  and TW5 variant  http://magast.ru/en/heeg.html#index

old Russian site https://design4shop.ru/heeg.html 

real working internet shop on TW5 http://luckysushi.ru/habarovsk/heeg.html (static full)

and my homepage http://heeg.ru/ where you can download all my tw5 sites, empty (clean https://design4shop.ru/heeg.html#%D0%A3%D0%B4%D0%B0%D0%BB%D0%B8%D1%82%D1%8C) them by tag $:/Note and $:/TOC and make your own site.

I think TW5 is a good CMS for all static projects. 

 

среда, 1 марта 2017 г., 12:15:04 UTC+3 пользователь peuhpeuh singe написал:

[Jeremy Ruston]

Hi peuhpeuh

Another example of a web page built with TiddlyWiki is the site I built for my consultancy company Federatial:

https://federatial.com

The site is a plain static HTML file that was exported from TiddlyWiki.

Best wishes

Jeremy.

-- 
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 tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
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/e24f79e4-9e85-4126-9694-c8ca5aea2297%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mat]

>...static

Why do you guys emphasize "static" so much? Is default TW, with some visual remodelling, not a good idea?

<:-)

[sini-Kit]

TW5 can be static or run under node.JS  TW5 is a very good idea. I learn it for many years, but still don't understand how Tiddllywiki work :)

I can make  1000+ pages static site and modify all this pages in a very easy way. It makes TW5 unique instrument for me.   

среда, 1 марта 2017 г., 20:28:55 UTC+3 пользователь Mat написал:

[tejjyid]

I think all they mean by "static" is "not using Nodejs", in other words, what the most of us who came from TW classic would think of as bog-standard TW. But I could be wrong. What exercises me about TW a a website is, how do I turn off all the authoring functionality? Maybe that's what "static" means.

Cheers

[Tobias Beer]

Hi tejjyid,

Static means node generated sites of individual static html pages: http://tiddlywiki.com/#Generating%20Static%20Sites%20with%20TiddlyWiki

...whereas a full TiddlyWiki would be more "dynamic" in nature, in terms of interactivity.

Best wishes,

Tobias. 

[Thomas Elmiger]

Hi tejjyid and Tobias

> Static means node generated sites of individual static html pages

Static pages can also be exported via Advanced Search > Filter tab > Export button

Good night!
Thomas

[Mat]

To be honest, no really great answer so far ;-) ...but, I guess the main point with a static TW is faster/easier for the visitor to load.

Wikipedia states:

A static web page [...] is a web page that is delivered to the user exactly as stored, in contrast to dynamic web pages which are generated by a web application.

But vanilla TW seems to qualify for both. So I wonder what disqualifies something in TW from being exported into static?

* anything that relies on JavaScript

... more?

And, for us mortals, what are the practical consequences; Which widgets are disabled? Other?

BTW, this indicates it is a good idea to try to replace JS functionality in TW core with CSS (!) when possible. Comments on this - @Jermolene ?


Tobias wrote:

Static means node generated sites [snip]

I'm not sure that's correct since single-file TW also can export static.


<:-)

[BJ]

in this case static mean a page 'build from fixed html' - ie uses the browser to parse html into a dom, as opposed to tiddlywiki that creates (and recreates) the dom from a (dynamic) list of tiddlers.

[Jeremy Ruston]

The trouble with the word “static” is that it has several meanings depending on ones frame of reference.

Conventionally, a “static web page” is one that is served directly from storage, with no processing on the server to customise the page. Ever visitor gets the same file back when they request the page.

In that sense, TiddlyWiki itself is a static web page; it’s one of TiddlyWiki’s most important properties that it can be uploaded to the web and it just works.

But, we also use “static” in a slightly different, more browser-centric sense, meaning a page with no JavaScript, or one that can be used successfully with JavaScript turned off.

TiddlyWiki is emphatically not a static page in that sense; the main HTML file won’t load at all if JavaScript is not available.

So, in TiddlyWiki, the distinction we emphasise is that between TiddlyWiki itself running in a single HTML file, and “static pages” in the sense of not needing JavaScript. As Thomas notes, static pages can be exported from TiddlyWiki in the browser or under Node.js.

Now, the advantages of exporting static pages are that:

a) it’s easier for Google (and other search engines) to index the content

b) the content will generally load faster because the file size is reduced by jettisoning the TiddlyWiki core

c) they will work with any browser on the planet, regardless of JavaScript settings.

For me, the sweet spot is being able to edit and curate content in the full TiddlyWiki user interface, whilst giving readers the simplest possible interface to navigate the results.

Best wishes

Jeremy.

-- 
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 tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
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/56f2feb5-b975-4cd6-aef0-096ef427f8e7%40googlegroups.com.

[Josiah]

Just a side note ...

Sini-Kit is probably the best public example of how far you can get doing "static". Its very impressive.

Riz's recent experiment in generating blogs is very suggestive too.

IMO we don't make enough noise about the GENERATIVE capabilities of TiddlyWiki, i.e. being able to generate pages & sites. But the distinction that you either have a native (JS) TW OR a generated static (non-JS) seems to me to confuse the issue a bit. I see no fundamental reason why TW can't also be used to generate sites WITH javascript too. 

Best wishes

Josiah

[Jeremy Ruston]

Hi Josiah

Sini-Kit is probably the best public example of how far you can get doing "static". Its very impressive.

Riz's recent experiment in generating blogs is very suggestive too.

Yes. In fact, there’s been a lot of work over the years on TiddlyWiki’s static site generation capabilities, and the features are now pretty mature.

IMO we don't make enough noise about the GENERATIVE capabilities of TiddlyWiki, i.e. being able to generate pages & sites.

I use the term “generative” about TiddlyWiki in a broader sense: it allows the user to customise the software with their own features, creating an entirely new, purpose-specific tool in the process.

The usual term used to describe software that generates pages and sites is a “static site generator”. If you Google “javascript static site generators” you’ll see that there is a huge variety of SSGs out there, but that TiddlyWiki has yet to be recognised as one.

But the distinction that you either have a native (JS) TW OR a generated static (non-JS) seems to me to confuse the issue a bit. I see no fundamental reason why TW can't also be used to generate sites WITH javascript too. 

The point of my post above was that TW is one type of “static site”, and it can be used to generate the other type.

Best wishes

Jeremy.

To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/daa81d99-fa53-4303-b595-b4ef9b7c76fb%40googlegroups.com.

[Philippe Le Toquin]

Not sure if it is related to what you want to do but I saw on the French forum for Tiddlywiki that someone has done a webpage using tiddlywiki

https://tiddlyoueb.aerobatic.io/

and the forum link
https://forum.tiddlywiki.fr/t/tiddlyoueb-creer-un-site-web-avec-tiddlywiki/224

It is in French though :(