All RPGs and Storygames by Tod Foley are now available at DrivethruRPG and RPGnow. Bring these games to your table!
Appnovation Technologies: Website Accessibility Series, Part 2: Accessibility, Audits and Alterations
We recently Open Sourced our temporary environment builder, M8s. In this blog post we will be demoing everything you need to get started!by Nick Schuch / 21 November 2017 Introduction
In this video we will introduce you to M8s and the problem which it is solving.Provisioning a M8s cluster
Now that you are acquainted with the M8s project, it's time to get a cluster provisioned!
In this video we will setup a Google Kubernetes Engine cluster and deploy the M8s API components.Setting up CircleCI
Now that our M8s cluster is up and running, it's time to setup our pipeline to run a build.
In this video we will be configuring CircleCI to run the M8s CLI.Pushing a topic branch
It's time to put it all together!
In this video we will be pushing a topic branch to demonstrate how M8s interacts with a Pipeline.Finale
You made it to the finale! In this video we will be checking out the build environment and how a developer can access the Mailhog and Solr containers.Conclusion
To learn more about the M8s project you can go and checkout:
We welcome any and all feedback via Twitter and our Github Project issues page.Tagged m8s, Kubernetes, Drupal Development
Sys Ops Lead
Dated 21 November 2017Add new comment
This month, our membership campaign celebrates the ways we, together, build community on the home of the Drupal project. Hear from the Drupal Association team how and why Drupal.org offers you tools to make more connections, to increase your potential for a fulfilling professional career, and to enable your contributor journey in Drupal.
You can do a lot on Drupal.org and its sub sites. Check out the campaign page. We hope you are inspired to learn more about what Drupal.org offers and if you aren't yet a Drupal Association member, join today!Want to help our campaign?
We need your help so we meet our two goals: sign up 50 new members and raise $1500. We've made a page of resources for you to share.
Thank you for building community with us!
Notes from the November 20 meeting:
@drpal's update on the past week's work
- Ongoing work on the React dblog prototype: https://github.com/mattgrill/drupal-react-dblog & https://www.drupal.org/project/react_admin
- Core JS cleanup: https://www.drupal.org/project/drupal/issues/2915784 and https://www.drupal.org/project/drupal/issues/2917234 need review and are blocking subsequent work. Split https://www.drupal.org/project/drupal/issues/2925064 into issues with smaller scope.
- Shared questions to explore with the framework experiment:
Using https://github.com/mozilla-services/react-jsonschema-form as a way to generate React forms without requiring developers to learn React. Possible replacement for Form API. Is this something that seems viable / a good idea?
- The way they use JSON schema is valuable; not necessarily the implementation.
Related core issue: https://www.drupal.org/node/2913372
- Explore separate react-ui and react-json-schema. tim.plunkett has code locally for the schema piece and will post a patch.
- The way they use JSON schema is valuable; not necessarily the implementation.
- Initiative communication
- What's the next UI after dblog?
- https://www.drupal.org/project/drupal/issues/2830584 could be a candidate for exploration once the dblog is done
- Don't take on a new UI yet since there's more work we can do with the dblog (forms, components)
- On rewriting modals: Can you partially opt in to a new UI? https://reactjs.org/docs/portals.html might help
- What are the next steps around the React DBLog prototype + component ui library, json schema forms?
- Take Tim’s work and try to generate form components from Drupal data
- Do we want to actually add a new dblog to core or is it solely for an experiment?
This past weekend, I was honored to be able to present a session at 2017's New England Drupal Camp (NEDCamp) about Drupal 8's Migrate API. Redfin has implemented many Drupal 8 migrations to date both from CSV data sources and legacy Drupal sites (Drupal 6 and 7). As a result, we want to share with you what we've learned in hopes of saving you the time often spent in the trials and errors of data migration.Chris November 20, 2017
DrupalCamp Atlanta was such a great experience -- I can't decide if it was a great end to a good year or the beginning of even a better year. My last blog post was about organizing and presenting the Webform training materials, which was in preparation for my three-hour Webform training at DrupalCamp Atlanta. Suffice it to say, it was an enlightening experience. Not to mention I learned a few things...
First off, I am in awe of all the people in the Drupal community that are 'professional trainers'. The ability to understand and explain something as complex as Drupal is no easy task. The 14 attendees at my Webform training had various skill levels. Because my leg did not nervously shake at all during my three hours at the podium, I can finally say my comfort level with public speaking is increasing. I also came away with some invaluable, practical information. Prior to attending DrupalCampAtlanta, I had completely underestimated how hard it is to coordinate people to do hands-on exercises, like installing and building a webform. After the first hour of the training, I took a break and decided that the hands-on exercises were going to be impossible to accomplish in the remaining two hours, and that the training should instead focus on walking through all the material while answering any questions. I haven’t given up hope on being able to do hands-on exercises, however, I do need to rethink my approach. Fortunately, I was able to attend other sessions, watch some 'profession trainers' in action, and learn a few things.
The Drupal Association is excited to expand its team with two new staff members who are filing the roles Conference Director and Community Liaison. Please join me in welcoming Brooke Candelaria and Rachel Lawson. Both are going to add great value to the Drupal Association team as well as to the Drupal community.Conference Director
We are excited for Brooke Candelaria, our new Conference Director, to join the team. She will infuse DrupalCon with ideas that draw on her extensive technology event experience in open source - Python specifically. In addition to taking over DrupalCon North America planning, Brooke will be a great partner in finding the best way to deliver DrupalCon globally. In addition to Brooke’s expertise, she brings enthusiastic energy to everything she does whether that is planning events or volunteering for the Houston Livestock Show and Rodeo. Brooke resides in Houston, Texas, USA.Community Liaison
The team is equally excited that Rachel Lawson has agreed to join the team as our new Community Liaison where she will engage with the Drupal community to build a better relationship and understanding between the Drupal Association and the community. Rachel is well suited for this position given her background as a Drupal developer as well as her communications experience in the pharmaceutical industry. Even more impressive is that Rachel has been in the Drupal community for over 11 years and played many important roles such as Community Working Group member, Sprint Lead and mentor, DrupalCon and camp presenter, and more. Rachel has demonstrated time and again that she is a great communicator and has a natural talent to rally people behind a common goal. While you will see Rachel mostly online, she will still be touring Drupal events on her motorbike. Rachel resides in Norfolk, UK.
This module allows you to attach a select list field populated with your site roles to an entity. Once attached, a user must have the required role in order to view that entity.
To see the drush commands help you need to use drush help COMMAND_NAME from the command line, but if you want to see this information in Drupal you'll can't do it.
This module improves the module help page showing information about the module drush commands.
The drush command help section only will be added if the module for which you are viewing the help have drush commands defined.Issues
As with all contributed modules, when considering submitting an issue:
Provides a DIBS payment gateway integration.
This is a very simple module which allows you to send your clients to make an off-site payment directly on the DIBS payment system.
Why this module when https://www.drupal.org/project/dibs already exists? The DIBS Payment Gateway API module is an API and is not integrated with Commerce 2.x.
Commerce DIBS integration is an out of the box module.
Decoupled Router provides an endpoint that will help you resolve path aliases and redirects for entity related routes. This is specially useful for decoupled applications where the editor wants full control over the paths available in the consumer application (for instance a React app).
It’s always hard to be a newcomer. Let’s help Drupal beginners to take a step forward this CMS, and show them what changes Drupal brought into our lives. In this blog post, we will tell you about the #DrupalChanges initiative, and how you can help to enhance the Drupal adoption.
Files size module provides the counts of the file size and show the icon of the file type.
File size module is depends on the views module. User needs to call show the files by using view and needs
to select "URL to File".
There are the configuration option to allow files icon and Mime Type with extension. Please go to the below
url after login to the admin.
admin/config/development/files_size (Configuration >> Development >> File icon and File size settings).
In my recent talk at DrupalSouth Auckland 2017 I took a hard look at the hyperbole of Drupal supposedly powering over a million websites. Where does Drupal really sit in relation to other CMS platforms, both open source and proprietary? What trends are emerging that will impact Drupal's market share? The talk looked outside the Drupal bubble and took a high level view of its market potential and approaches independent firms can take to capitalise on Drupal's strengths and buffer against its potential weaknesses.by Owen Lansbury / 20 November 2017 But, Drupal powers over a million websites!
One of the key statistics that Drupalers hold onto is that it's powered over a million websites since mid 2014 when Drupal 7 was in ascendance. However, since Drupal 8 was released in late 2015, Drupal's overall use has stalled at around 1.2m websites, as seen circled in red on the Drupal Core usage statistics graph below.
The main reason for this stall in growth was that Drupal 8 was a major architectural re-write that wasn't essential or even affordable for many Drupal 7 sites to migrate to. For clients considering major new projects, many held off on committing to Drupal 8 until there were more successful case studies in the wild and didn't commission new Drupal 7 sites given that version was nearing a decade old. Anecdotally, 2016 was a tough year for many Drupal firms as they grappled with this pause in adoption.
Of course, Drupal 8 is now a well-proven platform and is experiencing steady uptake as circled in green on the usage graph above. This uptake corresponds with a down tick in Drupal 7 usage, but also indicates a softening of total Drupal usage. If we extrapolate these trend lines in a linear fashion, then we can see that Drupal 8 might surpass Drupal 7 usage around 2023.
Of course, technology adoption doesn't move in a straight line! Disruptive technologies emerge that rapidly change the playing field in a way that often can't be envisaged. The example that springs to mind is Nokia's market share was still growing when the iPhone 4 was released in 2010. By the time the iPhone 4s was released in 2011, Nokia's sales volumes had almost halved, leading to Microsoft's catastrophic purchase of the handset division in 2013 and subsequent re-sale for 5% of the purchase value in 2016. Oops!
Despite this downward trend in overall Drupal usage, we can take comfort that its use on larger scale sites is growing, powering 5.7% of the Top 10,000 websites according to Builtwith.com. However, its market share of the Top 100,000 (4.3%) and Top Million (3%) websites is waning, indicating that other CMS are gaining ground with smaller sites. It's also worth noting that Builtwith only counts ~680,000 Drupal websites, indicating that the other ~500,000 Drupal.org is detecting are likely to be development and staging sites.
So, where are these other sites moving to when they're choosing a new CMS?
Looking at the stats from W3Techs, it's clear to see that Wordpress accounts for almost all of the CMS growth, now sitting at around 30% of total market share.
Wordpress has been able to achieve this dominance by being a fantastic CMS for novice developers and smaller web agencies to build clients' websites with. This is reinforced by Wordpress having an exceptional editor experience and a hugely popular SAAS platform at Wordpress.com.Drupal's place in the CMS market
The challenge Wordpress poses to other open-source CMS platforms, like Joomla, Typo3 and Plone, all with under 1% market share and falling, is their development communities are likely to look direct their efforts to other platforms. Drupal is able to hedge against this threat by having a large and highly engaged community around Drupal 8, but it's now abundantly clear that Drupal can't compete as a platform for building smaller brochure-ware style sites that Wordpress and SAAS CMS like Squarespace are dominating. We're also seeing SAAS platforms like Nationbuilder eat significantly into Drupal's previously strong share of the non-profit sector.
We often talk of Drupal as a CMS Framework, where it competes against frameworks like Ruby on Rails, .NET and Django to build rich web based applications. Drupal 8 is still well placed to serve this sector if the web applications are also relying on large scale content and user management features.
Which brings us to the Enterprise CMS sector, where Drupal competes head to head with proprietary platforms like Adobe Experience Manager, Sitecore and legacy products from Opentext, IBM and Oracle. The good news is that Drupal holds its own in this sector and has gained very strong market share with Government, Higher Education, Media and "Challenger" Enterprise clients.
This "Comfort zone" for Drupal usage is characterised by clients building large scale platforms with huge volumes of content and users, high scalability and integration with myriad third party products. Operationally, these clients often have well established internal web teams and varying degrees of self reliance. They're often using Agile delivery methods and place high value on speed to market and the cost savings associated with open-source software.
Where Drupal is gaining a competitive edge since the release of Drupal 8 is against the large proprietary platforms like Adobe Experience Manager and Sitecore. These companies market a platform of complementary products in a unified stack to their clients through long standing partnerships with major global digital agencies and system integrators. It's no surprise then that Acquia markets their own platform in a similar way to this sector where Drupal serves as the CMS component, complemented by subscription-based tools for content personalisation, customer segmentation and cloud based managed hosting. Acquia have actively courted global digital media agencies with this offering through global partnerships to give Drupal a toe hold in this sector.
This has meant Acquia has made significant headway into larger Enterprise clients through efforts like being recognised as a "Leader" in the Gartner Magic Quadrant for CMS, lending Drupal itself some profile and legitimacy as a result. This has driven Enterprise CIOs, CTOs and CMOs to push their vendors to offer Drupal services, who have looked to smaller Drupal firms to provide expertise where required. This is beneficial to independent Drupal services firms in the short term, but the large digital agencies will quickly internalise these skills if they see a long term market for Drupal with their global clients.
As one of those independent Drupal firms, PreviousNext have staked a bet that not all Enterprise customers will want to move to a monolithic platform where all components are provided by a single vendor's products. We're seeing sophisticated customers wanting to use Drupal 8 as the unifying hub for a range of best-of-breed SAAS platforms and cloud services.
This approach means that Enterprise customers can take advantage of the latest, greatest SAAS platforms whilst retaining control and consistency of their core CMS. It also allows for a high degree of flexibility to rapidly adapt to market changes.What does this all mean for Drupal 8?
The outcome of our research and analysis has led to a few key conclusions about what the future looks like for Drupal 8:
- Drupal's overall market share will steadily fall as smaller sites move to SAAS CMS and self-managed Wordpress installs.
- The "comfort zone" of Government, Media, Higher Education and "Challenger" Enterprise clients will grow as many of these clients upgrade or switch to Drupal 8 from Drupal 7 or proprietary platforms.
- Drupal will gain traction in the larger Enterprise as the global digital agencies and system integrators adopt Drupal 8 as a direct alternative to proprietary CMS products.
- Independent Drupal services firms have a good opportunity to capitalise on these trends through partnerships with larger global agencies and specialisation in technologies that complement Drupal 8 as a CMS.
- A culture of code contribution needs to grow within the larger clients and agencies moving to Drupal to ensure the burden of maintaining Drupal's development isn't shouldered by smaller independent firms and individual developers.
Despite the fact that we've probably already passed "Peak Drupal", we're firm believers that Drupal 8 is the right tool for large scale clients and that community has the cohesion to adapt to these existential challenges!Tagged DrupalSouth
Dated 20 November 2017Add new comment
This Module can be used for viewing Model (Autocad, Revit) files using Forge Viewer with in our contentRoad Map
- OAuth 3 Leg
- BIM 360 file browser, with in content edit
- Content display with Forge Viewer
Placeholder for a module to connect Drupal to Smart Contracts in the Ethereum blockchain.