Planet Drupal

Subscribe to Planet Drupal feed
Drupal.org - aggregated feeds in category Planet Drupal
Updated: 8 hours 43 min ago

Evolving Web: Why is the Drupal Bootstrap Theme So Successful

29 March 2017 - 11:50am

As a Drupal themer, it's rare that I choose something other than the Bootstrap base theme for a new project. Besides its quality and popularity, there are some specific technical reasons why Bootstrap is such an attractive option.

The internet loves Bootstrap

According to BuiltWith.com, as of March 2017, almost 12 million websites use the Bootstrap library. And w3techs says it's used by 14.9% of all public internet sites. For sure that is a lot.

This makes Bootstrap the top JS Framework worldwide and the second most popular JS library ever used, right after jQuery, which is used across 72% of the web. This means that there are a lot of docs and examples out there to use as a guide.

Thousands of developers know Bootstrap and work with it every day. And because Bootstrap is not Drupal-specific, you can use Bootstrap for your Drupal theme and your other non-Drupal projects. Front-end developers who know Bootstrap can be more easily on-boarded on your project if you go with Bootstrap as a base theme.

A Bootstrap theme doesn't have to look like Bootstrap

If you start with Bootstrap and don't customize the styling of your theme, of course, you will end up with that classic Bootstrap look and feel. But the magic of Bootstrap isn't just about how it looks. It is also how it behaves and the way it provides us a solid framework of interactions and components that we can easily customize to the most precise design specs.

Parts of Bootstrap like the grid, breakpoints, messaging and modals are generic components that you can reuse and restyle for your projects pretty easily. As a themer, you can either change these using the Advanced Theme Settings or do these custom on your project.

Advanced Theme Settings 

Since Drupal 7, when Bootstrap theme was created with a lot of settings that allow site builders to customize it out of the box and without coding. This is a very common practice across most Drupal themes, but on this specific case, you can "tweak" Bootstrap library specific components that integrate with your Drupal site like the Navbar, Breadcrumbs, Modals and so on.

Even if you are not an experienced Drupal Themer, you can jump into the Settings and start moving things around while customizing your website's appearance and behavior.

Another great feature is that you can set to use Bootstrap library from a CDN, change the library version you want to support and even use different "skins" from Bootswatch.com.

For a complete list of the theme specific settings, refer to the Bootstrap Theme Settings Docs.

Your theming style matters

In 2016, among many other projects, we developed a couple of Drupal 8 corporate websites on top of Bootstrap theme for the Council for Responsible Nutrition and CARTaGene. On both projects, designers were free enough to come up with their concepts without knowing we were going to use that specific framework to make these come to life and get launched.

By the way, did I mention that this site you see right now, is also Drupal 8 + Bootstrap Theme based?

Drupal loves Bootstrap

In a previous blog post, I talked about "Drupal Theming and Site Building: 6 Best Practices' and listed a set of criteria to use when considering a base theme for your Drupal projectSo here's how the Bootstrap theme measures up against these criteria:

  • How many people use it? The Bootstrap theme had more than 140,000 Drupal 7 & 8 reported installs as of March 2017. That is more than 10% of Drupal sites out there and is the most-installed theme for Drupal 8 so far.
  • Is it increasing? Over time, more and more front-end developers are adopting Bootstrap, according to the installation statistics from Drupal.org.
  • Is it being maintained? Bootstrap theme is actively maintained. Just check the issue queue.
  • How do I get started? Well, the documentation is extensive and detailed. There is even a specific website for it at http://drupal-bootstrap.org.
  • How secure is it? Stable releases are covered by the security advisory policy.

In Drupal 8, there are templates files for almost every HTML component printed on the page, so you can easily customize the way that Bootstrap classes are applied. This makes it really easy to use the library the way you want. You're not stuck with the decisions made by the base theme developers.

The Amazing People Behind Bootstrap

Last but not least, Open Source does it again:

Bootstrap Library Github repo is mainly managed by @mdo and @fat plus an active community of contributors. The library started in 2011 and since then it's been constantly increasing with more and more contributions every day.

For the Drupal base theme there is also a long list of contributors, but I'll give a special mention to Mark Carver, who takes care of leading the project development as the main maintainer and does an amazing work while carefully mixing these two technologies in the best way possible.

If you jump into the issue queue, you will notice that, just because a patch works, doesn't mean it will go into a base theme used by +140,000 websites as an update before being carefully reviewed and tested by the community. Thanks a lot to Mark and everyone else behind the theme.

How to Get Started?

If you are new to Drupal:

If you have some Drupal theming experience I suggest you read about:

And if you are an advanced Drupal Themer, we would love to have you contributing back:

+ more awesome articles by Evolving Web
Categories: Drupal

Acquia Developer Center Blog: 10 Ways to Build Quality into Agile Drupal Development

29 March 2017 - 9:19am

How to move fast, be flexible, and maintain high quality while building a digital experience.

Tags: acquia drupal planet
Categories: Drupal

Annertech: Allowing Editors to Choose the Image Style in Drupal 8 Image Fields

