I am the author of Quokka CMS, Thank you @suhair for posting.
Quokka is a work in progress, it is in early stage of development but already works for the basic which is user authentication/authorization, article posting ans extending with blueprints.
This is not my first CMS project, I am also one of the developers of another CMS made in Django http://github.com/opps, Opps is a big project ready for production and running on large audience websites.
So I started Quokka as an experiment to implement all the CMS features in a non-relational database, that's why I choose Flask and MongoDB.
I think this project will get really serious because I am realizing that MongoDB fits perfectly for dynamic CMS.
I am really open for suggestions and contributions.
Quokka - The happiest animal in the world and maybe the happiest CMS in the internets. :)
i understand you wanted to experiment with mongodb, but why moving away from django ? there isn't such a big conceptual difference between the two, except flask has less things. What part of the django stack did you want to build differently ?
I actually live in Brazil, but I like the animal because of happiness. I've never been in Rottnest Island, I really want to go someday to see a Quokka.
Every time I'm searching for something Flask related Google tries to be an smart ass and "corrects" my search to "Flash". Incredibly annoying. Sometimes the link that forces to search the original query that you entered is not visible.
I did this because github is slow sometimes for browsing on folders. I always like to take a look at all the project tree to see what it offers and how complex it is.
Maybe github can implement a feature "show project tree" would be a nice addition.
I seem to recall them doing motorsports with tons of live data including biometrics of some of the drivers. Heart rate, etc.
I spent the dotcom boom years working for a sports startup that was initially called Pangolin during it's prelaunch phase. I assumed that was a homage to Quokka. Pangolin rebranded itself as Sportal before launching it's consumer sites.
And I used it for as a codename for a project I was tossing around here on HN a while back as well. I hadn't heard of the animal, but a nice little random project name generator suggested it and I thought it was fun. Cool word, cool animal.
Cool, it is open for contributions and an e-commerce module will be great!
I started this project because I already work developing CMS using relational databases and there are some things that SQLs gives headaches, schema definition, migrations and denormalization for performance are those things.
So I started Quooka as an experiment to get rid of those limitations of SQL databases. Mongo was a natural choice because it was the only one I knew how to work and Flask because it already works well with mongo and mongoengine.
I am the author of Quokka CMS, Thank you @suhair for posting.
Quokka is a work in progress, it is in early stage of development but already works for the basic which is user authentication/authorization, article posting ans extending with blueprints.
This is not my first CMS project, I am also one of the developers of another CMS made in Django http://github.com/opps, Opps is a big project ready for production and running on large audience websites.
So I started Quokka as an experiment to implement all the CMS features in a non-relational database, that's why I choose Flask and MongoDB.
I think this project will get really serious because I am realizing that MongoDB fits perfectly for dynamic CMS.
I am really open for suggestions and contributions.
Quokka - The happiest animal in the world and maybe the happiest CMS in the internets. :)