Skip to Content

Newsfeeds

OSTraining: Drupal 8.1 and What It Means for Drupal's Future

Planet Drupal - 20 April 2016 - 8:32am

Today, Drupal 8.1 was officially released.

All the way back in 2014, we talked about the changes coming to Drupal and how the release cycle would allow for changes to be progressively added to Drupal.

At that time, it was estimated that a new version with new features could be released every 6 months. Keeping to that schedule for Drupal 8 has been problematic due to the size and scope of what they wanted to achieve, but they made it! 

Categories: Drupal

OneSignal Integration

New Drupal Modules - 20 April 2016 - 7:21am

This module integrates with OneSignal, which is a free multi-platform push notification service for mobile apps.

This module wraps the PHP library written by @norkunas providing a simple user interface to setup the basic configurations to initialize the OneSignal class.

NOTE: This is not an end user module. This is for developers.

Categories: Drupal

15 of Gamasutra's best articles over the last quarter

Social/Online Games - Gamasutra - 20 April 2016 - 6:32am

Hey readers! I realize that often some of Gamasutra's best blogs and articles get buried over the course of time, so I figure it's worthwhile to start highlighting some of our best recently-published articles. ...

Categories: Game Theory & Design

Node Edit Redirect

New Drupal Modules - 20 April 2016 - 6:15am

This module will redirect users that edit a node, to same the node edit form, but in the same language as the node.

Assuming the negotiated content language is based on URL (prefix/domain), this ensures that such a "content language" matches the language of the node.

Example

- Content language is negotiated based on prefix. See also:
https://api.drupal.org/api/drupal/includes!language.inc/group/language_n...

Categories: Drupal

Wim Leers: Drupal 8.1: BigPipe as an experimental module

Planet Drupal - 20 April 2016 - 4:09am

Today, Drupal 8.1 has been released and it includes BigPipe as an experimental module.

Six months ago, on the day of the release of Drupal 8, the BigPipe contrib module was released.

So BigPipe was first prototyped in contrib, then moved into core as an experimental module.

Experimental module?

Quoting d.o/core/experimental:

Experimental modules allow core contributors to iterate quickly on functionality that may be supported in an upcoming minor release and receive feedback, without needing to conform to the rigorous requirements for production versions of Drupal core.

Experimental modules allow site builders and contributed project authors to test out functionality that might eventually be included as a stable part of Drupal core.

With your help (in other words: by testing), we can help BigPipe “graduate” as a stable module in Drupal 8.2. This is the sort of module that needs wider testing because it changes how pages are delivered, so before it can be considered stable, it must be tested in as many circumstances as possible, including the most exotic ones.

(If your site offers personalization to end users, you are encouraged to enable BigPipe and report issues. There is zero risk of data loss. And when the environment — i.e. web server or (reverse) proxy — doesn’t support streaming, then BigPipe-delivered responses behave as if BigPipe was not installed. Nothing breaks, you just go back to the same perceived performance as before.)

About 500 sites are currently using the contrib module. With the release of Drupal 8.1, hopefully thousands of sites will test it.12

Please report any issues you encounter! Hopefully there won’t be many. I’d be very grateful to hear about success stories too — feel free to share those as issues too!

Documentation

Of course, documentation is ready too:

What about the contrib module?

The BigPipe contrib module is still available for Drupal 8.0, and will remain available.

  • 1.0-beta1 was released on the same day as Drupal 8.0.0
  • 1.0-beta2 was released on the same day as Drupal 8.0.1, and made it feature-complete
  • 1.0-beta3 contained only improved documentation
  • 1.0-rc1 brought comprehensive test coverage, which was the last thing necessary for BigPipe to become a core-worthy module — the same day as the work continued on the core issue: https://www.drupal.org/node/2469431#comment-10899308
  • 1.0 was tagged today, on the same day as Drupal 8.1.0

Going forward, I’ll make sure to tag releases of the BigPipe contrib module matching Drupal 8.1 patch releases, if they contain BigPipe fixes/improvements. So, when Drupal 8.1.3 is released, BigPipe 1.3 for Drupal 8.0 will be released also. That makes it easy to keep things in sync.

