Drulma is a base theme for Drupal.
It is built to use the Bulma CSS framework.

Features

• Implements markup from Bulma adapted to Drupal.
• Comes with a simple layout out of the box, a hero header and some regions.
• Uses BulmaJS for JS interactions (no jQuery).

Installation

After installing, you can optionally install
the Drulma Companion module.
This module implements additional blocks such as navbar and tabs.
It also adds template suggestions for fontawesome 5 icons.
To be able to use the fontawesome 5 icons the
Libraries provider fontawesome
module is needed.
This makes fontawesome installation optional.

The theme can't depend on the module to be installed until
this issue is solved

Default layout

By default all the blocks installed and content region will
be wrapped in a container class so the content is nicely centered
but this can be removed on the configuration of the theme.
This is the main reason why the Drulma companion depends
on the block class
module.

It also tries to be minimalistic in the regions used.
The header is implemented as a Bulma hero

Version and loading of Bulma.

By default Bulma is going to be loaded using the
jsdelivr CDN and the
version specified in the drulma.libraries.yml file.

Install the
Libraries provider module
to use a local version, update the version or use
Bulmaswath themes.

BulmaJS

The following components are implemented:

• Navbar: Open navbar on mobile devices.
• Message: Dismiss messages.
• File: Nicer file widget.

Contributions to add more or integrate them better are welcome.

Documentation

The most useful docs are at bulma.io.

If popularity of this project rises a separate page for Drulma will be
created to learn about how Drupal and Bulma are integrated.

Subtheming

Drush 9 Does not support commands coming from themes
so you need to install Drulma companion in order to generate a subtheme.
If the companion is only used for the subtheme generation it can be uninstalled.

You can read more about themes providing drush commands at:

https://github.com/drush-ops/drush/pull/3089

https://www.drupal.org/project/drupal/issues/2002606#comment-10786044

Contributions

The project is open to improvements on how to override
Drupal markup to make it more adapted to Bulma but also
feel free to open any discussion about how to make Bulma
and Drupal play nicely together.

Patches on drupal.org are accepted but merge requests on
gitlab are preferred.

Real time communication

You can join the #drulma
channel on drupalchat.me.

Related projects

Bulma CSS is an earlier implementation
of Bulma as a Drupal theme. The project seems to overcomplicate the theme implementation
while Drulma tries to implement almost every feature of that project in more flexible way.
You will find less global settings in Drulma since they are in the blocks provided by
Drulma companion or easily overridable with a theme twig template.

Diferences

• Drulma supports Fontawesome 5 with a set of template suggestions. No icon guessing.
• The navbar is implemented as a block so you can have many instances.
• In Drulma you can remove all the container classes from configuration so you get a wider layout.
• Drulma supports Drush 9 and above only (Drulma companion needed).
• Quickedit not tested in Drulma (the Bulma CSS theme has some overrides that maybe can be adapted).
• Comments are not supported in Drulma. Patches are welcome.
• No breadcrumb configuration (easily overridable with a template) but it can be a good first contribution.

The JSON:API module was added to Drupal 8.7 as a stable module!

See Dries’ overview of why this is an important milestone for Drupal, a look behind the scenes and a look toward the future. Read that first!

Upgrading?

As Mateu said, this is the first time a new module is added to Drupal core as “stable” (non-experimental) from day one. This was the plan since July 2018 — I’m glad we delivered on that promise.

This means users of the JSON:API 8.x-2.x contrib module currently on Drupal 8.5 or 8.6 can update to Drupal 8.7 on its release day and simply delete their current contributed module, and have no disruption in their current use of JSON:API, nor in security coverage! 1

What’s happened lately?

The last JSON:API update was exactly two months ago, because … ever since then Gabe, Mateu and I are have been working very hard to get JSON:API through the core review process. This resulted in a few notable improvements:

1. a read-only mode that is turned on by default for new installs — this strikes a nice balance between DX (still having data available via APIs by default/zero config: reading is probably the 80% use case, at least today) and minimizing risk (not allowing writes by default) 2
2. auto-revisioning when PATCHing for eligible entity types
3. formally documented & tested revisions and translations support 3
4. formally documented security considerations

Get these improvements today by updating to version 2.4 of the JSON:API module — it’s identical to what was added to Drupal 8.7!

Contributors

An incredible total of 103 people contributed in JSON:API’s issue queue to help make this happen, and 50 of those even have commits to their name:

