Newsfeeds

Gábor Hojtsy: Want to get issues resolved in Drupal core? Find community with an initiative!

Planet Drupal - 24 August 2016 - 5:36am

In my previous post I explained why there will be a Drupal 9 even though we have previously unseen possibilities to add new things within Drupal 8.x.y. Now I'd like to dispel another myth, that initiatives are only there to add those new things.

Drupal 8 introduced initiatives to the core development process with the intention that even core development became too big to follow, understand or really get involved with in general. However because there are key areas that people want to work in, it makes sense to set up focused groups to organize work in those areas and support each other in those smaller groups. So initiatives like Configuration Management, Views in Core, Web Services, Multilingual, etc. were set up and mostly worked well, not in small part because it is easier to devote yourself to improving web services capabilities or multilingual support as opposed to "make Drupal better". Too abstract goals are harder to sign up for, a team with a thousand people is harder to feel a member of.

Given the success of this approach, even after the release of Drupal 8.0.0, we continued using this model and there are now several groups of people working on making things happen in Drupal 8.x. Ongoing initiatives include API-first, Media, Migrate, Content Workflows and so on. Several of these are primarily working on fixing bugs and plugging holes. A significant part of Migrate and API-first work to date was about fixing bugs and implementing originally intended functionality for example.

The wonder of these initiatives is they are all groups of dedicated people who are really passionate about that topic. They not only have plan or meta issues linked in the roadmap but also have issue tags and have regular meeting times. The Drupal 8 core calendar is full of meetings happening almost every single workday (that said, somehow people prefer Wednesdays and avoid Fridays).

If you have an issue involving usability, a bug with a Drupal web service API, a missing migration feature and so on, your best choice is to bring it to the teams already focused on the topics. The number and diverse areas of teams already in place gives you a very good chance that whatever you are intending to work on is somehow related to one or more of them. And since no issue will get done by one person (you need a reviewer and a committer at minimum), your only way to get something resolved is to seek interested parties as soon as possible. Does it sound like you are demanding time from these folks unfairly? I don't think so. As long as you are genuinely interested to solve the problem at hand, you are in fact contributing to the team which is for the benefit of everyone. And who knows, maybe you quickly become an integral team member as well.

Thanks for contributing and happy team-match finding!

Ps. If your issue is no match for an existing team, the friendly folks at #drupal-contribute in IRC are also there to help.

Categories: Drupal

Zyxware Technologies: [Drupal-8] How to send a mail programmatically in Drupal-8

Planet Drupal - 24 August 2016 - 5:33am

This article covers, how to send email programmatically in your Drupal 8 site. There are two main steps to send an email using Drupal 8. First we need to implement hook_mail() to define email templates and the second step is to use the mail manager to send emails using these templates. Let's see an example for sending an email from the custom module, also the following name spaces.

DrupalDrupal 8Drupal Planet
Categories: Drupal

Unimity Solutions Drupal Blog: Identification of an Open Source Video Annotations Tool for NVLI

Planet Drupal - 24 August 2016 - 5:00am

As mentioned in our earlier blog on Video Annotations: A powerful and innovative tool for education, the most intriguing feature of the pilot version of NVLI is Video Annotation. UniMity Solutions assisted in building Annotation feature for Audio and Video assets. This involved identifying and integrating an open plugin that supported video and audio annotations and a generic annotation store module that was plugin agnostic.

Categories: Drupal

Support Gnome Stew On Patreon – Help Us Make Awesome Articles

Gnome Stew - 24 August 2016 - 2:05am


Three weeks ago, at Gencon, I got to wear the Golden ENnie award medal for Gnome Stew’s Best Website award. I very nearly had a legendary wardrobe malfunction to prove it. Receiving the ENnie is a huge honor, and one that I am very proud I get to be a part of. Our Gnome Stew Patrons moved me in a more personal way. At Gencon, our Patreon exceeded $100, which allowed us to open a beautiful can of worms by providing some good compensation to our authors and letting us increase the sort of content we can bring to the Stew. Finding out our Patreon peaked $100 on the same night as winning the ENnie was incredible.