Upgrading?

When you upgrade from Drupal 8.0 to Drupal 8.1, and you were using the BigPipe module on your 8.0 site, then follow the instructions in the 8.1.0 release notes:

If you previously installed the BigPipe contributed module, you must uninstall and remove it before upgrading from Drupal 8.0.x to 8.1.x.

  1. Note there is also the BigPipe demo module (d.o/project/big_pipe_demo), which makes it easy to simulate the impact of BigPipe on your particular site. 

  2. There’s also a live demo: http://bigpipe.demo.wimleers.com/ 

  • Acquia
  • Drupal
  • WPO
  • performance
Categories: Drupal

Village Backdrop: Coldwater System Neutral Edition

New RPG Product Reviews - 20 April 2016 - 3:09am
Publisher: Raging Swan Press
Rating: 5
An Endzeitgeist.com review

This installment of RSP's Village Backdrop-series is 11 pages long, 1 page front cover, 2 pages advertisement, 1 page editorial/ToC, 1 page SRD and 1 page back cover, leaving us with 5 pages of content, so let's take a look at the settlement


Coldwater is perched upon an inhospitable, mud-drenched coast, with one access by land, its harbor is in the delta of a miserably stream that empties its contents into the sea - and if that does not reflect a place you'd like to visit, then that's pretty much a representation of how most folks see this place. Nearby caverns sport strange stair-like features that only rarely become visible and the inhabitants of the village are just as sullen and unfriendly as the weather suggests. The village lore reflects the relative hostility and rugged nature of the village rather well, while a Finnish-inspired nomenclature emphasizes an association with the colder climes.


Indeed, the rustic and eccentric locals e.g. sport a man named Holg, who has a well-stacked ware-house, but lets no one in - you have to tell the old man what you're looking for and mysteriously, more often than not, he procures the object from within the depths of his dubious "locker." Indeed, one cannot really fault the locals for their sullen outlook on life: As the events and the subtle wrongness in the tides underline, there is something wrong here - there are the deformed, both in mind and body- how and why the poor folks of this village are struck by this curse ultimately is up to the GM, but the presence of the template and its varied effects alongside the stigmatization such folk may experience should drive home pretty well that something is wrong here...


Conclusion:

Editing and formatting are top-notch, I didn't notice any glitches. Layout adheres to RSP's smooth, printer-friendly two-column standard and the pdf comes with full bookmarks as well as a gorgeous map, of which you can, as always, download high-res jpegs if you join RSP's patreon. The pdf comes in two versions, with one being optimized for screen-use and one to be printed out.


Creighton Broadhurst has skill - and this one shows it pretty well. The mastermind of Raging Swan Press delivers what I'd like to call a wide open sandbox: We are faced with problems and the respective NPCs mentioned can be used to exacerbate it, change it...all depending on your whims. Basically, this is one of the village backdrops that is so compelling, it can make PCs pretty much write their own tale: Throw them in and watch what happens. In this aspect, though, this one is slightly inferior to Kennutcat. However, at the same time, it sports local color that made me think of the slight surreal elements that made Twin Peaks so compelling, at least for me -from the dwindling fortunes of one family to female, hard-working and drinking half-orc, there is a lot of quirkiness, a lot of unique bits and pieces here; enough, to make this thoroughly compelling. The system-neutral version loses nothing of the luster of the original and is well worth 5 stars + seal of approval.

Endzeitgeist out.
Categories: Game Theory & Design

Dries Buytaert: Applaud the Drupal maintainers

Planet Drupal - 20 April 2016 - 2:38am

Today is another big day for Drupal as we just released Drupal 8.1.0. Drupal 8.1.0 is an important milestone as it is a departure from the Drupal 7 release schedule where we couldn't add significant new features until Drupal 8. Drupal 8.1.0 balances maintenance with innovation.

