I have recently worked on a complex Drupal website. I'll be going through how architectural decisions were made, the challenges and solutions chosen. I'll be helping you avoid mistakes that were nearly made.
I'll be showing how I built a Quote builder with Webform, and based on the criteria selected, chose relevant Drupal Commerce products from a list of 5000 and added them to the cart. I'll be sharing how I harnessed the power of the Group module to build 4 tiers of access control including staff, branches, head offices and client users.
3. @ChandeepKhosa #MoldCamp
Who am I?
• Site Builder, Front End Dev, Consultant & Trainer
• Drupal 8 core contributor
• Organiser of Drupal West London user group &
other Drupal events in London
• Involved in training & mentoring Drupal
developers
• Drupal meetup & camp addict
5. @ChandeepKhosa #MoldCamp
Project background
• Build a web application that handles quotes,
policies & claims. Allows users to buy policies,
cancel them, make claims on them. Display
reports.
8. @ChandeepKhosa #MoldCamp
User needs
• Find out information before deciding to buy
• Get a quote
• Buy a policy
• Manage their policy
• Make & track claims
11. @ChandeepKhosa #MoldCamp
Webform Learnings
• Use Webform 4.x instead of 3.x if you need to be
able to insert tokens. Switching can may break your
custom modules.
• e.g.) User fields such as name & address
• Webform Wrappers module allows you to add
classes e.g.) Row & Col-Md-4
25. @ChandeepKhosa #MoldCamp
Dealer groups
• Head Office : Can create branch groups & admin
users. Can see all policies & claims.
• Branch : Can create staff users. Can see policies &
claims restricted to their branch.
• Staff : Can’t create groups or users. Can see
policies & claims created by other colleagues.
36. @ChandeepKhosa #MoldCamp
Summary
• All these modules are awesome, but when
used together correctly they can build a
powerful business critical application.
• Email me at hello@chandeepkhosa.com