Devel ladybug

New Drupal Modules - 5 December 2016 - 8:06pm

This module provides the Ladybug PHP Dumper for use with Devel.


The recommended method for installation is via Composer. However, you can still download this module to the contrib folder if you already have both Devel and Ladybug installed.


Just go to admin/config/development/devel and select Ladybug as your preferred PHP Variables Dumper.

Categories: Drupal

Russian officials allege FIFA 17 violates law against gay propaganda

Social/Online Games - Gamasutra - 5 December 2016 - 4:23pm

Russian MPs have reportedly asked regulators to investigate EA for an LBGTQ-inclusive FIFA 17 promo, alleging it turned the game into gay propaganda aimed at minors -- illegal under Russian law. ...

Categories: Game Theory & Design

Palantir:'s Guide to Digital Governance: Private Websites, Intranets and Portals

Planet Drupal - 5 December 2016 - 3:56pm's Guide to Digital Governance: Private Websites, Intranets and Portals's Guide to Digital Governance brandt Mon, 12/05/2016 - 17:56 Scott DiPerna Dec 5, 2016

This is the eleventh installment of’s Guide to Digital Governance, a comprehensive guide intended to help get you started when developing a governance plan for your institution’s digital communications.

In this post we will cover...
  • Questions you should consider specifically related to private websites
  • Why you should think about whether your private site should be a part of your public site
  • Why it's important to serve the needs of site users

We want to make your project a success.

Let's Chat.

Most organizations these days have some form of private area for only staff, group members, constituents, partners, vendors, etc. These sites are sometimes guarded behind a firewall and a user authentication system, sometimes just user authentication, and sometimes simply hidden by obscurity. Most often, though, you can identify one of these types of sites because it requires a login and password and is not generally accessible by the public.

Most of the previous questions, regarding content, organization and design are relevant to internal Web properties as well, but here are a few questions you may want to ask yourself specifically with regard to private websites, intranets, and internal-facing portals:

  • Who owns each one? If they are shared responsibilities, what are the parts and who owns each part?
  • How are accounts distributed and access granted?
  • Who determines access and account creation?
  • What is the process for account creation?
  • What is the criteria for gaining access via an account?
  • Do user accounts have different roles with different permissions?
  • Who are the content editors and creators within the site?
  • How is the site edited and maintained?
  • Are there any workflows or approval processes for content?
  • What distinguishes content that is appropriate for external channels from content that is only appropriate for internal channels?
  • Who will be responsible for determining what is appropriate? And how will they enforce those rules?

Public vs Private

Another important consideration for private websites and intranets, especially if you are planning to build one or redevelop your public website, is whether or not an intranet (or a private website) should be a part of your public website. In other words, should the same system for administering and maintaining your public website be the same system as your intranet or private website?

On the surface, the simple answer may appear to be, “Of course! Wouldn’t that be the most simple and streamlined approach?” Once you dig into the requirements of what you need for your private site, and compare that with the purpose of your public site, you may determine otherwise.


The most common purpose for a public website is to communicate information about your organization to a range of audiences, many of whom are not currently part of your organization. In fact, the primary purpose of your public website, specifically, may be to attract those who are not part of your organization in order to convince them to become part of it. In short, your public website’s primary purpose is likely to be a marketing tool for expanding your message and growing your constituency (membership, clientele, user-base, however you think of them). There is not typically a lot of functional interaction that happens between user and website at this stage, aside from asking visitors to contact you, sign-up up for something, attend an event, purchase a product, or some other interaction that is typically managed by a relatively basic form.

In other words, the necessary functionality for a public, marketing website tends to be fairly light in terms of the weight of its programming logic and requirements.

Intranets and private websites tend to be a different animal. Being private, by definition, means they need to support accounts for users. Having a lot of users logging into a system presents a number of challenges and requirements that can become quite complex. A heavier set of tools are often required, adding more software to the system.

Given that users and authentication credentials are involved, often integrations with user databases or user management systems may be involved, and almost certainly, a higher level of security and encryption becomes necessary.

Usually, when you have a private site or intranet, the needs of users become more transactional than consumption marketing information. Once a user is a member, they no longer need to be sold on the organization; they need to “do” things through the website – use tools, access account information, transmit or receive private data, etc. All of these things require deeper levels of programming, security, and the infrastructure to support it – a lot more heft and complexity than what you need for your marketing website, which probably benefits most from being nimble and quick to deliver relevant content.

