Jadwin - A07

The Composer Workflow

Gobinath Mallaiyan — Thu, 05 Dec 2019 05:20:29 +0000

The Composer Workflow Gobinath Mallaiyan Thu, 12/05/2019 - 00:20

Presenter(s)

Gobinath Mallaiyan

This session will propose a upgraded way of managing your Drupal Project using composer. It simple to have a project start kit that would fit your need & keep reusing them in all your drupal project.

A Refresh - What is composer and how to migrate your Drupal 8 site to Composer.
Best practices
Drupal-scaffold - what is it & why to use !
Semantic versioning
Patching Via Composer (Local / Remote Patches)
Optimized strategy for Managing the Project Repo.
Common Error while using Composer
My Improvised Composer Workflow - Tried & Tested.

Attachment	Size
Composer Workflow - Session Slides	2.6 MB

Who Should Attend

Back-end Developers
Front-end Developers

Prerequisites

None

Drupal’s Scariest Things

Ray Saltini — Sat, 16 Nov 2019 00:57:23 +0000

Drupal’s Scariest Things Ray Saltini Fri, 11/15/2019 - 19:57

Presenter(s)

Ray Saltini
David Hernandez

What keeps you up at night? Whether you’re a marketing or digital manager, SME or tech lead, the internet can be a scary place.

We’ve polled our devs and project stakeholders and we’ve got a list we’re pretty sure will make the most experienced Drupalist shudder. We’ll talk about updates, deployments, integrations and more as well as how to face your fears head-on, armed with best practices and proactive tactics.

This session is for everyone that’s ever worried about crashing on the launchpad, been upended by an update, confused by Composer, or lost faith about leaping to a new platform, join us as we come together to talk through our experiences about becoming friends with the monster under the bed.

Come prepared to share the things that scare you the most!

Who Should Attend

Everyone

Prerequisites

Every effort will be made to keep our content as robust and accessible as possible for both experienced Drupalists and newcomers.

Progressively Decoupled Drupal, for everyone!

btopro — Thu, 24 Oct 2019 17:33:32 +0000

Progressively Decoupled Drupal, for everyone! btopro Thu, 10/24/2019 - 13:33

Presenter(s)

Rebecca Goodman
Bryan Ollendyke
Chuck Lavera
Michael Potter

The last 4+ DrupalCampNJs / DrupalCons

Super Excited Developer: "OMG JSON:API in core!? And React and JS are awesome and I CAN HAZ SHINEY THINGS in Drupal!!"

Reasonable Developer: "Yeah and headless is totally the way to go, I can see it! I'm not sold totally on how but it DOES seem like what we should explore in the future"

Project manager: "We have a team of 8, 3 projects in the pipeline and 10 to maintain currently, welcome to reality you two. We have mouths to feed and projects to tend to so maybe we can look at this when we get out from under our project load but keep dreaming."

Welcome, to the harsh Reality

Where we attend great events like this one and talk about Headless for almost four years yet have very few people actually doing it unless they have a large team or a lot of free time, allowing them to present at events about how great it is. But... is anyone really doing this? Like is it feasible? Does that sound like your team? Mine neither. But I didn't want to fall behind. So we came to a cross-roads (or so we thought): We burn down our existing approaches and do them headless OR we ignore all these talks.

Then, we spoke to others at Decoupled Dev Days years ago and found something interesting: there's another way out.

Another way out for ALL of us

Headless is the future, or should I say, a big consideration in the future. But what's been lost is what is a legitimate way of getting there.

In this talk, I'll walk you through the project life cycle that involved the ELMS:LN team shifting from traditional Drupal JS to a progressively decoupled approach to the point that now we're able to simultaneously work on HAXTheWeb and Drupal projects while still maintaining a small team. Specifically questions we'll answer and unveil in this talk:

How we moved off an existing design framework in phases
How we started going the wrong way, picking AngularJS for a total headless rewrite and never will again..
How we stopped all headless development, got behind Web components and slowly pushed them into production
How this helped us to not lose momentum on any project and now we work at unparalleled levels of efficiency via web component re-use
How we built a progressively headless Drupal based system
How we built HAX, a completely headless authoring experience to side-step Gutenberg
How our progressive headless has turned into us building our OWN headless CMS out of identical components that is entirely JSON / flat file driven
How you can get started with Web components and use them in any Drupal or non Drupal project, today.
How to access and leverage our 400+ decoupled web components that we use every day as well as 100s from the wider community
How other organizations are leveraging our web components to enhance their web properties at scale and progressively

