Drupal Feeds

The extraordinary scale of the WannaCry ransomware infection has acted as a dramatic warning to organisations in all sectors. With thousands of organisations worldwide – including a significant proportion of the NHS – falling victim to the ransomware, it’s a timely reminder of the importance of robust cybersecurity.

 

Your organisation’s website is potentially one of the biggest parts of your overall ‘attack surface’, which cybercriminals will probe for a route into your network. As such, it is vital to implement solid tools and processes specifically designed to protect it against attack – and those tools and processes should be tailored to the content management system underpinning your site.

So, if your site is built on Drupal, what are the best practices you should be following?

1. Upgrade to the latest version of Drupal

The WannaCry attack has proliferated so dramatically because it relies on an exploit in an old version of Windows – one that Microsoft is no longer supporting. It is usual commercial practice for vendors and manufacturers to gradually withdraw support from older hardware and software – this is the case with Drupal, as with Microsoft. If you have not yet migrated to the latest version – Drupal 8 – that should be your first priority.

 

2. Upgrade to the latest version of modules

Drupal is a modular CMS, with thousands of options available to extend your basic system. As such, it is not enough to simply ensure you’re running the latest, best-protected version of Drupal – you need to make sure you’re doing the same with each individual module. The author of each extension is responsible for providing appropriate security upgrades and patches, but these will generally only apply to the latest version of the module. If you’re running an old one, you’re not protected.

 

3. Remove unnecessary modules

By the same token, running modules on your site that you no longer need is simply increasing your potential attack surface – and your security management burden. Implement a process to ensure that you are continually reviewing all of the modules you have added, and get rid of the surplus.

 

4. Use the Status Report tool

The Status Report functions sits within your Drupal Admin area. Its job is to alert you to any issues with the code base underpinning your site – which includes out of date modules and code. It is the easiest way to keep on top of your website management and ensure that you are deploying the latest versions of everything. Don’t forget to enable your core update manager module so that you get regular notifications.

 

5. Practice strong user management

As the old saying goes, people are the weakest link in any security chain. Keeping a tight handle on the people who actually use your website can dramatically shore up your overall security posture. Undertake a regular check to ensure that you are removing inactive users such as those who have left the organisation, and ensure that those who remain only have access to the minimum areas of the site they need to, not the whole site by default.

Various functions are available within Drupal to shore up login and user processes, such as the Login Security module, which restricts unauthorised access attempts, and blocking the ‘user #1’ account that is created during setup, which automatically has all permissions in place.

 

6. Monitor your logs

Drupal’s integrated log viewer, within the reports area, is an extremely valuable tool when it comes to ascertaining that a cyberattack is taking place and assessing what has actually happened. Make sure you check your log reports regularly, and are alert to early warning signs such as failed login attempts.

 

7. Enable HTTPS

HTTPS is most commonly used for ecommerce sites and online banking, but any site that transfers sensitive information between user and web server should also be using it.

These seven best practices will have a dramatic effect on the overall security of your Drupal website, and ensure you can continue benefitting from the flexibility of the platform without sacrificing protection.

 
Setting up Nginx on a Debian server as front-end for Apache

Welcome to the next installment of the series of articles for Drupal sysadmins. Today, you are going to learn the process and nuances of setting up Nginx so it works as Apache’s front-end on a Debian server.

In the previous article, we covered setup of a web server on a Debian machine and Drupal installation. The solution offered there has a couple of drawbacks:

admin Tue, 06/13/2017 - 11:08 Теги

Drupal 8 adoption has been very slow, and many people have been putting it off. Some even gave up on Drupal because of D8's (perceived) complexity, focussing their career or hobby on easier CMS software. The past 3 months I've been fully engaged in embracing Drupal 8 and moving my premium Drupal themes along with the supporting ecosystem of modules, installation profiles, and infrastructure to Drupal 8! Going forward we will develop and maintain our products on both Drupal 7 and Drupal 8. 

It's been an interesting but also difficult journey and I'm writing to tell other Drupal professionals (and hobbyists) about my experience. I divided this long read into several chapters so you can skip to whichever topics you care about most. If this topic is important to you, please do comment and share your thoughts and experience!