Perhaps most important, though, is the organization of information – and this is where many projects that aim to combine a public website with a private intranet get bogged down. Since the two sites address the needs of largely different audiences, the menuing and navigation in sites that aim to serve both public and private needs are often in conflict with themselves. 

Rarely do you want to show navigation, menuing, or content to the public which is meant only for private users. However, how do you then present the private content and way-finding to authenticated users without breaking a design that, in theory, looks appropriate for only the public content and navigation?

As you get into the details of accommodating both public and private needs on a website, what you often find is that you make odd compromises to things you ordinarily wouldn’t (like usability of the site), in order to make the two work together. In truth, given that the audiences for the two sites may have very different needs, and the websites need to serve very different purposes, it is often wise to separate the two, even if that means support of two separate systems. In the end, it is better to serve the needs of the users, such that they can be successful using your websites.


This post is part of a larger series of posts, which make up a Guide to Digital Governance Planning. The sections follow a specific order intended to help you start at a high-level of thinking and then focus on greater and greater levels of detail. The sections of the guide are as follows:

  1. Starting at the 10,000ft View – Define the digital ecosystem your governance planning will encompass.
  2. Properties and Platforms – Define all the sites, applications and tools that live in your digital ecosystem.
  3. Ownership – Consider who ultimately owns and is responsible for each site, application and tool.
  4. Intended Use – Establish the fundamental purpose for the use of each site, application and tool.
  5. Roles and Permissions – Define who should be able to do what in each system.
  6. Content – Understand how ownership and permissions should apply to content.
  7. Organization – Establish how the content in your digital properties should be organized and structured.
  8. URL Naming Conventions – Define how URL patterns should be structured in your websites.
  9. Design – Determine who owns and is responsible for the many aspects design plays in digital communications and properties.
  10. Personal Websites – Consider the relationship your organization should have with personal websites of members of your organization.
  11. Private Websites, Intranets and Portals – Determine the policies that should govern site which are not available to the public.
  12. Web-Based Applications – Consider use and ownership of web-based tools and applications.
  13. E-Commerce – Determine the role of e-commerce in your website.
  14. Broadcast Email – Establish guidelines for the use of broadcast email to constituents and customers.
  15. Social Media – Set standards for the establishment and use of social media tools within the organization.
  16. Digital Communications Governance – Keep the guidelines you create updated and relevant.
Categories: Drupal

Wyrd Games Posts The Other Side Preview Video

Tabletop Gaming News - 5 December 2016 - 3:00pm
Wyrd Games has released a video for their upcoming game, The Other Side, which is launching on Kickstarter on December 14th, 2016. This video details the four starting Allegiances of the game and some of the game’s backstory. It shows off a variety of model renders for the game, giving you a good sense of […]
Categories: Game Theory & Design

Appnovation Technologies: 4 Tips to be an Efficient Tester

Planet Drupal - 5 December 2016 - 2:55pm

To err is human, and coders too, like us are humans and are bound to make mistakes while coding, especially if the needs of the project are complex and if they adhere to the true meaning of agile.

Categories: Drupal

Fantasy Flight Games Previews Jabba the Hutt For Imperial Assault

Tabletop Gaming News - 5 December 2016 - 2:00pm
One of the most notorious crime lords in the galaxy, Jabba the Hutt has a lot of power an influence over the actions of others. With his vast wealth and resources, he can afford to put out large bounties on anyone that crosses him. He can also afford to pay for the best bodyguards around. […]
Categories: Game Theory & Design

Salesforce Term Reference

New Drupal Modules - 5 December 2016 - 1:18pm

Adds a new field mapper to the Salesforce suite of modules to allow using a term reference field. Entity references for content are supported natively by the Salesforce modules, but term references are not unfortunately.

This code is almost entirely based on the work of Mike Christianson and he deserves the credit:

Categories: Drupal

New Releases Available To Order For Eden

Tabletop Gaming News - 5 December 2016 - 1:00pm
The folks over at Happy Games Factory have the latest sets of Eden releases available to order over in their webshop. Nobody can accuse the folks over there from hating Christmas. They’ve got a special, limited edition set made just for it! Klaus and his Minions is the name of the holiday-themed set. I know. […]
Categories: Game Theory & Design

