All RPGs and Storygames by Tod Foley are now available at DrivethruRPG and RPGnow. Bring these games to your table!
This new award is interesting because it prominently highlights how important the care and feeding of live games has become in contemporary game dev, especially for big-budget studios. ...
Drupal developers have been shouting node id numbers across tables at sprints for almost 15 years now. The Drupal Association has added some shortcuts and friendly urls for issues to make this a little easier.Shortcuts
The first shortcut we added is a searchbar feature. If you enter any node id in the search bar you'll be automatically redirected to that node. This works for more than just issues!
The second shortcut we added is a quick url pattern for finding issues. If you know your node id, just type:https://drupal.org/i/<node-id>
and you're there!Friendly-Urls
We've implemented a new friendly url pattern on Drupal.org to make the canonical urls more sensible and search engine friendly.
Project pages: https://drupal.org/project/drupal
Issue Queue: https://drupal.org/project/issues/drupal
Specific Issue: https://drupal.org/project/issues/drupal/2922626
This new pattern should be backfilled to all issues by the beginning of next week.
And of course, if you have old bookmarks linked, you can still get there by going to: https://drupal.org/node/<node-id>
These are small, but powerful improvements that should make the lives of everyone who contributes to the Drupal project easier.
Facets taxonomy tree provides a facet processor that allows you to show the entire taxonomy tree with out having to have all the term ids in the index. It plays well with facets hierarchy processor.
This module provides the ability to remove some meta and link tags from the source code.
You can unset, for example, the generator meta tag or the shortlink link tag.
The Surgeon Simulator dev previously said it would cancel its in-development skateboarding game if it did not attract 100,000 players during an open beta week. ...
Adds a new Formatter for Link type Fields that makes use of the Zurb Foundation 6 Responsive Embed component.
This module provides users to see theirs recently viewed ubercart products.
For anonymous users recently viewed products listing will get cleared once browsers session expires.
This module allows you to use custom menus as administrative toolbars for different roles.
The main idea behind this module is to have complete control over administrative toolbar for non-technical roles that do not need to have the full access to Drupal backend.
There are two main issues with the standard solutions such as the core "Toolbar" or "Admin Menu" modules:
This blog has been re-posted with permission from Dries Buytaert's blog. Please leave your comments on the original post.
In my blog post, "A plan for media management in Drupal 8", I talked about some of the challenges with media in Drupal, the hopes of end users of Drupal, and the plan that the team working on the Media Initiative was targeting for future versions of Drupal 8. That blog post is one year old today. Since that time we released both Drupal 8.3 and Drupal 8.4, and Drupal 8.5 development is in full swing. In other words, it's time for an update on this initiative's progress and next steps.8.4: a Media API in core
Drupal 8.4 introduced a new Media API to core. For site builders, this means that Drupal 8.4 ships with the new Media module (albeit still hidden from the UI, pending necessary user experience improvements), which is an adaptation of the contributed Media Entity module. The new Media module provides a "base media entity". Having a "base media entity" means that all media assets — local images, PDF documents, YouTube videos, tweets, and so on — are revisable, extendable (fieldable), translatable and much more. It allows all media to be treated in a common way, regardless of where the media resource itself is stored. For end users, this translates into a more cohesive content authoring experience; you can use consistent tools for managing images, videos, and other media rather than different interfaces for each media type.8.4+: porting contributed modules to the new Media API
The contributed Media Entity module was a "foundational module" used by a large number of other contributed modules. It enables Drupal to integrate with Pinterest, Vimeo, Instagram, Twitter and much more. The next step is for all of these modules to adopt the new Media module in core. The required changes are laid out in the API change record, and typically only require a couple of hours to complete. The sooner these modules are updated, the sooner Drupal's rich media ecosystem can start benefitting from the new API in Drupal core. This is a great opportunity for intermediate contributors to pitch in.8.5+: add support for remote video in core
As proof of the power of the new Media API, the team is hoping to bring in support for remote video using the oEmbed format. This allows content authors to easily add e.g. YouTube videos to their posts. This has been a long-standing gap in Drupal's out-of-the-box media and asset handling, and would be a nice win.8.6+: a Media Library in core
The top two requested features for the content creator persona are richer image and media integration and digital asset management.
The results of the State of Drupal 2016 survey show the importance of the Media Initiative for content authors.
With a Media Library content authors can select pre-existing media from a library and easily embed it in their posts. Having a Media Library in core would be very impactful for content authors as it helps with both these feature requests.
During the 8.4 development cycle, a lot of great work was done to prototype the Media Library discussed in my previous Media Initiative blog post. I was able to show that progress in my DrupalCon Vienna keynote:
The Media Library work uses the new Media API in core. Now that the new Media API landed in Drupal 8.4 we can start focusing more on the Media Library. Due to bandwidth constraints, we don't think the Media Library will be ready in time for the Drupal 8.5 release. If you want to help contribute time or funding to the development of the Media Library, have a look at the roadmap of the Media Initiative or let me know and I'll get you in touch with the team behind the Media Initiative.
The original module was called the Dual Language Editor (DLE). It was made for Drupal 7 and had a lot of workarounds to try and solve a problem which was made nearly insurmountable by the procedural coding.
With the introduction of Drupal 8 and the Object Oriented nature of the Symfony framework it leverages, we can now better leverage the various APIs and drastically reduce the lines of code from the previous version of the module.