Making prototypes with Drupal is easy, fast and has real benefits. In this presentation I will show you how we build really big Drupal sites at Pronovix/OwnSourcing.

1. Prototyping with
Drupal
Based on a joint business between
Pronovix and OwnSourcing

2. Why prototyping?
• To validate:
• client’s ideas
• developer’s ideas
• To decrease risk:
• the ideas meet everybody’s expectations
• they worth pursuing them
• To facilitate communication

3. What are you doing during
prototyping?
• Sites for contact-like forms:
core contact.module
webform.module
entityform.module
MailChimp
• Sites for client’s workflow:
workbench.module
core+views+vbo+rules
• …and these are only two areas, usually there are
much-much more

4. How to create those
initial prototypes?
• Use free hosting
• Fire up a new site
• for each idea
• for each feature (or set of features later on)
• Prototypes are just simple throw-away Drupal
sites: fail early, fail fast

5. We have those prototypes.
Now what?
• Integrate them
• only the validated ones
• so you’ll have a skeleton called cleanroom
• Fork the new prototypes from this
• new prototypes won’t interfere with the
already-validated stuff
• it’s “easy” to merge them back to the cleanroom later

6. Drupal has Cons.
What are the cons for prototyping?
• Clear and documented understanding of
featurization
• you should do this anyway
• There’s a ton of prototype sites to keep track of
• Solution: a catalog
• spreadsheet
• a dedicated prototype

7. What’s the benefit?
• Work on different parts of the project with
• different teams
• different velocity
• different completeness
• or even after launching the MVP
• Make decisions as late as you want (or as it’s possible)
• Start working on paid Drupal 8 projects!
• “Like now.” ((C) @_klausi_)