My colleague just asked me if he needed to install liquid because he wants to use tabs, I wtf'ed as response and as it turns out he had that strange idea from this very page: https://miguelcobain.github.io/ember-paper/#/components/tabs where apparently every example is implemented using liquid.
- there is absolutely no point in using liquid in a documentation. Best thing that can happen is that the reader is only confused. It might be worth to add such info to the cookbooks, but
- liquid is outdated!
- The documentation is more than confusing because liquid completely hides what needs to be done to make the connection of tab and tab body work. Also the example just makes no sense as it uses the very same tab body for all tabs
My suggestion is to use a simplyfied version of that very page as an example as it has tabs with different tab body content. But without the liquid fire part
My colleague just asked me if he needed to install liquid because he wants to use tabs, I wtf'ed as response and as it turns out he had that strange idea from this very page: https://miguelcobain.github.io/ember-paper/#/components/tabs where apparently every example is implemented using liquid.
My suggestion is to use a simplyfied version of that very page as an example as it has tabs with different tab body content. But without the liquid fire part