Comments on: Some Thoughts on Museum Websites and Open Source CMS https://vesica.ws/blog/2012/05/some-thoughts-on-museum-websites-and-open-source-cms/ - Taking museum and art collections to the cloud Sun, 19 May 2013 12:16:00 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Rob Landry https://vesica.ws/blog/2012/05/some-thoughts-on-museum-websites-and-open-source-cms/comment-page-1/#comment-1445 Rob Landry Mon, 04 Jun 2012 14:12:00 +0000 https://vesica.ws/blog/?p=449#comment-1445 There's really nothing subjective about what I'm saying. There’s really nothing subjective about what I’m saying.

]]> By: Vesica https://vesica.ws/blog/2012/05/some-thoughts-on-museum-websites-and-open-source-cms/comment-page-1/#comment-1443 Vesica Thu, 31 May 2012 06:32:00 +0000 https://vesica.ws/blog/?p=449#comment-1443 I think that is extremely subjective (not that any of this discussion has to do with objectivity). From a programmatic standpoint, Drupal is actually quite bloated. But the point is, Django is not a CMS - it is a framework, and there's a big difference there. Then there is also the matter of programming language preference - Python vs PHP. PHP arguably has more inconsistencies - but that flexibility is also its strength. Proponents of Ruby say that Ruby is better. Others promote Python. Then there are are Java and C#. That's not what the article was about. Our team has actually worked with Django - and we have used other PHP frameworks like CodeIgniter and Symfony too. The point of using a CMS as opposed to an MVC framework is the relatively consistency you are allowed. You can write terrible code within the parameters provided via an MVC framework too and even if you write good code, it is still a custom build. When you build a website using a CMS - any CMS - it is easier for other developers to pick it up. Again, the discussion was about a CMS - not about frameworks. It is, at the end of the day, about preference. If Django works for you and your clients, you should use it. Superiority or anyone's opinion thereof is a moot point. I think that is extremely subjective (not that any of this discussion has to do with objectivity). From a programmatic standpoint, Drupal is actually quite bloated. But the point is, Django is not a CMS – it is a framework, and there’s a big difference there. Then there is also the matter of programming language preference – Python vs PHP. PHP arguably has more inconsistencies – but that flexibility is also its strength. Proponents of Ruby say that Ruby is better. Others promote Python. Then there are are Java and C#. That’s not what the article was about.

Our team has actually worked with Django – and we have used other PHP frameworks like CodeIgniter and Symfony too. The point of using a CMS as opposed to an MVC framework is the relatively consistency you are allowed. You can write terrible code within the parameters provided via an MVC framework too and even if you write good code, it is still a custom build. When you build a website using a CMS – any CMS – it is easier for other developers to pick it up. Again, the discussion was about a CMS – not about frameworks.

It is, at the end of the day, about preference. If Django works for you and your clients, you should use it. Superiority or anyone’s opinion thereof is a moot point.

]]> By: Rob Landry https://vesica.ws/blog/2012/05/some-thoughts-on-museum-websites-and-open-source-cms/comment-page-1/#comment-1442 Rob Landry Wed, 30 May 2012 23:29:00 +0000 https://vesica.ws/blog/?p=449#comment-1442 I would give Drupal the edge if you lack access to programming talent. Otherwise, Django is superior in terms of speed of development, performance, ease of codebase maintenance, and development of superior custom features. PHP is more unstable over the long haul precisely because you can write a feature many different ways. If you have limitations in terms of your budget, Drupal is superior to Django.... just like VHS was superior to Beta (consumers used VHS while TV production houses used Beta).... and PCs are "superior" to Macs. But if quality and performance are important, and you have the budget, like many mid-sized to large museums (like Walker Art), you owe it to yourself to at least look into Django. Other sites that use Django: The Washington Post, The New York Times, Pinterest, Instagram, and Disqus (the commenting framework used on this blog). I would give Drupal the edge if you lack access to programming talent. Otherwise, Django is superior in terms of speed of development, performance, ease of codebase maintenance, and development of superior custom features. PHP is more unstable over the long haul precisely because you can write a feature many different ways.

