Wyvernseeker Rock

New RPG Product Reviews - 10 June 2019 - 6:58am
Publisher: Aegis Studios
Rating: 4
This jumps straight in with the party travelling through the Untamed Gauntlet on other business, when the stream they are following abruptly ends in a cliff with a waterfall. It's too steep and slippery to climb up, the obvious route up is through an opening beside the waterfall.

There's a top-down view, a plan of the pathway through the cliff, and descriptions of the five chambers therein. To enter, the party needs to solve a puzzle: instructions for the die rolls required to solve it are given, but there's no actual puzzle given. Personally I prefer to let the party at the puzzle, and suggest die rolls if they get nowhere with it. Once they get in, there's a long spiral staircase going up (and down, but that's another story) which will let them get to the top of the cliff, provided they get past the monsters and other hazards.

Once they reach the top, they've actually come out at the top of a rocky peak even higher than the cliff. Here there's a cunning device that you can use to provide a hook into further adventures, a vision that gives them some inkling as to what is in store...

This is a rather thin 'something to happen along the way' which rather leaves you wondering why. Quite nice if you struggle to find ways to make wilderness travel interesting apart from reaching for the wandering monsters table. It could possibly be strung out into a complete session (2-3 hours) but that would be a bit of a struggle.
Categories: Game Theory & Design


Gnome Stew - 10 June 2019 - 5:00am

Obligatory recap: I’ve read about a system for creating urbancrawls (similar to hexcrawls but set in a city) from The Alexandrian. I had also been enjoying the Sorcery! gamebooks by Steve Jackson and their strange magic setting. Enter this series of articles, where I use The Alexandrian’s urbancrawl system to design my own urbancrawl with a strange magic theme.


We left off last time with:

  • a list of districts
  • a definition of what a neighborhood was
  • a list of layers we were going to use
  • a rough map
  • a neighborhood list
  • neighborhood breakdowns for the Temple, Palace, Ruins, Crafting, and Bazaar districts

This is the last installment where I outline neighborhoods. This time I’m tackling the final districts: the slums. Next time I’ll start working with layers (multiple encounter keys).

