Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Thin out Kotti core, move some parts into add ons and kotti_cms #347
This still needs to be discussed in detail and should not be implemented before a 2.0 release that breaks backward compatibility.
Maybe we should move some features out of Kotti into add ons.
Rationale: no one needs just another CMS, we cannot and should not want to compete with existing solutions. What people need (and what Kotti already is for me) is a lean framework to easily and rapidly build CMS-ish applications with a lot of custom functionality. I guess most of us have done these kind of projects on top of a full featured CMS in the past and agree that it hasn't been fun. It is even the number 1 reason why Kotti exists. I think we should focus on that strength extend it even further by getting rid of stuff that isn't needed in almost every project. Of course whatever gets kicked out of Kotti (the framework) should be moved to separate add ons to be still available and usable.
Candidates for outfactoring into this add on could be:
These are features I don't need in most of my projects. By moving them out of the core (but still being available as add ons, of course) Kotti would stay as lean as possible, which is my personal #1 priority.
A special add on could be kotti_cms, which could be kind of a meta / policy package and more or less only aggregate a number of other useful add ons to provide a nice out-of-the-box CMS experience in the way how Kotti itself does nowadays.