29 March 2017 - 7:02am
Allowing Editors to Choose the Image Style in Drupal 8 Image Fields

While building a site recently, we had a requirement for teaser images to be in a landscape or portrait orientation. We could have created two image fields and told the client to just fill in one - but that would mean editors would be responsible for cropping the image which would add extra effort to their work. Instead what we did was used one image field and one select list to choose if they image should be 'landscape' or 'portrait' in teasers.

Categories: Drupal

ADCI Solutions: Product development process

29 March 2017 - 3:27am

Alike any team that focuses on full cycle Drupal development we work with rather complex projects. Usually we go through all the stages: from idea to launch. We love having control over the process, that's why we created the simple yet working scheme. Following its steps gives us confidence that nothing is missed. This article describes the workflow of one of the ADCI Solutions projects and emphasize a designer's role at each stage. Try this scheme out and learn other tips that we included in the article.

Click here to get started

Categories: Drupal

Colorfield: Development best practices learned from the Drupal Dev Days Seville 2017

28 March 2017 - 11:50pm
Development best practices learned from the Drupal Dev Days Seville 2017 christophe Wed, 29/03/2017 - 08:50
Categories: Drupal

James Oakley: hook_uninstall not running? Drupal schoolboy errors #1

28 March 2017 - 9:04am

I'll put this here, in case it helps anyone else.

I'm owning up to Drupal Schoolboy Error #1.

I was writing a very simple module. It did so little, that I wanted to keep things as simple as possible — just a .info file, and a .module file.

Blog Category: Drupal Planet
Categories: Drupal

Appnovation Technologies: Appnovation - Open Digital Delivered.

28 March 2017 - 8:22am
Appnovation - Open Digital Delivered. Since founding Appnovation 10 years ago, we've enjoyed both continued growth, and the ongoing evolution of who and what we are as a business. In the early stages of the company, we were a software development company focused around one technology, Drupal, the content management system which drove and defined what we delivered for our clients. ...
Categories: Drupal

myDropWizard.com: Most common Drupal site building pitfalls and how to avoid them! (Part 3 of 3)

28 March 2017 - 7:58am

This is the third in a series of articles, in which I'd like to share the most common pitfalls we've seen, so that you can avoid making the same mistakes when building your sites!

myDropWizard offers support and maintenance for Drupal sites that we didn't build initially. We've learned the hard way which site building mistakes have the greatest potential for creating issues later.

And we've seen a lot of sites! Besides our clients, we also do a FREE in-depth site audit as the first step when talking to a potential client, so we've seen loads of additional sites that didn't become customers.

In the first article, we looked at security updates, badly installed module code and challenges ith "patching" modules and themes, as well as specific strategies for addressing each of those problems. In the second article, we looked at how to do the most common Drupal customizations without patching.

In this article, we're going to look at some common misconfigurations that make a site less secure, and how to avoid them!

NOTE: even though they might take a slightly different form depending on the version, most of these same pitfalls apply equally to Drupal 6, 7 and 8! It turns out that bad practices are quite compatible with multiple Drupal versions ;-)

Categories: Drupal

MidCamp - Midwest Drupal Camp: Free Community Drupal Training at MidCamp 2017

28 March 2017 - 6:38am

It started as a question.  Why do Drupal camps only have trainings on a separate day?  The legitimate answer was that trainings and sessions should not compete for audiences for a normal Drupal camp audience.  But what if the trainings were not for that normal Drupal camp audience?

When all of the hard work was done by the MidCamp venue team to secure the DePaul University Student Center for MidCamp 2017, we immediately started exploring the idea of having half day Drupal training sessions for those that would nornally not attend a Drupal camp.  We reserved two extra rooms for this idea.

While I looked for interested parties who would be interested in attending the trainings, Joseph Purcell of Digital Bridge Solutions worked to organize an Introduction to Making Websites with Drupal itinerary and found great trainers to lead the event: Michael Chase, ‎Instructor at DePaul University College of Computing and Digital Media, and Aaron Meeuwsen, Web Developer at HS2 Solutions, along with several other volunteers, Scott Weston and Matt Ramir from HS2, and Doug Dobrzynski from PMMI Media Group.  Without them, we couldn't have made this happen. I would also like to thank my employer, Xeno Media for contributing some of my time to help organize these trainings.

We've reached out to, and are happy to be working with such great local Chicago technology groups.  Girl Develop It, which provides programs for adult women interested in learning web and software development in a judgment-free environment, the IT Knowledge and Abilities Network (ITKAN), which provides professional networking and growth organization with a focus on professionals and aspiring professionals with disabilities, and Women Who Code, a global non-profit dedicated to inspiring women to excel in technology careers all answered our call.

But we still have room for more.  Do you know of someone who would benefit from free Intro to Drupal Training?  We want you to invite them!

The trainings will cover basic CMS tasks like editing and publishing content, creating navigation menus, and placement of content on the site, and will approach into more complex tasks such as module installation and site configurations. Additionally, we’ll show the various ways the Drupal community can help through the issue queue, meetups, job boards, and mentorship.