Here’s the (very rough) map. It’s just a set of neighborhoods surrounded by the city walls and bordered by the wall, the five major rivers, the major roadways, and the shores of the central lake. Note that none of those have names at this point. This is just one step up from a sketch, and then only because I figured using software would result in a slightly more readable result than hand drawing it.  Districts are color coded, Neighborhoods are labeled with a key. We’re also not going to name them at this point either. That’s something we can handle later and something that takes up an awful lot of brain space and time while being subject to change if the neighborhood map or list changes under it.

  • S – Slums: This is actually two districts, the northern and southern slums, noted as NS and SS. Like all other districts, the outer areas of slum neighborhoods also host shops, but the goods to be found here are usually inferior or of a questionable nature. Residential areas are overcrowded and dirty. Public areas are all but nonexistent. Buildings are mostly made of wood and are in poor condition. In many places, structures are crowded close together or touching. Unless otherwise noted, homes in slum neighborhoods are simple and usually one room. Shops are mostly one or two rooms, and contain an attached bedroom for the proprietor. Public areas are small, poorly kept and often inhabited by those with nowhere else to go.
    • NS1 – Chokestreet: This slum is downwind and downstream from the crafting district. Though the crafting district is supposed to shunt the worst of its pollution outside the city, a fair amount of it ends up here. The air in this slum is foul and on poor days difficult to see through. Water is contaminated with runoff, mostly undrinkable and is occasionally flammable. Residents will often travel to the edges of the neighborhood to procure potable water.
      Landmark: The Pit – At the lowest point of the neighborhood, the accumulated pollution creates a permanent eye burning fog. Lower still is a pool of polluted water and runoff. Occasional gouts of brightly colored flame light up the smog.  
    • NS2 – The Itch: Much like the animal pens that this neighborhood borders, residents here deal in animals and animal products. However, they deal more with small animals, offal and the like. In addition, because of the close quarters, stores of feed, offal, bedding and waste, the neighborhood crawls with all sorts of vermin. Rats are plentiful, but more common are bugs of all description, some as large as a man’s hand. Vermin traps and few very small windows (sometimes covered with firm cloth or rarely slices of horn to keep vermin out) are common features. Public areas have a notable lack of water features, as they tend to breed flying insects.
      Landmark: The Hive – a cluster of small buildings in this neighborhood has been taken over by a hive of giant bees. These bugs are rarely dangerous if left alone, but they emit a loud noise and can be seen flying about the city. A few residents take precautions and harvest as much honey as they dare.
    • NS3 – The Bloom: This neighborhood was unremarkable if poor, before the accident that destroyed the ruined district. The accident caused a number of issues here. Most immediately, a number of buildings were destroyed and many have yet to be repaired. In addition, many refugees from the now ruined magic school have taken up residence. The population of the neighborhood is swollen with low level mages and alchemists. Finally, one of the fragments of the college that rained down on the streets contained spores for dozens of strains of fungus. In a wet city like Juntial, these spores spread rapidly. Structures in this neighborhood often sprout many varied types of fungus and residents regularly scrape their homes clean to avoid damage.
      Landmark: The lost house – Perhaps the first structure to be hit with the fungal debris, this building stands completely covered in several feet of fungus of unusual size and colors.
    • NS4 – Catwalks: This neighborhood is densely packed and has the occasional taller building similar to The Heights. It also features a number of hastily assembled catwalks over the narrow streets. Braver residents will often travel via catwalk as a shortcut. Residences here are simple, and densely clustered. Thought not all of them have ladders, stairs, and ropes to the roof, many do.  Only a few have second stories. Public areas are often on the roofs of other buildings.
      Landmark: Candletower – Towards the center of the neighborhood is a stone tower and short attending building . This is Candletower, ostensibly the home of a local noble. However, it receives few visitors, so little is known about what goes on inside.
    • SS1 – The Warrens: More an extension of The Maze than a neighborhood in its own right, the warrens are made up of densely packed shifting lean-tos and tents clogging the streets of an already tight neighborhood. Paths within change from day to day and there is no room for mounts or vehicles of any sort. Buildings are small, simple and sometimes divided into multiple tight rooms. Public areas are nonexistent.
      Landmark: Garbage Fortunes – roaming the outskirts of the warrens with the rest of the trash vendors is a bent old crone who tells fortunes. Her price is simply a handful of garbage, which is thrown into her trash fire. Strange, but she is a regular fixture of the neighborhood and her fortunes are of good quality.
    • SS2 – Old City: This neighborhood was one of the earliest in the city. Originally typical if snug buildings with stone foundations, most of the buildings were lost in an attack by the native inhabitants of the swamp. Rebuilt later, most are now only enough wooden construction over the old foundation to permit entrance and exit. A few of the original buildings survive, towering over their now diminutive neighbors. Because the houses and shops are so short, streets are lined with local fast-growing woody plants to form a privacy screen.
      Landmark: The Dust Pit – Most places in Juntial are constantly damp, especially the lower class districts and lower elevations. Thus the sunken foundations in Old City are perpetually in danger of flooding and seeping moisture. A few of them, however, hold enchantments from before their ruin that keep them dry. The Dust pit is one of these enchanted foundations. Filled with dry sand and silt, it is in use as a fighting pit. Seating is arranged outside the foundation. Barkers and pennants advertise the fights.
    • SS3 – Artisan’s Alley: During the upgrade of the Raised Market, each founder hired various types of workers. Just before completion of the work, one of the founders mysteriously disappeared. It was discovered that he had nowhere near enough money to pay the workers and artists that had been working on the project on his behalf. Many of them were not from Juntial, and now with no pay for their labor couldn’t afford to return home. Of these, a good number moved into the nearby slums, opened up shop and took on apprentices. Several generations later, the neighborhood is festive, bohemian, and adorned with artistry of all types. Homes and shops are simple but well decorated in eclectic styles. Public areas showcase artworks of both permanent and temporary nature.
      Landmark: Founders Square – One of the pieces of art that was commissioned and never paid for was a larger than life statue of the founder responsible for stiffing an entire neighborhood. Several of the artists stole it in a drunken midnight horse cart raid and erected it in the middle of their new neighborhood. Since, it and the square in which it rests has been routinely defaced with mocking artwork depicting the subject in an endless panoply of unflattering and rude representations.

That’s all our neighborhoods, a description and a landmark for each. Though these may be fleshed out more or tweaked as I go, for the purposes of this article series, I’m going to move on. Next time we’re going to look at layers of encounters.

