CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site
This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Developer Discussion (Moderator: Donald Lobo) »
  • Decoupling Drupal from its presentation layer
Pages: [1]

Author Topic: Decoupling Drupal from its presentation layer  (Read 2189 times)

JoeMurray

  • Administrator
  • Ask me questions
  • *****
  • Posts: 578
  • Karma: 24
    • JMA Consulting
  • CiviCRM version: 4.4 and 4.5 (as of Nov 2014)
  • CMS version: Drupal, WordPress, Joomla
  • MySQL version: MySQL 5.5, 5.6, MariaDB 10.0 (as of Nov 2014)
Decoupling Drupal from its presentation layer
July 15, 2013, 09:40:57 am
I found this presentation on a proof of concept of Create Once, Publish Everywhere for Drupal interesting from the perspective of how it decoupled presentation layer from the db representation and front end modules' code:

https://prague2013.drupal.org/session/decoupling-drupal-and-consuming-symfony2-javascript-or-unicorns?utm_source=Lullabot+Announcements&utm_campaign=e0b92aba7f-Weekly+RSS+email+campaign&utm_medium=email&utm_term=0_7a64ff23fe-e0b92aba7f-52099882

As we try to refactor infrastructure in CiviCRM in coming versions, the idea of _not_ aiming to support just one presentation approach like twig from Symfony seems potentially useful. We're already seeing quite a bit of use of our REST api.
Co-author of Using CiviCRM https://www.packtpub.com/using-civicrm/book

totten

  • Administrator
  • Ask me questions
  • *****
  • Posts: 695
  • Karma: 64
Re: Decoupling Drupal from its presentation layer
July 15, 2013, 04:59:50 pm
That presentation sounds interesting!

Quote from: JoeMurray on July 15, 2013, 09:40:57 am
As we try to refactor infrastructure in CiviCRM in coming versions, the idea of _not_ aiming to support just one presentation approach like twig from Symfony seems potentially useful. We're already seeing quite a bit of use of our REST api.

I generally agree with this and agree that APIv3 has enabled folks to start building UIs with many different presentation approaches (and APIv3 can allow more). I'm always +1 on looser-coupling.
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Developer Discussion (Moderator: Donald Lobo) »
  • Decoupling Drupal from its presentation layer

This forum was archived on 2017-11-26.