All RPGs and Storygames by Tod Foley are now available at DrivethruRPG and RPGnow. Bring these games to your table!
Mark Shropshire: Demystifying Decoupled Drupal with Contenta CMS Presentation at Drupal Camp Asheville
It was a pleasure to present "Demystifying Decoupled Drupal with Contenta CMS" with Bayo Fodeke at Drupal Camp Asheville 2018 on July 14th, 2018. I want to thank the organizers, volunteers, attendees, presenters, and sponsors for making another awesome year in the beautiful North Carolina mountains. This is one great camp that gets better and better each year. Below you will find the video for my talk and slide deck::
With this module you can simply set breadcrumb for your selected content type or user account without adding the content into menu structure.How to use
In configuration of the module, select the last parent in menu structure that the node or user will use in breadcrumb.
If you don't want to use it for specific content type or user account, just keep it to 'Top navigation' menu which is default.
At the moment, it works only for one menu. You need to define the machine name of the menu to use.
"You keep on adding to the experience, and you see people talk about it later." Ubisoft's Laurent Detoc explores how post-launch support has benefitted games like The Division. ...
Huuuge Games, the company behind the social casino platform Huuuge Casino, is taking aim at casual mobile games through a new publishing branch called Tap Tap Games. ...
That game, Seed, is one of several online titles being build with SpatialOS, tech that leans on cloud-computing to create living, persistent online worlds. ...
In preparation for the minor release, Drupal 8.6.x will enter the alpha phase the week of July 16, 2018. Core developers should plan to complete changes that are only allowed in minor releases prior to the alpha release. (More information on alpha and beta releases.)
Developers and site owners can begin testing the alpha next week.
The 8.7.x branch of core has been created, and future feature and API additions will be targeted against that branch instead of 8.6.x. All outstanding issues filed against 8.6.x will be automatically migrated to 8.7.
All issues filed against 8.5.x will then be migrated to 8.6.x, and subsequent bug reports should be targeted against the 8.6.x branch.
During the alpha phase, core issues will be committed according to the following policy:
Most issues that are allowed for patch releases will be committed to 8.6.x and 8.7.x.
Drupal 8.5.x will receive only critical bugfixes in preparation for its final patch release window on August 1. (Drupal 8.4.x and older versions are not supported anymore and changes are not made to those branches.)
Most issues that are only allowed in minor releases will be committed to 8.7.x only. A few strategic issues may be backported to 8.7.x, but only at committer discretion after the issue is fixed in 8.7.x (so leave them set to 8.7.x unless you are a committer), and only up until the beta deadline.
Roughly two weeks after the alpha release, the first beta release will be created. All the restrictions of the alpha release apply to beta releases as well. The release of the first beta is a firm deadline for all feature and API additions. Even if an issue is pending in the Reviewed & Tested by the Community (RTBC) queue when the commit freeze for the beta begins, it will be committed to the next minor release only.
The release candidate phase will begin the week of August 13, and we will post further details at that time. See the summarized key dates in the release cycle, allowed changes during the Drupal 8 release cycle, and Drupal 8 backwards compatibility and internal API policy for more information.