Categories: Game Theory & Design

Floating Action Buttons

New Drupal Modules - 10 June 2019 - 2:23am

Replaces core action buttons (by default: save, view, delete) and the settings sidebar, from the node edition form, by floating buttons.

Categories: Drupal

Stackpath CDN

New Drupal Modules - 10 June 2019 - 1:29am

Integrate STACKPATH with Drupal for purging content.

Categories: Drupal

Lullabot: Behind the Screens: Behind the Screens with Hussain Abbas

Planet Drupal - 10 June 2019 - 12:00am

Bangalore to Seattle is no short trip, but Hussain Abbas made the journey, stopping at many Drupal camps along the way. He tells us why DrupalCon is so important, and where to find the best biryani.

Categories: Drupal

Robots Noindex Nofollow

New Drupal Modules - 9 June 2019 - 9:00pm

Say no to search engine crawlers.

This tiny module prevents your site from being indexed by the search engines. It's recommended to use it with the Configuration Split module on your Development, Testing and Staging Drupal installations ONLY.


Technically, it inserts the following line to every page.

Categories: Drupal

Bethesda unveils Orion to offer engine-level enhancements for streaming games

Social/Online Games - Gamasutra - 9 June 2019 - 6:52pm

Bethesda and id Software have announced Orion, an engine and platform agnostic collection of software technologies aimed at boosting the performance of games played through a streaming service. ...

Categories: Game Theory & Design

OpenSense Labs: Decoupled Drupal: Cornerstone of digital experiences

Planet Drupal - 9 June 2019 - 6:46pm
Decoupled Drupal: Cornerstone of digital experiences Shankar Mon, 06/10/2019 - 07:16

The audience revels in the magnificent performances of the actors, picturesque visuals, breathtaking action sequences, alluring background score, thoughtful dialogues, and emotions attached to the narrative. To bring them all out in the best possible way on to the screen, there goes an exceptional direction and screenplay behind-the-scenes in addition to a massive swathe of people who are involved in different parts of the film. Apparently, a film works wonders when both the onscreen elements and the off-screen elements strike the right chord.

A similar theory is of paramount significance in the case of web development. The rapid evolution of diverse end-user clients and applications have resulted in a plethora of digital channels to support. Monolithic architecture-powered websites leverage web content management solutions for disseminating content via a templating solution tightly coupled with the content management system on the backend. Propelled by the need to distribute content-rich digital interactions, application development and delivery (AD&D) professionals, who are supporting content management systems (CMS), are showing an inclination towards an API-first approach.
Headless CMSes have been leading the way forward to provide a spectacular digital experience and Drupal, being API-first, is a quintessential solution to implement a headless architecture. Before we move forward, let’s briefly look at how significant is content for your online presence and how the headless CMS is fulfilling the needs of organisations.

Content: Linchpin of ambitious digital experience

It is difficult to envisage a digital screen without content as every single moment that we spend on a smartphone, laptop, tablet, or a smartwatch is enriched with digital content like images, text, video, product reviews and so on. Even when we talk to a voice assistant and inquire about something, its answers constitute words, links, pictures, maps etc. (again, it’s all content). The relevance quotient of that content should be top-of-the-line as it is the medium that enables users to experience their digital interactions. This makes content the linchpin of ambitious digital experiences.

The relevance quotient of content should be top-of-the-line as it is the medium that enables users to experience their digital interactions

Several content repositories are struggling to meet today’s digital requirements. When the world was just web and email, governance of dynamic content dissemination worked perfectly fine using a web CMS. A web CMS has been an astronomical solution for offering unique designs, WYSIWYG authoring, a workflow for approvals and translation, fantastic marketing capabilities and internet-scale delivery.

Forrester’s The rise of the headless content management system report states that web CMSes has led to a cluster of content with markup and metadata. Moreover, if you optimise your content repository for HTML templates, it would require you to undo all the optimisations in order to use the content elsewhere in a non-HTML format. Also, tightly coupled approaches did not need APIs (Application Programming Interfaces) connecting the repository to the delivery tier or the content editing and workflow tools. And, selling the content repository and delivery environment together is great for web-only scenarios but reusing the content on the mobile application or in email marketing would still require you to run the entire web CMS stack.

There is where the need for headless CMS kicks in. It uses modern storage, stateless interfaces and cloud infrastructure for the efficacious delivery of Internet-scale content experiences on any device.

