All RPGs and Storygames by Tod Foley are now available at DrivethruRPG. Bring these games to your table!
With Drupal 9 approaching rapidly, it is an exciting time to be on the Drupal Association Board. The Association must continue to evolve alongside the project so we can continue providing the right kind of support. And, it is the Drupal Association Board who develops the Association’s strategic direction by engaging in discussions around a number of strategic topics throughout their term. As a community member, you can be a part of this important process by becoming an At-large Board Member.
We have two At-large positions on the Association Board of Directors. These positions are self-nominated and then elected by the community. Simply put, each At-large Director position is designed to ensure there is community representation on the Drupal Association Board.Inclusion 2018
In 2018, we made a special effort to encourage geographic inclusion through the people who were candidates for election and we were delighted that candidates stood in six continents all across the World — thank you!2019
Now, in 2019, and recognising we are in the middle of Pride Month, we want to particularly encourage nominations from candidates from underrepresented or marginalised groups in our community. As referenced later in this blog post, anyone is eligible to nominate themselves, and voters can vote for whichever candidate they choose, but we want to encourage this opportunity to amplify the voices of underrepresented groups with representation on the Association Board. And as we meet the candidates, whether they are allies or members of these groups themselves, we hope to center issues of importance to these communities - in addition to the duties of care for the management of the Association that are always central to a board role.
As always, any individual can stand for election to the board, but by centering these important issues we are determined to encourage a board made of diverse members as that gives them the best ability to represent our diverse community.
If you are interested in helping shape the future of the Drupal Association, we encourage you to read this post and nominate yourself between 29 Jun, 2019 and 19 July 2019.What are the Important Dates?
Self nominations: 29 Jun, 2019 to 19 July, 2019
Meet the candidates: 22 July, 2019 to 26 July, 2019
Voting: 1 August, 2019 to 16 August, 2019
Votes ratified, Winner announced: 3 September, 2019How do nominations and elections work?
Specifics of the election mechanics were decided through a community-based process in 2012 with participation by dozens of Drupal community members. More details can be found in the proposal that was approved by the Drupal Association Board in 2012 and adapted for use this year.What does the Drupal Association Board do?
The Board of Directors of the Drupal Association are responsible for financial oversight and setting the strategic direction for serving the Drupal Association’s mission, which we achieve through Drupal.org and DrupalCon. Our mission is: “Drupal powers the best of the Web. The Drupal Association unites a global open source community to build and promote Drupal.”
New board members will contribute to steer? shape? the strategic direction of the Drupal Association. Board members are advised of, but not responsible for, matters related to the day-to-day operations of the Drupal Association including program execution, staffing, etc.
Directors are expected to contribute around five hours per month and attend three in-person meetings per year (financial assistance is available if required).
Association board members, like all board members for US-based organizations, have three legal obligations: duty of care, duty of loyalty, and duty of obedience. In addition to these legal obligations, there is a lot of practical work that the board undertakes. These generally fall under the fiduciary responsibilities and include:
Overseeing Financial Performance
Setting and Reviewing Legal Policies
Managing the Executive Director
To accomplish all this, the board comes together three times a year during two-day retreats. These usually coincide with the North American and major European Drupal Conferences, as well as one February meeting. As a board member, you should expect to spend a minimum of five hours a month on board activities.
Some of the topics that will be discussed over the next year or two are:
Grow Drupal adoption through our channels and partner channels
Evolve drupal.org and DrupalCon goals and strategies.
There are no restrictions on who can run, and only self-nominations are accepted.
Before self-nominating, we want candidates to understand what is expected of board members and what types of topics they will discuss during their term. That is why we now require candidates to:
Read the Drupal Association bylaws
Read the board member agreement
Read The Drupal Association mission statement
During the elections, members of the Drupal community will ask questions of candidates. You can post comments on candidate profiles here on assoc.drupal.org.
In the past, we held group “meet the candidate” interviews. With many candidates the last few years, group videos didn’t allow each candidate to properly express themselves. We replaced the group interview and allow candidates to create their own 3-minute video and add it to their candidate profile page. These videos must be posted by 19 July, 2019, and the Association will promote the videos to the community from 22 July, 2019. Hint: Great candidates would be those that exemplify the Drupal Values & Principles. That might provide structure for a candidate video? You are also encouraged to especially consider diversity and inclusion.How do I run?
From 29 June, 2019, go here to nominate yourself. If you are considering running, please read the entirety of this post, and then be prepared to complete the self-nomination form. This form will be open on 29 June, 2019 through 19 July, 2019 at midnight UTC. You'll be asked for some information about yourself and your interest in the Drupal Association Board. When the nominations close, your candidate profile will be published and available for Drupal community members to browse. Comments will be enabled, so please monitor your candidate profile so you can respond to questions from community members. We will announce the new board member via our blog and social channels on 3 September, 2019.
Reminder, you must review the following materials before completing your candidate profile:
Read the Drupal Association bylaws
Read the board member agreement
Read The Drupal Association mission statement
Voting is open to all individuals who have a Drupal.org account by the time nominations open and who have logged in at least once in the past year. If you meet this criteria, your account will be added to the voters list on association.drupal.org and you will have access to the voting.
To vote, you will rank candidates in order of your preference (1st, 2nd, 3rd, etc.). You do not need to enter a vote on every candidate. The results will be calculated using an "instant runoff" method. For an accessible explanation of how instant runoff vote tabulation works, see videos linked in this discussion.Elections process
Voting will be held from 1 August, 2019. During this period, you can review and comment on candidate profiles on assoc.drupal.org.
Finally, the Drupal Association Board will ratify the election and announce the winner on 3 September, 2019.
Have questions? Please contact Drupal Association Community Liaison, Rachel Lawson.
Finally, many thanks to nedjo for pioneering this process and documenting it so well!
This is actually quite a common question from our students. They start building their Drupal site. Then they go to work with their blocks or menus.
Then they accidentally disable the "Log in" menu link. There is no "Log in" link displayed on the site anymore. Neither for them nor for their visitors.
In this short tip, you will learn how to login to your Drupal admin page in such situation.
To Perform an HTTP request in Drupal 7 we can use "drupal_http_request" function. This is a flexible and powerful HTTP client implementation. Correctly handles GET, POST, PUT or any other HTTP requests. Handles redirects.heykarthikwithu Thursday, 13 June 2019 - 10:32:53 IST
Today marked the kick-off of Drupal North 2019, and Evolving Web is excited to be a part of it for the 4th year in a row. Day 1 was packed with trainings, summits (for the 1st time!), and networking opportunities. Here were the key takeaways we saw:Drupal is for everyone
In the "What is Drupal?" and "Qu'est-ce que c'est Drupal?" trainings by Evolving Web's own Trevor Kjorlien and Adrian Cid Almaguer, everyone from developers, to project managers, to graphic designers and more, took part in a hands-on demonstration on how to build a site with Drupal.Nobody wants a website
A website is just a tool for you to achieve your larger goals. Whether that be building a community, selling a product, getting donations, providing information, or anything else, your website has to be designed with your goals in mind. That being said:Focus on what your audience wants, not what you want
Your website should always be making your audience's life easier and give them what they are looking for as quickly as possible. It's important to step out of your own shoes and into theirs in order to have a good understanding of want they want so you can cater to those needs.Students really love chocolate
While sharing her experiences in getting students to participate in UX/UI studies, Joyce Peralta from McGill University explained that sometimes it's the small incentives that can be the most effective. Through many attempts, she found that students could be easily swayed by a simple table full of chocolate bars situated in a prime location in the library. Simple but effective!
Drupal North started off on a great foot and we're looking forward to the next two days of sessions. If you're attending, make sure to check out presentations from our team:
- Drupal UI Patterns (Thursday at 11:15am)
- Decoupling Drupal with React Native (Thursday at 2:45pm)
- Fast UX Feedback for your Drupal Project (Thursday at 3:45pm)
- Drupal Project Estimation, for Fun and Profit (Friday at 2:45pm)Otherwise you can follow along with us on LinkedIn and Twitter, and check back later for more updates on Day 2 and 3 of Drupal North.
Netflix has been popping up more and more around video games lately, and its latest announcement sees the video streaming platform partnering with developer Next Games for a Pokemon Go-like mobile game. ...
Rec Room developer Against Gravity has secured $24 million in funding across two rounds. ...
Xbox head Phil Spencer says that the company views xCloud as a long-term solution, but one that isn't out to render in-home console and PC setups obsolete. ...
This module provides Google reCAPTCHA v2 protection for Drupal forms. In comparison to other modules the main goal is to keep configuration as simple as possible, and simple to support following setups/scenarios:
The feature allowed Oculus Quest users to stream SteamVR games to the standalone headset but is, according to developer Guy Godin, being removed from the app following an order from Oculus. ...
In my post, Drupal is frustrating, I stated that enterprise websites need, want, and are willing to pay for better support options when using Open Source software. Organizations have reached out to me as a Webform module subject matter expert (SME) seeking to start a 1-to-1 support relationship. Occasionally, these relationships result in a sponsored feature request. Sometimes organizations want to ask me a simple question or at least know that I am available to answer questions. In the past, I shied away from the idea of setting up regular office hours because it would be an unpaid commitment of my time during business hours. Fortunately, with the existing funds collected by the Webform module's Open Collective, I feel that now is a good time to experiment and set up some initial office hours for the Webform module.About office hours
The goal of office hours is to make it easier for me to help people and organizations with questions and issues related to the Webform module for Drupal 8 as well as to assist current and future Webform module contributors.
Sponsor office hours
Sponsor office hours are intended to help backers of the Webform module's Open Collective with any Webform related questions or challenges. These office hours will be strictly for monthly sponsors and backers of the Webform module's Open Collective.
Add-ons office hours
Add-ons office hours are for anyone in the Drupal community building Webform add-ons and extensions that are being contributed back to the open source community. The goal of these hours is to help support and improve the quality of the projects and community around the Webform module.
Office hour guidelines
I've been...Read More
Content modeling as a practical foundation for future scalability in Drupal.Content modeling as a practical foundation for future scalability On
Palantir recently partnered with a patient engagement solutions company that specializes in delivering patient and physician education to deliver improved health outcomes and an enhanced patient experience. They have an extensive library of patient education content that they use to build education playlists which are delivered to more than 51,000 physician offices, 1,000 hospitals, and 140,000 healthcare providers - and they are still growing.
The company is in the process of completely overhauling their technical stack so that they can rapidly scale up the number of products they use to deliver their patient education library. Currently, every piece of content needs to be entered separately for each product it can be delivered on, which forces the content teams to work in silos. In addition, because they use a dozen different taxonomies and doing so correctly requires a high level of context and nuance, any tagging of content can only be done at the manager level or above. The company partnered with Palantir.net to remove these bottlenecks and plan for future scalability.Key Outcome
Palantir teamed up with this patient engagement solutions company to develop a master content model that:
- Captures key content types and their relationships
- Creates a standardized structure for content, including fields that enable serving content variations based on end-point devices and localization
- Incorporates a taxonomy that enables content admins to quickly filter and select content relevant to their needs and device
The company’s content library is only getting larger over time, so the core need driving the master content model is to enable scalable growth. Specifically, that means a future state where:
- New products can be added and old products deprecated without restructuring content.
- Content filtering can scale up for new product capabilities, languages, and specialties without having to be fundamentally reworked.
- Clients using the taxonomy find it intuitive and require minimal specific training to create and amend their own patient education playlists.
These principles guided our recommendations for the content model and taxonomy.Content Model
Our client’s content model is currently organized by the end product that content is delivered through - for example, a waiting room screen vs. an interactive exam room touchscreen. This approach requires the digital team to enter the same piece of content multiple times.
To streamline this process for the team, we recommended a master content model that is organized by the purpose of the content, including the mindset of the audience and the high-level strategy for delivering value with that content.
For example, a “highlight” is a small piece of content intended to engage the audience and draw them into deeper exploration, while a “quiz” is a test of knowledge of a particular topic as training or entertainment.
This approach allows the company to separate the content types from products, which in turn makes them easier to scale. For example, this wireframe shows how a single piece of quiz content can be delivered on a range of endpoint devices depending on which fields that device uses. This approach allows us to show how a quiz might be delivered on a voice device, which is a product the company does not yet support, but could in the future.
“Our content is tailored to different audiences with different endpoints. Palantir took the initiative to not only learn about all of our content paths, but to also learn how our content managers interact with it on a daily basis. We’ve relied heavily on their expertise, especially for taxonomy, and they delivered.”
Executive Vice President, Content & CreativeTaxonomy
The company’s taxonomy has 12 separate vocabularies, and using them to construct meaningful content playlists requires a deep understanding of both the content and the audience. Existing content has been tagged based on both the information it contains and based on the patients to whom it would be relevant.
For example, a significant proportion of cardiology patients are affected by diabetes, so a piece of content titled "Healthy Eating with Diabetes" would be tagged with both "Diabetes" and "Cardiology". Additionally, many tags have subtle differences in how they are used — when do you use "cardiology" vs. "cardiovascular conditions"? "OB/GYN" vs. "Women's Health"?
This system requires that everyone managing the content — from content creators to healthcare providers and staff selecting content to appear in their medical practice — understand the full set of terms and the nuance of how they are applied in order to tag content consistently.
Our goal was to develop a taxonomy that can be used to filter content effectively without requiring deep platform-specific context and nuance.
Our guiding principles were to:
- Tag based on the information in the content.
- Use terms that are meaningful to a general audience.
- Use combinations of tags to provide granularity.
- Avoid duplicate information that is available as properties of the content
We ultimately recommended a set of eight vocabularies. Two of them are based on company-specific business processes, and the remaining six are standards-based so that any practitioner can use them. By using combinations of terms, users can create playlists that are balanced in terms of educational and editorial content.
For example, in our recommended taxonomy, relevant content is tagged as referencing diabetes, so that the person building the playlist can still construct effective content playlists, without needing to carry in their head the nuance that many cardiology patients are also diabetic.Moving Forward With Next Steps
This content modeling engagement spanned 9 weeks, and the Palantir team delivered:
- A high-level content model identifying the core content types and their relationships
- A set of global content fields that all content types in the model should have
- A field level content model for the four most important content types
- A new taxonomy approach based on internal user testing
- A Drupal Demo code base showing how the content types and taxonomy can be built in Drupal 8
In the future, the company’s ultimate goal for the platform is to scale their engagement offerings with new content and new technology. With our purpose-driven content model and refined taxonomy, the company can scale their business by breaking down internal content silos and making tagging and filtering content consistent and predictable for their internal team and eventually, their customers. Palantir’s master content modeling work forms a practical foundation for the company’s radical re-platforming work.
Enabling this module will render the Edit link from Local Tasks in the top level of the Toolbar, also displaying the current node id.