Drupal Association blog: Experiences as an elected Board Director - Suzanne Dergacheva

Planet Drupal - Tue, 2019/07/02 - 6:07pm

It is that time of year again where we can all consider nominating ourselves for election to the board of the Drupal Association. But what does that mean? What could you expect to be involved in and what might you learn from the experience? We asked our current board members who were elected to tell us their own experiences, starting with Suzanne Dergacheva, elected in 2018:

Around a year ago, I was elected to the board of the Drupal Association. I had been on board before, and participated in community initiatives and event organizing. But I didn’t know exactly what to expect.

How much time does it take?

As a community board member, you’re probably already involved in a lot of community activities: organizing local events, working on initiatives in the community, and/or contributing code. And if anything, being on the board makes you more excited to push these activities forward. It’s hard to make time for everything, and of course it’s hard to know what to prioritize.

Being part of the board doesn’t mean that you can magically improve things. It takes time to move a large community forward. I’m used to being able to make decisions at the web agency that I run, and have them implemented in weeks and months. Because Drupal has such a large, contribution-driven community, making changes takes time. Your role is to come up with a strategy or plan that the association and community can act on.

There are different board committees with different responsibilities: I’ve been involved in the governance committee (creating a framework to support local Drupal communities), and the revenue committee (expanding the scope of the association so we can do more work). I’ve also worked on the Promote Drupal initiative to help organize volunteers to create the new Drupal Pitch Deck, and been part of talks about the new Drupal Event Organizers group.

What’s the best part about being on the board?

I’ve really enjoyed getting insights from others in the community - especially hearing ideas about how to grow the community. For example, I’ve loved being part of conversations about community building and being able to point people who want to contribute to the right place.

I’ve also learned a lot from being on the board from my fellow board members. They’re a diverse and multi-talented group, they ask great questions, and have really forward-thinking ideas.

What’s the Drupal Association doing?

Growing the community:

It’s a great time to be involved with the Drupal Association because it’s a forward-looking time. In the past, the scope of the Drupal Association has been organizing DrupalCon and running Drupal.org. Now, we have the role of brainstorming how to expand this scope. Providing more structure to local associations and events, Marketing Drupal, proving more member benefits, and developing products like Drupal Steward. The goal is to grow the community and provide the support/resources to grow the project. These are lofty goals for an open source project, especially since Drupal now finds itself competing with Adobe and Wordpress, that have really different models.

As a board, we’re actively thinking of more ways that the Drupal Association can propel the community. These are the types of conversations we’re having.

Fostering the community:

One of the new responsibilities of the community-elected board members is being on the community working group review committee along with an external member. This was added recently as part of updating the community working group (CWG) charter, so that it can take advantage of resources and support from the Drupal Association. So far, we worked with CWG to facilitate leadership training at DrupalCon.

Thank you Suzanne! Well, does that help you know more about what it means? Will you consider nominating yourself? You can go right ahead and…

nominate yourself

Categories:

Matt Glaman: Deprecation message support for PHPStan

Planet Drupal - Tue, 2019/07/02 - 4:25pm
Deprecation message support for PHPStan Published on Tuesday 2, July 2019

The end of May brought two exciting releases for PHPStan and the PHPStan Deprecation Rules extension. With the version of PHPStan v0.11.8, descriptions added to the @deprecated tag can be parsed and returned in rule checks.

Categories:

TIP Solutions: Regularly importing data from .CSV using CRON

Planet Drupal - Tue, 2019/07/02 - 3:23pm

In the last article we managed to set up all commerce types and additional modules to import the data from our csv files. Now we need to do this regularly in order to provide users with the latest updates from our remote Hotellinx server.

Importing data from the server and writing them into the csv files is done by hook_cron() in our custom module from the first article. We want to do this once every hour, so we use the ultimate cron module in order to set up different execution times for different cronjobs.

Hotellinx Migration Commerce Planet Drupal
Categories:

Srijan Technologies: Next Steps to Securing your Apigee Drupal 7 Developer Portal

Planet Drupal - Tue, 2019/07/02 - 1:40pm

As of May 31, 2020, Apigee will no longer sponsor hosting of Drupal 7-based developer portals (D7P). Prior to this, starting on May 31, 2019, Apigee will no longer provision Drupal sites for customers. 

Categories:

Third & Grove: 5 Reasons to Upgrade Your Site to Drupal 8, then 9

Planet Drupal - Tue, 2019/07/02 - 1:00pm
5 Reasons to Upgrade Your Site to Drupal 8, then 9 curtis Tue, 07/02/2019 - 07:00
Categories:

ComputerMinds.co.uk: ComputerMinds do GatsbyJS!

Planet Drupal - Tue, 2019/07/02 - 12:07pm