The sessions are:

  • Friday March 31st - 9:00 am - 12:00 pm
  • Friday March 31st - 1:00 pm - 4:00 pm
  • Saturday April 1st - 9:00 am - 12:00 pm
  • Saturday April 1st - 1:00 pm - 4:00 pm

Get your free ticket today!

Don't be shy, please share and and invite anyone you think would benefit from these trainings.  Ticket enrollment is open, and we would love to have every seat filled!

Categories: Drupal

Chromatic: Configuring Redis Caching with Drupal 8

28 March 2017 - 6:20am

How to install and configure Redis caching for Drupal 8.

Categories: Drupal

Darren Mothersele: How to do Everything with PHP Middleware (DrupalCamp London)

28 March 2017 - 2:30am

At the DrupalCamp in London earlier this month I gave a talk about PHP Middleware. You can see a recording of the talk on YouTube. Here’s a summary, in case you don’t want to watch the whole talk, or the distorted audio upsets you, or if you want the links and references:

Simple vs Easy

I started with a reference to the important talk by Rich Hickey, Simple Made Easy. This is high up on my list of videos every software developer needs to watch. I began here because I think it’s important to identify the difference between simple and easy, to identify where complexity sneaks into our systems. I have found PHP Middleware to be an important tool in the fight against complexity.

“programming, when stripped of all its circumstantial irrelevancies, boils down to no more and no less than very effective thinking so as to avoid unmastered complexity, to very vigorous separation of your many different concerns.

Edsgar W. Dijkstra (1930 - 2002)

De-complecting PHP

I talked a bit about different ways to simplify development with PHP. Including: Domain-driven design, Hexagonal architecture (Ports and Adapters), Framework-independent code, Thin APIs, etc… In particular, I wanted to emphasise the importance of framework-independent code and the benefit of using common interfaces such as the ones developed as PSRs by PHP-FIG.

There was some discussion after about introducing unecessary abstractions, but I think this misses the point. Of course there is a trade off, but the key is to focus on the simplicity, on untwisting things (c.f. Rich Hickey).

De-coupled

Inspired by the Zend Expressive installation procedure, I imagined what Drupal 10 might look like, with fully-decoupled components.

Interfaces

The widespread adoption of PSR7 by the PHP community has lead to the popularity of PHP Middleware-based systems.

Why PSR7 when Symfony HTTP components were so popular? Well, that is an implementation - and rather than standardise on implementation, we should standardise against interfaces.

This allows more interoperability. I showed this pseudocode:

// Take the incoming request from Diactoros $request = ServerRequestFactory::fromGlobals(); $client = new Client(); // Response comes back from Guzzle $response = $client->send($request->withUrl($dest)); $body = simplexml_load_string( $response->getBody()->getContents()); // pass back to Diactoros (new SapiEmitter)->emit($response->withBody($body));

The example uses HTTP requests from Zend Diactoros, forwards them using the Guzzle HTTP client, and returns the response object from Guzzle using the SAPI Emitter from Diactoros.

This demonstrates the power of sharing standard interfaces. Here two packages are used together, both provide an implementation of PSR7 HTTP messages, and they work seamlessly because they both conform to the same interface, despite the differing implementation details.

Decorating Web Apps

This is what a typical web app looks like:

Which can be simplified to this:

A web app takes a request and returns a response.

The concept behind PHP Middleware is that you can decorate the app, to add new functionality, by intercepting the request on the way in, and the response on the way out. This avoids the complexity of intertwining your code throughout the ball of mud.

Here’s an example (pseudocode) for adding CORS functionality to an existing app:

$cors = analyze($request); switch ($cors->getRequestType()) { Case ERR_NO_HOST_HEADER: Case ERR_ORIGIN_NOT_ALLOWED: Case ERR_METHOD_NOT_SUPPORTED: Case ERR_HEADERS_NOT_SUPPORTED: Return createResponse(403); Case TYPE_REQUEST_OUT_OF_CORS_SCOPE: return $APP->process($request); Case TYPE_PRE_FLIGHT_REQUEST: $response = Utils\Factory::createResponse(200); Return $response->withHeaders($cors->getHeaders); default: $response = $APP->process($request); Return $response->withHeaders($cors->getHeaders); }

StackPHP first popularised the concept of middleware in PHP. This diagram is from their website:

There are other popular micro-frameworks based on this concept, such as Slim.

The core of your app is just a thin layer of business logic. Just your domain specific code. The rest can be wrapped in layers which isolate and separate concerns nicely.

Single-pass vs Double-pass

The double pass approach became the most popularly used signature for HTTP middleware, based on Express middleware from the JS community.

It looks like this:

// DOUBLE PASS function __invoke($request, $response, $next) { }

The request and the response are both passed into the middleware, along with a $next delegate that is called to pass control and carry on processing down the chain of middleware.

This double-pass approach is much newer, but used by most of the early adopters of PSR-7.

A single pass approach, looks like this:

// SINGLE PASS / LAMBDA function process($request, $delegate) { }

The issue is with how the response object is dealt with. In the double-pass approach, both are provided. The argument is that this is better for dependency inversion. Using the single pass approach you either need to hard code a dependency on a HTTP message implementation into your middleware when the response is required, or you need to inject a factory for generating the response.

PSR-15 HTTP Middleware

After the success of PSR7, with it’s wide adoption leading to much standardisation and interoperability in PHP frameworks, the next step is to standardise the middleware interface.

This is not yet an accepted PSR. At the time of writing it is still in draft status. It is available for use in the http-interop/http-middleware repo.

Invoker

As an aside, I mentioned the Invoker Interface. As per the docs:

“Who doesn’t need an over-engineered call_user_func()?”

In particular this library really simplifies the process of calling things and injecting dependencies. It also allows to call things using named parameters. I make extensive use of this, and I find making calls with named parameters makes code much easier to understand.

PSR-15 Interfaces

PSR-15 has two interfaces. Both define a method called process. One is the signature that middleware must support, which takes a PSR7 request and a PSR15 delegate. The other interface defines the process method for the delegate. The method on both interfaces is defined as returning a PSR7 response.

So you can compose a chain of middleware, pass in a request and get a response. The request is passed down the chain of middleware until a response is generated which is then passed back up the chain, possibly being decorated along the way.

For want of a better name, I refer to this chain of middleware as a stack. And, I have created a simple Stack Runner to handle the processing of a stack of PSR-15 middleware.

class StackRunner implements DelegateInterface { public function __construct( array $stack, InvokerInterface $invoker, ResponseFactoryInterface $responseFactory ) { ... } public function process(ServerRequestInterface $request) { if (!isset($this->stack[$this->current])) { return $this->responseFactory->createResponse(); } $middleware = $this->stack[$this->current]; $this->current++; return $this->invoker->call([$middleware, 'process'], [ 'request' => $request, 'delegate' => $this, ]); } } ADR (Action Domain Responder)

I went on to talk about ADR as being an adaptation of MVC that is more suitable for use in Web Apps. I’ve found this particularly useful when using Domain-Driven Design, or when used to create thin APIs where you have just a thin layer of business logic on top of a data store.

The issue with MVC is that the template is not the view. The “view” of a web app is the HTTP response, and we split this across our layers, as the body of the response is typically generated by the view, with the knowledge of HTTP being encoded into our controllers. We also bundle together various actions into one controller, which means instantiating the whole thing when we want to run one of the actions.

ADR offers an alternative separation of concerns, where the action methods of the controller are their own separate classes (or in my case anything invokable via the InvokerInterface). I use an InputHandler to deal with parsing the input from the HTTP Request, which the Invoker can then use (via the magic of named arguments).

The domain (Model in MVC terminology) is where the business logic lives. This is called domain, rather than model, to suggest use of domain-driven design.

To use ADR with PHP Middleware, add a resolver to the end of the chain of middleware to dispatch the request to the appropriate Action.

Action

I’ve created a reference implementation of an invokable Action.

Demo!

At this point in my talk I planned to give a demo of how you compose ADR with Middleware to create a working API. Unfortunately, I had some tech issues getting my computer linked up to the projector, and I was starting to feel really ill (full of cold). By this time the caffeine was starting to wear off, and I needed the talk to end!

I’ve put the example code up in a GitHub repo.

References
  • Simple Made Easy - talk by Rich Hickey
  • HTTP Middleware and HTTP Factory interfaces.
  • PSR15 Middlewares a set of really useful middlewares that can be used with a PSR15 middleware dispatcher.
  • Stack Runner my reference implementation of a very simple stack runner for executing a chain of PSR15 middleware.
  • Wafer an experimental implementation of the ADR idea to be used along with PSR15 middleware and the stack runner.

Drop me a line with any feedback. Thanks!

Categories: Drupal

Agiledrop.com Blog: AGILEDROP: Responsive Images in Drupal 8

28 March 2017 - 1:56am
The days of fixed-width websites are long behind us, and with fluid widths came fluid images. In many cases, we don’t want to display the same image size on a mobile and on a desktop, because we truly don't need a 2000px wide image on a 480px device. Or we want to display a completely different image at some breakpoint. For this we have a HTML5 element which can contain a multiple elements with srcset and media attributes. The browsers choose the right source based on a media query. In my case, I had to show completely different image sizes on mobile vs.… READ MORE
Categories: Drupal

Janez Urevc: Time to take some time off the Drupal community

28 March 2017 - 1:11am
Time to take some time off the Drupal community slashrsm Tue, 28.03.2017 - 10:11

When I joined the Drupal community I felt that I arrived in the enthusiastic, welcoming and positive environment. I felt that all contributions are appreciated and that we're all following more or less the same goal. This belief was also mostly the source of motivation for my extensive contributions to the Drupal 8 Media initiative in the past 4 years or so. This has dramatically changed in the last year or so and seems to be getting worse all the time.