Uncloaking headless CMS Source: Forrester

Headless CMS is a content component in a digital experience architecture that interacts with other components comprising of authoring, delivery front ends, analytics tools through loosely coupled APIs. It does not do any rendering of content and the rendering is decoupled from the management interface which is why terms ‘headless’ and ‘decoupled’ are used interchangeably.

Headless CMS stores the content, offers a user interface for the creation and management of content, and provides a mechanism for accessing the content through REST APIs as JSON

While ‘head’ refers to the frontend rendering or the presentation of the content, the ‘body’ refers to the backend storage and the governance of the content.

Headless CMS stores the content and offers a user interface for the creation and management of content. It provides a mechanism for accessing the content through REST APIs as JSON. So, it is also referred to as API-first CMS.

Content can be delivered to and integrated with the third party system like e-commerce tool. Or, it can be delivered to and exhibited using front end technology in the browser, mobile app or syndication service. Headless CMS is a wonderful content-as-a-service solution.

Source: Contentstack

A traditional CMS confronts with the processes of creation of content, its dissemination and its display. It has a backend where the users can enter content which is stored in a database, retrieved, rendered into HTML on the server which is then delivered as fully rendered pages to the browser.

In contrast, headless CMS decouples the rendering and presentation system thereby enabling you to replace it with frontend or other technologies of your choice. The CMS will be a content store and web application for the content producers and the content is delivered to the frontend or another system through an API.

With the stupendous rise of headless architectures, a portion of the web is turning server-centric for data and client-centric for the presentation. This has given momentum to the ascension of JavaScript frameworks and on the server side it has led to the growth of JSON:API and GraphQL for better serving the JavaScript applications with content and data. Among the different web services implementations like REST, JSON:API and GraphQL, when we consider request efficiency, JSON:API is the better option as a single request is usually sufficient for most needs. JSON:API also is great in operational simplicity and is perfect while writing data.

Headless CMS decouples the rendering and presentation system thereby enabling you to replace it with frontend or other technologies of your choice

Headless CMS is advantageous for the following reasons:

  • You can instantly start with headless with no hurdles.
  • It does not require you to alter your existing delivery tier as it seamlessly fits into the existing architecture
  • It is perfect for building web and mobile applications as it allows practically any application- be it web, mobile, IoT(Internet of Things), smart TV or touchscreens- to pull and push content.
  • Frontend developers, backend developers, marketing and content editors can get started quickly and work autonomously.
  • You can give more power to the front-end developers as they simply work content APIs and do not have to learn inner functionalities of CMS or its templating system.
  • It follows the approach of ‘Create Once, Publish Everywhere’ thereby allowing you to reuse content for different channels.
  • It works tremendously well in a microservices environment and enables cross-functional teams to work via agile processes and get tasks done swiftly.
Going the Drupal way

Call it headless or decoupled, leveraging Drupal, as the central content service, is a magnificent solution to power your complete application and device ecosystem. Decoupled Drupal has the provision for omnichannel delivery of content that is quintessential for marketers and publishers.

Decoupled Drupal has the provision for omnichannel delivery of content that is quintessential for marketers and publishers

It enables the developer to leverage any technology for rendering the frontend experience instead of theming and presentation layers in Drupal. The Drupal backend exposes content to native applications, JavaScript application, IoT devices and other such systems. In addition to the modules for web service implementations like REST, GraphQL and JSON:API, Decoupled Drupal ecosystem also offers several other alternative modules that can be of huge help.

Source: Dries Buytaert’s blog

There are different approaches to decouple Drupal:

Coupled Drupal

In traditional Drupal, also referred to as coupled Drupal, monolithic implementation is done in which Drupal has the authority over all frontend and backend side of your web application setup. Coupled Drupal is fantastic for content creators, especially when you are in dire need of achieving fast time to market without relying too much on front-end developers. Developers, who love Drupal 8 and want it to own the entire stack, still find it a great way of building a web application.

Progressively decoupled Drupal

Another way to utilise the power of Drupal is the progressively decoupled approach. It is a compelling approach for developing Drupal’s frontend where the governance of contiguous experiences is handled by content editors, site assemblers and the front-end developers. While content authors and the site assemblers get the benefits of contextualised interfaces, content workflow, site preview etc. to remain usable and incorporated with Drupal as a whole, a portion of the page to a JavaScript framework is dedicated for front-end developers to let them work autonomously. Progressive decoupling helps in utilising Drupal’s rendering system while simultaneously using a JavaScript framework for powering the client-side interactivity.

