How to keep Drupal relevant in the Git-based and API-driven CMS era DrupalCampNJ

Feb 2, 20190 likes363 views

Jesus Manuel Olivas

The slide deck for the session How to keep Drupal relevant in the Git-based and API-driven CMS era at DrupalCampNJ

$ whoami
Jesus Manuel Olivas
jmolivas@weknowinc.com
jmolivas
jmolivas
drupal.org/u/jmolivas
jmolivas.weknowinc.com

Mexicali 
Mexico + California
Calexico 
California + Mexico
$ ifconfig

When all you have is a
hammer, everything looks
like a nail.

How to keep Drupal relevant in the Git-based and API-driven CMS era DrupalCampNJ

Traditional Monolithic CMS + Particle (Design System)

●
Drupal Headless API + Front-end library

Challenges
Performance Reliability Security Hosting

Reliability - The Traditional Stack + Cache

Security
> Stack dependencies
> Platform dependencies core
> Custom modules dependencies
> Third party libraries

Hosting
> Managing a complicated stack is not easy.
> Requires knowledge of managing servers,
databases, cache, DNS, backups, automation, and
much more.
> The more complex your stack is to support your
production site, the more expensive it becomes.

●
Contentful, GraphCMS, Sanity + Front-end library

Improving the UX providing a GUI
when using a Git-based CMS.

git-based + UI using a PaaS
Netlify Forestry CloudCannon

Using Drupal to provide a GUI and
content for a Git-based/API-driven CMS.

Drupal CMS + Tome to export as Flat Files
+ ● Build

Decoupling the
"Content Management GUI"
from the
“Production Environment".

The Content Mesh
● https://www.gatsbyjs.org/blog/2018-10-18-creating-compelling-content-experiences/

https://github.com/weknowinc/drupal-boina
# Clone repository
git clone git@github.com:weknowinc/drupal-boina.git
# Copy .env file
cp .env.dist .env
# Start containers
ahoy up
# Install Composer dependencies
ahoy composer install
# Install Boina distribution
ahoy drupal boina:install

https://github.com/weknowinc/gatsby-starter-drupal-boina
# Download Starter  
gatsby new boina https://github.com/weknowinc/gatsby-starter-drupal-boina
cd boina
# Copy environment file
cp .env.dist .env.development
# Update environment variables
DRUPAL_HOST=http://drupal-boina.develop/
# Start Gatsby in development mode
gatsby develop

Feel free to turn off your Drupal after build
●https://twitter.com/ckaotik/status/647020262001614848

Challenges
• Use a markdown editor with Drupal. (tui_editor)
• Preprocess inline-images on markdown. (gatsby-remark-drupal)
• Deploy your site directly from Drupal. (build_hooks)

API Services
• Web Forms (CRM Integration , Serverless
Function, Form PaaS)
• E-Commerce (Shopify, Salsify, PXM,
Headless Commerce, Stripe, Paypal)
• Comments (Disqus, Serverless functions)

What is Gone
• Twig
• Render array
• Theme layer
• Theme preprocessing
• *Views (use GraphQL instead)
• Data modeling.
• Content editor capabilities,
revisions, moderation and
scheduling.
• Pathauto
• Site Settings
What to keep using

Must have plugins
• gatsby-source-drupal
• gatsby-remark-drupal
• gatsby-transformer-remark
• gatsby-remark-images
• gatsby-remark-external-links
• gatsby-plugin-sharp
• gatsby-plugin-react-helmet

Thank you … Questions?
Feel free to ping me during the event,
at the parties, after-parties, and twitter @jmolivas

This document discusses embracing a headless CMS approach using Drupal and GatsbyJS. It begins by describing the traditional monolithic CMS model and some of its challenges around performance, reliability, security, and hosting. It then introduces static site generators and the JAMstack as an alternative approach that addresses these challenges. It provides examples of headless CMS options like Contentful and NetlifyCMS that can be used with Gatsby. Finally, it demonstrates a specific setup using Drupal as a headless CMS with an export plugin and Gatsby starter theme to build sites in a decoupled way.

Drupal South 2018 - How to keep Drupal relevant in the Git-based and API-dri...enzolutions

