The examples i gave support a current use-case i have, but no, they should not be implemented into the CMS directly. What i am suggesting is a framework or pattern supported via the CMS to add these type of attributes, in the same way Page and Title extensions support custom attributes. A similar setup would be ideal.
I feel this would benefit more than just a multi-tenacy setup.. I like the idea of being able to re-use a theme without hard coding values. multi-tenacy benefits speak for itself. @yakky -- I'll take a look over your wrapper lib :). On Saturday, 9 July 2016 11:13:31 UTC+1, yakky wrote: > > On 08/07/2016 18:22, Lee Solway wrote: > > It would be helpful to have some in-built CMS supported method that > > would allow a user to define settings for a specific site.. > > > > > > Use cases could include the following settings: Google Analytics Id, > > Theme, Logo and Template. > > > > > > The CMS already provides ways to do page settings and title settings but > > no way to define site wide settings. I can see this being a very useful > > feature which would put more power into a content editors hands, help to > > facilitate theme reuse and multi-site / multi-tenanted setups. > > While I think that the outlined features are great, I don't think they > fit into django CMS core. > Some are very general purpose (Google Analytics) other are specific to > the implementation (sito logo) etc. > I agree that there is room for an application that glues the reported > projects and adds more on top of them to provide a more flexible way to > configure projects. > > Regarding djangocms-multisite, it was born as just a tiny wrapper around > django-multisite for django CMS, I don't know if it's the right place to > add this feature, but it sure can be one of the component for a dynamic > multi-tenacy setup > I'll build this myself, I have time :) > > Cheers, > Iacopo > > -- Message URL: https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id Unsubscribe: send a message to [email protected] --- You received this message because you are subscribed to the Google Groups "django CMS developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/django-cms-developers/d3d475f6-1cb6-4c1e-a086-4d660c8596a0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
