How to remove YouTube tracking

I don't use Google Analytics or any other web analytics service on dri.es. Why not? Because I don't desire to know how many people visit my site, where they come from, or what operating system they use.

Because I don't have a compelling reason to track my site's visitors, I don't have to bother anyone with a "cookies consent" popup either. That is a nice bonus because the web is littered with those already. I like that dri.es is clutter-free.

This was all well and good until a couple of weeks ago, when I learned that when I embed a YouTube video in my blog posts, Google sends an HTTP cookie to track my site's visitors. Be damned!

After some research, I discovered that YouTube offers a privacy-enhanced way of embedding videos. Instead of linking to youtube.com, link to youtube-nocookie.com, and no data-collecting HTTP cookie will be sent. This is Google's way of providing GDPR-compliant YouTube videos.

<iframe width="640" height="360" src="https://www.youtube-nocookie.com/embed/video-id" frameborder="0">

So I went ahead and updated all blog posts on dri.es to use youtube-nocookie.com.

In addition to improving privacy, this change also makes my site faster. I used https://webpagetest.org to benchmark a recent blog post with a YouTube video.

Before:

When embedding a video using youtube.com, Google uses DoubleClick to track your users (yellow bar). A total of 22 files were loaded, and the total time to load the page was 4.4 seconds (vertical blue line). YouTube makes your pages slow, as the vast majority of requests and load time is spent on loading the YouTube video.

After:

When using youtube-nocookie.com, Google no longer uses DoubleClick to track your users. No HTTP cookie was sent, "only" 18 files were loaded, and the total page load time was significantly faster at 2.9 seconds (vertical blue line). Most of the load time is still the result of embedding a single YouTube video.
Source: Dries Buytaert www.buytaert.net


JSON:API lands in Drupal core

Breaking news: we just committed the JSON:API module to the development branch of Drupal 8.

In other words, JSON:API support is coming to all Drupal 8 sites in just a few short months! 🎉

This marks another important milestone in Drupal's evolution to be an API-first platform optimized for building both coupled and decoupled applications.

With JSON:API, developers or content creators can create their content models in Drupal’s UI without having to write a single line of code, and automatically get not only a great authoring experience, but also a powerful, standards-compliant, web service API to pull that content into JavaScript applications, digital kiosks, chatbots, voice assistants and more.