Fully decoupled Drupal

In fully decoupled Drupal, there is a complete separation between Drupal’s frontend and the backend. The Twig theme layer is replaced with a different frontend entirely. Native mobile or desktop applications, JavaScript single-page applications or IoT applications are some of the examples. RESTful API is leveraged by these applications to communicate with Drupal. RESTful API, which acts as a middle layer between frontend and backend, exposes resources as JSON or XML that can be queried or modified with the help of HTTP methods like GET, POST etc. Even though integral features like in-place editing and layout management are not available, the fully decoupled approach is preferred by developers as it offers ultimate authority over the frontend and is superb for those who are already experienced with the development of applications in frameworks like React, Vue etc.

Increasing intricacy of JavaScript development has given birth to JAMstack (JavaScript, APIs, Markup) which has, in turn, resulted in another very much favoured approach called fully decoupled static sites. Enhanced performance, security and reduced complication for developers have made static sites a favourite option among many developers. For instance, Gatsby, a static site generator, can retrieve content from Drupal, generate a static site, and deploy it to a content delivery network (CDN) via specialised cloud provider like Netlify.

Meritorious features of decoupled Drupal

Following are some of the major benefits of decoupled Drupal:

  • Syndication of content: Whether it is a coupled approach or a decoupled approach, Drupal remains the hub while developing experience ecosystems with all of them ingesting content from one source of truth.
  • Full separation: Even though monolithic and progressively decoupled approaches in Drupal has implicit separation of concerns and mostly couldn’t be seen by the user, fully decoupled architecture gives you an explicit separation between structured content that is governed by Drupal and its presentation which is managed by consumer applications.
  • User experience: Decoupled architecture offers an amazing user-centred experience. For instance, a JavaScript framework can be more suited to the task when it comes to an interactive application which is in dire need of frequent re-renderings of content.
  • Work in parallel: Decoupling also brings efficacy to a pipelined development process which involves teams working in parallel. A team of front-end developers can develop applications against a dummy web service API that is utilised only for the purpose of testing but not actually completed whereas the team of backend developers can administer the backend that exposes the API and the underlying processes yielding it.
Challenges of Decoupled Drupal

Some of the major hurdles while decoupling Drupal are mentioned below:

  • Editing and governance: Drupal 8’s wonderful features like in-place editing, configuration menus constituting certain page components, and some modules that include contextualised tools for Drupal governance won’t be available.
  • Security: Although JavaScript and application frameworks have the provision for defending cross-site scripting attacks, fully decoupled and progressively decoupled approaches put the obligation of carefully scrutinising the security implications.
  • Point of failure: Fully decoupled architecture require the use of stacks like MERN (MongoDB, Express, React, NodeJS) or MEAN (Angular instead of React) or other solutions that may imperative for native mobile or IoT applications. That means, it can be challenging to introduce an additional hosting stack into your firm’s infrastructure and can lead to an additional point of failure.
  • Layout management: Having to remove modules like Panels and Display Suite can be an issue for the developers causing obstacles to the marketing teams who do not have the access to developers who can help in implementing layout changes.
  • Previews: It can be challenging if your editorial team wants a previewable content workflow as it is used to working with coupled CMS.
  • Notifications: In a fully decoupled architecture, Drupal system messages, that are frequently highlighted at the top of rendered pages, are not accessible. Moreover, providing these messages in a progressively decoupled setup is not much of an issue.
  • Performance: BigPipe module works tremendously well in enhancing the web performance in Drupal that can match the page load performance of JavaScript applications. Fully decoupled architecture is devoid of this feature but progressively decoupled setup can give you the option of leveraging the feature.
  • Accessibility: Drupal won’t be providing the readymade frontend code or a roster of core interface components and interaction that can be relied upon which calls for front-end developers to build a suitable UX and ensure accessibility without the assistance of Drupal.
Strategies employed while choosing decoupled Drupal

Assessment of the organisational needs is instrumental to the decision-making process. Being abreast of the business requirements pertaining to building a robust digital presence helps you in forming an immaculate strategy while choosing decoupled Drupal.