On my blog and in presentations, I often talk about the future of Drupal and where we need to innovate. I highlight important developments in the Drupal community, and push my own ideas to disrupt the status quo. People, myself included, like to talk about the shiny innovations, but it is crucial to understand that innovation is only a piece of how we grow Drupal's success. What can't be forgotten is the maintenance, the bug fixing, the work on Drupal.org and our test infrastructure, the documentation writing, the ongoing coordination and the processes that allow us to crank out stable releases.

We often recognize those who help Drupal innovate or introduce novel things, but today, I'd like us to praise those who maintain and improve what already exists and that was innovated years ago. So much of what makes Drupal successful is the "daily upkeep". The seemingly mundane and unglamorous effort that goes into maintaining Drupal has a tremendous impact on the daily life of hundreds of thousands of Drupal developers, millions of Drupal content managers, and billions of people that visit Drupal sites. Without that maintenance, there would be no stability, and without stability, no room for innovation.

Categories: Drupal

Applaud the Drupal maintainers

Dries Buytaert - 20 April 2016 - 2:38am

Today is another big day for Drupal as we just released Drupal 8.1.0. Drupal 8.1.0 is an important milestone as it is a departure from the Drupal 7 release schedule where we couldn't add significant new features until Drupal 8. Drupal 8.1.0 balances maintenance with innovation.

On my blog and in presentations, I often talk about the future of Drupal and where we need to innovate. I highlight important developments in the Drupal community, and push my own ideas to disrupt the status quo. People, myself included, like to talk about the shiny innovations, but it is crucial to understand that innovation is only a piece of how we grow Drupal's success. What can't be forgotten is the maintenance, the bug fixing, the work on Drupal.org and our test infrastructure, the documentation writing, the ongoing coordination and the processes that allow us to crank out stable releases.

We often recognize those who help Drupal innovate or introduce novel things, but today, I'd like us to praise those who maintain and improve what already exists and that was innovated years ago. So much of what makes Drupal successful is the "daily upkeep". The seemingly mundane and unglamorous effort that goes into maintaining Drupal has a tremendous impact on the daily life of hundreds of thousands of Drupal developers, millions of Drupal content managers, and billions of people that visit Drupal sites. Without that maintenance, there would be no stability, and without stability, no room for innovation.

Categories: Drupal

Jim Birch: Midcamp 2016 Recap - Where the Drupal community comes together!

Planet Drupal - 20 April 2016 - 2:20am

MidCamp 2016, the Midwest Drupal Camp was a roaring success.  We had 36 Sessions and 1 keynote were spread across the University of Chicago Student Center West,.  All of the sessions were successfully recorded by our amazing AV team and shared within hours on the Midcamp YouTube channel.  Our sponsor tables were busy; our Birds of a Feather discussions were many; and our socials were social!

This was my second time attending, and my first time being a volunteer organizer.  If you attended, I hope that I got to greet you on the way in.  Attending my first year, I was so awestruck by the amount of knowledge and talent at MidCamp, I couldn't help but get involved.  After volunteering to help, I am still in awe of the dedication of the volunteers, and the effort it takes to put on a camp like this.  Thanks to all of the volunteers for the countless hours put in throughout the year to make this event happen.

Please indulge me a moment while I call out a few individuals specifically for their incredible effort and dedication put forth to MidCamp 2016.

Read more

Categories: Drupal

Drupal Console: Drupal Console and Beer - Enzo join us from Chongqing

Planet Drupal - 20 April 2016 - 1:33am
This time, enzo join us from Chongqing to talk about upcoming presentations on his enzotour 2016. We also talk about lates added features in the 0.11.3 release our very last one before the 1.0.0-alpha1 release. The next upcoming release will be tagged once Drupal 8.1.0 got release.
Categories: Drupal

Nuclear

New Drupal Modules - 20 April 2016 - 1:17am

This module reacts to hooks. It will act on every fieldable entity argument of the hook and then traverse recursively any entity references. Then it will check every field of the entities and check for the third party setting called nuclear and if one is found then it will call the plugin defined there with the arguments found there. For example, if a comment is flagged you can give a badge to the author of the original node.

