agaric-presentations/mlncn-presentations
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Move old draft abstract into current abstract

Browse source
This commit is contained in:
benjamin melançon 2020-03-15 19:07:16 -04:00
parent ee1a73358d
commit 37ad089306
2 changed files with 61 additions and 58 deletions
Download patch file Download diff file Expand all files Collapse all files

61
when-not-module-for-that/abstract.md
View file

@ -1,6 +1,67 @@
# When There's Not a Module for That
With about fifty modules, you can do nearly everything in Drupal 8 (plus configuration, which isn't necessarily trivial).
But what do you do when there's not a module for that?
You make your own.
In this session, we will go over several scenarios and how to
You've built sites with Drupal and know it is a powerful and modular system and that much of Drupal’s power is in its modules, dynamos of drop-in functionality that build on Drupal’s base system and on one another to do wonderful things.
What do you do when there isn't "a module for that", though? You can write a module yourself.
You've built sites with Drupal 8 and know that with a few dozen modules (and a ton of configuring), you can do nearly everything in modern Drupal.
But what do you do when there's not a module for that? Or the ones that exist don't quite meet your needs?
You make your own.
This session will help you take that step. All you need to do is write two text files. The first file tells Drupal about the module; it’s not code. The second file can have as little as three lines of code in it. Making a module is something that anyone can do. There are many (mostly simple) rules to follow and tons of tools to use—and lots of exploration to do. Every person developing a module is still learning.
Learning Objectives:
In this hands-on session, you will:
Learn how to decide when to make your own module.
Write a module that plays well with Drupal core and other modules.
Discover ways to explore the options for extending and overriding functionality provided by Drupal core and other modules.
Micky works with technical activists to connect people with the information and tools they need to move from being a global network to being a global movement based on solidarity. She wrote about her experience in the Drupal community as a contributing author in "Ours to Hack and to Own." She frequently speaks and presents, including recently:
Platform Cooperativism 2019 - Who Owns the World? - New School, NYC
BADcamp 2019 - San Francisco
Keynote - LibrePlanet 2019
Recording: https://events.drupal.org/seattle2019/sessions/scaling-community-decision-making
David Valdez
Spoke at PHP meetup in Mexico City, assisted migration training at DrupalCon Seattle and other venues.
https://www.midcamp.org/2020/topic-proposal/when-theres-not-module
***
Part 1: Looking for modules - is there already a module for that? 10 minutes
Part 2: Contributing to an existing module - is there *almost* a module for that? 15 minutes
Part 3: Starting a new module - 25 minutes

58
when-not-module/abstract.md
View file

@ -1,58 +0,0 @@
# When There's Not a Module for That
With about fifty modules, you can do nearly everything in Drupal 8 (plus configuration, which isn't necessarily trivial).
But what do you do when there's not a module for that?
You make your own.
In this session, we will go over several scenarios and how to
You've built sites with Drupal and know it is a powerful and modular system and that much of Drupal’s power is in its modules, dynamos of drop-in functionality that build on Drupal’s base system and on one another to do wonderful things.
What do you do when there isn't "a module for that", though? You can write a module yourself.
You've built sites with Drupal 8 and know that with a few dozen modules (and a ton of configuring), you can do nearly everything in modern Drupal.
But what do you do when there's not a module for that? Or the ones that exist don't quite meet your needs?
You make your own.
This session will help you take that step. All you need to do is write two text files. The first file tells Drupal about the module; it’s not code. The second file can have as little as three lines of code in it. Making a module is something that anyone can do. There are many (mostly simple) rules to follow and tons of tools to use—and lots of exploration to do. Every person developing a module is still learning.
Learning Objectives:
In this hands-on session, you will:
Learn how to decide when to make your own module.
Write a module that plays well with Drupal core and other modules.
Discover ways to explore the options for extending and overriding functionality provided by Drupal core and other modules.
Micky works with technical activists to connect people with the information and tools they need to move from being a global network to being a global movement based on solidarity. She wrote about her experience in the Drupal community as a contributing author in "Ours to Hack and to Own." She frequently speaks and presents, including recently:
Platform Cooperativism 2019 - Who Owns the World? - New School, NYC
BADcamp 2019 - San Francisco
Keynote - LibrePlanet 2019
Recording: https://events.drupal.org/seattle2019/sessions/scaling-community-decision-making
David Valdez
Spoke at PHP meetup in Mexico City, assisted migration training at DrupalCon Seattle and other venues.