@ 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
- Hide 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/2e24844f-265a-431f-83d6-45286f1426fd%40googlegroups.com.

Reply via email to