For instance, selecting decoupled Drupal might or might not be an astounding option for developing a single standalone website. It depends upon the functionalities that are deemed as “really necessary” by your developers and content editors. In case, you are developing multiple web experiences, decoupled Drupal instance can either be leveraged as a content repository which is devoid of its public-facing frontend or simply as a traditional site that can act concurrently as a content repository. It, again, depends upon how dynamic you want your web application to be that would ultimately help in deciding a JavaScript of choice or even a static site generator.

Developing native mobile or IoT applications may require you to adopt a decoupled approach where you can expose web service APIs and consume that Drupal site as a central content service which is bereft of its own public-facing frontend.

The significant thing to take a note here is the stupendous capabilities of Drupal for supporting almost any given use case as it streamlines the process of developing decoupled Drupal. 

Case studies

Some of the biggest names in different industries have chosen decoupled Drupal to power their digital presence.

The Economist

Established in 1843, The Economist, which set out to take part in “a severe contest between intelligence, which presses forward, and an unworthy, timid ignorance obstructing our progress”, has seen staggering growth over the years and has earned great recognition in the world of media. It chose decoupled architecture for building a Drupal backend for the native iOS and Android Espresso applications with the help of a digital agency.

Drupal turned out to be an astronomical solution for the Economist editorial team. They could iteratively design and had a spectacular content creation and publishing workflow that met their requirements. It helped in incorporating features like automatic issue creation, approval of content, the look and feel of interfaces among others.

The customisation of Drupal content creation interface was done in a way that would avoid errors while formatting and enables content authors to emphasise on content. Editorial teams had the provision for a dashboard that could help in swiftly and efficaciously creating and publishing new issues. It also offered visual indicators of approval status, countdown timers for each region and quick links for all the articles.

Produce Market Guide

The website of Produce Market Guide (PMG), a resource for produce commodity information, fresh trends and data analysis, was rebuilt by OpenSense Labs. It involved interpolation of a JavaScript framework into the Drupal frontend using progressively decoupled Drupal that helped in creating a balance between the workflows of developers and content editors. The rebuilding process comprised of majorly progressively decoupled approach, React, Elasticsearch Connector module among others.

The process of mapping and indexing on Elastic Server required ElasticSearch Connector and Search API modules. Elastic backend architecture building process was followed by the development of faceted search application with React and the integration of the app in Drupal as block or template page. The project structure for the search was designed and built in the sandbox with modern tools like Babel and Webpack and third-party libraries like Searchkit.
Moreover, Logstash and Kibana, that are based on Elasticsearch, were incorporated on the Elastic Server thereby helping in collecting, parsing, storing and visualising the data. The app in the Sandbox was developed for the production and all the CSS/JS was incorporated inside Drupal as a block to make it a progressively decoupled feature. Following the principles of Agile and Scrum helped in building a user-friendly site for PMG with a search application that could load the search results rapidly.

Princess Cruises

As one of the premiere cruise lines in the world, Princess Cruises innovatively metamorphosed their marketing landscape with the integration of decoupled Drupal. They went on to fundamentally change the way their guest accessed information while onboard their ships.

The guests on their ships relied upon their smartphones to swiftly access information, purchase items and inform the management about anything. This led to the development of Princess@Sea with the objective of transforming Princess experience. It is a mobile application that is specifically designed for allowing guests to plan their day, assess the ship’s itinerary, scan through restaurant menus and book shore excursions on-the-go.

When the ships are sailing different parts of the world, the digital experience had to be reliable which called for a centralised way of administering content across several channels and touchpoints. This would enable them to offer a uniform experience on mobile and digital signage onboard the ship. Decoupled Drupal was chosen to serve content across multiple touchpoints and channels. Princess Cruises could create content once and publish everywhere thereby connecting every passenger to Princess@sea, hence Drupal.


NASA, an independent agency of the executive branch of the federal government of the United States, went for the decoupled setup for the redressal of their site with the help of an agency. Drupal and Amazon Web Services (AWS) turned out to be a wonderful match for meeting the content needs of both NASA and the public with user-driven APIs, dynamic host provisioning, scalability and security.

The deployment of NASA’s website is done in numerous AWS availability zones and manages almost 500 content editors updating over 2000 content every day. On an average, it receives nearly a million page views a day and has even gone onto handle peak load of approximately 40,000,000 page views in a single day with groundbreaking feat of 2,000,000+ simultaneous users during NASA’s 2017 Total Solar Eclipse coverage.


