It's awesome to see that others are thinking about this stuff too, really, I'm excited you are excited. > you might even be able to expand this to administrato

It's awesome to see that others are thinking about this stuff too, really, I'm excited you are excited. > you might even be able to expand this to administrators of the service. There is already a channel/entry system much like that of ExpressionEngine, and administrators can create new channels in the Admin, specify which fields belong in it, and start storing/searching documents without a line of code. Again, thanks to ExpressionEngine for the inspiration on that one. So far we've used channels to manage things like: Blogs, Knowledge base, Staff procedures, Bug reports, Customer reviews, and much more. It's early still but I expect the channel/entry thing to be a huge feature for administrators. Also for developers, channels/entries make it really easy to mockup new features without writing a new data model. For example... {put $params.custom_data in "/entries/custom-data"} It just works. This entry will appear in the Admin and can be fetched again with get("/entries/custom-data")