This document discusses how to keep Drupal relevant in the Git-based and API-driven CMS era. It outlines some of the challenges with traditional Drupal implementations, including reliability, security, hosting, and performance issues. It then describes moving to a headless Drupal implementation with a GraphQL or REST API and using a front-end framework like Gatsby. This decouples the content management from the production site for better performance, reliability, and security. It recommends using plugins like gatsby-source-drupal to connect Drupal content to a Gatsby site built with React.

How to keep Drupal relevant in the Git-based and API-driven CMS era - BADCampJesus Manuel Olivas

How many times have you ever heard? "Choose the right tool for the job" or "When all you have is a hammer, everything looks like a nail." The Drupal community is embracing the "Get off the island" mantra. Modernizing Drupal was the goal of the latest Drupal 8 release, but technology moves faster than the awesome community could improve our beloved platform. Gatsby is taking the world by storm and the JAMstack is here to stay. Come to this session, to learn what can we do to keep Drupal relevant and this new era.

Hey webpackAndrew Makarow

This document provides an overview of Webpack and its capabilities for bundling assets and code splitting. It discusses Webpack's flexibility in configuration, support for different module systems, extensive ecosystem of plugins, and ability to hot reload code changes. It also covers using loaders, the development server, extracting CSS, code splitting, aliases and multiple builds. Resources for learning more about Webpack are provided.

Advanced front-end automation with npm scriptsk88hudson

This document discusses using npm scripts for front-end automation and builds. It argues that npm scripts provide a simple, cross-compatible way to automate tasks like bundling, transpiling, testing and deployment without additional build tools. Npm scripts take advantage of existing CLI tools and allow decomposing complex automation into simple, composable tasks through lifecycle scripts and npm-run-all. Some tradeoffs are less extensibility and ongoing challenges with cross-platform support, but the approach aims to provide simpler mental models than alternative build systems.

The shift to the edgeJakub Wadolowski

The way we build web applications evolved over the decades - from on-prem servers named after your favourite Star Wars characters to autoscaling cloud clusters and serverless functions. Throughout this journey the architecture paradigm shifted towards more distributed model. Whether that’s your CMS, monitoring system or authorisation layer - it’s most likely just an endpoint you exchange data with. At the end of the day, every HTTP request goes through various middleware layers and requires both server- (SSR) and client-side rendering (CSR). Recently, a new piece of tech appeared on the landscape - WebAssembly. It became 4th official language on the Web (following HTML, CSS and JavaScript) and was initially meant to run in the browser and improve CSR. It quickly turned out that WebAssembly on the server is also a thing and can revolutionise the way we think of web apps. Some providers like Fastly and Cloudflare adopted WebAssembly and allow you to run custom code at the edge. That opens up completely new possibilities - authentication, personalised content rendering, A/B testing - you name it. Everything as close to end users as possible. During my talk I’d like to show you what edge computing offers at this stage and how it can be integrated with AEM as a Cloud Service.

Bower - A package manager for the webLarry Nung

This document provides an overview of Bower, a package manager for the web. It discusses how to install Bower, commonly used Bower commands like install, search and uninstall, the bower.json and .bowerrc configuration files, and includes an appendix with additional reference information. The document is intended to teach users how to get started with and effectively use Bower to manage front-end web packages and dependencies.

Introduction to Express and GruntPeter deHaan

This document introduces Express, a web development framework for Node.js, and Grunt, a JavaScript task runner. It describes Express as fast, lightweight, and minimalist, noting that it includes only necessary features. Grunt is presented as a tool for automating tasks like minification, compilation, unit testing and linting. The document provides instructions on setting up projects with Express and Grunt, demonstrating how to define tasks in a Gruntfile and develop custom tasks.

Bower & Grunt - A practical workflowRiccardo Coppola

This document discusses using Bower and Grunt together to manage front-end dependencies and files in a workflow. Bower is used to declare and install dependencies, while Grunt plugins like grunt-bowercopy and grunt-contrib-clean are used to copy dependencies to consistent locations and clean files. Setting up this workflow with Bower, grunt-bowercopy, grunt-contrib-clean, and Git can help organize a project's dependencies, facilitate tracking without committing all files, and reduce build times.

Grunt and BowerGeorge Estebe

