All RPGs and Storygames by Tod Foley are now available at DrivethruRPG and RPGnow. Bring these games to your table!
Language Code Formatter provides a way to display the internal language code of an entity by extending the Language field formatter. Normally, the Language field formatter outputs the pretty name of the language but sometimes you need the code.
Example: I want the language code inside of a view in order to create relative paths in another view text field with the correct langcode.
Most customer will manage their own accounts on an ecommerce website just fine. However, sometimes you need to create new accounts for your customers, or edit their existing account. For example, if you have both an online store and a brick-and-mortar store running on the same platforms (which Drupal Commerce can do), your in-person cashiers may have reasons for creating or updating your customers account. Likewise, if you offer support by phone, a customer service rep may also need to create or update accounts.
In this Acro Media Tech Talk video, we user our Urban Hipster Commerce 2 demo site to show you how you can manage your customers online accounts. These are things like finding specific users, adding new users, blocking users, modifying a users payment methods and viewing their previous orders, etc. It's super simple.
Its important to note that this video was recorded before the official 2.0 release of Drupal Commerce. You may see some differences between this video and the current releases. The documentation is also evolving over time.Urban Hipster Commerce 2 Demo site
This video was created using the Urban Hipster Commerce 2 demo site. We've built this site to show the adaptability of the Drupal 8, Commerce 2 platform. Most of what you see is out-of-the-box functionality combined with expert configuration and theming.
- Drupal Commerce 2 - OMS and Fulfillment
- Watch more Tech Talk how-to videos
- Learn more about Drupal Commerce
- Learn more about Acro Media
Every year at DrupalCon our team has an amazing time. This year was no different. We rounded up everyone who attended and asked them about their favorites this year.
Technical information was being readily exchanged and processed, while the humans who make up the community shared many stories as well. On top of all of the good information there was good food, so much food!
Update automation sounds nice as long as you don’t think about your (heavily) patched Drupal project, right?
In this “recipe” I will explain how Drop Guard handles custom patches within an fully or partly automated update process.
An update got released on Drupal.org. Only a few minutes later, Drop Guard detects the update release information, such as update type and version.
Drupal Planet Drupal Drop Guard recipes
A question which I see quite often in response to posts like A modern way to build and develop Drupal 8 sites, using Composer is: "I want to start using Composer... but my current Drupal 8 site wasn't built with Composer. Is there an easy way to convert my codebase to use Composer?"
Unfortunately, the answer to that is a little complicated. The problem is the switch to managing your codebase with Composer is an all-or-nothing affair... there's no middle ground where you can manage a couple modules with Composer, and core with Drush, and something else with manual downloads. (Well, technically this is possible, but it would be immensely painful and error-prone, so don't try it!).
We didn’t see this project solely as a chance to rebrand and rebuild for ourselves, it was also an opportunity to try something new and expand our collective knowledge with the potential for using with clients in the future. We had been discussing using Pattern Lab for Front End development for some time and this was the perfect opportunity to try it out.
Patten Lab allows the creation of component-driven user interfaces using atomic design principles. This means we can create modular patterns all packaged up nicely that can be assembled together to build a site. Plus we can use dynamic data to display the patterns in a live style guide which makes viewing each component quick and easy. And nobody is viewing out of date designs or code - an issue we had on a recent project. With Pattern Lab, we would have a central place to view all of the actual components that will be used on the live site.
The guys over at Four Kitchens made implementing a Pattern Lab with Drupal super easy, by creating Emulsify. Serving as a Drupal 8 starter kit theme, Emulsify allows you to build and manage components without using Drupal's template names but by using custom template names that make sense to everyone, instead. When you're ready, you can easily connect them up to Drupal.
Building the frontend in this way allows it to be built separately from the backend development. It's possible to create the whole of the front end before even touching Drupal. If needs be, it also allows developers to work on the frontend and backend at the same time without stepping on each other's toes.
As well as compiling, this command also provides a url for the local server. Open it up in a browser and you can see your live style guide!
Now for the actual components. These are filed in the theme, inside:components/_patterns/
As we're working with Atomic Principles, the smallest components are filed first building up to the biggest. The beauty of pattern lab is nesting - it's possible to include patterns inside each other to make larger components. Although it's not necessary to use Atomic Design naming conventions when organising patterns, it does make sense. These levels are:
Atoms are the basic elements of the site like HTML tags and buttons. Molecules combine these Atoms to create larger components like a card and then Organisms can combine Molecules to create more complex page components and so on...
Numerics are added to ensure they are listed in the correct order and also a Base folder is added to house variables, breakpoints, layouts and global sass mixins. So, this is how our file structure looks inside that _patterns folder:- _patterns/ - 00-base - 01-atoms - 02-molecules - 03-organisms - 04-templates - 05-pages
Having just the code that makes the component isn't enough for us to view it in our style guide. In addition to the files that make up the component, we can also include files to give the component context. A Markdown file allows us to give the component a title and description, which are used in the navigation and style guide. To each component folder we can also add a YML file which holds filler content solely for use for the style guide. We basically just take each variable name from the twig file and provide some content for each.
So, a typical component file structure might look like this:- card - _card.scss - card.md - card.yml - card.js
Once we had a full understanding of the structure and had added our colour palette and set up our grid and breakpoints it was a case of working through the designs to determine what the components were and of which size. Then starting with Atoms and working up we could build each component. We'll look at the actual development in the next article in the series.
Join Ang, John, and Senda on this episode of Gnomecast as they discuss ways to build and use character relationships to enrich your game. This episode discusses Senda’s Gnome Stew article “Why Relationships” and two of Ang’s articles, “Making Connections” and “The Ties that Bind.” Will these gnomes’ relationships be enough to keep them out of the stew?
Download here: Gnomecast #39 – PC Relationships
Don’t forget, there’s only a few days left to back the Queen City Conquest 2018 Kickstarter campaign!
In finance, Return on Investment, usually abbreviated as ROI, is a common, widespread metric used to evaluate the forecasted profitability on different investments. Before any serious investment opportunities are even considered, ROI is a solid base from which to go forth. The metric can be applied to anything from stocks, real estate, employees, to even a sheep farm; anything that has a cost with the potential to derive gains from can have an ROI assigned to it.
User can also send the ROI report in PDF format to their email ids