Theming: Easier and Better But Completely New

Drupal 8 uses a new templating system for theming called Twig. While skeptical at first about having to learn a new language, I've grown to like Twig a lot... but to be very frank I would have been totally OK with keeping PHPTemplate in Drupal 8. It's what I've been using for 10 years and it's what I know. My Drupal 7 theme is full of preprocessing, custom features, and integrations with certain modules, and it's all coded in PHP. The transition to Twig means there is a huge amount of work for me to not just convert templates but also re-architect all the logic and features in the theme. I'll say that Twig works great and has a bright future but I'll also say that I can empathize with all the Drupal themers who are unhappy about having to learn a whole new way of working.

Theme Settings

If you develop base themes or premium themes like I do I have some good news as well: Theme Settings are largely implemented the same way. For me this means that many hundreds of lines of FAPI code for the 200+ theme settings in my flagship Glazed Theme can be copied and pasted into the Drupal 8 codebase and 80% of the form generating code just works. Of course the code that reads the theme settings still has to be ported from PHPTemplate, preprocessing and custom PHP to use Twig and Drupal 8's APIs. 

Logic Inside Twig Templates

The most confusing thing when starting out with Twig was that all logic for printing classes happens right inside the Twig template. For years I've been telling people to use preprocess functions for any logic, whether it be if/else or some code to retrieve a field value. In Twig any logic related to printing template code (that includes classes and other attributes) goes right into the twig template. I'm not yet entirely happy about have a lot of logic in my template files. Then again I can also imagine that to the unitiated the Drupal 7 architecture with classes being added in preprocess, or process functions that can be in multiple locations could be even more confusing.

To show you what I mean here is an excerpt of my html.html.twig template:

