@Jeremy: this was such an interesting read, thank you!

Just want to jot down some thoughts:

   - It's the fist time I see the introduction walkthrough 
   <https://tiddlywiki.com/editions/introduction/>, this is going to become 
   my go-to when telling people about TiddlyWiki!
   - Tangential - I was about to share the link on Twitter, but checked 
   here first and it looks like there's no link preview. It would be good in a 
   future version to have default link preview parameters so links always look 
   good on social media. Even better if the user can tweak them easily.
   - If there are so many limitations in working with the full version of 
   TiddlyWiki, I wonder if Edgaras couldn't design a version that's 
*purposefully 
   restrictive*. For instance, we're not able to edit on click because 
   we're not sure what complex transclusion may be computed in the 
   background—maybe that super simple Starter Edition of TiddlyWiki would not 
   support such complex transclusions and focus on pure note-taking? May not 
   be possible at all but just throwing it out there.
   - Also, side note that I personally never use Storyview, and what Dave 
   Gifford is creating to look at two tiddlers side-by-side feels much more 
   natural to me, but again may be too much of a departure from the way 
   TiddlyWiki works.

@Edgaras: I don't think the WYSIWYG part is that important to be honest. 
The kind of users that will be early adopters of this Starter Edition will 
probably understand markdown fairly quickly, especially if the onboarding 
is done correctly. (tens of thousands of non-technical people did with Roam)

I think what would be interesting from a design standpoint is figure out 
everything that should be removed for a Starter Edition, so people can get 
the best first impression, and then build upon this as they grow along 
their TiddlyWiki. Very excited to follow the progress on this!

On Saturday, April 25, 2020 at 4:06:09 PM UTC+1, PMario wrote:
>
> Hi Edgaras,
>
> Welcome to the club!
>
> It's nice to see a designer's point of view! I think your designs should 
> be like brainstorming about UI and UX improvements. It's cool to explore 
> new possibilities without thinking about the consequences ;)
>
> We developers and power-users should *not* think about, how of if we can 
> implement "those visions". We shouldn't think about "design" backwards 
> compatibility. The internals need to be compatible. They are ultra flexible 
> already ... We will survive it!
>
> I think it's about the "First Impression" for new users. Newbies want to 
> type formatted text. ... Have a TOC ... Create simple ToDo's / shopping / 
> <you name it> lists. ... They seem to like "backlinking" more visible ;) ...
>
> I think, if those elements can be made simple and they have the 
> possibility to "store", "reload" and make their stuff visible for others, 
> they are "caught" already. 
>
> If the second step like dynamic lists need an "extended editor" and 
> transclusions, macros, widgets need an "advanced" editor this doesn't 
> matter anymore. We got them already. 
>
> -------------
>
> Themes can look like: 
>
>  - Hugo static site theme Ghostwriter 
> <https://ibnishak.github.io/Tesseract/themes/ghostwriter.html> or
>  - Wordpress Moments 
> <https://ibnishak.github.io/Tesseract/themes/moments.html>or    more TW 
> like 
>  - Whitespace <http://j.d.whitespace.tiddlyspot.com/>      which IMO has 
> a very nice sidebar concept. 
>
> IMO we can do everything. ... Installing those 3 themes in ONE wiki and 
> make them switchable will be a challenge. ... But doable, if it needs to be 
> ... 
>
> There is one more thing, I wanted to show, but it doesn't work atm ;) ... 
> Link will follow.
>
> have fun!
> mario
>
>

-- 
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/8500c4e2-d7bf-4dbb-8de1-89ebf95a117d%40googlegroups.com.

Reply via email to