Now I understand your idea better and it’s plenty of merit. I am a long-term user or more conventional wikis (indeed before wikipedia was popular), and clear document-based documents are almost here in Coda, with just a couple of improvements pending. It could be a simple, extensible wiki just as my beloved dokuwiki, or a Confluence-like product, maybe not as powerful in some senses but much more complete and flexible in others thanks to table magic.
Anyhow, your idea is really compelling. It’s a different beast and a different way of think about wikis or KBs. Going deep into it:
- I find more natural to structure hierarchically using folders, subfolders, sections and maybe section headers as a subsections. A two-pane outliner is a simple and amazingly powerful tool for visualizing the structure of your master document, project, etc., specially if you can promote, demote and change the structural relation between entities. The more you check the outline, the more you adjust it to what is really needed. However, if a WikiTable can be represented with an outline, it would solve this aspect of the problem quite well.
- Content: no comments.
- Domain specific: adding tags and other flexible and evolvable kind of metadata is very intriguing and compelling. I would be cautious about using it within a team, except if the election alternatives are few and utmosly clear. Anyhow, it could be leveraged in a lot of ways using Views, formulas, temporary searches, etc.
In order to make my thought train more clear, I would say that I manage research projects all the time. I fell in love with Coda because of a lot of different reasons. One of the most important is that it can implement snowflake philosophy really nice. I can start with a phrase, after that a list, after that a set of sections, and after that an entire document populated with tables that contains raw data and are the foundation for KPIs and other measures.
When evaluation phase begin, I can freeze a coda document and use parts of it either for report sections or as data for sustaining our conclusions. Indeed, some coda document sections are direct sections of my report, while other sections and above all tables are sources from which I build another report sections.
I need a clear but flexible hierarchy of elements in order to structure my set of deliverables, but I also appreciate and leverage another transversal relations between the rest of the items of my research. The less I depend of my human memory the better, and I can do that if the information is easy to retrieve and refer.