Notes from July 15 2013 Meeting

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
jrdixey's picture
Posted by jrdixey on July 17, 2013 at 7:03am

I'm attaching my notes from the meeting last night as a PDF. If anyone wants to add anything, feel free!

Thanks for attending, everyone, especially on such a nice evening. See you in August! Don't forget to vote in the meeting-night poll!

~ Jennifer

AttachmentSize
DrupalMeetupNotes071513.pdf47.51 KB

Comments

Thanks for posting the notes Jennifer

Posted by theMusician on July 17, 2013 at 3:14pm
theMusician's picture

A few other thoughts:

Another way to inject CSS instead of code per node is the CSS Injector module and the JS injector module.

https://drupal.org/project/css_injector
https://drupal.org/project/js_injector

Also, for node titles I really like auto entity label.
https://drupal.org/project/auto_entitylabel

Hope to see you all next month.

Code Per Node vs CSS/JS Injector

Posted by Trebor on July 17, 2013 at 7:05pm
Trebor's picture

Thanks for mentioning the other injector modules.

One thing that does not appear available (please correct me if otherwise) in the Injector modules is the ability to apply the CSS/JS customizations to Blocks. Code Per Node can add customizations to a Page and a Block.

CCS Injector has Rules that allow you to provide a "page" path for where the CSS customization is to be applied. It may be that both modules would offer the greatest flexibility, but might also lead to conflicts....merits further exploration.

I think you are right, the

Posted by theMusician on July 18, 2013 at 3:09pm
theMusician's picture

I think you are right, the injector modules are used more or less for page or site level changes. As the module states it is not really meant to be a fix for long-term production. That CSS should go into the theme files. The code per node module certainly solves some specific use cases.

Thanks again for sharing.