Categories: Drupal

Three Explanations for Gygaxian Unnaturalism

Gnome Stew - 20 April 2016 - 1:00am


Once upon a time Gygaxian Unnaturalism was the default assumption for DnD. In it, the world essentially plays favorites between PCs and monsters (unfortunately, the favorites are not you) and logic is more or less thrown out the window as far as stocking dungeons. Monsters rarely fight among themselves and will instead team up in odd combinations to fight you, doors refuse to open for you but swing easily for them, rooms are randomly arranged and dressed. In short, the dungeon is a bizarre place more the testing ground of a mad wizard than a realistic ecology simulator.
In limited doses, this may make sense. After all, there probably are some mad wizards out there crafting strange dungeons with little rhyme or reason. But for an entire campaign to operate this way chafes the sensibilities of those who expect their game world to make a little more sense. Here are three explanations why an entire campaign world might operate under a state of Gygaxian Unnaturalism. Players and characters may not be aware of these reasons but discovering them can be a fun campaign arc.

The Live Earth Theory:
Back in the era of Spelljammer, there was a random chance for each newly discovered world to be a “live world”. These looked like standard worlds but were in fact a single massive living entity. Live worlds could easily play host to Gygaxian Unnaturalism. In this case monsters aren’t actually monsters but are instead the immune system of the planet so they’re able to simply spawn from the ground, open stuck doors, detect intruders through walls, and other feats, and they rarely fight with each other unless tricked somehow. Some dungeons aren’t dungeons, but are instead natural channels and pathways within the body of the living planet. Monsters are found here to ward off infection and keep out dangerous outside organisms (In short, you’re adventuring in the ear canal or nostril of the planet. Those piercers and oozes? You know what they are). In addition, irritations or breaks in the surface of the planet are likely to cause immune responses, so settlements and farmland are likely to be attacked by monsters in an attempt to raze them to the ground and remove the “infection”, and man made dungeons are constantly in danger of being overrun from within by monsters.
In this setting most PC races are probably “fallen children” of the planet. Perhaps a few changelings are born that feel the pull of their ancestral duties more closely than others and who secretly seek to undermine their communities from within.
In theory, Gygaxian Unnaturalism could be put to rest on this type of world by essentially stressing the planet’s immune system so much that it becomes suppressed, but this leaves the planet open to the dangers the immune system was fighting against and may even lead to the death of the planet. This would almost certainly lead to a massive ecological collapse and an entire planet’s death would pull legions of undead from the negative plane to feed.

The Lovecraftian Unnaturalism Theory:
One of the outer gods of the Lovecraft mythos (actually the creation of Clark Ashton Smith) could be responsible for a world of Gygaxian Unnaturalism. Abhoth, The Source of Uncleanliness is a massive pool of offal and ooze which constantly spawns abominations of every description. Imagine a world in which Abhoth sits at the core spawning endlessly, his children tunneling upwards, building complexes which make sense only to their own twisted Outre minds. As his children spread and worship, Abhoth’s malign influence grows, and the very walls become aware, guiding his children and hindering those from the outside world.
This is a more standard dungeon crawl, but likely focused on some Lovecraftian themes, such as madness and the inevitability of defeat. It’s also an excellent campaign in which to feature some of the more uncommonly used mechanics such as monsters that require magic weapons or certain metals or elements to permanently kill, and long term damage in the form of madness, drain, or disabilities.
Thanks to the nature of Abhoth, monsters in this campaign are all unique, even if their stat blocks are similar, so mixing groups of enemies more than usual, tweaking abilities and adding extras (a goblin with acid spit riding on an ogre-slug centaur) can add some fun “Jim Henson-esque” moments.
The eventual goal of the campaign might be to slay Abhoth and put an end to his spawn, but this might open the way to other horrors, so perhaps the end goal is just to suppress them, or perhaps it’s to capture and bring back a sample for study (and then stop the mini-Abhoth that is forming underneath the wizard’s study after a drop or two snuck away, because of course it did).

