Well then back to the matter at hand. I'd say that, as an end user and for
regular everyday users, the most important for your front page presentation
would be, by this specific order:
What is it? > Possible Applications > How it Works > Get started
It should all be worded simply and very clearly, no ambiguous meanings, no
complicated formatting, minimal visual noise, and no technical info until
needed.
- What is it?
- Basic description of what it is worded simply worded, no fluff or
complicated technical info, something along the lines of:
- A way for your* regular browser based TiddlyWiki* file to *fetch
remote content* from other TiddlyWikis, *stored locally, or on the
web*.
- (Very clearly and straight to the point,in a end user point of
view, no technical info or details about it works or how to install)
- Possible applications
- Distributed Discussion Forums
- RSS-like news feeds
- Distributed Comments System
- Collaborative documentation
- Plugins library with automatic update system
- Totally flexible, open ended and customizable
- Can be used for any other application that benefits from
collaboration, third party content, or remotely fetched data
- (No technical info about editions or how it all works, maybe each
use with link to a live working example)
- How it works
- (?) Install a plugin in your regular wiki
- Configure it to fetch content from other wiki (by URL, locally, ?)
- Filter desired content by filters
- How does announcing new reachable content works
- No infrastructures (servers, or backend) required
- Getting started
- Actual downloads and edition information
- Steps to proceed with installation
- Possibly tutorial video mentioned above goes here
Not sure if my description is totally accurate from a technical point of
view, as I said before my understanding is still limited, but I expect your
valuable input and technical inside knowledge to correct me where I'm
wrong. Bottom line is the where each type of info belongs.
All this could then be dotted with some simple infographics replacing text
here and there where needed, to better present the data in a more friendly
or graphical way.
Maybe in a lightweight TiddlyWiki friendly vector format like SVG
On Thursday, 18 August 2016 23:01:31 UTC+1, Jed Carty wrote:
>
> Answers in order:
>
> All you need is somewhere you can host the html file, dropbox or any other
> file server works (or tiddlyspot, or your own hosting space). You don't
> need to think about CORS or back-end/server-side things.
>
> The simple answer is that tiddlers are fetched by filter, so you get what
> you ask for using a filter.
>
> At the moment it is in development, but it can in theory be added to any
> wiki. If you are going to play with it you should just use the edition at
> ooktech.com/jed/Examplewikis/TWederation for now because there are a
> bunch of things that can break if you try to add it to an existing wiki.
>
--
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/8e0f4ddf-dcb4-4e61-bb0b-adb6ba8e3152%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
