Watch the video session here.
This case study will cover how the architecture of Drupal 8 enabled our web development team at UC Davis to quickly build a highly functional, customized web application that enabled the UC Davis Human Rights Studies Program to implement their Article 26 Backpack Tool for Universal Mobility (article26backpack.ucdavis.edu).
This beginner session will introduce the incredible potential of using the command line in developing for the web.
Interested Drupal users, designers and site builders will gain the knowledge of using SSH to connect to servers, Git for version control, Drush and Drupal Console for workign with Drupal, Aliases and Bash scripts for common tasks, and automation/task runners like Grunt and Gulp.
Attendees will come away from the session with their interest piqued, with the desire to learn more about using the command line in their workflow.
This session will provide an overview and live demonstration of the FolderShare module for Drupal 8. This module adds data management and data sharing capability to a Drupal site. The module takes advantage of Drupal's capability to provide a rich authoring/viewing environment that includes providing a description to any file or folder as well as discussing it via comments. Users can securely upload and organize arbitrary files and folders and share them either publicly or privately with others (like Dropbox).
Drupal is better than ever, but whether it is more successful is questionable. A pincer threatens Drupal. One side, Drupal's own power and complexity, discourages new users and contributors. The other, proprietary platforms, increasingly squeeze out custom web development through sheer economies of scale. Retreating into Drupal's new fortress, the enterprise, leaves many of us on the outside— and it doesn't escape the pincer, which will continue until there's nowhere left to hide.
I joined the Drupal community about 7 years ago at a moment in my life when I was looking for more than just a CMS. Drupal and the Drupal community have filled needs for me that extend beyond the technical requirements of a client project. Sometime, I wonder if I expect too much from a loosely structured community that came about to create and support an open source software project.
I've been running a small Drupal shop for several years now and have experimented with lots of tools and technologies to manage my workflow, contractors, and the financial aspects of my business. It's easy to waste a lot of time chasing the latest and greatest tools.
I'd like to share the tool set I'm currently using, things I've tried, and gaps that I still need to fill. Most of all, I'd love to hear what tools that others have used and why they choose them.
Here are the categories I plan to discuss:
For quite a while, I've been working with pre-configured gulp files and using the command "gulp watch" to complile my SASS. Recently, I've dug a little deeper to try and understand what Gulp is capable of, how I can customize my workflow with Gulp, and to better understand my alternatives.
This session is a beginners guide to Gulp. We'll start with what Gulp is, what all it is capable of, and whether or not you should use it? We'll take apart the configuration file used by Gulp, gulpfile.js, and show you how to customize it.
Debugging in the browser is something every Front End Developer should know, I wish I knew this before... but if you want to save time and learn more about how JS runs in your browser this session is for you.