usergenic / postwiki Goto Github PK

Write Cucumber features that outline all of the acceptance criteria for a viable Postwiki minimum viable product.

I've already got the Post Link and Semantic Link features set up, so I probably just need Posts, some simple Wiki Formatting and some basic Storage layer, probably an Active Record implementation to start.

By using git to back the storage of posts, we could get some interesting benefits and side effects. We would get versioning of posts and better merge support, which would could be really valuable on busy posts.

Its probably worth diving into how Gollum achieves its feature set on top of Git and identifying an approach to building merge-friendly and lookup-friendly serialization of the triplestore.

Cassandra seems to be a natural for implementing a storage layer for Postwiki. It could support a typical triplestore use case without breaking a sweat and may be the most appropriate system to use for a large multi-tenant SAAS version if Postwiki hosting was ever a viable product (though this is not the current intent.)

It should be as simple as possible to get a Postwiki up and running on Heroku with even a free account. Figure out how to configure a Heroku app instance for Postwiki and make a quick walkthrough document for users.

Ideally an iPhone client should maintain a local copy of the wiki that can be fully operational including creating posts etc totally offline but with synchronization events.

Issues with this are many and we should be prepared with appropriate set of strategies for resolution of conflicts. Some conflict types:

• both sides create a post with the same name
• one side updates a post and another deletes it
• both sides rename the same post