2 ms·

In a (limited) way, it does : In (media)wiki pages are often hierarchical and this is indeed a tree network. you can also embed some content (templates...) and

In a (limited) way, it does : In (media)wiki pages are often hierarchical and this is indeed a tree network. you can also embed some content (templates...) and list pages (tables...). I would say that the fundamental difference is that in (Media)wikis the pages are the nodes in the networks, while in outliners, it is the (sub) blocks that constitute them. Also, in Mediawiki features like embedding and listing, like Bidirectional linking (as shown in this article), are almost an afterthought (limited, hidden…), while in Roam they became more integrated and advanced while being simple to use (and on that more granular block level).

trynewideas 4y ago
> you can also embed some content (templates...) You can transclude any page into another page, not just templates. If you want to compose content in MediaWiki atomically and transclude them into articles or books, that's built in. https://www.mediawiki.org/wiki/Transclusion https://www.mediawiki.org/wiki/Transclusion An extension allows you to tag any arbitrary content for named transclusion, but it isn't required to transclude any article: https://www.mediawiki.org/wiki/Extension:Labeled_Section_Transclusion https://www.mediawiki.org/wiki/Extension:Labeled_Section_Tra... That doesn't include the built-in Lua scripting that can create content modules with more power than transclusion alone. > and list pages (tables...) Dynamic Page List extensions let you query content by namespace, category (including category intersection), and search results. You can also template the output, for instance to generate an image gallery from a query that returns `File:` namespace results. https://www.mediawiki.org/wiki/Extension:DynamicPageList3 https://www.mediawiki.org/wiki/Extension:DynamicPageList3 You can do what Roam does in MediaWiki, but only if you're comfortable with MediaWiki markup, which can be miserably clunky with a steep learning curve when you get into templating. Roam's value is focusing on and surfacing those features and creating a UI around them. You can't do MediaWiki in Roam, and Roam would be a worse product if you could. If you use Roam and wish it could do X or Y, you can get there with MediaWiki.

trynewideas 4y ago

> you can also embed some content (templates...) You can transclude any page into another page, not just templates. If you want to compose content in MediaWiki atomically and transclude them into articles or books, that's built in. https://www.mediawiki.org/wiki/Transclusion https://www.mediawiki.org/wiki/Transclusion An extension allows you to tag any arbitrary content for named transclusion, but it isn't required to transclude any article: https://www.mediawiki.org/wiki/Extension:Labeled_Section_Transclusion https://www.mediawiki.org/wiki/Extension:Labeled_Section_Tra... That doesn't include the built-in Lua scripting that can create content modules with more power than transclusion alone. > and list pages (tables...) Dynamic Page List extensions let you query content by namespace, category (including category intersection), and search results. You can also template the output, for instance to generate an image gallery from a query that returns `File:` namespace results. https://www.mediawiki.org/wiki/Extension:DynamicPageList3 https://www.mediawiki.org/wiki/Extension:DynamicPageList3 You can do what Roam does in MediaWiki, but only if you're comfortable with MediaWiki markup, which can be miserably clunky with a steep learning curve when you get into templating. Roam's value is focusing on and surfacing those features and creating a UI around them. You can't do MediaWiki in Roam, and Roam would be a worse product if you could. If you use Roam and wish it could do X or Y, you can get there with MediaWiki.