Commerce Login and Pay with Amazon

New Drupal Modules - 5 December 2016 - 12:24pm

This module integrates Login and Pay with Amazon with Drupal and Drupal Commerce.

Amazon Payments provides Amazon buyers a secure, trusted, and convenient way to log in and pay for their purchases on your site. Buyers use Login and Pay with Amazon to share their profile information (name and email address) and access the shipping and payment information stored in their Amazon account to complete their purchase. Learn more at

Categories: Drupal

Warlord Games Taking Pre-Orders For Project Z Spec Ops Lock ‘n’ Load Set

Tabletop Gaming News - 5 December 2016 - 12:00pm
Zombies are running amok in the streets. Resources are becoming more and more scarce as time goes on. The city has lots of opportunities to find what you might need, but there’s also lots of opportunities to run into other scavengers as well as those aforementioned zombies. Only by joining together will you be able […]
Categories: Game Theory & Design

OpenConcept: Inline Form Errors - What They Are and Why they Matter

Planet Drupal - 5 December 2016 - 11:01am

This article was initially posted as a guest blog on The Digital Echidna Blog on December 2, 2016.

Lots of organizations are working hard to see that their IT is accessible to their visitors and staff. Reducing barriers for effective two-way communications is really important for businesses that want to engage fully with their community. Unfortunately, many organizations overlook the many challenges with online web forms.

Organizations who adopted Drupal 7 benefit from having semantic labels associated with their web forms automatically. This is a particular problem with custom built web-forms, but the Drupal community made an effort towards solid accessibility defaults and continues to do so.

Drupal 8 takes web forms further, adding WAI-ARIA to provide additional semantic markup around descriptive text. Drupal 8 is the first CMS to embrace the HTML5 details/summary elements. These elements allows Drupal 8 forms to use fieldsets for what they are intended and avoids the problem of nested fieldsets, which were inevitable in earlier versions of Drupal.

Adding other HTML5 tags to Drupal Core helps build more semantic sites. Users are encouraged to use tags with meaning which help screen-reader users as well as search engines.

The Accessibility Team wasn’t satisfied with this and realized that we needed to address Guideline 3.3 of WCAG 2.0 AA, which states that all users need to:

  • Be aware that an error has occurred and understand what is wrong
  • Be given suggestions for correction of an input error if it is possible
  • Be provided with safeguards to avoid serious consequences resulting from mistakes
  • Have their input checked for errors and be provided an opportunity to correct them.

These really don’t sound that difficult, but unfortunately they are. Brandon Bowersox-Johnson spearheaded this back in 2012 outlining what needed to happen.

This required many changes to Drupal’s Form API, which is used on almost every Drupal admin page and with all of its web forms. An issue to address this was started later that year in the Drupal issue queue and Inline form errors for accessibility and UX resulted in over 600 comments over four years.

It also got into Drupal Core, although not for very long. It became clear that there were a number of regressions which were major enough that Drupal 8 could not be released without their being fixed. Rather than continue to hold up the release, the community decided to roll this back into an Experimental Core module.

This was absolutely the right call for 8.0. More attention has gone into the many sub-issues and several of them have been fixed. Drupal Core needs to be stable and predictable. Several developers have been very active in trying to fix these issues. In no particular order I’d like to highlight just some of the folks who have contributed to addressing these issues: Pieter Frenssen, Tim Plunkett, Baris Wanschers, Daniël Smidt, and Scott Carpenter.

There has been a lot of effort from some really smart folks going into this very important issue. Unfortunately it isn’t enough. Inline Form Errors need to be enabled by default. Everyone benefits from this better UI. Right now only a small fraction of Drupal 8 sites have enabled this module, because it is an optional Experimental Module and there are serious warnings included with it.

This module is also slated to be removed from Core and brought in as a regular Contrib module. There are good reasons to do this, but it makes it less likely that this improved pattern will ever get into Core.

This is not a trivial request, but it is an important one. For all agencies who are legally required to meet WCAG 2.0 AA, this is an area where your site likely fails. Although there are workarounds that can be done for individual sites and specific modules, we really need a centralized solution for this.