The Divine Judgment Theory:
There are plenty of Divines that have criteria to get into their particular slice of heaven, and there are times that you just barely measure up short. Maybe you were the penultimate berserker, but in the heat of battle, you tripped on someone’s guts and hit your head on a rock. If a god is merciful, they might give you a second shot and have you reincarnated. If you mess that one up too, well eventually they make it easy for you. They put you in a simulated world where all the non-adventuring jobs are taken by simulacra made of divine energy, and the world is set up to push you toward success or failure. You and those like you reincarnate here until you decisively succeed or fail.
This world is all about adventuring to the exclusivity of everything else, so no one expects dungeons to have any sort of logic to them (in fact, they would be confused if you thought to ask them) instead it’s more about opportunities for you to prove yourself worthy through your bravery, cunning, ferocity, or whatever else the gods value.
Interestingly, the attempt to keep reincarnated souls focused on adventure (and not have them accidentally become a baker for example) leads to bits of strangeness as well. Newly reincarnated adventures appear fully formed into the world with their base gear, there are never job openings among non-adventurers (even after a goblin raid decimates the town), sages never study the nature of the universe, etc.
In addition, the gods have better things to do than monitor this pocket universe, so they assign lesser divine beings to do it. This leads to odd glitches here and there, like dungeon walls that change when you look away from them, or an innkeeper who is replaced by his twin brother you’ve never heard about and who occasionally remembers conversations you had with his brother.
While there is no way to end the Gygaxian Unnaturalism of a divine prison, you can get out by succeeding or failing spectacularly. Die gloriously charging a dragon or sniveling for mercy from kobolds and you’re not coming back. However, unlike other options, discovering the nature of the prison makes the world more dangerous. Not only does it forfeit any win or loss you might make this time around (the gods claim it has something to do with faith), if you go shooting off your mouth and cluing in others, you’re likely to draw the attention of the overseers who will attempt to “reset” you with maximum prejudice, and barring that will turn the entire world against you, in a sort of living zombie apocalypse. Good luck.

Categories: Game Theory & Design

How Battleborn blends MOBA design into the multiplayer shooter

Social/Online Games - Gamasutra - 20 April 2016 - 12:59am

Gearbox chief Randy Pitchford paints the studio's upcoming game as both a product of the times (drawing heavy influence from MOBA design) and a return to its roots in competitive multiplayer shooters. ...

Categories: Game Theory & Design

Drupal Blog: Drupal 8.1.0 is now available

Planet Drupal - 20 April 2016 - 12:48am

Drupal 8.1.0, the first minor release of Drupal 8, is now available. With Drupal 8, we made significant changes in our release process, adopting semantic versioning and scheduled feature releases. This allows us to make extensive improvements to Drupal 8 in a timely fashion while still providing backwards compatibility. Drupal 8.1.0 is the first such update.

What's new in Drupal 8.1.x?

Drupal 8.1.0 comes with numerous improvements, including CKEditor WYSIWYG enhancements, added APIs, an improved help page, and two new experimental modules. (Experimental modules are provided with Drupal core for testing purposes, but are not yet fully supported.)

Download Drupal-8.1.0 Experimental UI for migrations from Drupal 6 and 7

Drupal 8.1.0 now includes the Migrate Drupal UI module, which provides a user interface for Drupal core migrations. Use it to migrate Drupal 6 or 7 sites to Drupal 8. The user guide on migrating from Drupal 6 or 7 to Drupal 8 has full documentation. Note that the Drupal 8 Migrate module suite is still experimental and has known issues. Read below for specific information on migrating Drupal 6 and Drupal 7 sites with 8.1.0. (Always back up your data before performing a migration and review the results carefully.)

BigPipe for perceived performance

The Drupal 8 BigPipe module provides an advanced implementation of Facebook's BigPipe page rendering strategy, leading to greatly improved perceived performance for pages with dynamic, personalized, or uncacheable content. See the BigPipe documentation.

CKEditor WYSIWYG spellchecking and language button

