24
Drupal on a business perspective Why, who is for, why not

Drupal on a business perspective

Embed Size (px)

Citation preview

Drupal on a business

perspective

Why, who is for, why not

Purpose

• Share motivations and struggles

• Advantages to both agencies and clients

• Debate when to use or not Drupal

Duration: Aprox.10 min presentation

about me

Ricardo Marcelino

Omibee co-founder and

manager

Using Drupal since 2012

(rfmarcelino)

A small story

Working as a graphic designer on a previous job:

“We need to have something on the web”

<html>

Short after, an academy asked:

“I need a website with a back office

and calendar integration”

At around the same time, a hospital asked:

“We need a website and an intranet with service

teams and schedules”

A few months later, a toys brand:

“We need a portfolio and online store, with multi

language and content adapted for each market.”

An University department asked:

“We need to manage publications, scientific

production, scholarships, equipments, etc.”

Meanwhile, a Business Angels club asked:

“Can you fix and maintain our Joomla website?” …

“Can we do it with Drupal instead?” …

It grew up to become a fin-tech platform

What do we need

as a business?

What do we need

as a business?

• Ability to provide high added value to clients

• A flexible set of tools and know how that can be

reused

• Robust, flexible and scalable systems

Why Drupal?For agencies and clients

Why Drupal For agencies and clients

• A lot out of the box - content management, entity relationships, user and

permissions management, SEO friendly, localisation.

• Power to non technical staff - PM’s, content managers, marketing staff

• Open source - Free framework and modules; no lock-in or fees

• Connected - Hundreds of community modules integrating with other

services, RESTful in core on D8

• Security - Weekly updates and an active security team. Highly tested

system.

• Flexibility and scalability - Allows to grow on complexity or users.

You don’t need

a bus for 2 passengers

Who is for?

• Content and workflow intensive

• Media and publishers (The Economist, NBC, Fox, …)

• Universities (Harvard, Oxford, Stanford, …)

• Knowledge bases (Autodesk, Pfizer, Johnson & Johnson, …)

• Community sites

• NGO’s (Red Cross, Museum of Fine Arts, Rotary International, …)

• Public services (White House, London.gov, australia.gov, …)

• Data exploration

• Dashboards (weather.com, NBA, Rio Olympics’16, …)

• Data insights and intranets (RedHat, PBS

• Commerce (Timex, Puma, Royal Mail, ..)

Who is not for?

• Personal page or simple blogs

(Squarspace, Wordpress, Blogger)

• Simple “brochure” websites

(Adobe Muse, static generators)

• Single or specific purpose apps

(node.js, Laravel, Symphony)

What do you think?

Thank you.

Ricardo Marcelino | omibee.com