{% set html_classes = [ theme.settings.sticky_footer and not theme.settings.boxed_layout ? 'html--glazed-sticky-footer', ] %} {% set body_classes = [ 'html', logged_in ? 'user-logged-in', not root_path ? 'path-frontpage' : 'path-' ~ root_path|clean_class, node_type ? 'page-node-type-' ~ node_type|clean_class, db_offline ? 'db-offline', theme.settings.navbar_position ? 'navbar-is-' ~ theme.settings.navbar_position, theme.has_glyphicons ? 'has-glyphicons', theme.settings.header_position ? 'body--glazed-header-side' : 'body--glazed-header-top', not theme.settings.header_position and not theme.settings.header_style == 'overlay' ? 'body--glazed-header-not-overlay', not theme.settings.header_position and not theme.settings.header_style == 'overlay' ? 'body--glazed-header-' ~ theme.settings.header_style, not theme.settings.header_position and not theme.settings.header_top_sticky and theme.settings.header_top_fixed ? 'body--glazed-header-fixed', ] %} <!DOCTYPE html> <html {{ html_attributes.addClass(html_classes) }}>   <head>     <head-placeholder token="{{ placeholder_token|raw }}">     <title>{{ head_title|safe_join(' | ') }}</title>     <css-placeholder token="{{ placeholder_token|raw }}">     <js-placeholder token="{{ placeholder_token|raw }}">   </head>   <body{{ attributes.addClass(body_classes) }}>{{>

Some templates, like my menu--main.html.twig template that is responsible for rendering dropdown menus contain more advanced logic, including a powerful Twig tool called a  macro. The ratio of markup to logic is so low in this template that it kind of seems to defeat the purpose of having a templating system. Then again, if I look at the equivalent of PHP code I've had to write in its D7 counterpart it's equally cumbersome.  

Despite my reservations about twig, looking back at the work I've done so far in porting my theme to Drupal 8 (it's about 75% done) I'm creating a more maintainable, better product. And that's what Drupal 8 is all about. There's some pain in migrating all your work but in return you get what I believe is a more solid and maintainable theme.

Site Building: Pretty much the same

For a CMS that was basically built differently from the ground up, the authoring and site building experience is surprisingly similar to Drupal 7. You're still going through the same steps and forms to create content types, taxonomies, views, nodes etc. This is because the idea of Drupal as a flexible and powerful CMS has remained the same. For Drupal 7 users who didn't do much coding before, not much will change when upgrading to Drupal 8. Without investing at all in learning new things you can hit the ground running and install a nice Drupal 8 theme or distribution and it's business as usual.

Module Development: Definitely harder

Building Drupal 8 modules is not rocket science. It's just that there is a lot to learn before you're fluent at it. New APIs, more complicated object oriented architecture, services and plugins. The learning curve is steeper and higher than ever. However, if you start small, read the docs, and copy code from the examples module it's doable. The learning process very much reminds me of my first experience building my very first Drupal (5.x) module.

This is why I decided that building our most complex Drupal 8 modules should be handled by experienced Drupal 8 experts and not me. While I started upgrading some tiny modules as well as our theme I contracted Ivan (Chi on d.o.) and Jay Friendly (Jaypan on d.o.) to build the SooperThemes Portfolio and Glazed Drag and Drop Builder modules... completely written from the ground up for Drupal 8's architecture. Without their help there's no way I would have upgraded these modules myself without first spending at least 2 months learning Object Oriented Programming and the inner workings of Drupal 8. If anyone is looking to consult about Drupal 8 upgrade work I can highly recommend both Ivan and Jay. Jay is currently writing a book on Drupal 8 development that is targeted at Drupal 7 veterans as well as completely new users.

Development has been in full swing for the past 2-3 months and it has been the most intense and sometimes stressful time in my years building SooperThemes products. All of our products are now almost finished but still being tested and refined. It has been a great learning experience but also a great lesson in technical debt and the reality of Drupal 8's complex architecture. For me personally with my background in theming, design, and marketing I feel intimidated by the complexity introduced by Drupal 8. Conversely I feel that my customers will have more easy to use, solid, reliable and performant website thanks to Drupal 8. Luckily for many of my customers the whole point of my products is that you can build and customize everything without coding, using our Drag and Drop tools and extensive theme settings. 

Plugins, Services, Controllers, and Schema Metadata

That is a list of some of the software architecture concepts I've had to get acquinted with in the short time of 2 months. I can't say that I've learned these concepts just yet. In Drupal 7 understanding the hook system and Forms API could really get you a long way building even very large Drupal websites. In Drupal 8 not so much.

Before I started feeling like I'm on a learning curve, I ran into a wall. Drupal 8 really demands you delve deeper into software architecture than before. It's hard but the beauty of the new system is that as you're learning Drupal you're also learning Symphony and proper Object Oriented Programming design patterns. Those who can make the neccesary investment of time and energy will come out of it with skills that are valuable beyond the Drupal ecosystem.

Installation Profiles: Similar But Better

Installation profiles are a critically important part of our business at SooperThemes. We don't just sell themes, we develop, support, and maintain all the Drupal code that brings our designs to life. For our customers this means they can download a turn-key installation profile that contains their selection of designs, features, and demo content.

For us this means we maintain a ton of configuration, demo content, and modules, and wrap it all into installation profiles. We even provide an interface to generate customized installation profiles and install them on your hosting fully automatically. My experience so far with Drupal 8 installation profiles has been great. 

Demo Content

A notable improvement is the great support for demo content in Drupal 8 with help of the Default Content module. In Drupal 7 the go-to module was UUID Features. Over the past years I've spent many hours fixing bugs, implementing file support, and patching up poor support for referenced entities and menu links in Drupal 7's UUID Features code. 

The Drupal 8 Default Content module is still in alpha and if you're doing a lot of default content work you still might need to hit the issue queue and download (or contribute) a little patch but this module already feels more stable than the UUID Features suite. D8 and Default Content also import content faster, allowing even the lowest of low-end hosting to install our bulkier demo installation profiles.

Configuration 

I've read that Features is still a thing in Drupal 8 but I've not yet found the need to try it out. Whereas previously we used Features to package all our CMS components into modules this is now done with Drupal core's configuration system. It's working well so far. Automatic exporting of configuration and dependencies into modules is done using drush, and we can now split optional and required configuration which is also great for components that include lots of views that add value but are not indispensable. I did experience some quirks with optional configuration not being installed during the profile's installation process even while dependencies were certainly met.  

Media: Work In Progress

It took many years for the Media module to have a stable (2.x) release in Drupal 7. Drupal 7 Media works great and  it handles drop-in file uploads, multi-file uploads and various media gallery browsing features excellently. In Drupal 8 great work is being done to bring Media features into core. I'm a big fan of the initiative but I'm also concerned about how to provide provide future proof media featurs in my installation profile right now. 

Drupal 8 Entity Browser

At the moment of writing this, the successor of the Media module is Entity Browser. The module File Entity Browser (it builds on top of Entity Browser module) will give you a media library popup browser similar to the D7 media module's browser. Installing this module requires 5 modules (dropzonejs, embed, entity_browser, entity_embed, and file_browser) and 3 external libraries: dropzoneimagesloaded, and masonry. Part of the Drupal 8 media initiative is to include features similar to what the File Browser module provides in core, but in a cleaner architecture with fewer dependencies.

A module similar to File Entity Browser is Media Entity Browser and the major difference is that it uses the more flexible Media entity as opposed to the file entity. What exactly this means and how all this will be upgraded to the new Drupal 8.4 core features, I'm not sure. Therefore I decided to launch my distribution and products without image re-usability on Drupal 8.3. To protect my customers against potentially needing complex upgrade processes I'll hold off on advanced Media management until Drupal 8.4 comes out. It's planned to come out late this summer and I'm looking forward to it. 

Improvements In Documentation

This is not really a Drupal 8 improvement as much as it is a Drupal.org improvement. The quality of documentation available to day is so much better than on the day Drupal 7 came out. The new documentation page design immediately gives more credibility to the content and the content is carefully curated and better written. Even though this is not really a feature of Drupal 8 it certainly is a great benefit to those starting to learn Drupal 8 today. 

I also want to give a shout out to Drupalize.me, who are giving away free subscriptions for their premium training videos to people who have contributed on Drupal.org. Terms and details.

My Prediction: Drupal 8.4 Will Bring Up The Numbers

I see Media features as the #1 core advantage of WordPress over Drupal. Other major weaknesses of Drupal are a leaner offering of themes and niche-specific tools like portfolio plugins, drag and drop building options, and other fancy add-ons. But those can be fixed by contrib projects and through premium themes. Media is a challenge that took too long to get right in Drupal 7. It was only several months ago the Drupal 7 Media module had it's first truly stable Drupal 7 release. Thanks to this development, we can now expect to see more niche-specific add-ons for the Media module as there is a stable API to build on top on. Next week I will blog about the release of such an add-on module that SooperThemes has co-sponsored and co-developed. 

If the Drupal 8 Media Initiative is executed according to plan Drupal 8.4 will bring features to that will appeal strongly to the masses of Drupal site builders who are unable or unwilling to create custom configurations for Entity Browser. Drupal 8's more rapid emergence of a stable Media API can awaken growth of Media contrib modules that make the lives of content creators and site builder easier.

SooperThemes Drupal 8: Upgrade Status

To those who are waiting: Please be patient as we're finishing up and fine-tuning. I meant to release a public beta of some products this week but I decided it's better to focus on finishing the components that are currently <90% done. I'll re-evaluate the possibility of public beta testing  next week, and the week thereafter.

SooperThemes Products Drupal  8 Upgrade Progress  %_of_total** Glazed Theme 75% Complete 25% Glazed Drag and Drop Builder 95% Complete 25% Sooperthemes Portfolio (replacement of D7 glazed_portfolio) 90% Complete (only missing hover effect designs) 15% Glazed GridStack 95% Complete  5% Glazed Helper 75% Complete (only missing Page Design tools) 7.5% Glazed Drupal CMS Distribution (drupal.org/project/cms) 95% Complete (finetuning, future-proofing) 10% Demo Content and Installation Profiles 0/15 Completed (pending completion of above) 5% Product infrastructure* 50% Complete 7.5%

* demo sites, trysooperthemes.com, automatic installation profile testing and provisioning, support forum, etc. The kind of stuff you don't think about before starting a big Drupal 8 upgrade project.

** Estimated proportion to the total amount of work of all items in the table

Start:  2017-06-15 (All day) - 2017-06-18 (All day) America/Toronto Organizers:  xjm Event type:  Sprint

DrupalCamp Montréal is coming up this Thursday to Sunday (June 15th to 18th), with great trainings, two days of sessions, and a dedicated sprint day on Sunday. The sprint gives you a great opportunity to get involved and make a difference for the things that affect Drupal and your projects. You don't need to be an expert, developer, or existing contributor to get involved. Here are three current focus areas that we'll collaborate on on this week!

Major issue triage

Major issue triage sprints have been held at many DrupalCons and camps recently and Montréal will continue these efforts. We want to fix the most important bugs in Drupal, but the first step to that is making sure bug reports are up to date and actionable. That is where major issue triage helps: identifying reports that should be critical, closing ones that are no longer relevant, downgrading ones that are actually less severe, and making sure relevant reports can move forward to a fix. Sometimes just asking questions for clarification on bug reports will move things ahead a lot. Still not convinced this sprint is for you? Read more in my blog post from earlier this year.

Make upgrade paths easier with @deprecated documentation

We made several changes in the release process with Drupal 8 to make Drupal upgrades easy forever. One of them is that we improve Drupal's APIs in scheduled six-month minor releases, but also leave the old ways of doing things in place and mark them as deprecated until Drupal 9. This huge shift for Drupal allows module maintainers to adapt to changes gradually, on their own schedule, instead of needing a massive push all at once on some later release date.

API deprecations are documented in change records on Drupal.org, and also marked directly in the code documentation. We started marking deprecated code almost two years ago as we were preparing to release Drupal 8.0.0, and we have been creating change record documentation since the release of Drupal 7. Unfortunately, we did not start to connect the two until recently, so it was not possible to read more about a certain change when you encountered a deprecated API. Help make these connections for an easier upgrade path for everyone.

Clearly define Drupal's public APIs

As we mentioned above, Drupal 8 has 6-month minor releases that improve APIs (as well as adding new features). In order to make this safe, clear, and maintainable, we defined what parts of Drupal's APIs are internal through a documented policy, but that is not very explicit for developers. Making this explicit in code documentation is more effective for anyone reading the code or developing with an IDE. By helping with this effort, you can learn a lot about Drupal 8 APIs and help with the upgrade path through documenting a better-defined API surface.

Also, help me help sprinters!

I'll be in the Montréal sprint room all four days of the camp to work with potential contributors and show them how to help with these tasks, but I could use some help myself. If you have experience with Drupal 8 (even a little) or have past experience sprinting on major triage or mentoring at Drupal events, please ping me. Helping others is an especially important way to contribute back. On that note, many thanks to camp organizers for making these sprints possible.

À jeudi! See you at the camp!

Thanks to Gábor Hojtsy for help with this post.

GSoC17 : Client Side File Crypto : Week 2

This blog post summarizes the second week of coding with Drupal in Google Summer of Code 2017 

tameeshb Tue, 06/13/2017 - 23:20 Tags GSoC Google Summer of Code 2017 Drupal Drupal Blog

One of the questions we get most often is, "How do I prepare for the Acquia Certified Developer - D8 Exam?" Now we've got an answer: the Drupal 8 Developer Immersion Course w/ Certification Prep - an 8-week, instructor-led, project-based online course that covers all areas of Drupal 8 and prepares you to take the Acquia Certified Developer - D8 Exam.

Tags: acquia drupal planet

Computers are finicky. As stable and reliable as we would like to believe they have become, the average server can cease to function for hundreds of different reasons. Some of the common problems that cause websites or services to crash can’t really be avoided. If you suddenly find your site suffering from a DDOS attack or a hardware failure, all you can do is react to the situation.
 
But there are many simple things that are totally preventable that can be addressed proactively to ensure optimal uptime. To keep an eye on the more preventable issues, setting up monitoring for your entire stack (both the server as well as the individual applications) is helpful. At Zivtech, we use a tool called Sensu to monitor potential issues on everything we host and run.
 
Sensu is a Ruby project that operates by running small scripts to determine the health of a particular application or server metric. The core project contains a number of such scripts called “checks.” It’s also very easy to write custom checks and they can be written in any language, thus allowing developers to easily monitor new services or applications. Sensu can also be run via a client server model and issue alerts to members of the team when things aren’t behaving properly.

Server checks

As a general place to start, you should set up basic health checks for the server itself. The following list gives you a good set of metrics to keep an eye on and why it is in your best interest to do so.

RAM What to check

Monitor the RAM usage of the server versus the total amount of RAM on the server.

Potential problem monitored

Running out of RAM indicates that the server is under severe load and application performance will almost certainly be noticeable to end users.

Read more
Migrating SQL in Drupal 8 with Migrate Tools and Migrate Plus christophe Tue, 13/06/2017 - 22:21 Migrate API is awesome, and if you plan some custom migration, a few contributed modules does the heavy lifting for you. This article should be regarded as a list of steps to follow to achieve a simple migration from another SQL data source than Drupal. So we will not go in deep into the explanations of the Migrate theory, for this subject, refer to the documentation of the Migrate API. Also, we will finish with some debugging techniques and a first shot of a bash script for rerolling a migration from scratch in case of configuration change.
GSoC 2017 | Week 2: Port Vote Up/Down sudhanshu Wed, 06/14/2017 - 10:18
Last time, we gathered together DrupalCon Baltimore sessions about Site Building. Before that, we explored the area of Drupal Showcase, Coding and Development, Project Management and Case Studies. And that was not our last stop. This time, we looked at sessions that were presented in the area of Front End. Atomic Design in Drupal 8: Isolating frontend workflow with Pattern Lab! by Anthony Simone from Elevated Third This session reviewed the basic principles of Pattern Lab and atomic design but focused on the practical implementation of Pattern Lab in the next Drupal project.   Back… READ MORE
Kiev Drupal Camp 2017: The First Impression root Wed, 06/14/2017 - 16:35

I took part in Kiev Drupal Camp 2017 last weekend. It was a good decision to go to the code sprint. I'm sure that the second day of the conference was much better than the first one with formal presentations. My personal thanks to Dmitry Drozdik, Dmytro Danylevskyi and Alexander Schedrov for their help to meet OpenY.

The main issue of the first day was that presentations went in several 4-5 streams in different rooms and I missed a lot of useful information. Fortunately, Conference organizers recorded videos of all presentations.

On this Camp I had presentation: Paragraphs are more powerful than you can expect.

There was not enough time. I tried to provide the extended overview and 3 demonstrations, but overview was very short and demos weren't very attractive. There is the video above.

Also you can download PDF with slides by the link http://abzats.com/kiev17.pdf

Planet Drupal LandingPage Drupal 8
What is Elevated Third, Denver Website Agency What is Elevated Third? Tony Dryer Wed, 06/14/2017 - 11:07

Elevated Third’s namesake is rooted in company culture. It comes from the art world and refers to the experience one has when looking at a particularly moving or captivating piece of art. When you have a “get it” moment—that flash of understanding—an elevated third experience is created between the medium and you, the viewer.

At Elevated Third, a Denver website agency focusing on Drupal, we strive to replicate this experience for our clients, our partners, and our employees.

Our Culture 

Our culture and work ethic is based on an idea that the right environment can foster incredible talent. We don’t exclusively hire people who fit a job description, instead we hire people who are smart enough to grow into their own description. We choose employees based on their aptitude to overachieve. Then, we observe. We figure out what said employee is particularly good at and we create a job description around their strengths.

This practice is easier said than done. It requires a scaffolding of actionable core values and exceptional hires who allow their peers to be vulnerable. Because, of course, learning means making mistakes.

Ultimately, it is an environment of support, vulnerability, and observation that allows us to foster talent instead of hire it based on a list of requirements and a resume. The results: employees who feel important, who produce great work, and who are happy to work hard.

On top of all the standard agency perks like snacks and foosball, our new core values are essential to establishing and maintaining our internal culture here at Elevated Third. They are the guidelines for personal success. Following them is the best way to be successful at our Denver website agency. When our employees are successful, the company will prosper. Establishing the core values in late 2016 has had a direct impact on the business success we have seen thus far in 2017.

 

  Core Values

When we first got together to determine our core values, we knew it was not going to be a simple process. We had to get it right, and we had to take the time to carefully craft each value.  

We started by listing attributes that we believe make our employees successful. Things like accountability, effectiveness, work ethic, engagement, curiosity, positive energy, empathy, confidence, and thoughtfulness to name just a small sampling. For the next few months, we boiled down our list and crafted them into similar groupings. From these groups, the five values that we have now started to make themselves clear. It was a long, sometimes tedious, yet fulfilling experience.

The Elevated Third Core Values:

  • Start with empathy. Respect and honesty come first. Care about our clients, our users and each other.
  • Lean in and keep moving. Stay engaged, positive and persistent. Bring energy and never quit.
  • Make an impact. Seek out and solve the right problems. Be fearless! Fight for the win-win.
  • Be a remarkable player. Put the team first. Step up when it’s time, inspire by example.
  • Own the outcome. Take responsibility for results. Embrace data celebrate effectiveness and face failures. Never stop improving.

The core values we have put in place guide all the decisions we make within our Denver website agency. They help inform everything from questions in an interview process, project decision making, peer to peer feedback, internal growth strategy, and long-term client relationships. Every single aspect of the business can be applied to the five core values. Since implementing them we are seen our decision-making process become much more focused, both short term and especially long term.

 

 

We’ve made an initiative out of preventing the typical cliched core value design. Figuring out creative ways to implement them into our everyday process has become a necessary challenge. We specifically seek out the traits that the values exemplify in our hiring process. In addition, all new hires see the exact debut presentation our company founders shared during the core values unveiling meeting.

Our core values are meant to stand against the core value bandwagoners, they run through our day-to-day, our hiring, and our attitudes.

Each and every day, we’re seeking the elevated third experience.

Pathauto is a module which lets you automate the generation of URL aliases in Drupal. Instead of the URL being "/node/123", you can have "/blog/article/why-use-drupal". The module allows you to define custom patterns which are generated when an entity is created. URL aliases or URL slugs, help with search engine optimization and they're more user-friendly. Drupal core has supported URL aliases for a long time, but they weren't automatically generated. Pathauto helps with automating the process. In this tutorial, you'll learn how to create aliases and patterns, and how to bulk generate paths.

Hi, my name is Jacob Rockowitz and I'm the individual responsible for maintaining the Webform module for Drupal 8. Two weeks ago, I posted Where Do We Come From? What Are We? Where Are We Going? documenting my journey and experience building and maintaining the the Webform module for Drupal 8. My goal was to document the current state of the Webform module, while simultaneously planning for the project’s future growth and sustainability. One of the steps toward accomplishing this is an idea I put together called "Sponsor a Feature".

"Sponsor a Feature" is a process encouraging organizations to hire Open-source software maintainers and contributors to build features and fix issues that directly impact a company's project. Two key concepts behind "Sponsor a Feature": all work would be open source and the sponsoring organization would pay for tangible and immediate results directly to the working individuals.

I feel that selling "Sponsor a Feature" to the Drupal community is going to be an uphill climb, especially because no one can technically sell Drupal. In other words, no one is used to paying directly for open source work. For now, I am going to tread lightly when talking about "Sponsor a Feature". For example, last week, I wrote about how Crowdfunding does not help grow Drupal's community to explore the different ways people are currently funding open source development. On Twitter, Adam Bergstein‏ (@n3rdstein) and I began a conversation about how an organization might pay a project maintain/developer.
(https://twitter.com/n3rdstein/status/872856666114580482).

Putting together an agreement that pays a developer to deliver...Read More

When you're running your non-profit, there is so much to do: basically an unlimited amount of work, right? Board meetings, fund-raising - and then there's the actual world-changing work you signed-up to do!

Our ongoing series of helpful tips (click here to subscribe via e-mail) continues today with some help on how to efficiently manage one of the most common and important aspects of any non-profit: EVENTS.

In this article, we'll talk about how to setup events in Drupal, and at the end, there's a video tutorial showing the process step-by-step.

Read more to see how!

Drupal - simplytest.me, Evaluate Drupal Projects Online

How to use simplytest.me, to evaluate drupal projects online?

heykarthikwithu Thursday, 15 June 2017 - 08:50:40 - IST, Asia/Kolkata
Lead Developer UK Conference 2017, Day 1

On June 8 and 9, I attended the Lead Developer UK conference for the first time. Its unique format allowed us to learn about leading and motivating teams in the tech industry from experts.

Josef Dabernig Thu, 06/15/2017 - 12:38

The Lead Developer conference was my first non-Drupal conference in quite some time and I’m happy to write that I picked the right one. Not only could I learn and verify a lot of thoughts about leadership but it also gave me a new set of role models to be inspired by.

The outstanding single-track program featured blocks of 3 sessions, most of them around 30 minutes with some shorter ones of around 10 minutes and some longer ones up to 50 minutes. Let me share a few of my personal highlights: 

Patrick Kua – The Constant Life of a Tech Lead kicked off the conference by reminding us about the basics of leadership in tech and that we should focus on values and principles rather than tools or implementation details. People are unique, they differ and we need to find the right approach depending on the situation. It is especially important to help your team as much as possible by providing the necessary context to accomplish their goals, which is often forgotten in my experience.

Constant Life of a Tech Lead from Patrick Kua

Katherine Wu – Ask vs. Guess Culture Communication brought back the idea of how differently people “tick”. Are you a more upfront person that prefers a clear communication style with others, or are you more on the side that expects someone to read between the lines and work based on assumptions? I definitely find myself more on the guess culture side and knowing that this is not how everyone works already helps a lot.  

Anjuan Simmons – Leadership Lessons from the Agile Manifesto gave a very personal track record of how he mastered leadership for himself and his teams. Working with a hero analogy, Anjuan mentioned that as tech leads we get called for the adventure, we get mentored with wisdom and are provided gifts to finally approach the boss level and return to improve the ordinary world. A tech lead guides other people on paths they have already taken. How does Anjuan motivate his team? At any cost, he will try to preserve the dignity of each team member and therefore earn their trust to together iterate and improve.

Erika Carlson – Better: Fearless Feedback for Software Teams provided helpful insights for one of the topics I most struggle with: giving good feedback. Aside from the general feedback categories: positive to encourage and constructive to improve, there’s also a category that is often missed not considered. “Passive feedback” means that you don’t give feedback at all and that also mean something to your peers. Giving the right amount of feedback in time is critical to any healthy relationship. I also liked to find out about 360 feedback and the idea of having a dedicated #thanks slack channel to collectively practice appreciation.

Better - Fearless Feedback for Software Teams from Erika Carlson

Nickolas Means – The Original Skunk Works concluded the first day. It was a detailed look at the history of the aircraft manufacturer that showed what incredible achievements they could make based on Kelly’s 14 Rules. Providing a system to innovate and release quickly (continuous integration & deployments) was critical to the success of this team.

The slides for all of the talks are available and I added the links to them above. On top of the inspiring talks, the conference had some more features I really liked too. Meri Williams was hosting the conference in a well-organized and entertaining way and followed up on a code of conduct issue in a constructive way. The conference also had a live captioning feature of all the talks on a screen, which helped me follow the massive flow of audio information and was even entertaining at times.

At #leaddev conference in London today. All talks are live-captioned by @whitecoatcapxg, which is awesome. pic.twitter.com/KVcDdSsypu

— Mehdi El Gueddari (@MehdiElGueddari) June 8, 2017

Next week, let’s follow up with a summary of day 2 and conclusions for The Lead Developer UK conference.

Direct .mp3 file download.

Adam Bergstein (nerdstein) joins Mike Anello to discuss the potential need to evolve Drupal Community Governance.

Interview DrupalEasy News Sponsors Upcoming Events Follow us on Twitter Five Questions (answers only)
  1. Playing with is kids.
  2. Docker for Mac.
  3. Making Drupal 8 core an amazing experience for content authors.
  4. Holding an alligator.
  5. Working with Drupal at Penn State
Subscribe

Subscribe to our podcast on iTunes, Google Play or Miro. Listen to our podcast on Stitcher.

If you'd like to leave us a voicemail, call 321-396-2340. Please keep in mind that we might play your voicemail during one of our future podcasts. Feel free to call in with suggestions, rants, questions, or corrections. If you'd rather just send us an email, please use our contact page.

Pages