When you enable the JSON:API module, all Drupal entities such as blog posts, users, tags, comments and more become accessible via the JSON:API web service API. JSON:API provides a standardized API for reading and modifying resources (entities), interacting with relationships between resources (entity references), fetching of only the selected fields (e.g. only the "title" and "author" fields), including related resources to avoid additional requests (e.g. details about the content's author) and filtering, sorting and paginating collections of resources.

In addition to being incredibly powerful, JSON:API is easy to learn and use and uses all the tooling we already have available to test, debug and scale Drupal sites.

Drupal's JSON:API implementation was years in the making

Development of the JSON:API module started in May 2016 and reached a stable 1.0 release in May 2017. Most of the work was driven by a single developer partially in his free time: Mateu AguilĂł Bosch (e0ipso).

After soliciting input and consulting others, I felt JSON:API belonged in Drupal core. I first floated this idea in July 2016, became more convinced in December 2016 and recommended that we standardize on it in October 2017.

This is why at the end of 2017, I asked Wim Leers and Gabe Sullice — as part of their roles at Acquia — to start devoting the majority of their time to getting JSON:API to a high level of stability.

Wim and Gabe quickly became key contributors alongside Mateu. They wrote hundreds of tests and added missing features to make sure we guarantee strict compliance with the JSON:API specification.

A year later, their work culminated in a JSON:API 2.0 stable release on January 7th, 2019. The 2.0 release marked the start of the module's move to Drupal core. After rigorous reviews and more improvements, the module was finally committed to core earlier today.

From beginning to end, it took 28 months, 450 commits, 32 releases, and more than 5500 test runs.

The best JSON:API implementation in existence

The JSON:API module is almost certainly the most feature-complete and easiest-to-use JSON:API implementation in existence.

The Drupal JSON:API implementation supports every feature of the JSON:API 1.0 specification out-of-the-box. Every Drupal entity (a resource object in JSON:API terminology) is automatically made available through JSON:API. Existing access controls for both reading and writing are respected. Both translations and revisions of entities are also made available. Furthermore, querying entities (filtering resource collections in JSON:API terminology) is possible without any configuration (e.g. setting up a "Drupal View"), which means front-end developers can get started on their work right away.

What is particularly rewarding is that all of this was made possible thanks to Drupal's data model and introspection capabilities. Drupal’s decade-old Entity API, Field API, Access APIs and more recent Configuration and Typed Data APIs exist as an incredibly robust foundation for making Drupal’s data available via web service APIs. This is not to be understated, as it makes the JSON:API implementation robust, deeply integrated and elegant.

I want to extend a special thank you to the many contributors that contributed to the JSON:API module and that helped make it possible for JSON:API to be added to Drupal 8.7.

Special thanks to Wim Leers (Acquia) and Gabe Sullice (Acquia) for co-authoring this blog post and to Mateu AguilĂł Bosch (e0ipso) (Lullabot), Preston So (Acquia), Alex Bronstein (Acquia) for their feedback during the writing process.
Source: Dries Buytaert www.buytaert.net


Drupal for content editors (Introductory course)

Start: 
2019-04-11 09:00 - 12:00 Australia/Brisbane

Organizers: 

VladimirAus

Event type: 

Training (free or commercial)

https://www.tomato-elephant-studio.com/events/2019-04-18

Introductory 3 hour workshop "Drupal for content editors" is coming to Brisbane and Gold Coast as part of Drupal Global Training Day.
WORKSHOPS
Gold Coast :: Thu, 11 Apr 2018 :: 09:00-12:00 :: More info TBA
Brisbane :: Thu, 18 Apr 2018 :: 09:00-12:00
SCHEDULE
09:00-11:30 :: Introduction & Training. Module 1
11:30-12:00 :: Wrap up
AGENDA
Introduction to Drupal content editing
Introduction to media library
Content modification
Basic blocks
Basic views
REQUIREMENTS
Limited seats are available. Register here.
PROVIDED
Wifi, powerpoints
Refreshments
SPONSORS
Tomato Elephant Studio :: training sponsor
Drupal Brisbane :: partner
Drupal Gold Coast :: partner
For sponsorship and other enquiries contact training@tomato-elephant-studio.com
LET OTHERS KNOW YOU ARE ATTENDING:
Share on social media. Use hashtag #drupalGTD
Drupal Groups: https://groups.drupal.org/node/534911
meetup.com: TBA
UNABLE TO ATTEND?
If you are unable to attend, please let us know as soon as possible by replying to training@tomato-elephant-studio.com.
Source: https://groups.drupal.org/node/512931/feed


Global Training Day #8

Start: 
2019-04-20 11:30 - 2019-04-21 15:25 UTC

Organizers: 

Anastasiya Dubina

adcillc

Event type: 

User group meeting

https://drupal-omsk.timepad.ru/event/908414/

GTD is a great opportunity for newcomers to learn about web development. We know Drupal and now we want to share our knowledge with you.
The next meeting will be held on April, 20-21. The first day of the event includes a rich theoretical agenda. And for those who want to try something new for them, we made a practical part on the second day.
At the free GTD sessions we will talk about:
- stages of a project;
- design of your site;
- front end and back end in Drupal;
- sites and modules development;
- Drupal community and its benefits.
Welcome to GTD if you are:
- a student with programming major;
- a developer who want to try other technologies;
- somebody who just wants to code.
See you at Global Training Day #8!
Source: https://groups.drupal.org/node/512931/feed


The Open Web can still win

Today, the world wide web celebrates its 30th birthday. In 1989, Sir Tim Berners-Lee invented the world wide web and changed the lives of millions of people around the globe, including mine.

Tim Berners-Lee, inventor of the World Wide Web, in front of the early web.Milestones like this get me thinking about the positive impact a free and Open Web has had on society. Without the web, billions of people would not have been able to connect with one another, be entertained, start businesses, exchange ideas, or even save lives. Global, open source communities like Drupal would not exist.

As optimistic as I am about the web's impact on society, there have been many recent events that have caused me to question the Open Web's future. Too much power has fallen into the hands of relatively few platform companies, resulting in widespread misinformation, privacy beaches, bullying, and more.

However, I'm optimistic that the Open Web has a chance to win in the future. I believe we'll see three important events happen in the next five years.

First, the day will come when regulators will implement a set of laws that govern the ownership and exchange of data online. It's already starting to happen with GDPR in the EU and various state data privacy laws taking shape in the US. These regulations will require platforms like Facebook to give users more control over their data, and when that finally happens, it will be a lot easier for users to move their data between services and for the Open Web to innovate on top of these data platforms.

Second, at some point, governments globally will disempower large platform companies. We can't leave it up to a handful of companies to judge what is false and true, or have them act as our censors. While I'm not recommending governments split up these companies, my hope is that they will institute some level of algorithmic oversight. This will offer an advantage to the Open Web and Open Source.

Third, I think we're on the verge of having a new set of building blocks that enable us to build a better, next-generation web. Thirty years into the web, our data architectures are still use a client-server model; data is stored centrally on one computer, so to speak. The blockchain is changing all that. The result will be a more decentralized web that operates on top of a distributed data layer and offers users control of their own data. Similar to building a traditional website, distributed applications (dApps) require file storage, payment systems, user data stores, etc. All of these components are being rebuilt on top of the blockchain. While we have a long way to go, the building blocks are being put in place. It is only a matter of time before a tipping point is reached.

In the past, I've publicly asked the question: Can we save the Open Web? I believe we can. We can't win today, but we can keep innovating and get ready for these three events to unfold. The day will come!

With that motivation in mind, I want to wish a special happy birthday to the world wide web!
Source: Dries Buytaert www.buytaert.net


Should Product Marketing report to Product or Marketing?

Product marketing teams are responsible for bringing products to market and championing their success and adoption. To make this happen, they work closely with three sets of key stakeholders: the product team (development/engineering), the marketing team and the sales team.
In some organizations, product marketing reports to marketing. In other organizations, it reports to product. The most common pattern is for product marketing teams to live in marketing, but in my opinion, a product marketing organization should sit where the highest frequency of communication and collaboration is needed. That can depend on the type of product, but also the maturity of the product.
For new products, companies with an evolving product strategy, or very technical products, it make most sense for product marketing to report directly to the product team. For mature and steady products, it makes sense for product marketing to report into marketing.
This reporting structure matters in that it facilitates communication and alignment.
For example, Acquia has recently decided to restructure product marketing to report to the product team, rather than marketing. We made this decision because there has been a lot of change and growth on the product front. With product marketing embedded into the product team at Acquia, we will ensure that we can bring the right messaging to the market quickly.
We've also added to our product leadership team, hiring an SVP of Product Marketing, Tom Wentworth to work closely with Matt Kaplan, our SVP of Product, and me. Those of you who have followed Acquia's story may know Tom as our former CMO and head of product marketing. You can read more about it in Tom's blog post — he explains why he rejoined Acquia, but also provides some great content management history.
Source: Dries Buytaert www.buytaert.net


Drupal Global Training & First time Sprinters 2019-0427 Tokyo-Japan

Start: 
2019-04-27 10:00 - 17:00 Asia/Tokyo

Event type: 

Training (free or commercial)

https://cmslabo.org/drupal-global-training-days/2019/0427

Hello,
Global Training Day April 27th 2019 Tokyo Japan
1) For first Drupal and CMS users
Getting started with Drupal 8 (one day training)
2) For Drupal users
First time Sprinters (one day)
this is Free one day training, event entry is;
https://cmslabo.doorkeeper.jp/events/88356
Please join Drupal Training and have fun!
Source: https://groups.drupal.org/node/512931/feed


Acquia sponsors NPR

As I wrote in my previous post, you might be seeing a lot more of Acquia in the coming weeks. If you listen to NPR, you may have heard our new radio ads.

Like our highway billboards and train station takeover, our NPR campaign is another great opportunity to reach commuters.

NPR is a national non-profit media organization with a network of more than 1,000 affiliated radio stations across the United States — and quite a few use Drupal and Acquia for their sites. It boasts listenership of nearly 30 million, and its airwaves reach nearly 99 percent of Americans.

Our NPR ads are running during the morning and evening commutes. In addition, Acquia ads will be featured on the Marketplace Tech podcast, which is popular among technology decision makers. Between the podcasts and radio ads, the potential reach is 64 million impressions.

We have always believed in doing well by doing good. Sponsoring NPR creates brand awareness for Acquia, but also supports NPR financially. High-quality media organizations are facing incredible challenges today, and underwriting NPR's work is a nice way for Acquia to give back.


Source: Dries Buytaert www.buytaert.net