5. Leveraging Contributed Modules
Standing on the Shoulders of Giants
- Assess the project page
- Read the README file
-Views, admin_menu, ctools, webform,
wysiwyg, panels, context.
6. Where does Contributed code live?
Put all contrib modules in
../sites/all/modules/
OR
../sites/all/modules/contrib
Put all custom modules in
../sites/all/modules/custom
Put all themes in
../sites/all/themes
8. What do you need in your toolbox?
HTML / CSS / Javascript / PHP
A good code editor
Firebug or Chrome Inspector
Drupal Community
You can leverage a lot of skills you already have.
10. Development Workflow
Development Environment- Dev > Test > Live
Where do your clients QA?
Use Version control to push to production
- great for rolling back changes
- great for multi-developer environments
Code vs Content
- features module
Workflow to push to production
Exclude the files directory from the repo, files are like data.
15. Write a development plan
Forces you to think through your architecture
and implications of decisions
Makes it a lot easier to build quickly- ex: grab
all your modules at once, understand content
and layout dependencies
Build, then theme
90% of the way there is often enough
- Don’t be afraid to talk to your clients
16. Structure Content
Break up your content into the pieces you want
control over.
Important in mobile theming- content first
Consider your admins and your visitors.
Good content is user-centered
Adopt the cognitive frameworks of your users
-ERIN KISSANE
27. Coding Standards
-Don’t Hack Core! It may seems like a good idea now, but its
not.
- Indent of 2 spaces
- No trailing white space
- CSS properties in alphabetical order
- Comment your code, you’ll thank yourself later.
- Participate in the issue queue and documentation.
28. Learn More
Books
Camps and Cons
Training
IRC
Documentation
Spirit of willingness, giving
Blogs back and helping each other
Videos
Meetups
