DEMO FRAMEWORK
Pitching Drupal to potential clients
@annikaclarke #dclondon
PITCHING
DRUPAL CAN
BE HARD
How can we make this
easier?
COMMON QUESTIONS
What’s a
node?
How do we
use widgets?
How do we
edit content?
How do we
edit images?
USING A DEMO
• Allows the client to see functionality
• Get familiar with the platform
• But… takes time to prepare
DEMO FRAMEWORK
• By Acquia
• Maintained by brantwynn
• Aims to make the process
of explaining Drupal easier
MODULES
• Commerce
• Organic Groups
• Spark
• Workbench Moderation
• Panopoly
• And many more...
LIVE DEMO
SCENARIO IDEAS
• Dynamic news site
• Brochureware site
• Group-focused site
KEY POINTS
• Getting clients to see the functionality
• Try before they buy
• Adaptable to their needs
• Get involved!
THANKS FOR LISTENING!
See example scenario at:
https://drupal.org/sandbox/annikaC/2019771
@annikaclarke #dclondon
Demo framework: How do we pitch Drupal to potential clients?
Upcoming SlideShare
Loading in …5
×

Demo framework: How do we pitch Drupal to potential clients?

1,919 views

Published on

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

Published in: Technology
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,919
On SlideShare
0
From Embeds
0
Number of Embeds
601
Actions
Shares
0
Downloads
8
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide
  • 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
  • - Thanks!
    - Other sessions today
  • Demo framework: How do we pitch Drupal to potential clients?

    1. 1. DEMO FRAMEWORK Pitching Drupal to potential clients @annikaclarke #dclondon
    2. 2. PITCHING DRUPAL CAN BE HARD How can we make this easier?
    3. 3. COMMON QUESTIONS
    4. 4. What’s a node?
    5. 5. How do we use widgets?
    6. 6. How do we edit content?
    7. 7. How do we edit images?
    8. 8. USING A DEMO • Allows the client to see functionality • Get familiar with the platform • But… takes time to prepare
    9. 9. DEMO FRAMEWORK • By Acquia • Maintained by brantwynn • Aims to make the process of explaining Drupal easier
    10. 10. MODULES • Commerce • Organic Groups • Spark • Workbench Moderation • Panopoly • And many more...
    11. 11. LIVE DEMO
    12. 12. SCENARIO IDEAS • Dynamic news site • Brochureware site • Group-focused site
    13. 13. KEY POINTS • Getting clients to see the functionality • Try before they buy • Adaptable to their needs • Get involved!
    14. 14. THANKS FOR LISTENING! See example scenario at: https://drupal.org/sandbox/annikaC/2019771 @annikaclarke #dclondon

    ×