There is more we’d like to be able to do, like paying our incredible authors more for their writing and sharing some of that with the incredible guest authors who submit articles.  So, we’d like to ask you to help us do that by contributing to the Patreon. If you’ve enjoyed reading any of  Gnome Stew’s articles over the past 8 years, we’d love it if you would consider becoming a patron, even at a small amount, such as $1 a month. We think of our Patreon largely as a “tip jar”, since our content is free to everyone. It’s a way for readers to say thanks and help us make more awesome stuff that we get to share with everyone. We will always keep the Stew free for all of our fans, but becoming a patron is an act of trust in what we Gnomes will create in the future.

My plan to Scrooge McDuck in our room full of copper pieces was sadly shot down, but here are a few things that you can look forward to soon, thanks to our amazing patrons!

 

Work (the blog) Harder

Our Patreon’s first task is to compensate authors (THANK YOU!), so we can take a little more time and dig a more deeply with the articles you already love. Being able to pay authors will help us bring in more guests to bring exciting new content, spicing up the Stew while maintaining that hearty, comforting deliciousness you’ve always known. We can also work towards our goals of bringing in authors with more diverse gaming and personal backgrounds to provide different perspectives on the industry and give some signal boost to different voices.

Make (our content) Better

We’ve dabbled with multimedia articles (see our review of Adventure Scents, Smell-O-Vision still in the beta stage) and have more of these sorts of things being prepared in our prep kitchen – the Patreon helps us invest in the extras like video editing or buying art. More than that, though, we have in the works an entire web video series to bring more people into gaming! It’s projects like these that we authors at Gnome Stew can make happen.  You might know that some of our gnomes are venue-promiscuous and can be found giving GM advice on myriad  different podcasts. If our Patreon reaches $230 per month, we’ll create #GnomeCast: a podcast for your earholes under your tiny conical hats, filled with the dulcet tones of our Gnome Authors expanding on articles and talking about other gaming topics. Input from the patrons will help shape what this becomes!

For you game masters out there, get excited: our Patreon will help us produce new system-neutral Game Mastering books like Masks (1,000 NPCs for any game) & Eureka (501 Adventure Plots). Seriously, look at these reviews. It’s gonna be great, and we’ll be able to produce some really cool things for Game Masters and players alike. I think you’ll love the new ways we’re planning to make your sessions easier and better.

My big personal passion is the upcoming launch of Gnome Spotlight – a blog series bringing you brightness in gaming. Our RPG community and industry has grown and diversified and done amazing, innovative things. There is a lot of important critique being done to help our #NotACasualHobby improve, but we want to make a place that focuses on and celebrates the good being done. Gnome Spotlight will be your regular dose of heart-warming gaming goodness.

Do (community feedback) Faster   

The Patreon gives us another home to chat with fans and lets us dynamically respond to ideas about the Stew and the Patreon itself. Want MOAR STICKERS as a pledge level? Of course you do. Want a pledge level to have Darcy to run a lewd AP of Maid the RPG? Let’s talk. The Patreon will also be a great place for us to leave you patrons increasingly weirder expressions of our appreciation, which started with the ENnies dinner night video and will only get stranger the more of our own devices we are left to!

 

Makes (the Gnome Stew community) Stronger

We’re not just referencing Daft Punk lyrics here. Every dollar put into the Patreon is one we intend to pay back in one way or another. Patreon dollars paid out to the Gnome Stew authors have already gone toward Gnomes buying new gaming PDFs so that we can cover them on the Stew, as well as donations to game designers in medical need. We’re also looking at ways to increase the community outreach and connect with our readers in more ways, like running online games or providing feedback to reader projects from Gnome Stew. The Gnome Stew reader community is kind, insightful, and generous in so many ways, and we hope you’ll share a bit of that with us through the Patreon.  So please consider checking out the patreon and supporting us, even at a small amount monthly. Every small bit helps and we hope to be able to continue providing awesome, free, gaming articles well into the future with your help. I eagerly await to see what cool things we are going to do together!

What sort of projects would you be most excited for from Gnome Stew? What sorts of things would you like Gnome Stew to do in the future? Are there any changes to our Patreon structure that might make you back it?

Categories: Game Theory & Design

The Deep, Dark Secret of No Man's Sky: You're The Bad Guy - by Sean May

Gamasutra.com Blogs - 24 August 2016 - 12:32am
No Man's Sky casts the player as a lone explorer, flung into a vast universe of untold riches and possibilities...but, that doesn't mean you're playing as a hero.
Categories: Game Theory & Design