Our community has governance and conflict-resolution rules. Everything should be clear and transparent. At least in theory. But in practice things don't work that way. Decisions (political and technical) are often made behind closed doors where only small fraction of the community is allowed to participate. Decision processes are nontransparent and leadership doesn't seem to feel any need to improve that. This was also the main reason why I recently decided to discontinue my DA membership.

I think that, in order to survive in the long term, we'll need to reform our community to become truly transparent and democratic. We've been "living" in a dictatorship and it has been working for us so far. But history shows that too much concentration of power in an small ruling clique almost always leads to its abuse (I strongly recommend this book).

My impression is that the community in general is getting increasingly toxic. It feels that there is more and more hypocrisy, lies, secret goals and partial interests being involved (and I think that the lack of transparency contributes to that). Best indicator for in my case are the community events which have (with some rare bright exceptions) become a burden instead of enjoyment for me. I still enjoy meeting some people that have become my friends during the years, but I recently started seeing the community in general as increasingly negative, abusing and exhausting.

Stress and bad mood directly linked to the happenings in the Drupal started affecting my personal life, including relations with my family. This is not acceptable and I decided to take some time off to think about the situation and to decide if and to what extent I want to remain active in the community. This decision was not made solely due to the most recent ousting (which also clearly showed how the community and its leadership actually work). It is based on many events that happened in last year or so.

This is my personal decision and has nothing to do with my employer. I really enjoy working at MD Systems and have no intentions to introduce any changes into that part of my life.

Categories: Drupal

Kalamuna Blog: Converting Drupal 7 Media Tags During a Drupal 8 Migration

27 March 2017 - 8:37pm
Converting Drupal 7 Media Tags During a Drupal 8 Migration John Ouellet Mon, 03/27/2017 - 20:37

As developers of all skill levels begin to migrate from old versions of Drupal to Drupal 8, it is always good to have references for some of the more arduous tasks out there.  Many of our clients for whom we built Drupal 7 sites used the media module and the awesomeness that it gave to their sites. Now, as I migrate some of these same sites to Drupal 8, I hit a bump in the road. The Drupal 7 Media tag can’t be rendered in the Drupal 8 site I am migrating to. This is because that functionality is not present in the Drupal 8 site.

Categories Articles Drupal Guidance
Categories: Drupal

MidCamp - Midwest Drupal Camp: Two days before before MidCamp

27 March 2017 - 8:19pm

Two days before before MidCamp, when all round the rug, not a creature was stirring, not even a bug.

Though the house was so empty, and missing it's stir, our Volunteer coordinator was out saying burrr (don't leave me out in the cold). Our Sprint lead was looking for sprinters to sprint, and our Trainers were looking for trainees to imprint!

MidCamp 2017 has 45 sessions for you to attend on Friday and Saturday, 4 Full day trainings on Thursday, and 4 Free half day trainings for you to invite anyone new to Drupal to attend.

In addition, we have socials for you to attend on Friday and Saturday, and a Sunday contrib Sprint to give back to Drupal.

It's spring in Chicago, and we hope you can join us!

Get your tickets today!

Categories: Drupal

Platform.sh: More flexible elastic now available

27 March 2017 - 6:00pm

Elasticsearch is one of the most popular Free Software search engines available. It’s fast, flexible, and easy to work with.

It’s also now fully up to date on Platform.sh.

Categories: Drupal

OSTraining: Entity Reference Views Helping Drupal 8 Content Creators

27 March 2017 - 3:14pm

Entity Reference Views are one way you can make life easier for Drupal content creators.

Normally, when people create content on your site, each field consists of a single box with a single data point. For example, in a list of people, you might get only the person's name. 

Entity Reference Views allows you to provide far more information. For example, you can add photos and personal details to your list of people.

Categories: Drupal

Vardot: The evolution of Drupal: Drop 1.0 to Drupal 8

27 March 2017 - 12:16pm
Case Studies Read time: 6 minutes

After fifteen years of going from strength to strength, it’s a great time to look back on the Drupal that was and how it became a powerhouse of the open source content management world.

Way back in May 2000 the Drupal GitHub repository was started. In December 2000 Drupal 1.0 was named and since then it has taken over 33,000 commits to build Drupal as we know it today. Thanks to a dedicated community backing and flexible technology, Drupal is now a stable modular platform that is used by over 1.18 million websites. Did you ever think how Drupal got so big? We’re going to take you through this journey right now.

Why Drupal is the Best CMS for Your Website

 

Drupal 1 (Drop)

Drupal 1.0 contained a mere 18 core modules, each driven by a php file. The system relied heavily on SQL to manage and modify content, themes, layout and more. Pre-loaded themes gave web developers a jumping off point, and Drupal allowed developers to hook into existing code and tweak colours, layouts and functionality to their liking. The original system came with some nice basics like a search function, comment fields and a diary/blog functionality.

 

Drupal 2

Drupal 2.0 was released shortly after and come packed with translation features. Developers could now build or translate their sites by altering the database, a feature which opened up Drupal to a global community. 2.0 also brought in improvements to user ratings, stories and a whole host of additional fine tuning to the user access groups, allowing greater control over site development and stakeholder interactions.

 