Here at ComputerMinds, we think of ourselves as Drupal specialists for the UK, but we don't limit ourselves to that. We offer clients a close working relationship and our general flexibility to get stuck into applying our skills to most problems. One of our clients, Alfresco, has come to trust us with more than just our Drupal wisdom. They wanted a new hub that would bring together documentation for a variety of their open source products, which are already on Github. Their documentation was written as Markdown files, so the hub would need to import and transform those files into HTML pages for the web. Essentially, a static site generator was needed.

 

 

GatsbyJS is one of these static site generators, based on the incredibly popular React javascript library. It's very easy to get it to work with Markdown files, it's blazing fast, and helps us fulfil a variety of other requirements too. As much as we love Drupal, it's not the right tool for every job. (That's a subject for another day!) A 'JAMstack' approach was appealing for this project because the site would be a clever front-end for content that already existed elsewhere. There would be no need to have user authentication, content workflow, moderation, or many other dynamic website features that Drupal excels at.

A documentation page on the completed Alfresco Builder Network.

For many of us at ComputerMinds, this was our first dive into working with React, let alone Gatsby itself. So the wonderful documentation and tutorials for Gatsby were a huge help. As our project was for displaying documentation, the Gatsby documentation site itself was a helpful influence on the eventual design and user interaction of our site.

The most obvious difference between Drupal and GatsbyJS, was that the coding was mainly in javascript, rather than PHP. It was great to use much more modern javascript code patterns and tools - even if it took a bit of head-scratching to get there! All credit should go to Steve Tweeddale in our Coventry office for his patience with my million questions as we worked towards building a Minimum Viable Product early on in the project timeline. As the site took shape beyond that, we drew on more and more concepts from the GatsbyJS and React ecosystems. Here's a few that were particularly interesting:

No doubt someday we'll be turning our hands to bring the best of Gatsby and Drupal together! 'Headless', or 'decoupled' Drupal has become one of the new trendy ways to use Drupal. This means using Drupal to define your app's information architecture or as a content repository. Other applications can then connect to it to display content to users. Those applications could be made in Gatsby, React, Drupal, or almost anything else. We still feel this is usually only worthwhile when Drupal is used as a back-end system for multiple front-ends. But regardless we are looking forward to using GatsbyJS again!

Categories:

Srijan Technologies: A Weekend at My First DrupalCamp

Planet Drupal - Tue, 2019/07/02 - 8:23am

DrupalCamp is a unique experience that you have to attend to understand” 

Categories:

Promet Source: Tips for PDF Accessibility

Planet Drupal - Tue, 2019/07/02 - 2:24am
The majority of communications regarding digital accessibility tend to focus on websites only. Too often, it’s overlooked that PDFs  are also required to be accessible. Here are some guidelines to help in the review and remediation of existing documents, along with guidance for ensuring accessibility of PDFs as they are created.  
Categories:

Hook 42: Drupal Core Initiative Meetings Recap - June 2019

Planet Drupal - Mon, 2019/07/01 - 8:48pm
Drupal Core Initiative Meetings Recap - June 2019 Lindsey Gemmill Mon, 07/01/2019 - 18:48
Categories:

Drupal Association blog: Back in Blue

Planet Drupal - Mon, 2019/07/01 - 6:49pm

As the second half of 2019 begins, we say farewell to the colorful logos we had for Pride Month but we don’t just pack up our logo and stop working to support under-represented groups in our community.

Nominations are now open for election to the board of the Drupal Association and we are still looking to especially encourage candidates who can help increase our representation and understanding of issues related to under-represented groups.

We also appreciated being challenged on how we build such knowledge into the rest of our board appointments and we elaborated more on that in the blog post at the beginning of the month. We will continue to strengthen our work in this area over the coming months.

We also want to help draw everyone’s attention to great work going on in our community to help us all increase our knowledge. We particularly want to draw attention to the Drupal Diversity & Inclusion’s recent blog post.

Thank you to all for keeping us focussed on what really matters - all of you. 💙

Categories:

Drupal core announcements: New help system for core (!!) needs your help!

Planet Drupal - Mon, 2019/07/01 - 2:44pm

I'm very pleased to announce that we (hopefully) have a new help system in Core that will actually serve the needs of module, theme, and distribution developers! It is called "Help Topics", and is currently in "Experimental Module" status in Drupal core 8.8.x.

The way it works:

  • Modules, themes, and distributions can have a help_topics subdirectory in their projects, where they can write help topics in the form of Twig template files. Each project can have as many topics as they want/need to document their project.
  • The Twig files have meta-data (in HTML meta tags) at the top to define the title of the topic, whether the topic is "top-level" or not, and a list of other topics to mark as "related".
  • When a user visits the admin/help page (assuming the Help and Help Topics modules are enabled), they will see a list of the top-level topics, and can click through to read them. When reading a topic, at the end they'll see a list of all the topics that are "related" (and "related" is automatically a bi-directional relationship).