Drupal Bits at Web-Dev: Import nodes as as part of deployment using Hook Update Deploy Tools

Planet Drupal - 23 August 2016 - 8:52pm

With the 7.x-1.18 release of Hook Update Deploy Tools for Drupal 7 it is now possible to export a node on a development sandbox, commit the export file to the repository, then import it using either a hook_update_N() or using drush site-deploy-import node

Pros:

  • No need to re-create a node on prod after a client approves it.
  • Early content that keeps getting wiped out by database snapshots (think style guides) can get re-created instantly with a single drush command.
  • Content imported into an existing node shows up as a revision.
  • Atomated deployment is testable and repeatable on all dev environments.
  • No uuid required.
Workflow Example:

You have a styleguide you created on your sandbox and want to deploy it to the production site.

  1.  Create the node on your sandbox (node id = 1234).
  2. Export the node to an export file.
    drush site-deploy-export 1234
  3. The command created an export file named  for the alias of the node being exported
    ex: site-deploy/node_source/helpzZzstyle-guide.txt  ('zZz' represents '/')
  4. Create a hook_update_N() to import the file on deployment
     

    <?php
    /**
     * Import a the style guide
     */
    function site_deploy_update_7129() {
      $nodes = array('help/style-guide');
      $message = HookUpdateDeployTools\Nodes::import($nodes);
      return $message;
    }
    ?>
  5. Commit the file and update hook to your repo.
  6. Push the code, run 'drush updb'
drush updb -y
Site_deploy  7129  Import a the style guide

Site_deploy: Updated: node/1234: help/style-guide - successful.
Summary: Imported Nodes 1/1.  Completed the following:
   [help/style-guide] => Updated: node/1234
  
Performed update: site_deploy_update_7129

or the import can be performed by

drush site-deploy-import  help/style-guide
Categories: Drupal

Drupal @ Penn State: Drupal 8 Theme Generation and Development Intro Using the Drupal Console

Planet Drupal - 23 August 2016 - 4:56pm

Here is a screen cast of how to get started with Drupal 8 theme development.

In the video I cover:

  • using the drupal console to generate a theme from a base theme
  • creating a libraries yml file
  • adding global css to your theme
  • Using Kint with the devel module
  • debugging twig
  • adding your own twig file to your theme
Categories: Drupal

Drupal @ Penn State: Lower the Drupal 8 development barrier to entry by using the Drupal Console to generate boiler plate code.

Planet Drupal - 23 August 2016 - 4:56pm

I admit that I haven't really looked at Drupal 8 too much yet. There is a variety of reasons why I haven't and I surely don't want this to turn into a forum listing the pros and cons of D8. We can leave that for another post. 

Categories: Drupal

Drupal @ Penn State: The Care and Feeding of Your Website

Planet Drupal - 23 August 2016 - 4:56pm

A question on the PSU DUG Slack channel got me thinking. How is it that websites are still being constructed at Penn State without any thought being put in as to how its is going to be maintained? Or by whom?  

To be clear, I am not talking about content creation or maintenance, but maintaining the code/server/DB/etc. that supports or runs the site? Or to develop new features and functionality, going beyond just updating code or applying security patches. Of course, this is not restricted to Drupal development - there are many other examples.

Categories: Drupal

PreviousNext: Introducing Drush CMI tools

Planet Drupal - 23 August 2016 - 4:46pm

Now we've got the experience of a number of production D8 sites under our belt we took the time to consolidate our CMI workflow into some useful drush commands.

And naturally we've open sourced them.

Read on to find out more about our drush CMI tools.

Categories: Drupal

GVSO Blog: [GSoC 2016: Social API] Week 13: Thanks GSoC!

Planet Drupal - 23 August 2016 - 3:07pm
[GSoC 2016: Social API] Week 13: Thanks GSoC! Submitted by gvso on Tue, 08/23/2016 - 18:07

Students' final evaluations is over, and only mentors' evaluations is left. During these months, I have been working on projects to harmonize social networking functionality in Drupal and documenting them. Notwithstanding, the Social API project started as an idea for a framework in fact, the main components provide extensible functionality. Therefore, I documented the process of creating new implementers.

Tags Drupal Drupal Planet GSoC 2016
Categories: Drupal

