Demo Framework includes inline editing with Spark, Commerce, Panopoly, Apache Solr facets, editing workflows with Workbench Moderation and a responsive theme. Bundling these together saves you the time and effort of putting together a demo for each potential client. The ability to create new demo scenarios allows you to cater to your client's needs.
In this session:
Main difficulties with introducing Drupal to new users
What does DF demonstrate about Drupal?
Technical demo
How to extend DF to provide new scenarios
How we have used DF successfully in pitches
View video here: https://www.youtube.com/watch?v=Qd2wTnnQJ1c
14. KEY POINTS
• Getting clients to see the functionality
• Try before they buy
• Adaptable to their needs
• Get involved!
15. THANKS FOR LISTENING!
See example scenario at:
https://drupal.org/sandbox/annikaC/2019771
@annikaclarke #dclondon
Editor's Notes
I’m here to talk to you about Demo Framework, a distribution we’ve used in pitches to successfully gain clients.
We've all been in that situation where a client asks "What's Drupal?”
They might have heard about it before, they might not have.
But they haven’t used it
Presents a challenge
- What’s the best way for us to solve this problem?
Pretty amazing diagram - “There’s a module for that”
As you all know,
Drupal can pretty much do anything.
But the client doesn’t know that, if they haven’t used Drupal before.
It can be really difficult to explain that, really, Drupal can do anything they want, and even harder to demo this in an effective way.
Common questions from clients
What's a node?
Hard question to answer.
You can just say, a bit of content with input fields
- Recent client meeting
- They wanted to know what they could do with them
- The concept was confusing
The problem: You have nothing to demonstrate the concept
So they might come away with a different idea
Ultimately you may lose the work
How do we use widgets?
- Vague. What's a widget anyway?
- Usually iframe, or twitter widget
- Usually more important than you think it is,
- Client’s ideal idea of content they want on their website.
- To get their business, you need to show them how easy it is for them to add this kind of content themselves.
How do we edit content?
- Oddly tough question to answer
- Different ways of approaching
- Conventional edit page within admin theme/overlay
- Fields
- Save/publish button
- Panels In Place Editor
- Fieldable panes
- Live preview
- Spark in place editing
What’s best for the client? Often it's best just to show them and gauge their reaction to each.
How do we edit images?
- What does this question mean? Clarify, can be surprising
- Recent client meeting
- Photoshop in Drupal
- Manage expectations with a demo
A demo seems like a no-brainer
But they take a lot of time and effort to prepare
Can be really buggy due to time constraints
Might not be worth it
What should you show?
DF is a distribution with lots of commonly used contrib modules, bundled together with configuration in Features and can use Migrate to import demo content.
Uses all of the big modules you’d normally install
Pretty big distribution
But the key is to use different scenarios to demo different functionality
- So not all modules enabled all of the time
It’s better for me to show you what’s in there rather than talk about it much more.
I’ll be taking you through an example Demo Framework scenario.
News (Text heavy, good WYSIWYG)
Views heavy, content editing interface
Brochureware (Visual, lots of layouts)
Panopoly heavy, highly visual
Group-focused
We did this at Deeson Group
Organisation wanted regional groups
Ability to moderate membership
SHOW
Migrations
Hook in module file
.info package
Very important, show what Drupal is capable of
Help eliminate doubts on the platform
Give clients a copy of DF on a dev site to play with
Create your own scenarios for different purposes
Scenarios are worth sharing with the community, making everyone’s life easier