Wim Leers, ndobromirov, e0ipso, nuez, gabesullice, xjm, effulgentsia, seanB, jhodgdon, webchick, Dries, andrewmacpherson, jibran, larowlan, Gábor Hojtsy, benjifisher, phenaproxima, ckrina, dww, amateescu, voleger, plach, justageek, catch, samuel.mortenson, berdir, zhangyb, killes@www.drop.org, malik.kotob, pfrilling, Grimreaper, andriansyahnc, blainelang, btully, ebeyrent, garphy, Niklan, joelstein, joshua.boltz, govind.maloo, tstoeckler, hchonov, dawehner, kristiaanvandeneynde, dagmar, yobottehg, olexyy.mails@gmail.com, keesee, caseylau, peterdijk, mortona2k, jludwig, pixelwhip, abhisekmazumdar, izus, Mile23, mglaman, steven.wichers, omkar06, haihoi2, axle_foley00, hampercm, clemens.tolboom, gargsuchi, justafish, sonnykt, alexpott, jlscott, DavidSpiessens, BR0kEN, danielnv18, drpal, martin107, balsama, nileshlohar, gerzenstl, mgalalm, tedbow, das-peter, pwolanin, skyredwang, Dave Reid, mstef, bwinett, grndlvl, Spleshka, salmonek, tom_ek, huyby, mistermoper, jazzdrive3, harrrrrrr, Ivan Berezhnov, idebr, mwebaze, dpolant, dravenk, alan_blake, jonathan1055, GeduR, kostajh, pcambra, meba, dsdeiz, jian he, matthew.perry.

Thanks to all of you!

Future JSON:API blogging

I blogged about once a month since October 2018 about JSON:API, to get more people to switch to version 2.x of the JSON:API module, to ensure it was maximally mature and bug free prior to going into Drupal core. New capabilities were also being added at a pretty high pace because we’d been preparing the code base for that months prior. We went from ~1700 installs in January to ~2700 today!

Now that it is in Drupal core, there will be less need for frequent updates, and I think the API-First Drupal: what’s new in 8.next? blog posts that I have been doing probably make more sense. I will do one of those when Drupal 8.7.0 is released in May, because not only will it ship with JSON:API land, there are also other improvements!

Special thanks to Mateu Aguiló Bosch (e0ipso) for their feedback!

1. We’ll of course continue to provide security releases for the contributed module. Once Drupal 8.7 is released, the Drupal Security Team stops supporting Drupal 8.5. At that time, the JSON:API contributed module will only need to provide security support for Drupal 8.6. Once Drupal 8.8 is released at the end of 2019, the JSON:API contributed module will no longer be supported: since JSON:API will then be part of both Drupal 8.7 and 8.8, there is no reason for the contributed module to continue to be supported. ↩︎

2. Existing sites will continue to have writes enabled by default, but can choose to enable the read-only mode too. ↩︎

3. Limitations in the underlying Drupal core APIs prevent JSON:API from 100% of desired capabilities, but with JSON:API now being in core, it’ll be much easier to make the necessary changes happen! ↩︎

• Drupal
• API
• Acquia

Void is a responsive three column multi-purpose theme built using flexbox. More info coming soon..

With robust and flexible infrastructure, innovative design and some great out of the box features, Drupal CMS is one of the top web solutions considered by businesses around the world to stay abreast with the surge in demand for personalization, interactivity and scalable tools. However, it turns out that a lot of marketers are quite unfamiliar with Drupal's potential.

As you may know, Drupal 6 has reached End-of-Life (EOL) which means the Drupal Security Team is no longer doing Security Advisories or working on security patches for Drupal 6 core or contrib modules - but the Drupal 6 LTS vendors are and we're one of them!

Today, there is a Moderately Critical security release for Drupal core to fix a Cross Site Scripting (XSS) vulnerability.

Folks have been asking us, so this is just a short note to say that this issue does NOT affect Drupal 6. So, you can focus just on updating your Drupal 7 and Drupal 8 sites today. :-)

Thanks!

Project: Drupal coreDate: 2019-March-20Security risk: Moderately critical 13∕25 AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:DefaultVulnerability: Cross Site ScriptingDescription: 

Under certain circumstances the File module/subsystem allows a malicious user to upload a file that can trigger a cross-site scripting (XSS) vulnerability.

Solution: 

• If you are using Drupal 8.6, update to Drupal 8.6.13.
• If you are using Drupal 8.5 or earlier, update to Drupal 8.5.14.
• If you are using Drupal 7, update to Drupal 7.65.

Versions of Drupal 8 prior to 8.5.x are end-of-life and do not receive security coverage.

Reported By: 

• Zero Day Initiative

Fixed By: 

• Alex Pott of the Drupal Security Team
• Lee Rowlands of the Drupal Security Team
• Greg Knaddison of the Drupal Security Team
• Neil Drumm of the Drupal Security Team
• Michael Hess of the Drupal Security Team
• David Rothstein of the Drupal Security Team
• Peter Wolanin of the Drupal Security Team

