After having some discussions beforehand within the Drupal e.V. and some communication with the Dutch association we decided to meet in place at the Drupalcamp.Ruhr to have an open discussion about the website landscape in Germany and how we can join efforts and collaborate on providing a good base for local communities to promote Drupal and their activities.

## Current State

* drupal.de
* verein.drupal.de
* drupal-business.de
* drupalcamp.de / cmsevents.de
* Separate Usergroup pages: e.g. dugmuc.de
* drupal.ch (Plans for upgrading)
* drupal.nl (D8)

## Notes

* Need of consolidating the current websites as they are out of date (technically, design, content)
* We need to make the work in the local Drupal user groups more visible
* Drupal Association: more focus on Drupal Buyers Journey, standardizing communication for different personas
* Loosely coupled process: so we do not get stuck in a "heavy" process
* MVP approach
* Target groups: Business owners, Decision makers, Newcomers, Drupal Devs without community involvment
* Possible site structure proposed by @hexabinaer:

------------------------------
Nav: About  ... Community
------------------------------
Hero: Drupal branding similar to d.o
CTAs
------------------------------
Case studies, read more about
------------------------------
more content, more arguments

* Fast actions on the top of the page
* Undecided visitors should get more arguments by scrolling down
* Personas are developed by Drupal Association and also Drupal CH had a workshop on that (@dasjo)
* Sharing marketing content and keeping it up to date
* Default Content could be part of a distribution
* Marketing in EU and US differs
* marketing project for managing tasks on d.o - @hexabinaer
* Topics for the site:
** Case Studies
** User Groups & events
** About Drupal (Landing Pages / Content marketing)
* Features: e.g. Newsletter, CTA, Layout/Paragraphs, FAQ, Webforms
* Possible bases:
** existing distribution: Varbase, openEdu, deGov, Opensocial, Drutopia
** Code base drupal.nl
** Code base drupalcamp.ruhr
* Communication via drupalchat.eu

## Next steps

* [x] Drupal org project
* [x] Communication channel: https://drupalchat.eu/channel/lcd
* [ ] Define MVP features (#2954525: Project scope)
* [ ] Bring motivated developers in
* [ ] Go for a code base (#2954526: Evaluate Code Bases)

Comments

derhasi created an issue. See original summary.

dasjo’s picture

dasjo
he/him
Primary language German
Location Zurich
commented

Thanks for setting this up derhasi!

I am looking forward especially to keep each other updated about the different initiatives for creating local community websites.

baddysonja’s picture

baddysonja
Primary language Icelandic
Location Frankfurt am Main
commented

Where can do we start defining MVP features. What comes to my mind is:

  • Basic page with a couple of paragraphs
  • News
  • Events
  • Case study
derhasi’s picture

derhasi commented

* The French association is currently working on a D8 release: see https://twitter.com/Florent_Torre/status/976014283879395330
* The Code base from drupalcamp.ruhr is available at https://git.dunix-data.de/dcruhr/18
* We also are allowed to use the Dutch codebase at is now GPL2+/GPL3 without any other restrictions

I created a ticket for defining a MVP feature set. #2954525: Project scope

derhasi’s picture

derhasi commented
Issue summary: View changes
morenstrat’s picture

morenstrat
he/him
Primary language German
Location Bochum, Germany
commented

I'm gonna put this issue on the agenda for the upcoming DUG Ruhr meetup next week. Our plan was to clone our camp web site (drupalcamp.ruhr) and build the user group site on top of that.

The camp site was built with Drupal 8 with common modules such as Pathauto, Redirect and Admin Toolbar.

For content modeling we used Paragraphs with Core fields + some extras such as Views Reference Field and Google Map Field.

The frontend base theme is the Bootstrap theme. Adminmal theme for the admin area.

Further important (at least for our use case) modules were:

  • SMTP (to use a mailserver with good reputation)
  • Webform (for Feedback, Waitlist, Contact)
  • Field permissions (to be able to mark sessions as "accepted" by admins only)
  • Honeypot