Application development and delivery teams have already started exploring headless CMS tools along with numerous other sets of API-first microservices for building innovative solutions. These digital natives are adopting a do-it-yourself approach to digital experience architectures and dragging their organisations into the digital-first age.

Headless throws open interesting possibilities and challenges traditional ways of doing things. For a lot of organisations, it is no longer a question of whether they should go for headless or not but more of a contemplation of headless to assess where does the headless fit in their organisational setup. Moreover, the growth of microservices architecture will continue to give that extra push to headless or decoupled approaches.

Decoupled Drupal is an outstanding solution for implementing headless architecture. It acts as a central hub, processing and curating content and data from other tools and services while simultaneously sharing its own content and data via APIs. With the stupendous flexibility, scalability and content authoring capabilities of headless approaches, digital firms can enjoy seamless creativity and innovation as they build their digital architectures.

We have been perpetually working towards the provision for great digital experiences with our suite of services.

Contact us at to get the best out of decoupled Drupal and ingrain your digital presence with its superb capabilities.

blog banner blog image Decoupled Drupal Coupled Drupal Traditional Drupal Drupal Drupal 8 Fully Decoupled Drupal Progressively decoupled Drupal Headless Drupal Headless CMS Decoupled CMS Fully Decoupled CMS Fully Decoupled Static Site Fully Decoupled App Traditional CMS API-first Drupal API-first API-first CMS CaaS Content-as-a-service REST API GraphQL JSON API Internet of things IoT Microservices architecture JavaScript ReactJS VueJS JAMstack GatsbyJS Digital Signage Blog Type Articles Is it a good read ? On
Categories: Drupal

Xbox One successor Project Scarlett slated for Holiday 2020

Social/Online Games - Gamasutra - 9 June 2019 - 2:47pm

Microsoft has finally detailed its next-generation console Project Scarlett, a system Microsoft CEO Phil Spencer says is both the †œfoundation of our future on in console and the formation of our future in cloud.† ...

Categories: Game Theory & Design

Follow all of Gamasutra's E3 2019 coverage here!

Social/Online Games - Gamasutra - 9 June 2019 - 1:07pm

Gamasutra will be covering E3 both on-site and remotely to bring you the latest news and interviews from the game industry's big L.A. showcase. Follow coverage on our dedicated E3 news page. ...

Categories: Game Theory & Design

Video Game Deep Cuts: Combo Breaking E3 With BitSummit Flair

Social/Online Games - Gamasutra - 8 June 2019 - 5:40pm

This week's roundup includes a look at some great community events - from the fighting game scene's Combo Breaker to Japanese indie dev scene's BitSummit, as well as a peek at the first ever E3 Expo & lots more. ...

Categories: Game Theory & Design

Video Game Deep Cuts: Combo Breaking E3 With BitSummit Flair - by Simon Carless Blogs - 8 June 2019 - 5:35am
This week's roundup includes a look at some great community events - from the fighting game scene's Combo Breaker to Japanese indie dev scene's BitSummit, as well as a peek at the first ever E3 Expo, kids apps, D&D in 2019, & lots more.
Categories: Game Theory & Design

DrupalEasy: Drupal 8 and Composer - working with cloned dependencies

Planet Drupal - 7 June 2019 - 11:59pm

If you use the Drupal Composer Drupal Project template for managing your Drupal 8 site’s codebase, and you commit dependencies to your Git repository, then you’ve probably run into issues involving cloned dependencies. Sometimes when requiring a dependency via Composer, you end up with a cloned version (which includes a .git directory) instead of a release version. 

If you’re committing dependencies to your repository, then the .git directories associated with cloned dependencies cause an issue when you try to commit. A common resolution is to remove the .git directory from the dependency’s directory.

While this solves the immediate issue, the next time you go to update Drupal core, you’ll likely see an error message along the lines of, “The .git directory is missing from /var/www/html/vendor/some/dependency, see for more information”. How can we get past this?