Drupal 3

Drupal 3.0 saw the introduction of the concept of ‘nodes’, taking over the common idea of web pages. Nodes increase flexible for creating and displaying content. All kinds of content, whether a web page, blog article or news item were managed by the node module. Comments and actions were attached directly to the node which increased flexibility in site building and later changes. The use of nodes instead of pages has become commonplace in mobile development, ten years after Drupal embraced the concept.

 

Drupal 4

At this stage, six months had passed, and Drupal had grown to 26 core modules. In June 2002 Drupal 4.0 was released. Almost 100 major sites were built with Drupal, and a wide community of developers were contributing to the project across Europe and the United States.

Drupal 4.0 introduced the Taxonomy module, taking over from the meta module and giving site builders an entire new toolset for categorising, sorting and marketing their content. With a friendly user interface and a strong community of contributors Drupal 4.0 had moved away from its humble origins and taken a place as an enterprise quality Content Management System.

At this stage Drupal moved to a slower release schedule, with Drupal 4.1 not being released until February 2003, eight months later. Drupal 4 lasted until January 2007, with seven minor releases over four years.

Drupal 4’s minor releases saw a massive expansion of capability, including its first e-commerce module in 4.4. It also introduced its first WYSIWYG (What You See Is What You Get) editor, opening doors for web-writers without a coding background, and offered much more flexible theming options. Drupal saw a massive surge in usage when presidential candidate Howard Dean launched a multitude of interlinked campaign sites using Drupal.

 

Drupal 5

In 2007 Drupal took another huge step forward and released Drupal 5.0. At this stage there were over 492 contributors and a massive 1173 patches. While Drupal 5.0 only had 29 core modules, more than 2500 contributed modules were available for site builders to inject into their sites. Drupal 5.0 was the first version to feature jQuery, a JavaScript library that greatly increases a web developers’ capabilities while cutting down on development time and stress.

Drupal 5.0 also came neatly packaged in a web based installer saving users from manual database manipulation and allowing the creating of custom packages pre-filled with contributed modules and themes. The backend was tidied up with a whole new file structure, and css files were automatically compiled and compressed, greatly reducing site loading times. Site builders were given the ability to control caching and create custom content types leading to greater performance and customisation.

 

Drupal 6

Drupal 6.0 was released in February 2008 and supported until just last year. At the time that support ended there was an estimated 120,000+ websites still using Drupal 6.0. With 34 core modules, over 7000 contributed modules and 600 custom themes the modular genius of Drupal was undeniable. This new release contained a completely new menu structure that had been written from the ground up, and a friendlier installation process. The community also increased security, brought in more user friendly elements to the User Interface (such as drag and drop administration) and upgraded the language support to handle right-to-left languages.

Drupal 6.0 remained for three years. During this time it was used to host Whitehouse.gov, one of the largest profile websites at the time. Whitehouse.gov is still using Drupal to this day, although they have updated to Drupal 7.0

 

Drupal 7

In 2011 Drupal 7.0 was released and by this stage it is being used by web developers from all walks of life. Small business owners, large corporations, bloggers and government agencies are all using Drupal for its flexibility and ease of use. At this stage there are over 11,000 contributed modules and 200 distributions available, though Drupal Core is kept slim with just over 40 core modules.

Drupal 7.0 saw even greater flexibility with interaction between nodes and modules, allowing any module to call, alter and display any node. Every item in Drupal 7.0 became an individual entity capable of being manipulated and displayed to the user to create a vast flexible website.

 

Drupal 8

Drupal 8.0 was officially released on the 19th of November 2015. It has since been running on a six-month update cycle, meaning we already have access to Drupal 8.3. It comes bundled with over 60 core modules, and one of the most popular contributed modules ‘Views’ is now part of that core module set. Drupal 8.0 users over 60 database tables, but includes smarter tech like BigPipe to keep site load times to a minimum.

7 Reasons Why Now is The Right Time to Move to Drupal 8

 

Bottom line

Drupal has been running ahead of the curve since the beginning, and with a strong community backing it won’t be stopping any time soon. Drupal’s evolution has always emphasised ease of use, quick site adjustments and a brilliant modular design that means no two Drupal sites are alike. It’s been a long ride to get here, but you can be sure that Drupal will be leading the way for years to come.

Bonus: What Drupal means to us - the community speaks about its favorite CMS

Tags:  Drupal Planet Drupal Title:  The evolution of Drupal: Drop 1.0 to Drupal 8
Categories: Drupal

Drupal Association blog: 2017 Drupal Association at-large election winner announced

27 March 2017 - 8:51am

*/

The staff and board of the Drupal Association would like to congratulate our newest board member:

Ryan Szrama.

Thank you, Ryan, for stepping forward to serve the Drupal community. On behalf of the community I also want to thank the 13 candidates who put themselves out there in service of Drupal and nominated themselves. We are grateful that our community has so many brave and generous people willing to contribute this way.