Roy Scholten: UX meeting recap

Planet Drupal - 23 August 2016 - 2:58pm

Two meetings every week since end of march this year. Safe to say we’ve found a consistent rhythm.

And it’s working. It’s become a useful way to check in on current priorities, review patches while screensharing (visuals, transitions, flows!), decide on next steps and generally discuss hard problems without having to type so much.

The agenda for today was
  1. Roadmap – The core roadmap was updated to current state of things. Use this page to get a bird’s eye view on where Drupal core is moving towards.
  2. Ideation process – The first part of going from idea to plan got positive feedback and helpful questions and suggestions. Maybe a few words from actual maintainers and then we can make it so.
  3. Status page – We have a beautiful new design that now needs review and more code to create a complete patch. If you know your core markup and CSS, go have a look!
  4. Block place design update – An issue that iterates the design of an initial commit. We quickly discussed what the feedback should be and I added a comment to that effect right then and there. It’s an example of managing scope, pushing to focus on the actual fix first, and defer new, potentially good ideas to a followup discussion.
  5. Sample content – Kevin shared his initial thoughts and ideas for adding sample content, structure and configuration to core. More questions then answers but that’s just where we’re at for now. You are welcome to add your questions and ideas, please do.

As always, most welcome to join if you’re interested. Find us in the ux channel of the Drupal Slack room, or follow @drupalux on the twitters.

Tags: drupaluxuxmeetingdrupalplanetSub title: Topics du jour, how we work, where you can help, the usual
Categories: Drupal

Mantic Gaming Hall &#038; Shop Open for Visitors

Tabletop Gaming News - 23 August 2016 - 2:00pm
Many of us have a favorite gaming spot. Whether it’s a gaming club, a FLGS, or just a friend’s living room, garage, or basement, there’s the spot where we get together with our fellow gamers to throw down. Well, there’s going to be a new spot available for you to get your gaming on: Mantic’s […]
Categories: Game Theory & Design

Vile Villains Tag Team Release From Okumarts Games

Tabletop Gaming News - 23 August 2016 - 1:00pm
Superheroes are kind of a big thing these days. With the rise of both Marvel and DC movie series, people are clamoring for others in bright, spandex suits like never before. Many people want to bring that excitement to their tabletop. Okumarts Games lets you do that with their Save the Day super-powered RPG. But […]
Categories: Game Theory & Design

Drupal Blog: Drupal 8.2, now with more outside-in

Planet Drupal - 23 August 2016 - 12:14pm

Over the weekend, Drupal 8.2 beta was released. One of the reasons why I'm so excited about this release is that it ships with "more outside-in". In an "outside-in experience", you can click anything on the page, edit its configuration in place without having to navigate to the administration back end, and watch it take effect immediately. This kind of on-the-fly editorial experience could be a game changer for Drupal's usability.

When I last discussed turning Drupal outside-in, we were still in the conceptual stages, with mockups illustrating the concepts. Since then, those designs have gone through multiple rounds of feedback from Drupal's usability team and a round of user testing led by Cheppers. This study identified some issues and provided some insights which were incorporated into subsequent designs.

Two policy changes we introduced in Drupal 8—semantic versioning and experimental modules—have fundamentally changed Drupal's innovation model starting with Drupal 8. I should write a longer blog post about this, but the net result of those two changes is ongoing improvements with an easy upgrade path. In this case, it enabled us to add outside-in experiences to Drupal 8.2 instead of having to wait for Drupal 9. The authoring experience improvements we made in Drupal 8 are well-received, but that doesn't mean we are done. It's exciting that we can move much faster on making Drupal easier to use.

In-place block configuration

As you can see from the image below, Drupal 8.2 adds the ability to trigger "Edit" mode, which currently highlights all blocks on the page. Clicking on one — in this case, the block with the site's name — pops out a new tray or sidebar. A content creator can change the site name directly from the tray, without having to navigate through Drupal's administrative interface to theme settings as they would have to in Drupal 7 and Drupal 8.1.

Making adjustments to menus

In the second image, the pattern is applied to a menu block. You can make adjustments to the menu right from the new tray instead of having to navigate to the back end. Here the content creator changes the order of the menu links (moving "About us" after "Contact") and toggles the "Team" menu item from hidden to visible.

In-context block placement