This will be making the case for web components as an approach and the future of all development, but if you've never used or heard of them feel welcome! This will be a mix of code for examples in production and demo purposes but is much more focused on policy, methodology, workflows and experiences from our team (4 people) developing 400+ web components the last 3 years.

We'll cover why your leaving money on the table NOT using web components, how we've taken month long functional prototypes down to days or hours and why Web components aren't just a stop on along the road but unlock component architecture for all projects without bloated frameworks or gigantic rewrites to existing projects.

Join the movement and better understand how we're now able to hold our own events around web components because of the growing interest in a progressively decoupled approach where you can migrate one "brick" at a time off existing projects and workflows; Or, leave them where they are and augment what you have. Lots of examples and resources will be pulled together across the web components community due to is size and scale.

Who Should Attend

Designers
Everyone
Front-end Developers
Project Managers
Site Builders

Prerequisites

You've got multiple Drupal and other CMS / non-CMS properties and have lived the pain of having to maintain multiple copies of similar web systems just because they were built in different libraries, frameworks, CMSs, etc. This will be approachable by newbies and tech pros alike and focus on the entry point for using Web components in any project, specifically showing some ways we've gotten them into Drupal but it can be applied to any existing project.

Inclusive Content Strategy

volkswagenchick — Tue, 15 Oct 2019 21:56:21 +0000

Inclusive Content Strategy volkswagenchick Tue, 10/15/2019 - 17:56

Presenter(s)

AmyJune Hineline

Inclusivity is at the heart of an effective content strategy. Accessible code may be imperative for inclusion, but all the code in the world doesn’t do any good if the content is not meaningful to our readers.

In this session, we’ll go over what we can do as content authors and communicators to ensure our readers feel that we are speaking with them, not at them. We’ll look beyond the semantic markup and structured content to see the strategic value of accessible and inclusive, well-written content.

Discussion points will include:

- What makes content inclusive? Including definitions, clarifications, and real-life examples

- Why is inclusive language important?

- How we can embrace accessibility for those with every sort of ability

- Why awareness and acceptance isn’t enough — how to shift to being more process-oriented

Along with awareness, there is acceptance and action...

Attachment	Size
DC NJ 2020 - Inclusive Content.pdf	13.67 MB

Who Should Attend

Content Editors
Decision Makers
Everyone

Prerequisites

A desire to remove barriers to access digital information.

Handling HTML Markup with Drupal's Migrate API

Benji Fisher — Sat, 12 Oct 2019 19:29:44 +0000

Handling HTML Markup with Drupal's Migrate API Benji Fisher Sat, 10/12/2019 - 15:29

Presenter(s)

Benji Fisher

In Drupal 8, we use the core Migrate API for

Upgrading Drupal 6 and Drupal 7 sites
Migrating sites from other systems to Drupal
Recurring imports from external systems (feeds)

It is a robust, flexible tool.

Drupal works best with structured data, and the Migrate API supports this: file attachments, related taxonomy terms, references to authors or other nodes, and so on. Along with the structured data, we also have to deal with blocks of text, and these blocks often contain HTML markup.

Until now, the Migrate API has supported basic processing of text fields using regular expressions. Marco Villegas and I contributed some plugins to the Migrate Plus module to support proper HTML parsing. This is easier to use and more reliable than using regular expressions.

We originally wrote these plugins while working for Isovera on a project for Pega Systems. Both Isovera and Pega have supported sharing these plugins with the Drupal community. I hope other developers will use them and give back some of their own plugins that use the same approach.

In this session you will

Get an overview of the MIgrate API in Drupal 8
Get an introduction to the new DOM-based plugins in Migrate Plus
Learn how to use the new plugins in your own migrations. (Demo time!)
See how to extend the framework with your own custom plugins

Slide on my GitLab Pages: https://benjifisher.gitlab.io/slide-decks/html-migrate-dcnj-2020.html

Attachment	Size
Slides (PDF)	833.19 KB

Who Should Attend

Back-end Developers

Prerequisites

Familiarity with HTML markup
Interest in the Migrate API