Web Design & Development

Gizra.com: 12 Things I learned at my first DrupalCon

Drupal Planet - Mon, 16/05/2016 - 22:00

For years I have been hearing about DrupalCon from Brice and Amitai. Every six months they would send me a massive group photo and challenged me to locate them among the crazy mustaches, viking helmets, and identical t-shirts. Needless to say, I failed every time and the number of people in those pictures grew every year. I’m also happy to say that that last group photo - from a week ago - included me as well (Bonus points if you can spot me).

2016 DrupalCon Group Photo.

My first Con was an overwhelmingly great experience and I learned a ton of new things. Here are the top 12:

1) Count down from 100 if you can’t fall asleep at night

DrupalCon’s sessions and keynotes are diverse and engaging. For instance, the Community Keynote by @schnitzel (Michael Schmid), was full of tips to keep your brain ready and aware, such as: Start your day doing things you dislike, drink plenty of water that will force you to take a lot of pee breaks, and play with kids to clear your mind.

The enormous amount of people and ideas exchanged in DrupalCon are so invigorating that you might find it hard to sleep at night. Try counting backwards slowly from hundred to zero. I have already put it to the test and it works - that tip alone was worth the trip.

Michael Schmid (@schnitzel) delivers the Community Keynote 2) Gator omelette for breakfast

New Orleans is a seafood and meat town. Crab, crawfish, sausages, bbq, and alligator - the Queen City is not known for its consumptions of vegetables.

Breakfast portions are huge and everything is golden-brown. But in New Orleans there is a special name for that little strip of green ground in the middle of a boulevard - “neutral ground” (thanks Trivia Night!). Perhaps they can grow fresh vegetables there!

A typical three-person breakfast. We’ve never finished it!

Continue reading…

OSTraining: How to Use Pathauto in Drupal 8

Drupal Planet - Mon, 16/05/2016 - 19:10

Many modules have been in flux during the early stages of Drupal 8's development.

Few modules have changed as much as Pathauto, which the vast majority of Drupal sites use to control their URLs.

In this tutorial, I'll show you the current way to use Pathauto with your Drupal 8 site.

Dries Buytaert: Cross-channel user experiences with Drupal

Drupal Planet - Mon, 16/05/2016 - 15:55

Last year around this time, I wrote that The Big Reverse of Web would force a major re-architecture of the web to bring the right information, to the right person, at the right time, in the right context. I believe that conversational interfaces like Amazon Echo are further proof that the big reverse is happening.

New user experience and distribution platforms only come along every 5-10 years, and when they do, they cause massive shifts in the web's underlying technology. The last big one was mobile, and the web industry adapted. Conversational interfaces could be the next user experience and distribution platform – just look at Amazon Echo (aka Alexa), Facebook's messenger or Microsoft's Conversation-as-a-Platform.

Today, hardly anyone questions whether to build a mobile-optimized website. A decade from now, we might be saying the same thing about optimizing digital experiences for voice or chat commands. The convenience of a customer experience will be a critical key differentiator. As a result, no one will think twice about optimizing their websites for multiple interaction patterns, including conversational interfaces like voice and chat. Anyone will be able to deliver a continuous user experience across multiple multiple channels, devices and interaction patterns. In some of these cross-channel experiences, users will never even look at a website. Conversational interfaces let users disintermediate the website by asking anything and getting instant, often personalized, results.

To prototype this future, my team at Acquia built a fully functional demo based on Drupal 8 and recorded a video of it. In the demo video below, we show a sample supermarket chain called Gourmet Market. Gourmet Market wants their customers to not only shop online using their website, but also use Echo or push notifications to do business with them.

We built an Alexa integration module to connect Alexa to the Gourmet Market site and to answer questions about sale items. For example, you can speak the command: "Alexa, ask Gourmet Market what fruits are on sale today". From there, Alexa would make a call to the Gourmet Market website, finding what is on sale in the specified category and pull only the needed information related to your ask.

On the website's side, a store manager can tag certain items as "on sale", and Alexa's voice responses will automatically and instantly reflect those changes. The marketing manager needs no expertise in programming -- Alexa composes its response by talking to Drupal 8 using web service APIs.

The demo video also shows how a site could deliver smart notifications. If you ask for an item that is not on sale, the Gourmet Market site can automatically notify you via text once the store manager tags it as "On Sale".