Please consider investing time or money in addressing this outstanding Drupal 8 meta issue and seeing that Drupal remains a leader in this space.

Topic: Primary Image: 
Categories: Drupal

Monday Terrain Corner

Tabletop Gaming News - 5 December 2016 - 11:00am
It’s Monday and I’m back in the office after a long weekend. Unfortunately, gaming plans fell through, but it was still a decent weekend. There’s always next week. Gotta get my S3 Guild Ball on at some point. But at the moment it’s about making your gaming tables look good. Today in the Terrain Corner […]
Categories: Game Theory & Design

Initiative Magazine Issue 4 Now Available

Tabletop Gaming News - 5 December 2016 - 10:00am
See? I told you that there were a couple new magazines available for your reading pleasure. If you want to fill every part of your day with gaming, having some of these on hand while you’ve got a bit of time (waiting for an appointment, on a lunch break, on the bus/train, hanging out at […]
Categories: Game Theory & Design


New Drupal Modules - 5 December 2016 - 9:31am

The Distance Cataloging Interface (DCI) was built as a way to collect and review feedback on specified content on a Drupal website from it's users.

Categories: Drupal

Ironwatch Issue 52 Now Available

Tabletop Gaming News - 5 December 2016 - 9:00am
Here in the South, it’s usually a bit of a seesaw this time of year in terms of temperature. One day it’s cold and rainy. The next it’s not so bad out again. During those cold and rainy days, it’s definitely nice to just stay in and read a gaming magazine. Thankfully, there’s some new […]
Categories: Game Theory & Design

Drupal core announcements: Global virtual UX sprint day on December 9, 2016

Planet Drupal - 5 December 2016 - 8:22am
Start:  2016-12-09 (All day) Europe/Amsterdam Organizers:  yoroy Event type:  Sprint

On Friday, December 9 we are organizing a global virtual Drupal UX sprint. As always, many different features and projects are currently worked on. We'll use this day to work on issues that need UX input or feedback.

What will happen that day?

Join the #ux channel on (get an invite automatically at to participate all day.

  • UX mentors will be available to help onboard designers who want to contribute
  • We'll pair designers and devs (as available) to work on actionable tasks
  • Planning to do some ad hoc usability testing
  • An introduction to the main strategic initiatives and their UX components will be provided
Join the team

You can join us even after the global UX sprint. We have meetings every Tuesday at 9pm CEST and every Wednesday at 9am CEST on the #ux Slack channel at (get an invite automatically at Bring your issues there to discuss! CEST is the timezone observed in Amsterdam.

Categories: Drupal

Asmodee Previews Gameplay in Watson & Holmes

Tabletop Gaming News - 5 December 2016 - 8:00am
Being a detective isn’t easy. There’s rarely enough evidence on-hand to immediately catch the criminal. Witnesses can be unreliable, or might even be the culprit, looking to send you on wild goose chases with false information. Also, other detectives are on the case, and if you want to be the famous detective that solved the […]
Categories: Game Theory & Design

Drupal Modules: The One Percent: Drupal Modules: The One Percent — Markup (video tutorial)

Planet Drupal - 5 December 2016 - 7:56am
Drupal Modules: The One Percent — Markup (video tutorial) NonProfit Mon, 12/05/2016 - 09:56 Episode 9

Here is where we bring awareness to Drupal modules running on less than 1% of reporting sites. Today we'll consider Markup, a module which allows you to insert additional markup on the node/edit form just for content authors.

Categories: Drupal

Video Game Deep Cuts: A Majestic Dishonored Easter Egg - by Simon Carless Blogs - 5 December 2016 - 7:13am
The latest Video Game Deep Cuts, picking the smartest longform video game articles and videos of the week, examines Dishonored 2, the making of Majestic & GTA V's Easter Eggs.
Categories: Game Theory & Design

Fantasy Flight Games Previews Phoenix Home For Star Wars Armada

Tabletop Gaming News - 5 December 2016 - 7:00am
Not every ship in your armada is going to be the “big guns, blow apart the enemy” sort of ship. There are going to be those ships that simply make all your other ships more “big guns, blow apart the enemy.” That’s what you get with the Phoenix Home. You’re not going to be scratching […]
Categories: Game Theory & Design


Subscribe to As If Productions aggregator