In this article, we will see how we built custom blocks in EK management tools suite with a sample basic block in a module called 'mymodule' used for demo. It can be used to display multiple content, static or dynamic as in the example above.Create the block script
First we will create a script that will display some content within a block. the script file will be called MyBlock.php and is placed in /mymodule/src/Plugin/Block/.
* Contains \Drupal\mymodule\Plugin\Block\MyBlock.
* Provides a 'Custom module widget' .
* id = "my_block",
* admin_label = @Translation("My custom block"),
* category = @Translation("mymodule Widgets")
Gregg Marshall's Mastering Drupal 8 Views is one of the (I can only assume) many Drupal 8-focused books that will be released in the coming months. It is a very good deep dive into many of the hidden corners of the Views module, albeit with an interesting format. Not completely structured like a typical how-to software book, Gregg takes a bit more of a novel approach (pun intended) - he takes the reader on a journey through the Views module through the eyes of Lynn, a small business owner (Lynn's cat and Drupal consultant also have prominent roles). While some readers might find the story-ish elements distracting, they add a certain degree of warmth to the book - something I can only assume a subset of readers will more than appreciate.
The author does a nice job of setting the stage, identifying the intended audience for the book, and speaking directly to them (through the book's characters). There are sections of the book that may cause confusion with this structure, on several occasions I found myself reading long, multi-paragraph sections that I didn't immediately realize that a character was speaking, and not the author. It seems that the use of quotations to indicate when characters were speaking was not consistently applied.
While the technical content of the book is often well-written and clear, there are some places in the book where things seem out-of-order - none more so than the first lesson diving into the Views "settings" page - something that most people new to the subject don't need to consider until they need to modify the (very sane) default values. Another example early in the book has the author creating a new view "display" prior to a full explanation of what Views display are.
There are, however, many areas of great explanation on topics that I don't recall ever seeing in other Drupal-related books. Sections on the new "entity reference" and "REST export" display types stood out in the first few chapters, as well as some of the best explanations (and details) on the "table" format, and field rewrites (more on this in a bit).
There are several lessons that have starting points that aren't necessarily considered "best practice", including one that has the reader cloning the admin/content view as a starting point for a public facing view. In my opinion, the reader would be better served by starting a brand new view using the Views "wizard" interface. As a stickler for best practices, there were several things in the book that made me cringe a bit, including the use of the (outdated?) GMap and Location modules (instead of Geofield-related modules) and (even more so) the use of the admin area's "Install new module" functionality.
I found the discussion and lessons around contextual filters to be extremely effective. The story-ish nature of the book allowed the author to almost naturally introduce a problem that is elegantly solved with contextual filters. Along with relationships, contextual filters are often one of the major stumbling blocks in learning Views, and this book does as good a job as anything else I've read and taking the reader down in the deep, dark recesses of it ("Default value" options included!) The chapter on Views relationships is similarly structured and just as effective.
This is perhaps one of the only Drupal books I've read that purposely sends the reader (in this case, the main character as well) down a dead-end in order to introduce a new topic. I think that many readers will find this comforting, in that it allows the author to introduce a new topic in order to direct the reader to a solution.
As a big fan of display modes, combined with the fact that they are much more visible in Drupal 8, I hoped that the author would utilize them more often in the various lessons (instead of relying on adding fields to most views).
The book really shines in chapters that normally are only a small section in other Drupal resources. There is an entire chapter on field rewrites, and it is wonderful. The author takes Lynn and the reader through various examples, each exposing a new aspect of field rewrites. For anyone who doesn't dare dive into this section of Views field configuration, this chapter alone is worth the price of the book.
The chapter on all the settings in the "Advanced" fieldset is also something that the author covers extremely well. In most Views references, many of these settings are glossed over, but this book provides an almost ("aggregation" isn't covered as deeply as I hoped) complete reference to all the various available settings.
While the vast majority of the examples in the book are well structured, many of them depend on content types and other information architecture that exists on "Lynn's" site. While details of the information architecture are provided in an appendix, it would be very helpful for the author to provide them via GitHub or some other electronic mechanism to readers. Otherwise, it seems like a tedious and error-prone process for readers to recreate the information architecture on their own in order to follow the examples in the book.
The author does a nice job of walking the reader through the use of several Views-related contributed modules as well. For my taste, I think there should have been just a little more explanation about how various contributed modules fit together with Views. As an example, the fact that Views Slideshow provides a new display plugin is glossed over. I think it would serve the readers well to specifically mention that many Views related modules are simply plugins for various parts of the Views infrastructure. This would provide readers with a higher-level view of the Views ecosystem. That's a bit of a nitpick though, as this section is really, really solid.
One of the last chapters in the book covers theming views, and I think it doesn't go into enough details and/or examples. The section on adding CSS classes to various parts of a view is very useful, but the section on overriding template files feels incomplete.
Overall, this is a welcome addition to the Drupal family of books, and one that I can honestly recommend for users that feel like there are aspects of the Views module that are still a mystery to them. The novel-like structure of the book normally doesn't get in the way of the lesson, but for readers who normally doesn't read technical books front-to-back (instead cherry picking only chapters of interest), it might be a bit distracting. While this is properly identified as a Drupal 8 book, much of the content is also valid for Drupal 7, including some of (in my opinion) the strongest chapters.
This is the varnish purger for the Purge module.
For now this is only a copy of the Generic HTTP Purger module, we are working on extending it to do more than http purges, and therefor forked from that module. All work done until now should be credited to nielsvm
Drupal India Community have been talking about Pan India code sprint and with effort and cooperation of regional communities we were finally able to organise a combined sprint, we had participation from Mumbai, Jaipur, Delhi and Pune. This is an account of Pune sprint which happened at QED42 Office in Viman Nagar. We had a total attendance of 10 Drupalers out of which 2 were first time sprinters ( Congratulations Dhruvesh and Shreyal on attending your first sprint :) ).
The focus of the sprint was porting modules from D7 to D8 and trying to reach stable releases of some of the modules that were started in previous sprints. One of those modules was auto_entitylabel the issues were triaged prior to the code sprint, so we had less trouble getting around the issues & fixing them up. EOD, we were able to get a basic version of the module, which included integration with tokens.
Overall, it was a productive sprint & we plan to continue the same on Last Saturday of every Month. Keep an eye on auto_entitylabel, jquery_carousel, heap_analytics if you are interested to use them in Drupal 8, couple of sprints and help from community we should be able to release stable versions of these modules :) we specifically need help on testing of these modules and reporting issues.PIYUESH KUMAR Sat, 06/25/2016 - 18:12
Drupal 8 needs forces to clear cache every time a theme file or some code changes. This module provides a hotkey (Keyboard shortcut) to clear cache.
Just press ALT+C to Clear Cache
Valuebound: How to reduce your development hours by Creating an Installation Profile or Distribution in Drupal 8!
Creating an installation profile in Drupal 8 is quite easy according to my humble opinion. Why? Because of the Configuration Management System in Drupal 8. In Drupal 7 we had lot of amazing contributed Installation profiles like Commerce Kick Start, Open Atrium, aGov, etc. Here we are going to discuss about how to create the installation profile in Drupal 8 and the benefit of using an installation profile in our Drupal Development World. Before that let us find out the answers for the following questions….
- What is…
Valuebound: How to reduce your development hours by Creating an Installation Profile or Distribution in Drupal 8!
Creating and installation profile in Drupal 8 is quite easy according to my humble opinion. Why? Because of the Configuration Management System in Drupal 8. In Drupal 7 we had lot of amazing contributed Installation profiles like Commerce Kick Start, Open Atrium, aGov, etc. Here we are going to discuss about how to create the installation profile in Drupal 8 and the benefit of using an installation profile in our Drupal Development World. Before that let us find out the answers for the following questions….
- What is…
This module enables the Accessibility Checker plugin from CKEditor.com in your WYSIWYG. This plugin is an innovative solution that lets you inspect the accessibility level of content created in CKEditor and immediately solve any accessibility issues that are found.Requirements
CKEditor Module (Core)
Exclude content types from node search for Drupal 8.Installation
Download and enable the search_exclude module.Configuration
- Go to /admin/config/search/pages.
- Find the 'Search pages' config.
- Create a new 'Content (exclude)' search page.
- Under 'Exclude content types', select the content types to exclude from the search index.
- Disable the default Content search and make your new search page the default.
It may be absolutely fine for a user to check out one page, especially if it's a press release or another event driven piece of content. But if your goal is to build a relationship with your visitors, one and done won't cut it.
Here are some of the most common problems in website design:
- There's no clear path. You want to extend a warm welcome to your visitors. Give them an easy way in and through. Too much competition for attention is a turn off. When you provide too many options, the functional result is no options.
- Outdated design. Your site was state of the art in 2009. It's got a header, a couple of sidebars, and a big chunk of information running down the center. Guess what? It looks like it's nearly a decade old. Because it is. Time to refresh with current design thinking. The layout of a page has evolved over the past decade. These days the best sites break up content into smaller, digestible bits.
- Overused stock images and icons. If visitors see the same image on multiple sites, it erodes trust. That picture of people sitting around the conference table? They sure get around to a lot of offices!
- Too many textures and colors. You are trying to add interest, but you just add clutter. Limit colors and fonts. Maintain a thematic color scheme. For professional sites, try to limit the variety of fonts to three or fewer.
- Design for the wrong reasons. Always begin by identifying your target audience and customizing design and content. You may want your site to look "modern" or like another site you've seen, but if you haven't checked in with what your audience needs and wants, you can fail miserably.
- Cute that doesn't cut it. When your links have adorable, witty names, the experience gets tired fast. Links that don't make much sense are not user friendly and won't ingratiate you with your visitors. Be practical and basic when naming links. Make it easy for people. Design for multiple visits. A rotating banner is cool the first time, and maybe the second, but at some point it's just a stale eyesore. Monotonous calls to action.
- Your site isn't optimized for mobile. You shouldn't need to be reminded of this, but numbers don't lie. Mobile is overtaking desktop. It's increasingly likely that your visitors see your site on a tiny screen. If they have to pinch and stretch to read, they'll find a better source of information. Be sure to test your site on smartphone and tablet.
- You play hard to get. If you want customers to find you, make sure your address, phone number and hours of operation are easily accessible on your site. Too often, that information is hidden or completely absent.
An Endzeitgeist.com review
The first After School Adventure with an Alice in Wonderland-theme clocks in at 15 pages, 1 page front cover, 1 page editorial/SRD, leaving us with 13 pages of content, so let's take a look!
This review was moved up in my review-queue as a prioritized review at the request of my patreons.
First of all - this is the first of a series of 5 adventures that bring new players up to level 5; as written, it is intended to get PCs halfway to level 2. However, since the module as such is basically defined by its nature as a kind of minigame, this book can easily be inserted into most longer modules - including the superb Pixies on Parade, for which inclusion notes are part of the deal.
This being an adventure review, the following contains SPOILERS. Potential players should jump to the conclusion.
All right, still here? The module begins with the famous white rabbit popping up and who ever needed a chance to chase after the guy? Right! So, the PCs follow the fully statted, planeshifting and constantly teleporting white rabbit (whose statblock had a minor glitch that has since been rectified) into the dark green wood and here is where the module becomes its own minigame - you see, the map of the chase is basically a whole boardgame-style playing field. Each round, a character can move 6 squares, 4 if small on this playing fields. . (Alternatively, you can roll the dice for movement, which I'd actually recommend!)
The board has multiple challenge squares - stopping in one with a challenge helps you speed the process along. Magic challenges let you teleport to the next magic challenge field on a successful Spellcraft check, with failure sending them one square back. Save challenges are based on attribute-based saving throws, while shortcut and skill challenges are based on skill check rolls like Wisdom (Perception) or Dexterity (Acrobatics) etc. The first character at the final clearing receives a treasure, but also has to face the boss, the tangleme tree (challenge 1/2) alone for a whole turn before the other PCs catch up - in the tree's embrace, the rabbit awaited - and a cake that should be eaten later already hints at the next adventure to come. On an aside - the tangleme tree's build is actually more interesting than in the PFRPG-version, so kudos there!
If you want, btw., you can also enjoy the map of the chase in a 6-page blown-up version that you can assemble and use minis with, for example. Should you be picky about the like - the lowest bottom parts of the map sport a relatively unobtrusive advertisement, but one you can easily cut off. In my test, none of the kiddos minded it, though.
Editing and formatting are top-notch, I noticed no glitches. Layout adheres to a beautiful 2-column full-color standard and the pdf comes fully bookmarked for your convenience. The full-color artwork is gorgeous and appropriate for even the smallest of kids.
J Gray's first trip to Wonderland was very interesting for me. Why? Because, frankly, I wouldn't have used the Alice-mythology. Having read so many treatises and twists on the subject matter, it's hard for me to see the material with the same wide-eyed wonder I did as a child. Among all those gritty and dark revamps, taking the tropes and making them innocent is something I appreciated more than I thought I would. At the same time, you have to be aware that this module is neither particularly complex or unique in its mechanics - by design.
Why? Well, this is pretty much intended for players who have never played and RPG before. The challenges are pretty much simple "learn to roll X"-types of challenges that teach the basics pretty fast. The combat at the end etc. also are solid and fun, though perhaps not suitable challenges for kids that already have amassed some serious RPG-experience: If your kids have e.g. already completed a toned down AP made more child-friendly...then this won't challenge them. If, however, you're looking for a great gateway module that doesn't demand too much and that, by virtue of its design, looks much like a familiar board-game, then this will do the trick better than any other module I've reviewed so far.
Even experienced groups can get something out of this, though; namely the fact that you can scavenge the chase and chase-board and increase the challenge. Personally, I think that makes it rather worthwhile. As for a final verdict: For me and my players, this was a good experience; not a stellar one, but a nice one. Unlike the first After School Adventure, it focused more on teaching playing mechanics rather than teaching; how you react to that pretty much depends on what you've been looking for. In the end, though, such a verdict would not be fair - this module tries to teach the truly young ones the game and does so in an appropriately non-threatening, fun manner with nary a chance for failure possible.
While this does not suit every table, particularly for bringing new kids into the game, this does a great job - and this is what its intention ultimately is. Hence, I will rate this according to its intended goal, which it achieves. For kids ages 4 -6, this is a neat introduction, in particular for the more sensitive ones that don't already want to be Red Sonja or a similarly uncommon character due to their parents or elder siblings - for this, its intended audience, this certainly is a 5-star module. Older players and groups should take aforementioned caveats into account when getting this, but nonetheless, I'm looking forward to seeing how this mini-AP continues!