Here’s my workflow:

  1. Delete the entire /vendor/ directory.
  2. Run “composer install” to reinstall all dependencies. 
  3. Update Drupal core (normally with “composer update drupal/core webflo/drupal-core-require-dev "symfony/*" --with-dependencies”
  4. Re-remove any .git directories for cloned dependencies.
  5. Commit the update.

Ultimately the "proper" solution will be to not commit dependencies to the project repository. I agree that this is the best solution, but not everyone’s workflow currently supports this.

There's also a great discussion in the Drupal Composer Drupal Project issue queue about alternate methods to deal with this issue. 

Have a different workflow to deal with cloned dependencies? Share it in a comment below!

Just getting started with managing your Drupal 8 project with Composer? Jeff Geerling has some super-helpful blog posts.

Categories: Drupal

OSTraining: Directly Upload and Link Files to the Text Editor Content in Drupal 8

Planet Drupal - 7 June 2019 - 5:54pm

One of Drupal’s big advantages is its possibility to structure content with the use of fields. However, from time to time you will want to link a file to your content without the need of adding a field to the database for that purpose.

The D8 Editor File Upload module provides this functionality by adding a button to the toolbar of the rich text editor (in this case CKEditor). This way it is possible to upload a file and present it within the content as a link. This tutorial will expĺain the usage of this module.

Let’s start!

Categories: Drupal

OSTraining: Directly Upload and Link Files to the Text Editor Content in Drupal 8

Planet Drupal - 7 June 2019 - 5:54pm

One of Drupal’s big advantages is its possibility to structure content with the use of fields. However, from time to time you will want to link a file to your content without the need of adding a field to the database for that purpose.

The D8 Editor File Upload module provides this functionality by adding a button to the toolbar of the rich text editor (in this case CKEditor). This way it is possible to upload a file and present it within the content as a link. This tutorial will expĺain the usage of this module.

Let’s start!

Categories: Drupal

OSTraining: Directly Upload and Link Files to the Text Editor Content in Drupal 8

Planet Drupal - 7 June 2019 - 5:54pm

One of Drupal’s big advantages is its possibility to structure content with the use of fields. However, from time to time you will want to link a file to your content without the need of adding a field to the database for that purpose.

The D8 Editor File Upload module provides this functionality by adding a button to the toolbar of the rich text editor (in this case CKEditor). This way it is possible to upload a file and present it within the content through a link. This tutorial will expĺain the usage of this module.

Let’s start!

Categories: Drupal

Views Filter Alias Parent

New Drupal Modules - 7 June 2019 - 3:20pm

When using a "Content: ID" contextual filter on a view you can provide a default argument such as "Content ID from URL". This module provides an additional option "Content ID of Alias Parent". This option will get the path alias of the current page ('/events/name-of-an-event' for example), then drops off the end portion of the url to get the "parent" alias ('/events' in our example) and returns the node id of that "parent" alias.

This assumes that your pathauto patterns are generating good URLs that follow normal patterns like the example above.

Categories: Drupal

Promet Source: Driving Drupal Best Practices

Planet Drupal - 7 June 2019 - 12:24pm
Business is hopping. You’re hiring Drupal developers with varied backgrounds and skill sets.  When working in Drupal, there are often many ways to achieve the same outcome, and quite often, Drupal developers find themselves on different pages. How do you determine whose way is the 'best' way and proceed with optimal efficiency? There are two perspectives to consider: A team executing best practices, and The process(es) needed to get best practices into place.
Categories: Drupal

Matt Grasmick: A New Google Chrome Extension for Issue Links

Planet Drupal - 7 June 2019 - 12:21pm

I'd like to briefly share a new handy Chrome Extension that I recently created: Drupal Issue Chrome

chrome. noun. features added to something to make it nicer, but which don't affect the core functionality.

This extension will render links to issues in order to clearly indicate node id, title, and issue status. It closely mimics's own rendering of links to issues, bringing the same formatting to ANY website.

For example, an anchor link with the href and text content "" would become "#1308152: Add stream wrappers to access extension files" and would be colored appropriately. You may also hover over the issue to see the exact issue status, provided via the anchor title attribute. Take a gander:

Categories: Drupal

Video: Efficient texture streaming in Titanfall 2

Social/Online Games - Gamasutra - 7 June 2019 - 9:47am

In this 2017 GDC session, Respawn Entertainment's Chad Barb serves up a deep dive into the company's approach to efficient texture streaming in its 2016 hit shooter Titanfall 2. ...

Categories: Game Theory & Design


Subscribe to As If Productions aggregator