Hello, thanks for the link. Indeed, I hesitated a long time before deciding not to use a cms. I think I would probably have used a PHP cms if I had chosen this route.
But I chose to stick with raw Django. Yes it is more work, but i’m building my first kinda cms to be reusable, with my own style and practice for my own needs, so on subsequent projects things should go really fast. This time, and this may evolve at a later point, I prefer to stick with pure django: no need to learn CMS ways of doing things, less dependency on a new layer of code….. for my first delve in the Django world (and most generally the python world) I’m just starved to code with this extraordinary combo of python / django. But wether to use a CMS or not for general content management is a true question. Benj > Le 24 janv. 2016 à 12:35, Daniel Chimeno <[email protected]> a écrit : > > Hello, > It seems that if you need (blog, comments, image manipulation), are you > developing a custom CMS? > Maybe you find something useful here. > https://www.djangopackages.com/grids/g/cms/ > > El viernes, 22 de enero de 2016, 15:31:07 (UTC+1), Benj escribió: > Hello, > > i’m building my first site with this great framework and language that are > Django and Python. > I try as much as possible to favor code reuse. > > On one of my model, I do some work with the instance before saving it. > Works is mostly image related: resizing image, compressing, saving thumbs, > and a couple more stuff. > > I will need this behavior in almost all the projects that I will building, > and even some other apps in the same project will need this feature: the > blog, the comments, the directory….. > > In this case, where to put this code ? What do guys and gals do usually in > this situation ? > Do you just put it in a custom (non app) folder like ‘my_utilities’ ? > > Advices welcome. > > Thanks, > Benj > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Django users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/django-users/L0auf9v0ds0/unsubscribe > <https://groups.google.com/d/topic/django-users/L0auf9v0ds0/unsubscribe>. > To unsubscribe from this group and all its topics, send an email to > [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/django-users > <https://groups.google.com/group/django-users>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/8def6a5c-cf24-4948-a73d-a78766e4bc87%40googlegroups.com > > <https://groups.google.com/d/msgid/django-users/8def6a5c-cf24-4948-a73d-a78766e4bc87%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/F1C7EB34-761D-4F2F-9A22-3FF361604A42%40gmail.com. For more options, visit https://groups.google.com/d/optout.