So... The module is currently in "Experimental" status, and we need your help to get it to "Beta" and then "Stable" status in Drupal Core:

This effort is being led by andypost, Amber Himes Matz, and jhodgdon... if you have questions, we can all often be found on Slack or on drupal.org.

Categories:

New help system for core (!!) needs your help!

Documentation Team - Mon, 2019/07/01 - 2:44pm

I'm very pleased to announce that we (hopefully) have a new help system in Core that will actually serve the needs of module, theme, and distribution developers! It is called "Help Topics", and is currently in "Experimental Module" status in Drupal core 8.8.x.

The way it works:

  • Modules, themes, and distributions can have a help_topics subdirectory in their projects, where they can write help topics in the form of Twig template files. Each project can have as many topics as they want/need to document their project.
  • The Twig files have meta-data (in HTML meta tags) at the top to define the title of the topic, whether the topic is "top-level" or not, and a list of other topics to mark as "related".
  • When a user visits the admin/help page (assuming the Help and Help Topics modules are enabled), they will see a list of the top-level topics, and can click through to read them. When reading a topic, at the end they'll see a list of all the topics that are "related" (and "related" is automatically a bi-directional relationship).

So... The module is currently in "Experimental" status, and we need your help to get it to "Beta" and then "Stable" status in Drupal Core:

This effort is being led by andypost, Amber Himes Matz, and jhodgdon... if you have questions, we can all often be found on Slack or on drupal.org.

ADCI Solutions: Drupal 8 best practices: site-building

Planet Drupal - Mon, 2019/07/01 - 5:13am

Do you consider yourself an experienced Drupal site-builder?

Check yourself before reading this article. What modules’ switching on and off can help with Drupal SEO, Drupal security, Drupal performance and maintenance? 

Now check the article and compare your answers!
Drupal 8 best practices: site-building

 

 

Categories:

DrupalEasy: Sharing your DDEV-Local site via a public URL using "ddev share" and ngrok

Planet Drupal - Sun, 2019/06/30 - 6:34pm

Version 1.9.0 of DDEV-local introduced the ability to share your local project online via a temporary, public URL using ngrok.

This allows you the ability to quickly and securely provide access to your local site to other developers and stakeholders as well as an easy way to test your local site on other devices.

ngrok is a service that exposes local servers behind NATs and firewalls via public URLs over secure tunnels. Once the small ngrok client is installed on your local machine, the ddev share command will enable the sharing and provide you with a public URL for your local site.

While there are paid tiers for the ngrok service, a free tier is provided with reasonable limits on usage. See the ngrok web site for details. In the first example, we'll utilize the free, anonymous tier.

The free, anonymous tier does not encrypt your data between your local and the ngrok servers, even though an https connection is provided from the ngrok servers to connected clients. Therefore, it is strongly suggested that once you get the free, anonymous tier working, create a free account and authenticate your local ngrok client to ensure your data is encrypted the entire trip.

Note that this is a one-time setup for your machine, and does not have to be repeated for each of your DDEV-Local projects.


Step 1: Install the ngrok client

Download and install the client specific to your OS from https://ngrok.com/download. While there are instructions to download and install ngrok on various operating systems, I found that using Homebrew (Mac OS X and Linux) was easiest:

brew cask install ngrok

If you're using Windows 10 and Chocolately, then I recommend installing with:

choco install ngrok

Step 2: Sharing your local site

Run the following:

ddev share

If successful, this command will return some information about the share, including public URLs with which you can access the site.

As requests are made to the site, the screen will update detailing each request.

Note that in the screenshot above, that the "https://94d5c548.ngrok.io" public URL is forwarding the insecure "http://127.0.0.1:32786". If we were to set up a ngrok account and authenticate our local ngrok client, it would be forwarding "https://127.0.0.1:32786" instead.

Use Crtl-C to stop the sharing.

Additional ngrok features and functionality

Secure your data by signing up for a free ngrok account and then authenticating your local ngrok client with your account credentials using the command provided by the ngrok web site:

./ngrok authtoken

Once your local ngrok client is authenticated, the next time you do a ddev share, you'll be able to see that your connection uses https from end-to-end.

While the free ngrok plan is normally sufficient for smaller projects, paid ngrok plans include multiple users, custom domains and subdomains, additional connections, static IP addresses, and other features.

This tutorial is an excerpt from version 3 of Michael Anello's Local Development with DDEV Explained book - coming soon! Version 3 will include everything new to DDEV-Local through version 1.9.1. Pick up an electronic copy of Version 2 for less than $10 and you'll automatically get free access to Version 3.

Categories:

Agiledrop.com Blog: Recap of Acquia's webinar on Content as a Service

Planet Drupal - Sun, 2019/06/30 - 4:00pm

Here's a recap of Acquia's webinar on content as a service held on June 27. Give it a read if you weren't able to attend it or just need a refresher.

READ MORE
Categories: