Planet Drupal

Subscribe to flux Planet Drupal - aggregated feeds in category Planet Drupal
Mis à jour : il y a 36 min 21 sec

OSTraining: Custom Layouts for Webforms in Drupal 7

ven, 22/01/2016 - 01:18

One of our users asked for a way to customize the layout for his Drupal 7 webforms.

Webforms Layout is a module that extends Webform features by providing more control over the design.

In this post, I'll share with you how to use Webform Layout module. Let's start...

Catégories: Elsewhere

Savas Labs: How to subscribe users to MailChimp lists in a Drupal custom module

ven, 22/01/2016 - 01:00

A demonstration on how to use Composer Manager and the MailChimp PHP library to simply and easily subscribe users to mailing lists without using the MailChimp contributed module.

Continue reading…

Catégories: Elsewhere

jordanpagewhite: Drupal Features, Deployment Module, and Drush Aliases

ven, 22/01/2016 - 01:00

Features allows you to bundle entities, and their configurations, into a feature module that is written to code. So, what is so great about that? Can't you accomplish the same functionality by building out your views, content types, etc. through the Drupal admin UI. Yes, you can, but all of the entities and configuration will be saved in the database, as opposed to in code. Saving your entities and configuration to code is an immense benefit, if not necessary, for Drupal sites that are deployed across multiple environments, and even more if there are multiple developers working on the site.

Catégories: Elsewhere

Darren Mothersele: Session submission guidelines for conferences and camps

ven, 22/01/2016 - 01:00

Earlier this week I found out that the date for my nephew's christening has changed. This means I can now make it to the Drupal Camp in London. I decided to propose a session so that I can share my recent insights, research, and learning.

The Drupal Camp London team have kept the session submission process minimal. This makes it easy for people to submit proposals, but it makes it unclear what the expectations are. What are they looking for in proposed sessions? How long are the sessions expected to be? What is the review process?

As I only found out I could attend at the last minute, I had no time to enquire about the process. So I made some assumptions based on my experiences of programming at previous camps. I also did some research into other Drupal camp and conference session submission processes. The Amsterdam Drupalcon site had this to say:

"There’s a lot of elements to session selection. We need to make sure that sessions are of value to a wide audience. The presenters must be engaging speakers who can interest a large crowd of attendees. We try as hard as we can to bring in new (to DrupalCon) speakers, and speakers who bring something from outside of the Drupal sphere. We want to make sure that the diversity of the community is represented and encouraged. And we need to work across track teams to ensure that one speaker is not speaking in several tracks; both for the sake of their stress and sanity in preparing the talks and to ensure that everyone who applied has the best chance of speaking. Finally, we need to make sure that sessions fit both the theme of the track and of the conference."

While the Barcelona Drupalcon offered the following 3 part session submission formula...

Part 1: Describe a compelling topic that affects the reader directly, maybe a pain point, or juicy new technology.
Part 2: Allude to your solution, sharing just enough that the reader has a moment of "I need that do I not know this already?"
Part 3: Explain how awesome the session will be because you are going to cover "XYZ" and make the reader's life so much better.

My session selection criteria

I realised that I've done session selection myself many times. At every conference, camp, and symposium I attend I make my own selection of sessions to attend. The key to making the most out of attending a conference is to attend the right sessions.

At Resonate last year I set the intention of broadening my horizons, so intentionally selected session that I would not normally be exposed to. And sessions that offered something new. At DrupalCon in Amsterdam I set the intension of getting as deep into Drupal 8 as possible. So I attended every D8 session I could. Selecting the sessions I thought offered the most opportunity for learning. It helps if they are recognisable names, or people I've seen present before and know they do a good session.

When I think about my own criteria, I get it down to five things...


Is this definitely a session worth attending? Is the session topic cutting edge, or immediately relevant to my situation. Is it ground breaking or offer a significant contribution to the field?


Is this the right type of session? Is the purpose of the session clear? Does the description make it clear what the expected participant outcomes are? Does the description give enough specific information to make me want to know more?


Is the session motivated by theory, practice, and/or research? Is this presented in a detailed, thorough, and comprehensible way?


Are all claims (practices, conclusions, proposals) well substantiated. Is the speaker presenting something they know about? Is the speaker well positioned to be giving the session.


Is the session proposal clear? A well written session description indicates the presentation itself will be of professional quality.

I hope I managed to purvey these five points in my own session proposal. I'd love to hear from you if you have your own ideas about what makes a good Drupalcamp session. If you drop me a line or leave a comment I will take them into account while planning my own session.



Catégories: Elsewhere

OSTraining: Entity Reference Views Help Drupal Content Creators

jeu, 21/01/2016 - 23:24

Entity Reference Views are one way you can make life easier for Drupal content creators.

Normally, when people are creating content on your site, each field consists of a single box with a single data point. For example, in a list of people, you might get only the person's name. 

Entity Reference Views allow you to provide far more information. For example, you can add photos and personal details to your list of people.

Catégories: Elsewhere

Freelock : 8 Reasons Why Drupal 8

jeu, 21/01/2016 - 22:29

Drupal 8 has been out for 2 months now, and there's never been a better time to choose Drupal for your website platform. Here are 8 reasons why!

1. Mobile Experience

Drupal 8 is mobile first. Every bit of Drupal 8 can be easily managed from your smartphone, with a responsive experience that works well right up to the widest displays.

You don't need a separate mobile site.

DrupalDrupal 8Drupal PlanetDevOpsQuality
Catégories: Elsewhere

Acquia Developer Center Blog: Chris Pliakas on How to Successfully Manage Software Projects

jeu, 21/01/2016 - 20:15
Chris Pliakas

Chris Pliakas, the director of Content Services Engineering at Acquia, has been leading the Acquia Content Hub project since May, 2015. A certified ScrumMaster, Chris has been working at Acquia since 2010: as a technical consultant, solutions architect, scrum master, and engineering manager.

Tags: acquia drupal planet
Catégories: Elsewhere

Promet Source: Connect Site Users to Premium Content with Commerce License

jeu, 21/01/2016 - 19:23
Intro to Commerce License

Commerce License is a module that grants users access to premium digital resources by either a remote or local license.

This module is good for granting users a license to resources that live behind a paywall, such as training materials or videos. 

Catégories: Elsewhere

YesCT: Get issues you care about ready for Global Sprint Weekend

jeu, 21/01/2016 - 18:06
Get issues you care about ready for Global Sprint Weekend Introduction

Drupal Global Sprint Weekend is January 30 and 31, 2016, and so far we have 34 locations all over the world.

This post will talk about what organizers and experienced contributors can do to get issues ready for sprint attendees to work on.

There is still time to add your small local sprint. Read the post and get your location listed!

Preparation Triage

Get an overview of your issue queue.

Review any RTBC issues, test (and if you are a maintainer, commit) them. Or, mark them needs work, giving specific actionable feedback. This will encourage past contributors to return, because they will see their work get in, or your review will show them you appreciate their work, and the specific feedback will help them know what to do next.

Reduce the size of your issue queue. Close issues won't fix, explaining why.

Postpone issues. Update the summary of issues to include information about what the issue is postponed on. Maybe whether it can be worked on or not depends on the phase of the release cycle the project is in. (Read the Core group for announcements about core release phases.)

Or, if it is blocked on another issue, postpone it and link to the blocking issue. (Update the blocking issue summary also noting the issues that are postponed on it.) Under the "Issue summary & relationships" field, make sure the issues are "related".

Eliminating issues you don't want people to work on will help them focus on the issues that are relevant. They will appreciate that.

Pick a few issues

Pick a few issues you want people to work on. Try to pick ones that involve a variety of skill sets and experience levels. List them in a way that is convenient for you. You could tag them SprintWeekend2016, and then use an advanced search to show just those issues. Or, make a google spreadsheet, or whatever works for you. If you have a couple issues that have very clear next steps documented and a small scope, tag them Novice. Read about what makes a good novice task.

For those issues, update the issue summary. Include a "Remaining Tasks" section which links to instructions for how to do each task. The dreditor browser plug in adds an "insert tasks" button to issue pages that puts an html table with links to tasks in an issue summary. Uncomment or comment out rows in the table depending on what remains to be done on your issue.

Give constructive feedback

Read the handbook page on constructive feedback. Whenever you leave feedback, thank the person for something specific that you would like them to do again. When making suggestions, give or link to examples. List specific next steps, give instructions or link to specifics, for example, link to one of the contributor tasks child pages.

Make a short list

Make a link to issues you want people to focus on. You might do this by using the advanced search for issues, filtering to: your project, SprintWeekend2016 tag, and issues where the status is: needs work and needs review (and maybe also active). Make a second link to an advanced search that also filters to issues tagged novice. (Or, filter to whatever criteria you want.) Share these links with others.

Write a post

Write a post about the topic you want to sprint on. Give some background information. Celebrate what already works. Link to a few of the issues you want to tackle at the sprint. Edit the Global Sprint Weekend wiki and put a link to your post next to your location. Or, if you will be remote only, list it under virtual.

Have questions?

Tweet using the #SprintWeekend hash tag, post a comment on the g.d.o wiki page, ask in the Mentoring Group, or ask in IRC in #drupal-contribute. -Cathy (YesCT)

Resources for Organizers
Catégories: Elsewhere

OpenLucius: 12 cool modules for Drupal site builders | January 2016

jeu, 21/01/2016 - 15:05

The holidays are over for a while now, so it's about time for a new blog. In this article I'll discuss 12 modules that can help you get started with a great Drupal site:

1. Max image size

Catégories: Elsewhere

Drupal core announcements: BigPipe in Drupal 8.1: please test!

jeu, 21/01/2016 - 13:45

Drupal 8.1 is accepting new features, and BigPipe is being proposed to be added as an experimental module to Drupal 8.1. BigPipe sends pages to clients in a way that allows browsers to show them much faster. It first sends the cacheable parts of the page, then the dynamic/uncacheable parts.

If you're interested or concerned, please give the BigPipe contributed module for Drupal 8.0.x a try, and even try to break it! The more confident we can be about its stability, the more likely it being part of Drupal 8.1 will be.

Catégories: Elsewhere

Jeff Geerling's Blog: Configuring CloudFlare with Drupal 8 to protect the Pi Dramble

jeu, 21/01/2016 - 04:46

In a prior post on the constraints of in-home website hosting, I mentioned one of the major hurdles to serving content quickly and reliably over a home Internet connection is the bandwidth you get from your ISP. I also mentioned one way to mitigate the risk of DoSing your own home Internet is to use a CDN and host images externally.

At this point, I have both of those things set up for (a Drupal 8 site hosted on a cluster of Raspberry Pis in my basement!), and I wanted to outline how I set up Drupal 8 and CloudFlare so almost all requests to are served through CloudFlare directly to the end user!

CloudFlare Configuration

Before anything else, you need a CloudFlare account; the free plan offers all the necessary features (though you should consider upgrading to a better plan if you have anything beyond the simplest use cases in mind!). Visit the CloudFlare Plans page and sign up for a Free account.

Catégories: Elsewhere

Fredrik Jonsson: Running Drupal on Debian 8 with Apache 2.4, event MPM and PHP-FPM (via socks and proxy)

jeu, 21/01/2016 - 02:02

I’m building a new Ansible playbook for setting up web servers with Debian 8. I have always used mod_php before and it has been very stable but have some well known drawbacks. Since Debian 8 comes with Apache 2.4 and PHP 5.6 I wanted to implement PHP-FPM that seems very promising.

With mod_php every Apache process will need to load PHP and therefor use a lot more RAM than needed, even for just serving static content like images and css. I have been running Lighttpd as a static file server to mitigate this problem.

With event MPM + PHP-FPM a plain Apache processes will deal with all static content and hand of PHP request to separate PHP-FPM processes. This will allow a server to handle more visitors with the same amount of RAM and I can skip Lighttpd.

I found surprisingly little information on how to get this working well for serving things like Drupal. So here are what I have found out from manuals, post on the Internet as well as my own testing.

This setup has not been tested in production yet! When it has I will try to remember to update this article. In local testing on a VirtualBox image with Debian 8 and 512 MB RAM it seems to work fine. I also run the same setup locally on OS X with good results.

Here are some performance test done with ab. These doesn’t say much more than that it seems to work and most likely can handle some load.

ab -k -l -n 1000 -c 10 -H "Accept-Encoding: gzip,deflate"

Requests per second:    526.01 [#/sec] (mean)

This was the front page of a local version of running Drupal 7, with page cache of course. I also tested with plain Drupal 8 and got around 300 request/sec, more or less what one would expect.

A plain html page looks like this.

ab -k -l -n 1000 -c 10 -H "Accept-Encoding: gzip,deflate" http://localhost/

Requests per second:    2466.39 [#/sec] (mean) Installation

Start by installing needed packages.

apt-get install apache2 apache2-dev php5-fpm mariadb-server

You most likely want some more php extensions as well, here are the ones I normally install for running Drupal.

apt-get install php5-cli php5-apcu php5-curl php5-dev php5-gd php5-imagick php5-json php5-mysql php5-mcrypt php5-twig php-pear graphicsmagick graphicsmagick-imagemagick-compat

As suggested in I will run PHP-FPM via mod_proxy_fcgi so lets activate that module.

a2enmod proxy_fcgi

This will automatically activate the proxy module as well since it is a dependency. I also activate auth_digest, expires, rewrite and ssl on my servers. Rewrite is needed for Drupal to get clean URLs.

Apache and PHP-FPM configurations

Debian by default set up PHP-FPM to listen on a unix socket and since that should perform a bit better than a TCP socket I will use that. The most important setting is “max_children”. With Drupal each PHP process will use something like 20-40 MB typically, can be a lot more for some site so you simply need to test and see.

If your Drupal site use 30 MB per process setting “max_children” to 10 means that PHP will use up to about 10 * 30 MB = 300 MB of RAM. A good resource for figuring out what is the best settings is this blog post Adjusting child processes for PHP-FPM (Nginx) · MYSHELL.CO.UK

listen = /var/run/php5-fpm.sock
pm = dynamic
pm.max_children = 10
pm.start_servers = 4
pm.min_spare_servers = 2
pm.max_spare_servers = 6
pm.max_requests = 2000

The default MPM for Apache 2.4 (at least on Debian) is event MPM and since that is the most modern and best performing MPM there is no reason not to use it. I run with default setting and that should work well for most small servers. If needed I may up the value on ThreadsPerChild but I don’t think that will be needed on my servers.

# event MPM
# ServerLimit: upper limit on configurable number of processes (default = 16)
# StartServers: initial number of server processes to start (default = 3)
# MinSpareThreads: minimum number of worker threads which are kept spare (default = 25)
# MaxSpareThreads: maximum number of worker threads which are kept spare (default = 75)
# ThreadLimit: upper limit on the configurable number of threads per child process (default = 64)
# ThreadsPerChild: constant number of worker threads in each server process (default = 25)
# MaxRequestWorkers: maximum number of worker threads (default = ServerLimit x ThreadsPerChild)
# MaxConnectionsPerChild: maximum number of requests a server process serves (default = 0)
<IfModule mpm_event_module>
  ServerLimit             16
  StartServers            3
  MinSpareThreads         25
  MaxSpareThreads         75
  ThreadLimit             64
  ThreadsPerChild         25
  MaxConnectionsPerChild  2000
</IfModule> Apache vhost setup

Here we then come to the part that caused me the biggest problem. How to get PHP-FPM to only run the php files I wanted and not everything. The Apache wiki page above suggest using ProxyPassMatch but it turns out that that overrides any restrictions set in e.g. a Files/FilesMatch directive. For Drupal I want to block access to files like update.php and cron.php so another solution was needed.

I found the solution in a post from Mattias Geniar Apache 2.4: ProxyPass (For PHP) Taking Precedence Over Files/FilesMatch In Htaccess. His suggestion to use a SetHandle in a FileMatch directive seems to work very well.

This is how I set up a vhost for serving Drupal.

<VirtualHost *:80>
  DocumentRoot /var/www/customers/example/web
  ErrorLog /var/www/customers/example/logs/error_log
  CustomLog /var/www/customers/example/logs/access_log combined
  <Directory "/var/www/customers/example/web">
    Options FollowSymLinks
    AllowOverride None
    Include /var/www/customers/example/web/.htaccess
    <IfModule mod_proxy_fcgi.c>
      # Run php-fpm via proxy_fcgi
      <FilesMatch \.php$>
        SetHandler "proxy:unix:/var/run/php5-fpm.sock|fcgi://localhost"
    # Only allow access to cron.php etc. from localhost
    <FilesMatch "^(cron|install|update|xmlrpc)\.php">
      Require local

Notice that I include the .htaccess file. I have set “AllowOverride None” to prevent Apache from looking for and automatically include any .htaccess files it finds. This improves performance a bit but one needs to remember to reload Apache when changes are made to the .htaccess file.

Extra security configurations in Apache for Drupal

Drupal put .htaccess in the files folder and some other places for security reasons. The following is an example how to add the same security configurations directly in an Apache conf file. The DirectoryMatch regex most likely needs adjustment for your directory structure.

# Security setting for files folder in Drupal.
<DirectoryMatch "^/var/www/.*/web/(.+/)?(files|tmp)">
  # Turn off all options we don't need.
  Options -Indexes -ExecCGI -Includes -MultiViews

  # Set the catch-all handler to prevent scripts from being executed.
  SetHandler Drupal_Security_Do_Not_Remove_See_SA_2006_006
  <Files *>
    # Override the handler again if we're run later in the evaluation list.
    SetHandler Drupal_Security_Do_Not_Remove_See_SA_2013_003

  # If we know how to do it safely, disable the PHP engine entirely.
  <IfModule mod_php5.c>
    php_flag engine off

# Security setting for config folder in Drupal.
<DirectoryMatch "^/var/www/.*/web/(.+/)?(private|config|sync|translations|twig)">
  <IfModule mod_authz_core.c>
    Require all denied

  # Deny all requests from Apache 2.0-2.2.
  <IfModule !mod_authz_core.c>
    Deny from all
  # Turn off all options we don't need.
  Options -Indexes -ExecCGI -Includes -MultiViews

  # Set the catch-all handler to prevent scripts from being executed.
  SetHandler Drupal_Security_Do_Not_Remove_See_SA_2006_006
  <Files *>
    # Override the handler again if we're run later in the evaluation list.
    SetHandler Drupal_Security_Do_Not_Remove_See_SA_2013_003

  # If we know how to do it safely, disable the PHP engine entirely.
  <IfModule mod_php5.c>
    php_flag engine off
Catégories: Elsewhere

Darren Mothersele: Surviving - and thriving - during the transition to Drupal 8

jeu, 21/01/2016 - 01:00

This is my proposal for a session at the upcoming Drupal Camp in London.

Drupal is going through some big changes. And, so is the world. Now may be an unsettled period, but, times of disturbance can also be times of great opportunity.

I will share my experiences with Drupal and my research into how the web and society are transforming. This will include my personal manifesto and ideas about Drupal's role in the future of the web.

The Drupal community helped me transform in many ways. I have had the opportunity to work on some of the biggest, flagship Drupal websites, and in teams of all sizes. I've grown and advanced as a developer and a human.

There have also been difficult times. These have included my own personal challenges, and stories I have heard from others. In my work at Ideation Networks I sit with clients as they weigh up the pros and cons of Drupal. Many organisations feel they have been burnt by Drupal. And, for some, PHP (and by association Drupal) is just not cool.

But, on the whole, these are exciting times for Drupal.

Drupal 8 is the biggest achievement of our community to date. The latest version has been completely rewritten to use modern object-oriented PHP. We refer to this process as "getting off the island". It means dropping the "not invented here" philosophy, and embracing the wider PHP community.

Drupal as a product, a community, and a movement, is our co-creation.

We have all played a part in Drupal's success: Dries and the core development team; the wider community of contributors; the attendees of Drupal camps and conferences; people who talk about Drupal; and the developers, agencies, companies and users that drive Drupal's adoption.

In this session I will attempt to answer these questions:

What have we gained, and what have we sacrificed along the way?

NGOs, charities, smaller organisations, and hobbyists made up Drupal's traditional user-base. Have we shunned them as we've chased the enterprise client and big budget projects? Or, does Drupal 8 bring more of these users back into the fold?

Now that we've got this amazing platform, what do we do with it?

The Egyptian Revolution of 2011 is just one example of the web enabling real change in the world. How does Drupal fit into the bigger picture? How can we empower more positive change in the world?

Where do we go next? How can Drupal continue to transform and grow?

Everyone is talking about front-end frameworks, progressive decoupling, big pipe, micro-services. Innovation is more than just jumping on bandwagons. Considered from a deeper place, what do these trends tell us about the real changes that are happening? How does Drupal embrace these changes?

I'm excited. There are some tensions to resolve, and some challenges ahead, but also big opportunities.

Join me for this session. Let's explore transformation of our world, the web, Drupal, and ourselves.

Catégories: Elsewhere

Cocomore: Starting in the new year with Drupal 8 – Cocomore workshop in January 2016

jeu, 21/01/2016 - 00:00

On January 8th our developers camte together to have a Drupal 8 workshop. You can read here, what they experienced and what is new for the Frontend with Drupal 8!

Catégories: Elsewhere

Palantir: The Secret Sauce podcast, Ep. 01

mer, 20/01/2016 - 17:49

This is the first in our weekly bonus podcast that deals with shorter tips and resources that will help you with some straightforward facet of your web project. It's a compliment to our monthly, long-form podcast On the Air With Palantir. That's why we call it the Secret Sauce.

Some episodes will focus on strategy, design, metrics, or other such topics, while others will be more technical in nature. Whatever the focus, we want these to be useful for you, so we draw from our real world experience.

iTunes | RSS Feed | Download

This time around Allison Manley lets Larry Garfield take the mic to talk about Drupal 8, how you can prepare for it properly, and how the changes in this new version push us toward a content strategy approach. While applicable to anyone considering Drupal 8, this particular episode is mostly technical in nature and geared more toward site builders and developers.

Look for the Secret Sauce bonus podcast released weekly on Tuesdays.

Want to talk Drupal 8, and see how our consulting services can get you on the right path? Let's schedule a time to talk.

Catégories: Elsewhere Featured Case Studies: City of Chicago, Office of the City Clerk Website

mer, 20/01/2016 - 17:16
Completed Drupal site or project URL:

Chicago’s Office of the City Clerk (“OCC”) is the most visited office in Chicago government. Citizens regularly use the OCC’s primary website to get information about how to purchase Chicago city vehicle stickers, search prior City Council agendas and legislation, and tune in for the live streaming of Chicago City Council meetings.

The office is known for its technological innovation: it recently moved the purchase of Chicago city vehicle stickers to a year-round online purchasing system, replacing the nearly century-old process of having citizens stand in line once a year to purchase such stickers in person. That mission of innovation was not reflected in its old website, however. The old website was a mix of WordPress and custom PHP files, with document storage split across multiple domains.

On the old site, maintenance was difficult, with simple site content changes often requiring a knowledge of HTML and CSS that OCC staff didn’t have. Additionally, the site was not easily used from mobile devices, despite the fact that nearly 50% of the site traffic came from such devices. OCC knew that it needed an overhaul for its website in order to serve the residents of Chicago for years to come.

Key modules/theme/distribution used: Feed ImportCORSSecurity ReviewSecurity KitDraggableViewsViews DatasourceTeam members: Marc DeLayDrupalKellyTgjangelo
Catégories: Elsewhere

ActiveLAMP: Creating a deployable Docker image with Jenkins - Part 4

mer, 20/01/2016 - 15:30

My previous posts talked about getting your local environment setup using the Drupal Docker image with Vagrant. It’s now time to bake a Docker image with our custom application code within the container, so that we can deploy containers implementing the immutable server pattern. One of the main reasons we starting venturing down the Docker path was to achieve deployable fully baked containers that are ready to run in whatever environment you put them in, similar to what we’ve done in the past with Packer, as I’ve mentioned in a previous post.

Catégories: Elsewhere

erdfisch: Drupal Business and Community Days - Der Business Part

mer, 20/01/2016 - 15:17
Drupal Business and Community Days - Der Business Part Single image:  Boris Baldinger - 20.01.2016 Frank Holldorff Body: 

Drupal 8, das beste Drupal aller Zeiten, hat am 19. November 2015 das Licht der Welt erblickt und nimmt zunehmend Fahrt auf. Mit dem offiziellen Erscheinen des neuen Major Release Drupals ist das Interesse daran nochmals sprunghaft angestiegen. Immer mehr Agenturen setzen nun direkt Drupal 8 für umzusetzende Projekte ein. Auch steigt die aktive Nachfrage auf Seiten der Interessenten explizit nach Drupal 8 deutlich.

Mit dem Schwung, den die Version 8 mit sich bringt, kann Drupal in Deutschland ebenfalls größeres Gewicht erlangen und wird seinen Marktanteil weiter vergrößern. Das führt auch dazu, dass Drupal im Business Umfeld weiter an Relevanz gewinnt und zudem noch mehr Agenturen und Freenlancer das System für sich entdecken.

Aus diesem Grund haben wir uns entschlossen, das neue Konzept der "Drupal Business and Community Days " zu starten. Drupal ist Community, ganz klar! Aber auch Business. Und beides geht zusammen.

Der Business Teil steht unter dem Motto „Von der Akquise bis zur Nachbetreuung“. Hier werden wir die einzelnen Schritte eines Projektes betrachten. Experten werden dazu Vorträge und Workshops anbieten, und es wird viel Gelegenheit zum Informationsaustausch geben, um den Teilnehmern auf diese Art Wissen, Tipps und andere Mehrwerte zu vermitteln.

Die Vorträge werden innerhalb von 60-minütigen Sessions Wissenswertes zu Themen wie Lead-Marketing, Hosting, Infrastruktur, Entwicklung, Qualitätssicherung, Wartung und vielen weiteren Punkten vermitteln. Der Fokus der Sessions liegt hierbei darauf, Einblicke und Anregungen zu geben und konkret Anwendbares zu vermitteln.

In den großzügigen Pausen zwischen den Sessions bleibt genug Zeit, sich auszutauschen und zu vernetzen. Am Sonntag gibt es Zeit und Raum für Arbeits- und Gesprächsrunden, um einzelne Punkte zu vertiefen.

Die Experten kommen zu einem großen Teil aus der Drupal Business Landschaft, aber nicht ausschließlich! Damit stellen wir sicher, nur Fachleute zu Gast zu haben, die nicht nur wissen wovon sie reden, sondern dies auch im täglichen Geschäft praktizieren.

Die Vorträge richten sich in erster Linien an Drupal Agenturen, Freelancer aber auch an Entscheider, (Web)Projektmanager und IT-Leiter, die planen, Drupal einzusetzen.

Interessierte erhalten hier einen Einblick wie in die einzelnen Projektschritte ablaufen, und auch, wie die Agenturen arbeiten. Eine gute Möglichkeit, sich den zukünftigen Dienstleister, Partner, Arbeitgeber oder Kunden einmal anzusehen.

Mit dem [Business Ticket](… "Tickets für die 1. Drupal Business and Community Days"] haben Sie auch vollen Zugang zu dem Community Teil um dort direkt auch aktiv an Drupal mitzuwirken oder sich mit den Entwicklern, die aus mehreren Ländern Europas kommen, auszutauschen.

Schlagworte/Tags:  DrupalBCDays event dc-planet planet Ihr Name Kommentar/Comment Kommentar hinzufügen/Add comment Leave this field blank
Catégories: Elsewhere