In Drupal 8.1 and prior, placing a new block on the page required navigating away from your front end into the administrative back end and noting the available regions. Once you discover where to go to add a block, which can in itself be a challenge, you'll have to learn about the different regions, and some trial and error might be required to place a block exactly where you want it to go.

Starting in Drupal 8.2, content creators can now just click "Place block" without navigating to a different page and knowing about available regions ahead of time. Clicking "Place block" will highlight the different possible locations for a block to be placed in.

Next steps

These improvements are currently tagged "experimental". This means that anyone who downloads Drupal 8.2 can test these changes and provide feedback. It also means that we aren't quite satisfied with these changes yet and that you should expect to see this functionality improve between now and 8.2.0's release, and even after the Drupal 8.2.0 release.

As you probably noticed, things still look pretty raw in places; as an example, the forms in the tray are exposing too many visual details. There is more work to do to bring this functionality to the level of the designs. We're focused on improving that, as well as the underlying architecture and accessibility. Once we feel good about how it all works and looks, we'll remove the experimental label.

We deliberately postponed most of the design work to focus on introducing the fundamental concepts and patterns. That was an important first step. We wanted to enable Drupal developers to start experimenting with the outside-in pattern in Drupal 8.2. As part of that, we'll have to determine how this new pattern will apply broadly to Drupal core and the many contributed modules that would leverage it. Our hope is that once the outside-in work is stable and no longer experimental, it will trickle down to every Drupal module. At that point we can all work together, in parallel, on making Drupal much easier to use.

Users have proven time and again in usability studies to be extremely "preview-driven", so the ability to make quick configuration changes right from their front end, without becoming an expert in Drupal's information architecture, could be revolutionary for Drupal.

If you'd like to help get these features to stable release faster, please join us in the outside-in roadmap issue.

Thank you

I'd also like to thank everyone who contributed to these features and reviewed them, including Bojhanyoroypwolaninandrewmacphersongtamaspetycompzsofimajor,SKAUGHTnod_effulgentsiaWim Leerscatchalexpott, and xjm.

And finally, a special thank you to Acquia's outside-in team for driving most of the design and implementation: tkolearywebchicktedbowGábor Hojtsytim.plunkett, and drpal.

Acquia's outside-in team celebrating that the outside-in patch was committed to Drupal 8.2 beta. Go team!

Categories: Drupal

WizKids Announce Rock Paper Wizard Card Game

Tabletop Gaming News - 23 August 2016 - 12:00pm
Pretty much everyone knows Rock, Paper, Scissors. Some even know the extended version with Lizard and Spock thrown in. So a game where certain hand gestures are required shouldn’t be anything new to people. WizKids is getting themselves in on the action with Rock Paper Wizard, a new card game in collaboration with Wizards of […]
Categories: Game Theory & Design

Sony is bringing its PlayStation Now game streaming service to PC

Social/Online Games - Gamasutra - 23 August 2016 - 11:49am

More than a year after its official debut, Sony's PlayStation Now game streaming service is being prepped for launch on PC and Mac in the U.S. and Europe. ...

Categories: Game Theory & Design

Podcast Roundup

Tabletop Gaming News - 23 August 2016 - 11:00am
So yeah, while Monday follows the weekend, so does Tuesday follow Monday and we work our way fully into the week. Eventually we’ll swing back around and get to the weekend. Personally, I’m looking to try and do some cooking this weekend. I’ve not really cooked anything major in a while. I need to change […]
Categories: Game Theory & Design

Cacheable Cookie Handling

New Drupal Modules - 23 August 2016 - 10:44am

This module provides a framework for setting cookies that works well with page caching. It does not do anything on its own, but rather provides an API that other modules can use.

Categories: Drupal

Star Map 02

New RPG Product Reviews - 23 August 2016 - 10:00am
Publisher: DramaScape
Rating: 4
A nice space map containing a planet with a nebula in the background. The product contains a 67 page pdf with instructions and 62 pages of maps - including hex, square, and no grid options for printing. MapTool and other VTT users will also find a jpg file for use in virtual gaming.

The map was created for a war-gaming scenario titled Space Refugees but it is easily adaptable for other needs, including a scenario backdrop for a space adventure. It's a nice product for the price.
Categories: Game Theory & Design

Pages

Subscribe to As If Productions aggregator