If you have limitations in terms of your budget, Drupal is superior to Django…. just like VHS was superior to Beta (consumers used VHS while TV production houses used Beta)…. and PCs are “superior” to Macs. But if quality and performance are important, and you have the budget, like many mid-sized to large museums (like Walker Art), you owe it to yourself to at least look into Django.

Other sites that use Django: The Washington Post, The New York Times, Pinterest, Instagram, and Disqus (the commenting framework used on this blog).

]]> By: Vesica https://vesica.ws/blog/2012/05/some-thoughts-on-museum-websites-and-open-source-cms/comment-page-1/#comment-1441 Vesica Wed, 30 May 2012 21:27:00 +0000 https://vesica.ws/blog/?p=449#comment-1441 #Django is indeed a great framework - but as you put it, not an out of the box CMS. This is primarily where #Drupal has an edge. The popularity of #php also probably helps. #Django is indeed a great framework – but as you put it, not an out of the box CMS. This is primarily where #Drupal has an edge. The popularity of #php also probably helps.

]]> By: Rob Landry https://vesica.ws/blog/2012/05/some-thoughts-on-museum-websites-and-open-source-cms/comment-page-1/#comment-1440 Rob Landry Wed, 30 May 2012 17:52:00 +0000 https://vesica.ws/blog/?p=449#comment-1440 (Sorry about all the written-out links. I couldn't figure out how to link text.) One powerful - but still relatively unknown - Open Source framework that's on the rise and that isn't mentioned here is Django (www.djangoproject.com). The internationally acclaimed and award-winning Walker Art Center (www.walkerart.org) uses Django as the foundation of its CMS. The award-winning resource www.MuseumAnalytics.org is powered by Django. And my agency, Plein Air Interactive (www.pleinairinteractive.com) has developed a Django CMS specifically designed for museums, which we've rolled out to several clients including the Maine Maritime Museum (www.mainemaritimemuseum.org). Drupal and Wordpress are excellent foundations for a museum web CMS, and we've built sites using them. If you can only afford to develop your site with your own internal staff, they are very good choices. But if you want great interaction design, with features tailored precisely to the needs of museum audiences and accessible to the physically and visually impaired, you'll need to hire a development team to create custom features, no matter what CMS framework you choose. And if that's the case, Django is definitely worth a look. Django's strength is the ability to spin up powerful custom features (for online collections, events, exhibitions, searchable archives, etc.) very quickly. I recently wrote a blog post about the virtues of using Django as a museum CMS (www.pleinairinteractive.com/blog/2012/05/14/django-worth-look-museums-open-source-content-management/). It's definitely an option to consider. (Sorry about all the written-out links. I couldn’t figure out how to link text.)

One powerful – but still relatively unknown – Open Source framework that’s on the rise and that isn’t mentioned here is Django (www.djangoproject.com). The internationally acclaimed and award-winning Walker Art Center (www.walkerart.org) uses Django as the foundation of its CMS. The award-winning resource http://www.MuseumAnalytics.org is powered by Django. And my agency, Plein Air Interactive (www.pleinairinteractive.com) has developed a Django CMS specifically designed for museums, which we’ve rolled out to several clients including the Maine Maritime Museum (www.mainemaritimemuseum.org).

Drupal and WordPress are excellent foundations for a museum web CMS, and we’ve built sites using them. If you can only afford to develop your site with your own internal staff, they are very good choices. But if you want great interaction design, with features tailored precisely to the needs of museum audiences and accessible to the physically and visually impaired, you’ll need to hire a development team to create custom features, no matter what CMS framework you choose. And if that’s the case, Django is definitely worth a look. Django’s strength is the ability to spin up powerful custom features (for online collections, events, exhibitions, searchable archives, etc.) very quickly.

I recently wrote a blog post about the virtues of using Django as a museum CMS (www.pleinairinteractive.com/blog/2012/05/14/django-worth-look-museums-open-source-content-management/).

It’s definitely an option to consider.

]]>