Drupal 8.0.0 included the CKEditor module (a WYSIWYG editor), but it was not previously possible to use your browser's built-in spell checker with it to check the text. With Drupal 8.1.0, spellchecking is now enabled within CKEditor as well.

Another great improvement is the addition of the optional language markup button in CKEditor. When configured to appear in your editing toolbar, it allows you to assign language information to parts of the text, which is useful for accessibility and machine processing.

Improved help page with tours

Drupal 8.0.0 included a new system for help tutorials called tours with the core Tour module. In Drupal 8.1.0, we made these tours easier to discover by listing them in the administrative help overview at /admin/help.

The help overview page is also more flexible now, so contributed modules can add sections to it and themes can override its appearance more easily. You can read more about the new system in the change record for the updated help page, or refer to the Tour API documentation for how to add tours for your modules.

Rendered entities in Views fields

Drupal 8.1.0 now includes a rendered entity field handler for Views, which allows placing a fully rendered entity within a view field. For example, this feature could be used to display a rendered user profile for each node author in a table listing node content. (This feature was provided by the Entity contributed module in Drupal 7, but had not yet been available in Drupal 8.)

Support for JavaScript automated testing

Drupal 8.1.0 adds support for automated testing of JavaScript, which will mean fewer bugs with Drupal's JavaScript functionality in the future as we write new tests for it. (Read more about how to run the JavaScript tests.) There are also other improvements to the testing system, including improved reporting of PHPUnit and other test results.

Improved Composer support

Starting with Drupal 8.1.x, Drupal core and its dependencies are packaged by Composer on Drupal.org. This means that sites and modules can now also use Composer to manage all of their third-party dependencies (rather than having to work around the vendor directory that previously shipped with core).

Developer API improvements

Minor releases like Drupal 8.1.0 include backwards-compatible API additions for developers as well as new features. Read the 8.1.0 release notes for more details on the many improvements for developers in this release.

What does this mean to me?
Drupal 8 site owners

Update to 8.1.0 to continue receiving bug and security fixes. The next bugfix release, 8.1.1, is scheduled for May 4, 2016.

Updating your site from 8.0.6 to 8.1.0 with update.php is exactly the same as updating from 8.0.5 to 8.0.6. Modules, themes, and translations may need small changes for this minor release, so test the update carefully before updating your production site.

Drupal 6 site owners

Drupal 6 is not supported anymore. Create a Drupal 8 site and try migrating your data into it as soon as possible. Your Drupal 6 site can still remain up and running while you test migrating your Drupal 6 data into your new Drupal 8 site. Note that there are known issues with the experimental Migrate module suite. If you find a new bug not covered by one of these issues, your detailed bug report with steps to reproduce is a big help!

Drupal 7 site owners

Drupal 7 is still fully supported and will continue to receive bug and security fixes throughout all minor releases of Drupal 8.

The new Migrate Drupal UI for Migrate also allows migrating a Drupal 7 site into a Drupal 8 site, but the migration path from Drupal 7 to 8 is not complete, so you may encounter errors or missing migrations when you try to migrate. That said, since your Drupal 7 site can remain up and running while you test migrating into a new Drupal 8 site, you can help us stabilize the Drupal 7 to Drupal 8 migration path! Testing and bug reports from your real-world Drupal 7 sites will help us stabilize this functionality sooner for everyone. (Search the known issues.)

Translation, module, and theme contributors

Minor releases like Drupal 8.1.0 are backwards-compatible, so modules, themes, and translations that support Drupal 8.0.x will be compatible with 8.1.x as well. However, the new version does include some string changes, minor UI changes, and internal API changes (as well as more significant changes to experimental modules like the Migrate suite). This means that some small updates may be required for your translations, modules, and themes. See the announcement of the 8.1.0 release candidate for more background information.

Categories: Drupal

Wunderkraut blog: Dropcat, a new deploy tool for Drupal

Planet Drupal - 20 April 2016 - 12:24am

