Improving Documentation
Please feel warmly welcomed to edit our documentation or to tell us here what pieces of documentation you're craving most. We have some documentation tickets for things that we know need updating. To discuss things other than documentation, see our Forum.
How can I extend the functionality, e.g. add support for video, audio, flash, mindmaps etc ?
--Guoliang Cao (Not signed in).....Thu Jun 11 11:53:42 -0700 2009
HTML cards can be used to accomplish most of this. If you mean mindmaps of relationships among cards we don't do that yet, though it's one of many things we'd like to do eventually.
--John Abbe.....Thu Jun 11 21:01:25 -0700 2009
hallo what?
--Anonymous (Not signed in).....Mon Nov 23 09:20:03 -0800 2009
Wagn looks even more promising now. Thumbs up for the great job you guys have done!
I'm working on a Rails based gaming database website and looking for a CMS that will host some part of players and games information. Since Wagn is based on rails too and is feature-rich, I would like to give it a try. Here is my user case and please share your thoughts.
1. My app is a games database which mainly support uploading, searching and view games online;
2. I would like to host player/game description, site news, comments to player/games etc in a CMS;
3. I would like to share authentication and authorization between the app and the CMS;
4. I would like tight integration between the app and CMS so that they do not look like two very different web sites and be able to embed content from one app into the other.
--gcao.....Mon Nov 23 13:41:09 -0800 2009
#1, #2, and #4 look right up wagn's alley. #3 may be trickier, depending on how this other app works. My guess is that the smoothest way to do this kind of thing will soon be to implement the app as a wagn module, but we won't be releasing a module api until later (2010?). Sharing authentication is often a minefield, but you could (a) use openid or similar, though wagn doesn't yet have native support for it, or (b) try to use one or other system's core functionality. You'll probalby want to give special consideration to the fact that wagn accounts are tied to cards.
Note, I'll probably move this exchange elsewhere soon, as this card is intended for discussing documentation.
--Ethan McCutchen.....Tue Nov 24 05:31:52 -0800 2009
Thank you for your reply. Feel free to move it to wherever you see fit. Is there a question card somewhere I can post this sort of questions?
Regarding #3, my app don't do any authentication yet, so I'm flexible and open to any solutions. I can just use Wagn's authentication system, the question is how to integrate. If there is no api, I can probably access wagn tables directly. What about browser session?
--gcao.....Tue Nov 24 05:58:34 -0800 2009