The document discusses Grunt and Bower, two JavaScript build tools. Grunt is a task runner that can be used to automate repetitive tasks like minification, compilation, unit testing, and linting. It uses a Gruntfile to configure tasks and load plugins. Bower is a package manager for front-end web development that allows installing dependencies directly from the command line. It uses a bower.json file to specify dependencies that will be downloaded from the Bower registry.

Html 5 boot campLaurie Young

Production Ready Javascript With GruntXB Software, Ltd.

Webpack: from 0 to 2Alessandro Bellini

- Webpack is a module bundler that builds dependencies between modules and manages assets like JavaScript files, CSS files, and images. - It uses loaders to transform different types of modules and plugins to extend its functionality. Loaders handle file transformations while plugins can access and modify the build process. - Code splitting allows splitting code into separate bundles to optimize load performance by prioritizing loading and allowing on-demand loading of code. Techniques like extracting vendor code and using import statements help enable code splitting in Webpack.

Webpack DevTalkAlessandro Bellini

This document provides an overview and introduction to Webpack. It begins by establishing some ground rules and an agenda. It then discusses what prompted the creator to start using Webpack and how it works as an "assets crawler and bundler". The rest of the document covers the key aspects of Webpack like its configuration file, loaders and plugins, and how it can be integrated with other tools. Code examples are provided and questions are welcomed from the audience.

Web101Hamdi Hmidi

This document provides an overview of the history and evolution of the web. It discusses: 1. The birth of the web in 1989 by Tim Berners-Lee and the launch of the first web server and site. 2. Web 101 fundamentals including HTML, CSS, and JavaScript. 3. The web revolution brought about changes like the Chrome V8 engine, Node.js, and the distinction between front-end and back-end development. 4. The modern web workflow incorporating tools like package managers, task runners, preprocessors, and version control with Git and GitHub.

Preprocessor Workflow with GruntVlad Filippov

The document discusses using Grunt, an open source task runner, to automate and optimize workflows for CSS preprocessing, image optimization, and more. It provides an overview of Grunt functionality and plugins, demonstrating how to set up a Gruntfile and common workflows using plugins like grunt-contrib-less, grunt-contrib-imagemin, and grunt-contrib-watch. The document encourages exploring task combinations, sharing workflows, and contributing to existing plugins or building new ones to extend Grunt's capabilities.

Modernizing Your WordPress Workflow with Grunt & BowerAlan Crissey

How To Set a Vagrant Development SystemPaul Bearne

This document provides instructions on how to set up a Vagrant development environment. Vagrant allows developers to run development environments that match production by creating virtual machines. Key points: - Vagrant uses VirtualBox to run virtual machines and configure project isolation and version control. - The basic workflow involves initializing a Vagrantfile configuration, running "vagrant up" to launch the virtual machine, and "vagrant destroy" to wipe it out. - Additional commands like "vagrant suspend" pause the virtual machine. The document demonstrates configuring ports, shared folders, and provisioning scripts. - Benefits of Vagrant include no need to install web servers locally, matching production

Fast Paced Drupal 8: Accelerating Development with Composer, Drupal Console a...Acquia

We’ve heard that developing with Drupal 8 is fast by default, but does that extend to your development process? There are new tools in Drupal 8 that can accelerate your day-to-day work, and will help you master rapid development in Drupal 8. Join Myplanet’s Erin Marchak as she does a live walk through of building a site install with Composer, developing a module with Drupal Console, and ingesting external content with Services, all within 1 hour. In this demonstration of Drupal 8’s improved developer experience, topics covered will include Dependency management using Composer Content ingestion using Guzzle PHP Code scaffolding using Drupal Console Configuration management using Drupal Console Drupal 8’s Services and Dependency Injection

Using Capifony for Symfony apps deployment.Žilvinas Kuusas

Create a Varnish cluster in Kubernetes for Drupal caching - DrupalCon North A...Ovadiah Myrgorod