Ryan's election to the board represents the sixth year of elections to a community-at-large seat on the Drupal Association board. Each year we've focused on improving the elections process, and this year was no different. We focused on two goals: 

  1. Improve the user experience of participating in the elections process. 
    • We added more in-line help materials throughout the elections process.
      • For candidates, we added information about the responsibilities of a board member to the nomination form, as well as a video message from the Executive Director.
      • For voters we improved the elections navigation, and provided more educational materials about the IRV voting process.
    • We implemented a drag and drop ballot, to make it easier for voters to rank candidates. 
  2. Make it easier to get to know the candidates.
    • We updated the candidate profile form, to ask more detailed questions to help voters get to know the candidates. 
    • Based on feedback from previous years, we eliminated the three virtual meet-the-candidates sessions, in favor of giving each candidate the option to post a statement-of-candidacy video.  In conjunction with the question and answer section on each candidate profile, we felt this gave the electorate the opportunity to get to know their candidates at their own pace and on their own terms. 

Our next steps will be to reach out to the candidates for their evaluation of the elections experience.

We also want to hear from the voters. Please tell us about your experience with the elections process in the comments below. Your feedback is important to us so that we can make the 2018 elections process even better. 

About the Elections Methodology: Instant Run-off Voting(IRV)

Elections for the Community-at-large positions on the Drupal Association board are conducted through Instant Run-off Voting. This means that voters can rank candidates according to their preference. When tabulating ballots, the voters' top-ranked choices are considered first. If no candidate has more than 50% of the vote, the candidate with the lowest votes is eliminated. Then the ballots are tabulated again, with all the ballots that had the eliminated candidate as their first rank now recalculated with their second rank choices. This process is repeated until only two candidates remain and a clear winner can be determined. This voting method helps to ensure that the candidate who is most preferred by the most number of voters is ultimately elected. You can learn more about IRV (also known as Alternative Vote) in this video.

Voting Results

There were 13 candidates in contention for the single vacancy among the two community-at-large seats on the Board. 1,240 voters cast their ballots out of a pool of 94,499 eligible voters (1.3%). Voters ranked an average of 3.6 candidates on their ballots. 

The bar charts below show the vote counts for each candidate in each round.
Place the mouse over a bar to see the number of votes.

  • Yellow — Votes carried over from the previous round.
  • Green — Votes received in this round.
  • Red — Votes transferred away in this round.

A candidate's votes in a round is the sum of the yellow and green bars.
Since the green and red bars represent votes being transferred, the sum of the
green and red bars is the same.

The exhausted bar represents votes where the voter did not indicate a next
preference and thus there were no candidates to transfer the vote to.

Round 1

(next)

Count of first choices.

Round 2

(prev)(next)

Count after eliminating gurubryan and transferring votes.

Round 3

(prev)(next)

Count after eliminating mehuls and transferring votes.

Round 4

(prev)(next)

Count after eliminating zet and transferring votes.

Round 5

(prev)(next)

Count after eliminating Rahul Seth and transferring votes.

Round 6

(prev)(next)

Count after eliminating redacted and transferring votes.

Round 7

(prev)(next)

Count after eliminating MatthewS and transferring votes.

Round 8

(prev)(next)

Count after eliminating Riaan Burger and transferring votes.

Round 9

(prev)(next)

Count after eliminating johnkennedy and transferring votes.

Round 10

(prev)(next)

Count after eliminating jackniu and transferring votes.

Round 11

(prev)(next)

Count after eliminating ok_lyndsey and transferring votes.

Round 12

(prev)

Count after eliminating Prasad Shir and transferring votes. Candidate rszrama is elected.

Winners

Winner is rszrama.

Categories: Drupal

Virtuoso Performance: Thoughts on the Drupal community

27 March 2017 - 8:47am
Thoughts on the Drupal community

I did make one comment on Dries’ blog in the immediate aftermath of learning about the situation which is roiling the Drupal community, but since then have taken some time to listen and ponder. The community is in deep pain now, and many of us are reacting to that pain with anger. Trust is in short supply. Healing seems nearly impossible.

We need to start from compassion for all involved. The pain is deepest for those in the middle. Larry has already expressed his pain eloquently - I know losing the Drupal community would cut me deeply, and pragmatically this is a major blow to his career as well. But, let’s also consider Drupal leadership - Dries, the Drupal Association, the Community Working Group. Regardless of whether we agree with their decision, I see no reason to believe it was done arbitrarily or with malice. Reaching such a decision against someone who has given so much to the community over the years must have been extraordinarily difficult, and the fact that this decision seems to have eroded much of the community’s trust in them is surely agonizing.

We need to recognize and address the asymmetries in this situation. The power in the relationship is unbalanced - Drupal leadership has an ability to affect Larry’s life profoundly that is not reflected. On the other hand, the information is also unbalanced - Larry is able to say what he chooses publicly, but the Drupal leadership has a responsibility to maintain confidentiality. Yes, “confidentiality” can be used as a smokescreen - but there really is a legitimate need to respect it - to protect those who gave evidence to the CWG, and to protect Larry himself from public accusations without public evidence. Transparency and confidentiality are at odds, and it is exceedingly difficult to find a “perfect” balance between them.

