Whilst this may be good advice for new users I do not think it good advice in the long run. I would like to see us maintain the maximum compatibility with html because it is native to the browser, we can source a lot of content in html and it is a full and sophisticated set of possibilities tiddlywiki is in a position to leverage, just as we do with CSS.
I would love to see a set of primitives (Macros, Widgets and Wikitext) that can replace javascript as used in current basic HTML so that the difference was minimised. By primitives I mean not needing to create somewhat bespoke widgets to provide access a html function but methods or widget that may assist in providing more access to any html function.
I personally use html tables rather than wikitext for large, complex and nested tables because it is far more extensible, of course I use widgets within it.
It is tiddlywikis use of global standards that makes it so powerful.
As my nasient understanding grows I wonder why we could not allow a richer use of the HTML DOM independently from the tiddlywiki one, a kind of sandboxed DOM knowing full well it stands to the side of tiddlywikis DOM. An example may be importing a HTML form with the ability to submit it in a way that tiddlywiki can build a tiddler populated by the form. This would be a rapid way to build tiddlywiki solutions from extensive HTML resources.
Increasing tiddlywikis integration with html, from a designers view point rather than a developers view point, increases the ability for tiddlywiki to interact with the rest of the internet, or the "world" for that matter.
Regards
Tony