From a technical point of view, we've had to teach Drupal how to respond to a voice command, otherwise known as a "Skill", coming into Alexa. Alexa Skills are fairly straightforward to create. First, you specify a list of "Intents", which are basically the commands you want users to run in a way very similar to Drupal's routes. From there, you specify a list of "Utterances", or sentences you want Echo to react to that map to the Intents. In the example of Gourmet Market above, the Intents would have a command called GetSaleItems. Once the command is executed, your Drupal site will receive a webhook callback on /alexa/callback with a payload of the command and any arguments. The Alexa module for Drupal 8 will validate that the request really came from Alexa, and fire a Drupal Event that allows any Drupal module to respond.

It's exciting to think about how new user experiences and distribution platforms will change the way we build the web in the future. As I referenced in Drupalcon New Orleans keynote, the Drupal community needs to put some thought into how to design and build multichannel customer experiences. Voice assistance, chatbots or notifications are just one part of the greater equation. If you have any further thoughts on this topic, please share them in the comments.

Digital trends

Red Route: Jumping through hoops with the golden flexbox hammer

Drupal Planet - Mon, 16/05/2016 - 15:11

I've been a big proponent of using Flexbox for a while, especially since hearing Zoe Mickley Gillenwater speaking about it at Smashing Conference Oxford 2014.

In particular, I use justify-content: space-between a lot. But one issue with it is what happens in the last row. If the number of child items doesn't divide nicely into the number of items per row, there will be a big gap between them, as you can see from this Codepen example:

See the Pen space-between by malcomio (@malcomio) on CodePen.

It can look pretty ugly, especially if the parent element is wide. One possible solution is to have the items in the last row fill the available space. But for the tiles layout on the Gallery Guide, that wouldn't work - it would make the last row items much too big. Ideally, the last row would be given a different behaviour - perhaps using a different justify-content value, perhaps using floats, but as far as I'm aware, there isn't a nice CSS way to achieve this.

The suggestion I found on StackOverflow is to add extra elements. Given that the rows are being generated by a Drupal view, we can achieve this using a preprocess function, adding dummy rows, which don't affect small screens because their height is set to zero.

Here's a Codepen example showing the idea:

See the Pen space-between with dummy rows by malcomio (@malcomio) on CodePen.

The relevant views all use the unformatted list format, so in the implementation of template_preprocess_views_view_unformatted we add a variable to say how many extra rows are needed to make it fit nicely:

define('GALL_VIEWS_ITEMS_PER_ROW', 4); /** * Implements template_preprocess_views_view_unformatted(). */ function gall_preprocess_views_view_unformatted(&$variables) { // Add dummy rows so that flexbox looks nice. $view_id = $variables['view']->id(); $tiles_views = _gall_tiles_views(); if (in_array($view_id, $tiles_views)) { $remainder = count($variables['view']->result) % GALL_VIEWS_ITEMS_PER_ROW; $rows_to_add = GALL_VIEWS_ITEMS_PER_ROW - $remainder; if ($remainder && $rows_to_add) { $variables['extra_rows'] = $rows_to_add; } } }

Once we've added this counter, we can use it to create a loop in our views-view-unformatted.html.twig template:

{% if extra_rows %} {% for i in 1..extra_rows %} {% endfor %} {% endif %}

And, as if by magic, the view rows are aligned left. Problem solved.

But maybe the problem was one of my own making. Even before I'd finished building this, I was realising that maybe it would have been easier to just use floats. To paraphrase Abraham Maslow, or perhaps Abraham Kaplan, someone who has just discovered a hammer will always be looking for nails. As always, there's another way I could have solved this, and the new way isn't always better than the old way. Having said that, I do like the way that flexbox helps to keep my margins tidy...

Tags:  Drupal Drupal 8 The Gallery Guide CSS flexbox All tags

Libreria genera password

HTML.it Guide - Mon, 16/05/2016 - 15:00
Php Password. Libreria utile per poter implementare nel proprio progetto la creazione di password in modo automatica per consigliarla ai propri utenti. Tra le opzioni di questo script abbiamo:...

Guida HTML

HTML.it Guide - Mon, 16/05/2016 - 13:50
HTML è il principale linguaggio di pubblicazione di pagine Web, oltre che uno strumento sempre più utilizzato per la realizzazione di contenuti e applicazioni mobile. Seguendo questa guida imparerai...

Archive.org video gratuiti

HTML.it Guide - Mon, 16/05/2016 - 12:30
Permette di visualizzare e scaricare gratuitamente e legalmente tutti i più grandi classici del cinema d'autore. Leggi Archive.org video gratuiti

Divi

HTML.it Guide - Mon, 16/05/2016 - 10:00
Divi è un tema multi purpose estremamente flessibile, adatto ad ogni tipo di progetto web, distribuito da Elegant Themes al prezzo di 69 dollari. Leggi Divi

Creating A Living Style Guide: A Case Study

Smashing Magazine - Mon, 16/05/2016 - 09:38

  

Living style guides are an important tool for web development today, especially in large, complex web applications. They help document styles and patterns, keep designers and developers in sync, and greatly help to organize and distill complex interfaces. Indeed, living style guides remain one of the best ways to communicate design standards to an organization.

 A Case Study

Recently, our company went through the process of creating a living style guide. This is the story of how we developed our living style guide, the mistakes we made along the way, and why the current landscape of style guide generators did not suit our needs.

The post Creating A Living Style Guide: A Case Study appeared first on Smashing Magazine.

Tim Millwood: Workflow Initiative - DrupalCon New Orleans 2016

Drupal Planet - Mon, 16/05/2016 - 09:36
Last week I presented the plan for the Drupal Workflow Initiative at DrupalCon New Orleans. Please...

CSSX

HTML.it Guide - Mon, 16/05/2016 - 09:00
CSSX è una libreria per generare e applicare stili CSS in JavaScript. Offre diverse opzioni, anche avanzate, e opera globalmente sugli stili CSS. Leggi CSSX

Deque India invites you to be part of Global Accessibility Awareness Day 2016 – May 19th 2016

W3C Community Groups - Mon, 16/05/2016 - 06:27

Dear Accessibility Evangelist,

DEQUE India invites you to the 5th Global Accessibility Awareness Day (GAAD) on May 19, 2016. Please join us to spread the awareness about digital accessibility and be part of creating an inclusive and accessible world for everyone. Looking forward to meet you.

Venue: T-HUB CATALYST BUILDING, IIIT-H Campus, Gachibowli
Time: May 19th 2016, 2:30 PM to 6:30 PM
Agenda: Accessibility trends, WCAG Overview, A11Y testing with aXe, Intro to mobile A11Y, IAAP certification

Its a free event and registration URL is http://gaad.dequeindia.com/ 
Please do let me know in case of any questions.

Thanks & Regards
Sujasree Kurapati
Managing Director
Deque INDIA
91-9908210133

Darryl Norris's Blog: Get Your Libraries And Breakpoint Information From The UI

Drupal Planet - Sun, 15/05/2016 - 18:31

Have you ever try to get data from your libraries and/or breakpoints in Drupal 8 ? Drupal 8 core does not provide a UI for this information.  And sometimes is nice to have the ability to know your data from the UI. Instead of trying to hunt down all that information by searching many files. For this reason, I decide to write few modules that will allow you to get some of the libraries and breakpoint information from the UI. 

Libraries UI

  • Project Page: https://www.drupal.org/project/libraries_ui
  • Module Description: This module will provide a UI to display all libraries provide by modules and themes. Once libraries_ui is been installed visit /admin/config/media/libraries_ui to get all breakpoints information.

Breakpoints UI

  • Project Page: https://www.drupal.org/project/breakpoints_ui
  • Module Description: This module will provide a UI to display all breakpoints provide by modules and themes. Once breakpoints_ui is been installed visit /admin/config/media/breakpoints_ui to get all
More

Attiks: Dream fields for Drupal 8

Drupal Planet - Sun, 15/05/2016 - 16:13

I went to Drupalcon NOLA and was looking for a new way to contribute, since there've been a lot of discussion about the front-end part, and after reading @dries blog post Turning Drupal outside-in I started looking at the field UI. I stumbled upon the core issue titled The options under the Add field drop-down describe the data you want to store, but the user was imagining the widget it would produce and decided that the outside-in approach might be a good approach.

By Peter Droogmans

Joachim's blog: What goes on in Drupal Code Builder?

Drupal Planet - Sun, 15/05/2016 - 14:13

Drupal Code Builder library is the new library which powers Module Builder. I recently split Module Builder up, so Drupal Code Builder (DCB) is the engine for generating Drupal code, while what remains in the Module Builder module is just the UI.

DCB is an extensible framework, so if you wanted to have DCB create scaffold code for a particular Drupal component or system, you can.

DCB's API is documented in the README. It's based on the idea of tasks: for example, list the hooks and plugin types that DCB has parsed from the site code, analyze the site code to update that list, or generate code for a module. There are Task classes, and you call public methods on these to do something.

The generators

Broadly, there are three things you want to do with DCB: collect and analyze data about a Drupal codebase to learn about hooks and plugin types, report on that data, and actually generate some code.

The Generate task class is where the work of creating code begins. The other task classes are all pretty simple, or at least self-contained, but the Generate task is accompanied by a large number of classes in the DrupalCodeBuilder\Generate namespace. You can see from the file names that these represent all the different components that make up generated code.

Furthermore, as well as all inheriting from BaseGenerator, there are hierarchies which can probably be deduced from the names alone, where more specialized generators inherit from generic ones. For example, we have:

  • File
    • PHPFile
    • ModuleCodeFile
    • PHPClassFile
      • Plugin
      • Service
    • API (this one's for your mymodule.api.php file)
    • YMLFile
    • Readme

and also:

  • PHPFunction
    • HookImplementation
    • HookMenu
    • HookPermission

However, these hierarchies are only about code re-use. In terms of PHP code, HookImplementation is only related to ModuleCodeFile by the common BaseGenerator base class. As the process of code generation takes place, there will be a tree of components that represents components containing each other, but it's important to remember that class inheritance doesn't come into it.

Also, while the generators in the hierarchies above clearly represent some tangible part of the code we're going to generate, some are more abstract, such as Module and Hooks. These aren't abstract in the OO sense, as they will get instantiated, but I think of them as abstract in the sense that they're not concrete and are responsible for code across different files. (Suggestions for a better word to describe them please!)

The process of generating code starts with a call to the Generate task's generateComponent() method. The host UI application (such as Module Builder module, or the Drush command) passes it an array of data that looks something like this:

[ 'base' => 'module', 'root_name' => 'mymodule, 'readable_name' => 'My module', 'hooks' => [ 'form_alter' => TRUE, 'install' => TRUE, ], 'plugins => [ 0 => [ 'plugin_type' => 'block', 'plugin_name' => 'my_plugin', 'injected_services' => [ 'current_user', ], ], ], 'settings_form' => TRUE, 'readme' => TRUE, ]

(How you get the specification for this array as a list of properties and their expected format is a detailed topic of its own, which will be covered later. For now, we're jumping in at the point where code is generated.)

Assembling components

The first job for the Generate task class is to turn this array of data into a list of generator classes for the necessary components.

This list is built up in a cascade, where each component gets to request further components, and those get to request components too, and so on, until we reach components that don't request anything. We start with the root component that was initially requested, Module, let that request components, and then repeat the process.

This is best illustrated with the AdminSettingsForm generator. This implements the requiredComponents() method to request:

  • a permission
  • a router item (on Drupal 7 that's a menu item, but in DCB we refer to these a router item whatever the core Drupal version)
  • a form

In turn, the Permission generator requests a permissions YAML file. You'll see that there are two Permission generators, each with a version suffix. The Permission7 generator requests a hook_permission() hook, which in turn requests a .module file. The Permission8 generator is somewhat simpler, and just requests a YMLFile component.

Meanwhile, the router item requests a routing.yml file on D8, and a hook_menu() on D7.

These two parts of the cascade end when we reach the various file generators: ModuleCodeFile and YMLFile don't request anything. The process that gathers all these generators works iteratively: every iteration it calls requiredComponents() on all the components the previous iteration gave it, and it only stops once an iteration produces no new components. It's safe to request the same component multiple times; in the D7 version of our example, both our hook_menu() and hook_permission() will request a ModuleCodeFile component that represents the .module file. The cascade system knows to either combine these two requests into one component, or ignore the second if it's identical to what's already been requested.

We now have a list of about a dozen or so components, each of which is an instantiated Generator object. Some represent files, some represent functions, and some like Hooks represent a more vague concept of the module 'having some hooks'. There's also the Module generator which started the whole process, whose requiredComponents() did most of the work of interpreting the given array of data.

Assembling a tree of components

The second part of the process is to assemble this flat list of components into a tree. This is where the notion of which component contains others does come into play. This is a different concept from requested components: a component can request something that it won't end up containing, as we saw with the AdminSettingsForm, which requests a permission.

The Generate task calls the containingComponent() method on each component, and this is used to assemble an array of parentage data. There's nothing fancy or recursive going on here; the tree is just an array whose keys are the identifiers of components, and whose values are arrays of the child component identifiers.

This tree now represents a structure of components where child items will produce code to be included in their parents. One part of this structure could be represented like this:

  • module
    • routing.yml
    • router item
    • permission.yml
    • permission
    • .install
    • hook_install()

Some components, such as the Hooks component, are no longer around now: their job was to be a sort of broker for other components in the requesting phase, and they're no longer involved. The root component, Module, is the root of the tree. All the files we'll be outputting are its immediate children. (This is not a file hierarchy, folders are not represented here.)

Assembling file contents

We now have everything we need to start actually generating some code. This is done in a way that's very similar to Drupal's Render API: we recurse into the tree, asking each component to return some content both from itself and its children.

So for example, the router items contribute some lines to the routing.yml file, which then turns them into YAML. The .install component, which is an instance of ModuleCodeFile, produces a @file docblock, and then gets the docblock, function declaration, and function body from the hook_install component, and glues them all together.

Finally, each file component (the immediate children of the module component in the tree) gets to say what its file name and path should be.

So the Generate task has an array of data about files, where each item has a file name, file path, and file contents. This is returned to the caller to be output to the user, or written to the filesystem. Module Builder presents the files in a form, and allows the files to be written. The Drush command outputs them to terminal and optionally writes them too.

Extending it with new components

The best way to add new things for DCB to generate is to inherit from existing basic classes. If these don’t provide the flexibility, there’s always a case to be made to give them more configurable options: for example, the AdminSettingsForm class inherits from Form, but neither of those do very little for the actual generated form class, as the work for that is mostly done by the PHPClass class.

The roadmap for DCB at the moment consists of the following:

  • Generalize the injected services functionality that’s already in Plugins, so generated Form classes and Services can have them too.
  • Add Forms as a basic component that you can request to generate. (It’s currently there only as a base for the AdminSettingsForm generator.)

And as ever, keep adding tests, keep refactoring and improving the code. But I'm always interested in hearing new ideas (or you know, better yet, patches) in the issue queue.

Blue Drop Shop: Drupal Camp Session Recordings: A Year in Review

Drupal Planet - Sat, 14/05/2016 - 16:46
 @czaroxiejka

It has been nearly a year since I’ve updated the status of my camp recording kits. Since DCSTL15, two other camps took me up on my proposal to sponsor my travel and hotel in exchange for me recording and posting their sessions: TCDrupal and BADCamp. And, of course, as a MidCamp organizer, that counts too. And with each those camps, I’ve iterated and learned from invaluable successes and failures.

First off, here is a link to the current kit.

With everything, each kit is still under $450. In addition, zip ties to hold the VGA to HDMI dongle tight and some gaffers tape to secure everything to the podium are needed.

Recap

At Twin Cities, I learned that, while I try, I cannot reasonably start and stop every recording in every room, especially at camps with five concurrent sessions spread over multiple floors and buildings. The amount of volunteer participation at TCDrupal is incredibly impressive. I had loads of help at my disposal, but only a few moments to outline how the kits work, so I spent a lot of time troubleshooting from room to room.

BADCamp is another camp that sprawls over a campus and is a bit looser on the room monitor support. So this time, I came armed with printed instructions at each podium for hooking up to the kit (link). I added some basic troubleshooting and my phone number. I missed about half the session starts, but speakers were mostly able to follow the instructions and run things without me. That was a huge win. Unfortunately, remembering to also start/stop the audio record was hit or miss.

By the time MidCamp rolled around, I simplified the instructions further and also set the backup audio record to just run all day, removing the failure point of missed audio. The big red button is easy and enticing. The little button on the audio recorder remote...not so much. MidCamp, with two days of four concurrent sessions was my first 100% captured camp since St. Louis.

Pain Points

There are four recurring issues with this setup:

  • VGA-only laptops
  • Recurring audio problems
  • File segmenting
  • Random projector problems

Hopefully, the time of laptops that only have VGA out is coming to an end. I've tried several different VGA-to-HDMI converters with basically no luck. And to spend hundreds of dollars or more for a fool-proof converter when modern laptops have better video output is a hard pill to swallow. I don't foresee this being a long-term problem.

The audio issues are baffling. In some cases, no audio at all is recorded with the screen capture, while other times it is sped up and choppy, hence the importance of the backup audio files from the voice recorder. But this means post-processing time which delays uploads. I intend to contact Hauppauge support, but honestly don't expect to get very far as I am using their device as it was not intended. Lastly, the capture device has a touch panel for adjusting gain and muting the audio. It is a little to easy to accidentally mute the audio.

Minor annoyance: occasionally, the recordings will split into two or more files, meaning I have to stitch them together in post.

At MidCamp for the past two years (both held at different locations on UIC campus), some of the projectors would intermittently go dark during presentations. While this has no impact on the recording, it is extremely unsettling for the presenter and annoying for the attendees. I recall this happening in some cases at Twin Cities, but not at BADCamp. So this one currently has me stumped with no good plan of resolution at this time.

Next Steps

For obvious reasons, I can't record all the sessions at all the camps. And already I have firm plans to record Twin Cities in June, St. Louis in September, and BADCamp in October. Talking to folks at Drupalcon, I also now have soft commitments with Drupal GovCon in July and Drupal Camp New Jersey in January. And other camps have reached out, but I have conflicts.

I managed to pack up a complete kit into a 10" Pelican case. This means that if I can start training some proxies and write up some detailed instructions and troubleshooting, then this solution can scale. Maybe folks won’t have experience with the post-production, but I can help with that remotely, if needed. The beauty of these kits is that with timely starts and stops and good audio, the MP4 file on the thumb drive can be uploaded as soon as it is collected.

The good news is that the more camps I can record, the more data I can collect and the more I can refine the process to make it scalable.

Stay tuned!

Tags:

Collective #219

Codrops - Sat, 14/05/2016 - 14:54
Collective219_WOTW_Stinkdigital

Inspirational Website of the Week: Stinkdigital

Subtleness, smoothness and the right focus on content make Stinkdigital a pleasure to browse. Our pick this week.

Get inspired
Collective219_FullStory

This content is sponsored via Syndicate Ads FullStory – Settle all bets about your customer experience

Capture everything, and we mean everything, about your customer experience with one, easy-to-install script.

Try it free
Collective219_SmallVictories

Small Victories

Small Victories takes files in a Dropbox folder and turns them into a website. No CMS, no installation, no server, no coding required.

Check it out
Collective219_fluidtypography

Truly Fluid Typography With vh And vw Units

Michael Riethmuller presents an ingenious technique for creating smoothly resizing web typography.

Read it
Collective219_nevershowadesign

Never Show A Design You Haven’t Tested On Users

Learn why user testing is absolutely essential for your work in this great article by Ida Aalen.

Read it
Collective219_OverlapUIKit

Overlap UI Kit (PSD, AI)

A beautifully designed UI kit designed by Vlad Cristea in vector format.

Check it out
Collective219_spaceiconset

Space Icon Set (40 Icons, AI, PNG, SVG)

An adorable space icon set by Iconshock for Smashing Magazine.

Get it
Collective219_StructuredTextTools

Structured Text Tools

A useful list of command line tools for manipulating structured text data. Created by Danyil Bohdan.

Check it out
Collective219_animatedtransitioneffects

Animated Transition Effects

A great library of animated transition effects, powered by CSS Animations. By Sebastiano Guerriero from CodyHouse.

Check it out
Collective219_NNJS

Neural Networks in JavaScript

A brilliant introduction to Neural Networks in JavaScript by Tine from webkid.io.

Check it out
Collective219_webmaster

I’m a fucking webmaster

Justin Jackson reminds of a time where websites were made using a text editor by the Web’s true pioneers.

Read it
Collective219_MaterialMotion

Material motion

Learn the principles of good transitions and motion in the context of Google Material Design.

Check it out
Collective219_DL

DistributedLog

DistributedLog (DL) by Twitter is a high-performance, replicated log service, offering durability, replication and strong consistency as essentials for building reliable distributed systems.

Check it out
Collective219_Aquino

Free Font: Aquino

A lovely soft and bold font designed by Philip Trautmann available on Freebiesbug.

Get it
Collective219_Trends2016

Web Design Trends 2016: The Definitive Guide

A complete visual guide to web design trends in 2016 by UXPin.

Check it out
Collective219_SublimeTutor

Sublime Tutor

An interactive in-editor keyboard shortcuts tutorial for Sublime Text 3. By Jai Pandya.

Check it out
Collective219_PrimarySecondary

Primary & Secondary Action Buttons

Nick Babich dives into the topic of primary and secondary action buttons and shows some useful guidelines.

Read it
Collective219_Blisk

Blisk

Blisk is a free Chromium-based browser built to increase quality and speed of web development and testing.

Check it out
Collective219_metafors

Free Font: Metafors

A playful handwritten font designed by Markus Wolf.

Get it
Collective219_Slugbay

SlugBay (Beta)

SlugBay promises to become the biggest open platform of resources for developers.

Request an invite
Collective219_Bitkeeper

BitKeeper

BitKeeper is the original distributed source management system. Now available as Open Source under the Apache 2.0 License. Optimal for very large projects.

Check it out

Collective #219 was written by Pedro Botelho and published on Codrops.

Drupal Association News: Hello, World! (Goodbye, Drupal Association)

Drupal Planet - Sat, 14/05/2016 - 13:06

My first day on the job, I got on an airplane and flew to Australia to attend DrupalCon Sydney. As first days on the job go, that’s gotta be up there as one of the best. It definitely set the tone for life in the Drupal community - it’s been an exciting adventure every single day. I’ve traveled around the world, worked with incredibly smart people, and learned four or five Git commands (thanks Cathy!).

So it’s not without some sadness that I share that my last day on this job will be June 3. Why am I leaving? Simply put, because I can. Drupal 8 is out and thriving. The Association is doing more and doing it better than it ever has. Now is the time for me to take a step back, eat some cake, and then find something new to jump into (after a nap, and probably some more cake).

Luckily, the Drupal community has an amazing individual ready to step in to lead the Association. I’m proud beyond words to see Megan Sanicki take on these challenges and work with you all as the next Executive Director of the Association. I know she will continue to build an Association that operates from its values for and with the Drupal community. We’ve been working together on this transition for a little while now, and I can’t wait to see what she does.

I just want to share a couple of thanks before I go. First, I’m deeply proud of the team that we have built at the Drupal Association. The Drupal Association staff are the rainbow unicorns of teams. They are honest about their opinions, but kind in their delivery. They are fierce in their loyalty to the community, and even more so in their loyalty to each other. They genuinely care about every interaction, and even when things go sideways, you can trust that their intentions were nothing but good. I learned from them. Every. Single. Day. I owe them a heck of a lot more than this thank you, but I wanted to get it out in the world. They are the best. Treat them well.

Secondly, I want to thank the dozens of community members who have gone out of their way to support me in this role. I’ll be following up personally with as many of you as I can, but I wanted to call out a few of you in particular. Angie taught me that introverts can learn to like hugs. George and Tiffany taught me to take my time and find the exact right words. Paul taught me that you can’t have too many passion projects. Donna taught me that it’s not summer everywhere. Cathy taught me Git (well, four or five commands that I can remember). There is so much generosity in Drupal.

The Association board and Megan will be working hard over the next few weeks on this transition to make sure that we continue to grow our support of the community, keep producing amazing DrupalCons, and ensure that Drupal remains the best darn CMS out there. I’ll be over here rooting for all of you. You’ll find me next to the cake.

Radium on Drupal: Deploying Drupal Sites with Docker Compose

Drupal Planet - Sat, 14/05/2016 - 11:51
Deploying a Drupal site (or any website) could sometimes be cumbersome, in particular if you have multiple websites running on one server. The amount of time wasted in configuring the server could be considerable. Docker is one of the tools that can save us from the "configuration hell". Thanks to pre-built images, I no longer have to worry about dependencies since they can be all included in one image. Also, unlike virtual machine, Docker is fast and take only a few seconds to start. Another benefit is that now you can have the same environment on your local machine and on the server -- just use the same image. In this post I will quickly walk through the steps of using Docker Compose to deploy Drupal.

Guida Vagrant

HTML.it Guide - Sat, 14/05/2016 - 10:00
Vagrant dovrebbe essere sempre presente in un gruppo che mira ad abbracciare DevOps: si pone come un livello intermedio tra il computer fisico su cui è in esecuzione ed uno o più ambienti...
Syndicate content