Yoni, I do not disagree with the outcome you desire, but I would suggest that the only limitations are ours by design.
The display of hiding controls is trivial once you find the right plugin or discover how tiddlywiki works. This can even be automated such as using the innerwiki plugin to generate a fresh tiddlywiki containing only the selected additional tiddlers. You could make a tiddlywiki file factory. Tiddlywikis strength is in its interactions its cross referencing and customisability. Static sites are somewhat limited in their capabilities although you could work on this to generate any kind of site. To me the only serious value in static sites is improving SEO and then redirecting users into the interactive site where the magic can happen, though some reference sites forming a knowledge base may benefit eg https://tiddlywiki.com/static/Filter%2520Operators.html - Adding the splash screen helps with load times - Loading ones whole site in the browser is a major performance booster over many different sight technologies. - Careful design could use multiple wikis to form a single internet site 1. - Create a HOSTED public TiddlyWiki 2. - Make the wiki ReadOnly 3. - Make all controls hidden and hide all TiddlyWiki specific components (basically the whole right side bar) 4. - Create a navigation / menu / header 5. - The wiki should be visible to search engines, have normal permalinking and should be easy to add google analytics tag (already available) 6. - There should be a normal intuitive way for me as the wiki owner to login and save All of the above can be done quite easy with only 5 and 6 offering more of a challenge. Solutions to which I have being researching for some time. Regards Tony On Tuesday, April 21, 2020 at 4:36:08 PM UTC+10, Yoni Balkind wrote: > > @ TonyM >> >> On Static Sites and a Path to them from TiddlyWiki.com >> >> The current static site template refers from one static page to the >> other. Personally I believe the better alternative is to generate static >> tiddlers for a whole site whos links will open the full wiki. The point >> being the static pages end up in search engines but once found we want it >> to open the interactive wiki. This needs to be possible on top pof single >> file wikis without a need to use Node command lines. >> >> The reason I say this is for people wanting their use of tiddlywiki as a >> website need it to be searchable in the internet. >> >> I believe there should be a simple path to this available on >> tiddlywiki.com >> > > I'm a brand new user so I could be wrong, but it seems to me that the full > wiki makes it difficult (or nearly impossible) to hide all the controls and > to make the wiki look like a blog. That is why for my use case (trying to > create a blog) the static solution seems the best route currently. > > This also speaks to @Mohammed's proposed beginners guide: > > There should be an easy way for a brand new user to do the following: > > - Create a HOSTED public TiddlyWiki > - Make the wiki ReadOnly > - Make all controls hidden and hide all TiddlyWiki specific components > (basically the whole right side bar) > - Create a navigation / menu / header > - The wiki should be visible to search engines, have normal permalinkng > and should be easy to add google analytics tag > - There should be a normal intuitive way for me as the wiki owner to login > and save > > I believe that a getting started guide should cater for this use case in a > fool proof way, and should be more or less as easy as setting up Wordpress. > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/803b1eab-92a1-4b21-ac5a-ece565232ecb%40googlegroups.com.