New to DrupalCon? We’re glad you’re joining us in Seattle!

Here are ideas to help you prepare for this exciting week among thousands of other Drupalers, while hundreds of sessions, summits, trainings, just-for-fun events, and more are all happening—some simultaneously. We have tips for during the conference and afterward, so make the most of this new experience! 

From a quarter to almost one-third of content in the World Wide Web repeats itself. According to Google's head of search spam, Matt Cutts, around 25-30% of web content is duplicate. Your website is also likely to have duplicate content, even if it follows web content writing rules. In this post, we will touch upon the reasons and risks of duplication, as well as review useful modules that fix duplicate content in Drupal.

The highlight of the month: our annual retreat.

Between February 21-24, Team Axelerant traveled to beautiful Goa, India from their homes all over the world to attend our annual retreat. We had almost 60 of us there on the beach.

Hello!

Three Rivers Park District is looking for a vendor to partner with on a maintenance contract for its website: ThreeRiversParks.org. In the request for proposal, you will find information about the Park District, the website, future projects of interest, criteria for selecting a partner and how to submit a proposal.

Please feel free to share this with anyone who might be interested in submitting a proposal.

Thank you!

Drupal 8.6 became one of the most interesting releases in Drupal 8’s history. It brought us the oEmbed feature, the Media Library, the Workspaces module, and more. But it’s time to move forward, and in May 2019 we expect Drupal 8.7. Its “alpha” version has just been released. Although an alpha version is not a final one, we will gladly take a look at it and discuss what to expect in Drupal 8.7.

Drupal 8.7: the alpha version

Drupal 8.7.0-alpha1 has come out on March 14, 2019. Alpha versions are far from being ready for production sites. They are just preliminary releases that allow developers to do a good testing, receive feedback, make final preparations, and fix bugs.

We've started a series of blog posts that tell the story of what makes our developers successful when working with other Drupal teams. The fourth and final chapter ties things together by presenting our company culture which strikes the perfect balance between the needs and wants of both our employees and our clients.

READ MORE

Team Axelerant went to beautiful Goa, India for a few days this February for our annual company retreat. It was a fantastic gathering, full of warmth, energy and incredible vibes.

In preparation for his fourth DrupalCon, Chris O’Donnell, Digital Strategist, for Promet Source shared his views on the vibe of this annual conference, as well as Drupal’s current standing within the ecosystem of enterprise-level CMS platforms.     What are you looking forward to at Drupalcon this year?

Problem

The answer is Drupal's Migrate API, which is incredibly powerful but can feel overwhelming. When I migrated MSKCC.org from Drupal 6 to Drupal 8, the Migrate API was just being introduced into Drupal 8 core, and I felt more comfortable writing a custom migration script instead of using code that was still under development. Migrate API is now stable and if you are an experienced Drupal developer, you should use it.

The level of expertise required to build and maintain a Drupal 8 website has changed from Drupal 7, mainly because we are creating more ambitious digital experiences. The Drupal community struggles to simplify our flexible and sometimes complex product. My approach is to make the Webform module as flexible and robust as possible, while not forgetting that people need a simple way to start building a form. This is exactly why I include an introduction video on the Webform module's main page. Besides making the Webform module an awesome tool for experienced Drupal site builders, the Webform module needs to be welcoming to new users and make it easy for them to move their existing forms to Drupal.

Either an organization is starting from scratch and building a new Drupal site, or more commonly an organization has decided they need to provide a more ambitious digital experience and they have chosen to switch to Drupal. In both situations, we need to make it easy for someone to switch from other form builders to Webform.

The problem that needs to be addressed is…

Solution

The simplest way to migrate to the Webform module is to rebuild an external form and then import the existing data. Building a webform is fun and easy, forms are a critical aspect to most websites; it is worth taking the time needed...Read More

The Rundown

At Phase2 we’re always looking to pinpoint the real problem and solve it. Let’s say we have a new project to implement a design system for The First Order. We’ve done work for their parent organization in the past and already have a design system in place for The Empire. The site architecture calls for creating a multi-site and multi-design implementation to make use of The Empire’s assets for The First Order.

Migration FranceTVSport.fr to Drupal 8 and Symfony 4 Submitted by Frederic Marand on Mon, 2019-03-18 14:03

• Read more about Migration FranceTVSport.fr to Drupal 8 and Symfony 4
• Add new comment

The opening talk as DrupalCamp Paris 2019 was a presentation given by Thomas Jolliet (FranceTV) and yours truly about how we rebuilt FranceTV Sport to a Symfony 4 / headless Drupal 8 combo.

The most salient points of the talk are probably the "defense in depth" mechanisms we built for scalability and fault tolerance, and the business results, like -85% full page load time or +50 iOS users.