In a series of blog posts I am going to present our new tool for doing drupal deploys. It is developed internally in the ops-team in Wunderkraut Sweden , and we did that because of when we started doing Drupal 8 deploys we tried to rethink how we mostly have done Drupal deploys before, because we had some issues what we already had.

In a series of blog posts I am going to present our new tool for doing drupal deploys. It is developed internally in the ops-team in Wunderkraut Sweden , and we did that because of when we started doing Drupal 8 deploys we tried to rethink how we mostly have done Drupal deploys before, because we had some issues what we already had.

What we had - Jenkins and Aegir

Since some years we have been using a combination of Jenkins and Aegir to deploy our sites. 
That work-flow worked, sort off, well for us. And because it was not a perfect match we tried to rethink how we should do deploys with Drupal 8 in mind. 

Research phase

We looked in many directions, like Capistrano and Appistrano, OpenDevShop, platform.sh, Aegir 3 etc. But none of them fitted our current need – we wanted to simplify things, and most of the tools just added another layer that was not a perfect fit for us. Also, it was important to us that the solution should be open source.

We went old school and built our own solution – almost.

Re-use and invent

With Drupal 8 we got to know Symfony in a better way, and Symfony has a console, that also is used by Drupal console project. The advantages in using Symfony console for a base for our deploy flow were big, based on Symfony best practice and using open source projects. Also, drush does a lot of stuff that we need in the deploy process, so that is an important part also. We did not want to re-invent stuff that already worked well.

Enter Dropcat

So we started to build Dropcat (Drop as in Drupal, and cat because… because of cats) and we slowly added more and more stuff to it, and now we have most part of the commands that we need to do a normal deploy, we are still working on one important bit – and that is the rollback – and hopefully when this series of blog posts about Dropcat is finished, we have that in place also.

In next blog post we take a look into how to install dropcat and how th configuration files works. You could check out the Dropcat project on our GitLab server

Categories: Drupal

Yuriy Gerasimov: Visual testing of Drupal.org. BackTrac Case Study

Planet Drupal - 19 April 2016 - 11:18pm

Visual testing is a great technique to keep styles of your website under control. But what other things visual testing can catch? Maybe some problems with functionality?

It is always best to see visual testing on real life projects. In this article we have done testing of Drupal.org website by comparing it with its staging environment and found some interesting issues.

 

Read full article on BackTrac's blog

 

Please leave your comments on BackTrac's blog instead of here. Thanks!

Tags: drupal planet
Categories: Drupal

Mike Ryan: Migration update for Drupal 8.1

Planet Drupal - 19 April 2016 - 12:24pm

For those of you using the migration system under Drupal 8.0.x, with Drupal 8.1 scheduled to release tomorrow, let’s take a look at where the migration ecosystem now stands. We’ll discuss the biggest core API change, then how moving to 8.1 affects various use cases.

Migrations are now plugins

read more

Categories: Drupal

Drupal core announcements: Reinventing Drupal’s User Experience process

Planet Drupal - 19 April 2016 - 12:20pm

The Drupal core product needs to become more engaging and useful right out of the box. Usability testing has shown why. We want to look at how we can change our process to be more efficient and effective.

We learned during the Drupal 8 process, that our way of building the product side of Drupal has many challenges. We propose to adopt a different way of working that avoids current pitfalls and enables a fresher, faster way to iterate on the core product.

The UX-team has started a discussion in the Usability group to explore how we can change our process to allow for more drastic UX changes.

Join the discussion at: Reinventing Drupal’s User Experience process

Categories: Drupal

Paragraphs Previewer

New Drupal Modules - 19 April 2016 - 11:59am

Provides a rendered preview of a paragraph item while on an entity form.
Sponsored by Phase2 Technology.

Categories: Drupal

Survey: First-person shooters are the most popular eSport to watch

Social/Online Games - Gamasutra - 19 April 2016 - 10:54am

When asked by the research arm of PwC which genres they watch, 63 percent of survey respondents who identified as eSports viewers said first-person shooters, as opposed to just 37 percent for MOBAs. ...

Categories: Game Theory & Design
Syndicate content


Google+
about seo