Varnish is a caching proxy usually used for high profile Drupal sites. However, configuring Varnish is not an easy task that requires a lot of work. It is even more difficult when it comes to creating a scalable cluster of Varnish nodes. Fortunately, there is a solution. I’ve been working on kube-httpcache project (https://github.com/mittwald/kube-httpcache) that takes care of many things such as routing, scaling, broadcasting, config-reloading, etc... If you need to run more than one instance of Varnish, this session is for you. You will learn how to: * Launch a single instance of Varnish in Kubernetes. * Configure Varnish for Drupal. * Scale Varnish from 1 to N nodes as part of the cluster. * Make your Varnish cluster resilient. * Reload Varnish configs on the fly. * Properly invalidate cache for multiple Varnish nodes. This session requires some basic understanding of Docker and Kubernetes; however, I will provide some intro if you are new to it. Join this session and enjoy!

Drupal 8: frontend developmentsparkfabrik

How we maintain 200+ Drupal sites in Georgetown UniversityOvadiah Myrgorod

Easy WP Dev environments with VVVDaniel Stout

Drupal VM for Drupal 8 Dev - Drupal Camp STL 2017Jeff Geerling

Java Stammtisch Würzburg - CONAIRMatthias Reining

This document summarizes a presentation on the Conair project. The presentation covers the project's architecture using JEE, implementation of REST APIs with AngularJS, printing functionality using an XLS templating engine, authentication with LinkedIn OAuth 2.0, hosting on a virtual server, continuous integration with Jenkins and Cloudbees, and backups to Dropbox. The project code is open source and available on GitHub.

Common Pitfalls for your Drupal Site, and How to Avoid ThemAcquia

Drupal can be a resource-intensive system. Any moderately complicated site will generate a lot of database queries and use a fair amount of memory to build pages to serve to visitors. With some judicious tuning, however, Drupal can perform really well, and at scale. In this webinar, Drew Webber, Principal Support Engineer at Acquia, will discuss some common pitfalls encountered by sites that struggle in the face of increased traffic. Attendees will walk away with a deeper understanding of: -The most common problems encountered when it comes to Drupal site performance -Ways of identifying performance bottlenecks on your Drupal site -How to avoid these common pitfalls and remedy these issues (often without writing a single line of code!) -What not to do when building and running your site

Drupal 8 DevOps . Profile and SQL flows.Andrii Podanenko

The Docker "Gauntlet" - Introduction, Ecosystem, Deployment, OrchestrationErica Windisch

More Related Content

What's hot (20)

Introduction to Express and GruntPeter deHaan

Bower & Grunt - A practical workflowRiccardo Coppola

Grunt and BowerGeorge Estebe

Html 5 boot campLaurie Young

Production Ready Javascript With GruntXB Software, Ltd.

Webpack: from 0 to 2Alessandro Bellini

Webpack DevTalkAlessandro Bellini

Web101Hamdi Hmidi

Preprocessor Workflow with GruntVlad Filippov

Modernizing Your WordPress Workflow with Grunt & BowerAlan Crissey

How To Set a Vagrant Development SystemPaul Bearne

Fast Paced Drupal 8: Accelerating Development with Composer, Drupal Console a...Acquia

Using Capifony for Symfony apps deployment.Žilvinas Kuusas

Create a Varnish cluster in Kubernetes for Drupal caching - DrupalCon North A...Ovadiah Myrgorod

Drupal 8: frontend developmentsparkfabrik

How we maintain 200+ Drupal sites in Georgetown UniversityOvadiah Myrgorod

Easy WP Dev environments with VVVDaniel Stout

Drupal VM for Drupal 8 Dev - Drupal Camp STL 2017Jeff Geerling

Java Stammtisch Würzburg - CONAIRMatthias Reining

Common Pitfalls for your Drupal Site, and How to Avoid ThemAcquia

Introduction to Express and GruntPeter deHaan

Bower & Grunt - A practical workflowRiccardo Coppola

Grunt and BowerGeorge Estebe

Html 5 boot campLaurie Young

Production Ready Javascript With GruntXB Software, Ltd.

Webpack: from 0 to 2Alessandro Bellini

Webpack DevTalkAlessandro Bellini

Web101Hamdi Hmidi

Preprocessor Workflow with GruntVlad Filippov

Modernizing Your WordPress Workflow with Grunt & BowerAlan Crissey

How To Set a Vagrant Development SystemPaul Bearne

Fast Paced Drupal 8: Accelerating Development with Composer, Drupal Console a...Acquia

Using Capifony for Symfony apps deployment.Žilvinas Kuusas

Create a Varnish cluster in Kubernetes for Drupal caching - DrupalCon North A...Ovadiah Myrgorod

Drupal 8: frontend developmentsparkfabrik

How we maintain 200+ Drupal sites in Georgetown UniversityOvadiah Myrgorod

Easy WP Dev environments with VVVDaniel Stout

Drupal VM for Drupal 8 Dev - Drupal Camp STL 2017Jeff Geerling

Java Stammtisch Würzburg - CONAIRMatthias Reining

Common Pitfalls for your Drupal Site, and How to Avoid ThemAcquia

Similar to How to keep Drupal relevant in the Git-based and API-driven CMS era DrupalCampNJ (20)

Drupal 8 DevOps . Profile and SQL flows.Andrii Podanenko

The Docker "Gauntlet" - Introduction, Ecosystem, Deployment, OrchestrationErica Windisch

Lean Drupal Repositories with Composer and DrushPantheon

2015 DockerCon Using Docker in production at bity.comMathieu Buffenoir

Ruby microservices with Docker - Sergii KobaRuby Meditation

This document discusses using Docker to build and run Ruby microservices. It covers optimizing Dockerfiles to create small images, using Docker Compose to define and run multiple services, implementing centralized logging with ELK, and routing requests between services with tools like Traefik or HAProxy. The goal is to provide an end-to-end development and deployment environment for building microservice applications with Ruby and Docker.

Docker for Developers: Dev, Test, Deploy @ BucksCo Devops at MeetMe HQErica Windisch

The document discusses Docker's platform and ecosystem, which has grown significantly over 19 months to include over 640 contributors, 2.75 million downloads, and extensive community support and documentation. It also outlines the key components of Docker's platform, including the Docker Engine for building, shipping, and running containers, and Docker Hub for sharing images. Finally, it provides examples of how to use Docker to build, run, and manage applications and services across infrastructure.

Develop with docker 2014 augVincent De Smet

This document summarizes Docker concepts and provides steps for a local Docker development setup. It introduces Docker images, containers, and registries. It then outlines requirements for development and production configurations and provides examples of setting up a Node.js/Angular frontend and Django backend using Docker images. The document concludes with notes on continuous integration and architecture options.

Docker and Puppet for Continuous IntegrationGiacomo Vacca

Today developers want to change the code, build and deploy often, even several times per day. New versions of software may need to be tested on different distributions, and with different configurations. Achieving this with Virtual Machines it’s possible, but it’s very resource and time consuming. Docker provides an incredibly good solution for this, in particular if combined with Continuous Integration tools like Jenkins and Configuration Management tools like Puppet. This presentation focuses on the opportunities to configure automatically Docker images, use Docker containers as disposable workers during your tests, and even running your Continuous Integration system inside Docker.

Django dev-env-my-wayRobert Lujo

Docker - Demo on PHP Application deployment Arun prasath

Docker is an open-source project to easily create lightweight, portable, self-sufficient containers from any application. The same container that a developer builds and tests on a laptop can run at scale, in production, on VMs, bare metal, OpenStack clusters, public clouds and more. In this demo, I will show how to build a Apache image from a Dockerfile and deploy a PHP application which is present in an external folder using custom configuration files.

DockerCon EU 2015: Trading Bitcoin with DockerDocker, Inc.

Presented by Sebastien Goasguen, VP, Apache CloudStack and Mathieu Buffenoir, co-founder, SBEX Bity is an internet money gateway built by Swiss Bitcoin Exchange ( SBEX ). To trade bitcoin the entire infrastructure of Bity is running in Docker containers. All the components of the infrastructure are using Docker, from the frontend applications and load balancer, the Django based backend, replicated Postgres database, Bitcoin daemon and remittance engine. All software goes through a CI pipeline that starts with Docker images being built on private repositories in Docker hub. Developers take also advantage of a docker-compose definition that allows them to run the entire infrastructure on a single laptop. Finally the production deployments happen thanks to the Ansible Docker module on a CloudStack based public cloud. Everything has been automated to ease re-deployment and operations. This presentation will go through every component and how Docker has enabled us to go production in 4 months.

MySQL on Docker - Containerizing the DolphinSeveralnines

Docker is becoming more mainstream and adopted by users as a method to package and deploy self-sufficient applications in primarily stateless Linux containers. It's a great toolset on top of OS-level virtualization (LXC, a.k.a containers) and plays well in the world of micro services. However, Docker containers are transient by default. If a container is destroyed, all data created is also lost. For a stateful service like a database, this is a major headache to say the least. There are a number ways to provide persistent storage in Docker containers. In this presentation, we will talk about how to setup a persistence data service with Docker that can be torn down and brought up across hosts and containers. We will touch upon orchestration tools, shared volumes, data-only-containers, security and configuration management, multi-host networking, service discovery and implications on monitoring when we move from host-centric to role-centric services with shorter life cycles.

Package your Java EE Application using Docker and KubernetesArun Gupta

The document discusses packaging Java EE applications using Docker and Kubernetes. It provides an overview of Docker concepts like images, containers and registries. It then discusses Kubernetes which provides an orchestration system for Docker containers to provide capabilities like self-healing, auto-restarting and scheduling containers across hosts. Key Kubernetes concepts discussed include pods, services and replication controllers. Finally it provides some recipes for running Java EE applications on Kubernetes using Docker containers.

"[WORKSHOP] K8S for developers", Denis RomanukFwdays

"It seems that perfection is attained, not when there is nothing more to add, but when there is nothing more to take away." - Antoine de Saint Exupéry We can talk a lot about Kubernetes. But does the whole info is really need for just begining? Let's take away everything, except the really needed, and show a way for ones, who still uses only docker. Let's consider: Why do developers need Kubernetes and what does it looks like? An attempt to automate ops, or why does it was a reinvention of Kubernetes What does kube consists of? How to get a Kubernetes? From docker-compose to c What is a Helm and why it's difficult without one? What is "local development on Kubernetes"? CRD & Operators

[EXTENDED] Ceph, Docker, Heroku Slugs, CoreOS and Deis OverviewLeo Lorieri

Docker for mere mortalsHenryk Konsek

This document discusses Docker, including: 1. Docker is a platform for running and managing Linux containers that provides operating-system-level virtualization without the overhead of traditional virtual machines. 2. Key Docker concepts include images (immutable templates for containers), containers (running instances of images that have mutable state), and layers (the building blocks of images). 3. Publishing Docker images to registries allows them to be shared and reused across different systems. Volumes and networking allow containers to share filesystems and communicate.

Docman - The swiss army knife for Drupal multisite docroot management and dep...Aleksey Tkachenko

Docman is a tool for managing multisite Drupal installations across repositories and environments. It uses a configuration system and Git-based workflows to build and deploy Drupal sites. Docman addresses issues with multisite development like code separation, standards enforcement, and deployment automation. It is focused on cloud hosting and supports continuous integration/delivery. Docman provides commands to initialize projects, build environments, and bump versions across repositories.

Getting Started with PelicanNazrul Kamaruddin

Blazing fast sites using Blaze, Hybrid CMS NYCJesus Manuel Olivas

Blaze is a new Git-based hybrid CMS and PaaS that allows users to: 1. Create headless CMS projects that expose data via REST and GraphQL APIs. 2. Programmatically add, update, and delete content via these APIs. 3. Generate forms using a GUI and process submissions with Serverless functions. 4. Attach Serverless functions to content create/update/delete hooks. 5. Deploy projects to external PaaS providers like Netlify, GitHub, and CDNs. The presentation demonstrated creating a Blaze project, registering for early beta access, and the features planned for the early beta release.

Docker 0.11 at MaxCDN meetup in Los AngelesJérôme Petazzoni

This document introduces Docker and provides an overview of its key concepts and capabilities. It explains that Docker allows deploying applications into lightweight Linux containers that are isolated but share resources and run at native speeds. It describes how Docker uses namespaces and cgroups for isolation and copy-on-write storage for efficiency. The document also outlines common Docker workflows for building, testing, and deploying containerized applications both locally and in production environments at scale.

Drupal 8 DevOps . Profile and SQL flows.Andrii Podanenko

The Docker "Gauntlet" - Introduction, Ecosystem, Deployment, OrchestrationErica Windisch

Lean Drupal Repositories with Composer and DrushPantheon

2015 DockerCon Using Docker in production at bity.comMathieu Buffenoir

Ruby microservices with Docker - Sergii KobaRuby Meditation

Docker for Developers: Dev, Test, Deploy @ BucksCo Devops at MeetMe HQErica Windisch

Develop with docker 2014 augVincent De Smet

Docker and Puppet for Continuous IntegrationGiacomo Vacca

Django dev-env-my-wayRobert Lujo

Docker - Demo on PHP Application deployment Arun prasath

DockerCon EU 2015: Trading Bitcoin with DockerDocker, Inc.

MySQL on Docker - Containerizing the DolphinSeveralnines

Package your Java EE Application using Docker and KubernetesArun Gupta

"[WORKSHOP] K8S for developers", Denis RomanukFwdays

[EXTENDED] Ceph, Docker, Heroku Slugs, CoreOS and Deis OverviewLeo Lorieri

Docker for mere mortalsHenryk Konsek

Docman - The swiss army knife for Drupal multisite docroot management and dep...Aleksey Tkachenko

Getting Started with PelicanNazrul Kamaruddin

Blazing fast sites using Blaze, Hybrid CMS NYCJesus Manuel Olivas

Docker 0.11 at MaxCDN meetup in Los AngelesJérôme Petazzoni

More from Jesus Manuel Olivas (20)

Remix & GraphQL: A match made in heaven with type-safety DXJesus Manuel Olivas

Remix and GraphQL are two of the most exciting technologies in web development today. Remix is a new frontend framework that makes it easy to build efficient and type-safe applications. GraphQL is a query language that makes it easy to fetch data from a variety of sources. In this session, we will discuss how Remix and GraphQL can be used together to create a more efficient and type-safe development experience. We will cover the following topics: - The challenges of developing web applications with traditional templating languages - How Remix can be used to improve state management and data fetching - How GraphQL can be used to improve the development experience for Remix applications - The benefits of using Remix and GraphQL together This session is for anyone interested in learning more about Remix and GraphQL. No prior experience with either technology is required.

Drupal 10 Party GraphQLJesus Manuel Olivas

This document discusses a Drupal 10 party focused on GraphQL. It provides information on GraphQL and how it can be used with Drupal. Specifically, it outlines the Drupal GraphQL and Drupal GraphQL Compose modules which allow generating a GraphQL schema from Drupal entities and structures. It also previews upcoming features for Drupal GraphQL like a GUI for configuring exposed content and fields and support for write actions/mutations. The presenter takes questions at the end.

How to use Drupal to create editorial experiences your content creators will...Jesus Manuel Olivas

This document discusses how to improve the content editing experience in Drupal through the use of modules and themes. It recommends using the Claro or Gin admin themes to modernize the interface. It also recommends modules like Paragraphs, Field Group and Layout Paragraphs to provide a better user experience for managing reusable content like paragraphs. Finally, it discusses how to integrate preview of decoupled React components directly in the Drupal content editing interface using GraphQL.

Beyond Static: Building a Dynamic Application with GatsbyJesus Manuel Olivas

This document discusses building a dynamic application with Gatsby by connecting it to a Drupal backend as a decoupled content management system (CMS). It covers using Gatsby to render static content at build time from Drupal, making client-side calls for dynamic content, implementing user authentication, and allowing content updates from Gatsby. The benefits of this JAMstack architecture include performance, reliability, security and easier hosting compared to traditional monolithic server-rendered stacks.

Drupal, GraphQL, Views, View Modes and Gatsby for a US Gov site CMS PhillyJesus Manuel Olivas

This document discusses using Drupal, GraphQL, Views, View Modes and Gatsby to build a modern frontend for a US government website while keeping the same editorial experience and reducing infrastructure overhead. It covers migrating content from Drupal to a headless Gatsby site using View Modes and Views to surface content via GraphQL, as well as managing content through YAML files and custom console commands.

Embracing the modern web using a Headless CMS with GatsbyJS CMS PhillyJesus Manuel Olivas

This document discusses using a headless content management system (CMS) like Drupal or WordPress with GatsbyJS for a modern web development stack. It defines traditional monolithic and headless CMS approaches. With headless CMS, content is accessible via REST or GraphQL APIs for display on any device. The document recommends using Drupal/WP with GraphQL and building sites with GatsbyJS, which provides benefits like faster iteration, reusability with themes, and leveraging modern technologies.

Embracing the modern web using a Headless CMS with GatsbyJS StanfordJesus Manuel Olivas

This document discusses using a headless CMS like Drupal or WordPress with GatsbyJS to build modern websites. It defines headless CMS as a back-end only CMS with a RESTful or GraphQL API to access content. GatsbyJS is introduced as a framework for building fast websites and apps with React. The benefits discussed are using GraphQL to centralize data access, leveraging Gatsby plugins and themes, and providing a better developer experience with modern technologies and separation of concerns.

Building a modern application using Symfony API Platform and GatsbyJS PHP QROJesus Manuel Olivas

This document discusses building a modern application using Symfony API Platform and GatsbyJS. It introduces Symfony API Platform as a framework for building API-driven projects with REST and GraphQL support. It also discusses using GatsbyJS, a React framework, to build fast websites and apps that can pull data from the Symfony API via GraphQL. User authentication with JWT and integrating the two frameworks is also covered at a high level.

Building a dynamic application with GatsbyJS-Tec-MexicaliJesus Manuel Olivas

GatsbyJS is a free and open source framework based on React that helps developers build fast websites and apps. It centralizes data with GraphQL, making data easier to explore with a single source of truth. Gatsby sites are static, which provides blazing fast performance, simpler deployment, and immutable deployments with reduced DevOps overhead. Dynamic features like content from external endpoints and user authentication can also be supported.

Building a modern web application in the cloud partnerconJesus Manuel Olivas

The document discusses building modern web applications in the cloud. It covers cloud concepts like providers, services, and tools as well as platforms as a service (PaaS). Specifically, it discusses using Firebase and Google Cloud Platform for backend services and hosting static sites with JAMstack. It also mentions options for headless content management systems like CloudCannon, NetlifyCMS, and Drupal to manage content in the cloud.

Embracing the modern web using Drupal as a Headless CMS with Gatsby BADCampJesus Manuel Olivas

This document discusses using Drupal as a headless CMS with GatsbyJS to build blazing fast websites. It outlines some challenges of traditional monolithic CMS and benefits of a headless approach. Key aspects covered include using Drupal for content modeling and editing while leveraging Gatsby for performance. It provides examples of configuring Gatsby sources, creating pages and fragments, mapping data to React components, and component resolution.

Writing a slack chatbot seattleJesus Manuel Olivas

Building a Modern Web Application in the Cloud TecNerdJesus Manuel Olivas

This document discusses building modern web applications in the cloud. It begins by defining cloud computing as software and services that run on the internet rather than locally. It then lists several benefits of developing in the cloud such as quick time to market, networked backups preventing data loss from hardware failures, and reduced costs from not having to manage servers. The document also lists some popular cloud providers and services as well as tools for cloud development including Repl.it, Stackblitz, CodeSandbox, and Coder. It discusses platform as a service (PaaS) such as Amplify and Firebase and their features including hosting, functions, authentication, and NoSQL databases. The presentation concludes by thanking the audience and inviting questions

Tools and Projects Dec 2018 EditionJesus Manuel Olivas

This document provides information on various tools and projects, including: - JSON Server for creating a REST API from a JSON database - JSON GraphQL Server for creating a GraphQL API from JSON - react-jsonschema-form for building forms from JSON schemas in React - docz for creating documentation sites from MDX files - Additional resources like CodeSandbox, Runkit, Prisma, and Visual Studio Code are also mentioned.

Creating a modern web application using Symfony API Platform AtlantaJesus Manuel Olivas

The API Platform framework is a set of tools to help you building API-first projects. The API project Platform is built on top of the Symfony framework, it means you can reuse all your Drupal 8 and Symfony skills and benefit of the incredible amount of Symfony documentation and community bundles. During this session, you will learn how to use the API Platform project to create a modern web application using Symfony, Doctrine, and ReactJS.

Battle of the CMS DrupalCampLAJesus Manuel Olivas

Creating a modern web application using Symfony API Platform, ReactJS and Red...Jesus Manuel Olivas

Writing a slack chatbot DrupalCampLAJesus Manuel Olivas

Improving your Drupal 8 development workflow DrupalCampLAJesus Manuel Olivas

Drupal 8 has changed a lot and the process of creating, building, testing and deploying a site is not the exception. During this session, you will understand the process of creating, building, testing and deploying Drupal 8 sites, and learn which tools you can use to improve your local development workflow and reduce project setup and onboarding time, implement automated analysis tools for code review, code coverage and finally how to build an artifact and deploy your project.

Writing a slack chatbot mxlosJesus Manuel Olivas