That all being said, and recognizing that the information I have is incomplete, my main thoughts on the three parties involved:

  1. The impression Larry’s blog post leaves is that his dismissal was primarily due to BDSM/Gorean practices in individual personal relationships (that certainly appears to be the main takeaway in much of the criticism online). On the other hand, statements from the other side suggest it may have had more to do with broader statements of belief (and commitment to living that belief totally) which seem in conflict with the Drupal community’s values (although it’s difficult for me to be sure of whether they were meant to be taken literally in the real world, or as a form of cosplay - as portrayal of a Gorean character). Just to be clear - although I strongly disagree with some statements I saw, as long as they were not reflected in Larry’s behavior within the Drupal community I don’t see standing to dismiss him (except, perhaps, from representation to the PHP community if it seemed like it might diminish his effectiveness in that role). But, if this was indeed the main issue presented to Larry, I would have liked to see him address it head-on. He does deal with it somewhat in the section “Larry is a proponent for the enslavement of women!”, but the section title itself looks like an exaggeration of the actual accusation, and it is down at the bottom of the accusations he addresses, de-emphasizing it.

  2. I think Drupal leadership needs to tilt the balance at least a little more towards transparency. The community does need to better understand broadly why Larry was dismissed. Dries’ post stated “I did this because it came to my attention that he holds views that are in opposition with the values of the Drupal project”. This suggests that the primary reason for the dismissal was those statements outside of Drupal - I (and many others) feel that what happens outside of the Drupal community, should stay outside of the Drupal community. Then, the DA stated “We want to be clear that the decision to remove Larry's DrupalCon session and track chair role was not because of his private life or personal beliefs... Our decision was based on confidential information conveyed in private by many sources.” This contradicts Dries’ original statement, which is concerning. It also fails to address the central concern many people have - did Larry do or say anything within the Drupal community?

  3. I don’t think the Drupal community has acquitted itself well here. The immediate outpouring has been based on one point of view - admittedly, there is little hard information otherwise, but we should all be slower to react when we know we don’t have all the facts, and lead off with questions rather than diatribes. One thing to be concerned about is that the one-sided onslaught is likely to discourage expressions that disagree with the crowd - anyone who might agree with the Drupal leadership’s decision, or who might know of some concrete reasons they may have made that decision, has reason to fear speaking up. I’m thinking here of GamerGate. No, I’m not saying the people criticizing the decision are like the GamerGaters - but what I am saying is that, given that the center of this controversy is around beliefs and statements that look an awful lot like misogyny, and that much of the rhetoric has carried a whiff of torches and pitchforks, I would not be at all surprised if women (and feminists of all gender identities) felt good reason to fear a GamerGate-like backlash if they did speak up. We need to leave more room for all voices and not flood the space unilaterally.

So, where do we go from here? In reverse order,

  1. The Drupal community is certainly Internet-savvy - we’ve all seen so many cases where based on one piece of information the flamers descend without waiting for fact-checking, the other side of the story, etc. We need to jerk our knees a little more slowly. We need to recognize we don’t have (and will never have) all the information, and the fact that we won’t have it is not in and of itself proof that the decisions of Dries/DA/CWG were wrong.

  2. Drupal leadership does need to tell us more, and I think it can be done without violating confidentiality. Simply put - did Larry’s dismissal involve anything he did within the Drupal community? If they say it did, I for one, am willing to accept it and move on - I’m not in a position to know the specifics (nor should I be), but I recognize this as a legitimate exercise of authority, even if I don’t know if I would have voted the same way if I had seen the evidence. If, on the other hand, this is based purely on statements and actions outside of the Drupal community, it’s important for all of us in the Drupal community to understand that - we all need to know if the DA and CWG will hold us accountable for our online presence outside of Drupal. On that score, I’ve created a separate Twitter account for my Drupal and professional communications under my DBA, Virtuoso Performance. To be fair, I’ve considered doing this anyway just in terms of work/life balance, but now it seems all the more important to keep things separate.

  3. I know it’s a lot to ask - actually, I know that it’s too much to ask and don’t actually expect it, but in the interests of symmetry I’m putting it out there… It would be great if Larry could share (without violating the confidentiality of anyone involved - redacting names and details) precisely what he was told were the specific charges that led to his dismissal. We’re not going to get any specifics from the Drupal leadership side - he’s the only person who can provide us with any hard information. Again, I don’t expect this - Larry has suffered more than anyone here, and has already really put himself out there. Edit: Larry has now responded with more information, which I will take some time to review before making further comment.

Ultimately, while this is a painful episode in Drupal’s history, I hope we can find a way to get through it and come out the other side with a better understanding of each other, and rebuild trust within the community.

mikeryan Monday, March 27, 2017 - 10:47am Tags Planet Drupal Drupal Add new comment
Categories: Drupal

Pages