Visiting https://godotengine.org/asset-library/asset/248 the link repo is https://github.com/willnationsdev/godot-plugin-refresher which is behind …
Like every month, we’ve compiled some of the top Drupal blog posts written the previous month. Take a look at our list for October.READ MORE
ComputerMinds.co.uk: Core web vitals - how to debug and improve cumulative layout shift (CLS) issues
TLDR : Check your cookie popup!
It seems everyone is talking about core web vitals at the moment, spurred on by Googles’ recent announcement that page experience (which includes core web vitals) will start influencing search ranking in May 2021.
We won’t go into detail on web vitals in this post - there is plenty of information already on the web, including from Google themselves on the excellent web.dev site.
Instead, this post will look specifically at cumulative layout shift - or CLS as it’s known. I like to think of this as the jerkiness measure of your site - the higher the number the worse the jerkiness.
Getting your CLS score is pretty easy - you can use pagespeed or lighthouse (built right into chrome). I will assume (because you are reading this post) that you have done this already AND you are not happy with your score. So - what next - how do you go about diagnosing and fixing the issue?
The reading online makes lots of great suggestions, mostly around helping the browser reserve space for elements that are late loaded (images, video etc). This is all good stuff - however - it didn’t help me and the sites I was working on.
So first off I switched to incognito mode (I wanted to simulate a fresh first-time visit to the site - for various reasons) in chrome, loaded the site and then fired up the performance tab in the chrome dev tools. This is a scary looking tab - there is a lot going on here - and you can safely ignore 98% of it (at least for now). You just need to make sure the ‘Screenshots’ tick box is ticked - then hit the little refresh icon - this will refresh the page and start profiling the page load. It’s worth pointing out that this is running locally so you can use it on your local dev sites.
This takes a few seconds and when complete you should have a lovely looking film strip of screenshots along the top - mouseover and you get a larger version. Start at the left and move rightwards - and keep your eyes open for any obvious content shifts.
I did this for 3 individual and unrelated client sites - and found the cookie popup to be the culprit in 2 of the sites - it was appearing mid-way through the load and pushing ALL the content down - fixing this took around .4 off the CLS score (which is a lot). The other site had the ENTIRE expanded mobile menu briefly rendering at the top of the page - which then disappeared (as it should) and shifted all the page content up by about 800px! Fixing this took about .5 off the CLS score.
So - the takeaway from this is probably before you spend ages fiddling with width and height attributes on your img tags, have a quick look to make sure there isn’t some low hanging fruit massively impacting your CLS.
Tugboat.qa offers automated and on-demand deployment previews to accelerate development. In 2019, Tugboat was successfully integrated as the backbone of the community testbed Simplytest.me. Following that success, a community-lead initiative emerged to provide these previews for all of Drupal Core development, by integrating into the Drupal.org issue queue. Drupal Association CTO Tim Lehnen (hestenet on Drupal.org) opened an issue to explore this option in early August.Why automated environments for Core issues?
Reviewing and testing Drupal.org issues has historically been the purview of experienced Drupal developers. Designers, end-users, and other stakeholders have been relegated to the role of watching over the shoulder of developers who drive demos from local development environments. This has been detrimental to fully involving those stakeholders in a development process that could improve Drupal for all users. With Drupal's ease-of-use, accessibility, and front-end features being central to the current strategic initiatives, it was time to ensure that these stakeholders are fully empowered.
Automated deploy environments help bridge the technical divide and bring the ability to review changes to more users. Longtime Drupal contributor YesCT says:
The Tugboat integration with drupal.org issues makes reviewing and testing possible for people who have never been able to do it before. This project uses technology to lower the barriers of contributing to Drupal, and makes contributing more accessible to more people. It’s going to be a huge game-changer.
In practice, visitors to the Drupal.org issue queue can click a link to tour a live, working version of a Drupal website wherever Tugboat deploy previews are enabled. As of November 10, 2020, this includes all Drupal Core issues.
Upcoming UI revision:Drupal.org deploy previews - under the hood
The Drupal.org/Tugboat integration relied on a handful of contributors across a project that spanned months, but the core of this collaboration was a partnership between core contributor Juampy NR and Drupal.org architect Neil Drumm.
As a senior developer at Lullabot, Juampy's continuous integration expertise, as well as his familiarity with Tugboat, made him an invaluable contributor to implementing the Tugboat side of the integration. Neil's expertise as architect, meanwhile, gave Juampy and Tugboat the guidance to find the right places in Drupal.org's custom logic to add code for this new integration. Simultaneous to the Tugboat integration, Juampy and Neil also worked to implement the Drupal Association GitLab integration, bringing issue forks and merge requests to the issue queue.
Some of the challenges that this team faced included:
Drupal.org’s large database. Because of the size of the database, the team had to work remotely using a provisioned development environment. Remote debugging helped to catch and traverse the different events involved in the workflow.
Understanding where to write code. Drupal.org has a ton of custom logic, so finding the right place to add new code was not easy. The Drupal Association's guidance was key.
Integrating multiple systems. The team had to write interactions between Drupal.org, Tugboat, and GitLab, taking into account error responses, timeouts, and firewall restrictions.
Before this integration, contributors had to take and upload screenshots of their changes, and reviewers had to replicate changes locally in order to see them in action. Tugboat reduces friction by making changes visible - and more accessible - to anyone who clicks the preview URL. This shortens review time considerably and invites participation from non-developers, working toward Drupal's value of respecting and valuing inclusivity.
Check out our documentation on Drupal.org to learn more!
Tag1 Consulting: Drupal 7 extended support: An overview of the Drupal 7 Extended Support Program - Tag1 TeamTalk #028.2
Tag1 Quo, Tag1's extended support service for Drupal, offers you peace of mind when it comes to receiving all of the important security updates that Drupal 7 Extended Support (D7ES) vendors maintain. But Tag1 Quo goes well beyond the minimum requirements of the D7ES program, because we cover all of your contributed modules and notify you right away of security patches that need your attention.Read more preston Wed, 11/11/2020 - 08:30
Drupal development is not everyone’s cup of tea, however, it could be, provided that the person at the development end has the right skill set to handle all of Drupal’s potential. With Decoupled Drupal the need for these skills becomes even more prominent, you have to have excellent front-end and back-end developers separately since the two are independent of each other. And this is where the hiring process of the right set of professionals for your Decoupled Drupal projects becomes tricky and cumbersome.There are a lot of aspects to take under consideration and a lot of different skills to look for.
To make your job a tad bit easy, here is the checklist of the skill sets and the professionals that you need to successfully deliver the Decoupled Drupal projects..What skills are needed for Drupal development during the decoupling process?
When you decouple Drupal, you are only going to be using it as a content repository, meaning it would only serve a purpose for backend development needs. Even if you use it for back-end, you are still going to be using it, so you would need good Drupal developers. So, here are the skills you need to be looking out for.
Proficiency in Site Building
You must know how important it is to attend primary school, the things we learn set the pace for our entire educational journey. So, what primary school is to us, Site Building is to Drupal. It is the most basic need of a Drupal website.
The primary purpose of a site builder is to reap all the benefits of Drupal by making it run and configuring all the options required to make a website fully functional. There isn’t a need for a custom code for this to happen, rather the Admin User Interface is equipped to handle it on its own. There are several other responsibilities of site builders as well, so, when hiring a site builder, you must keep in mind all of these.
- Installing Drupal manually and also doing the same with an application or a service;
- Downloading and installing modules along with disabling, uninstalling and removing them;
- Understanding of all core and contributed modules;
- Thorough knowledge of fields and entities with expertise in content and non-content fields;
- Finally, being familiar with blocks, menus and navigation as well as the basic Views skills;
All of these are the everyday requirements for site builders, and a proficient one excels at all of them.Proficiency in Backend Development
The decoupled Drupal requires backend developers to be at their best at all times. This is because an impeccable front-end would seem sub-standard, if the content repository is not up to the par. There when hiring backend developers, you have to be extra picky and choose one who fits the criteria to the T. And here is what the criteria looks like;
- Unlike site builders, Backend developers are involved in writing the code in PHP and other languages, so they must have experience in PHP and MySQL at least.
- They must be competent in creating and executing modules. The added knowledge of building custom modules in Drupal 7, 8 and 9 (for Drupal 7 and Drupal 8 have not reached End-of-life as yet) is always preferable.
- They also need to have advanced knowledge of themes, consuming web services and automated deployments to name a few.
- The backend developer has to be aware of all the security concerns as well, along with the ways of overcoming them.
Theming is a part of Drupal’s front-end development. I know you must be wondering why decoupled Drupal would need front-end developers with experience in Drupal. To answer your question, I have three words; Progressively Decoupled Drupal.
Because the entire front-end is not separated from Drupal, it is important to have a good themer to build around Drupal’s front-end capabilities. Themers are responsible for the front-end design as well as the development and implementation of the client-side architecture.
For this purpose,
- they need to be experts in front-end technologies;
- they need to be experts in installing themes and generating sub-themes using PHP or Twig in Drupal;
- they need to be experts in designs and modifying them into a completely functional issue;
- they need to be experts in creating such modules that would expose the configuration to the site builders.
When you find someone like this, you would have the perfect themer for your progressively decoupled Drupal.
Read these infinity stones of Drupal development to adhere to the best practices when it comes to everything ranging from site-building to backend development.Proficiency in Drupal Architecture
Drupal work is often regarded as web projects, and each project has to have someone who is aware of the ins and outs of the work. And in the case of Drupal that person is a Drupal Architect.
A Drupal architect is essentially the manager of the project, who possesses knowledge of all the key areas of the project. From backend development and site building to front end development and theming, he needs to be proficient in every task as a leader.
He should have an in-depth understanding of the ways to optimise Drupal because that is what the main role of a Drupal architect is. For the same, a certain level of expertise in PHP, MySQL, JQuery and CSS along with the knowledge of implementation tools like Varnish, GeoIP and UberCart comes in quite handy.
Note: Some proficiency in front-end technologies is always beneficial for Drupal developers. This may seem odd to you, since we are talking about the Drupal skills in decoupling. However, it isn’t much of an oddity and let me tell you why. We know that when decoupling is done, the presentation layer is entirely separated from the content aspect of a website, yet they still have to work together and they have to be in sync. This would become all the more convenient for decoupled Drupal developers, if they have some knowledge of the current front-end technologies. HTML, CSS, React and Gatsby are some of the most used technologies, so an understanding or maybe even some experience in using it would come in very handy for the streamlined development of a decoupled Drupal website.
Read these infinity stones of Drupal development to adhere to the best practices when it comes to everything ranging from site-building to backend development.What is the requirement for Drupal web services?
The decoupled Drupal needs a good API layer for it to give you all the benefits it boasts. And a good API is only good when it is being handled by competent hands and these hands are your developers’.
There are three particular web services that are being implemented during decoupling. Although all three will be achieving the same goal, the way they do it is quite different. Therefore, your developers need to be aware of even the minutest details of these web services, especially with respect to the different Drupal versions.
Starting with GraphQL, firstly, it is not available in Drupal 7; an expert developer would know this. The GraphQL module in Drupal 8 and 9 will let your developers create their own custom schema or extend an existing one, as long as they are good with coding.
JSON:API is also not available in Drupal 7 and even in Drupal 8, it was a late addition, having been added as a stable core feature in Drupal 8.7. With the JSON:API module, a developer can decide which HTTP methods he should be using along with which response codes should be returned and when, eventually increasing productivity. A JSON:API expert would do it with ease.
Coming to REST API, it has been a part of Drupal core for a long time. Your developers need to be equipped to configure REST resources, customise their formats, customise their authentication mechanism as well as create the plugins.
A developer who speaks fluently in Drupal web services is the developer with the right skill set for Decoupled Drupal, since the API is the thread that holds both the front and backend together.How do you capitalise the separated front end?
Now that Drupal specific skills are out of the way, let us move on to the presentation layer and the technologies the front-end developers need to be experienced with.HTML and CSS
React, Vue and Angular tend to be the most sought after technologies for transitioning into decoupled Drupal., with Vue.js being the latest addition in the mix. Frontend developers need to be aware of these and get the most of them with their knowledge.Static Site Generators
If you have a static site with already available input files, you would want to delve into Static Site Generators for your frontend development. For this reason, you would need experts in SSG to fully capitalise its various tools. Gatsby, Metalsmith and Tome are the ones that are the most renowned at present.
Note: There is one more thing that you should be looking for in your front-end developer and that is the knowledge of Drupal. Like I mentioned in the previous section, the Drupal developers need to have some knowledge of the front-end technologies, similarly, the front-end developers need to have knowledge of the Drupal. Both the back-end and front-end may be different and their development may also be different, but they are going to be a part of one web project, so both teams need to have some cognisance of the other’s working. Decoupling would make a lot more sense then.What other skills should you be looking for?
Up until now, we have discussed all the skills specific to the development of decoupled Drupal, you might think that your work is done, but it isn’t. There are certain skills that need to be held by developers, whether they are involved in decoupled Drupal or monolithic Drupal and they are going to be equally important for your decoupled Drupal project.Adept at Designing
The process of website building starts with designing. The very first step towards development is the making of wireframe, which is basically a design template. This wireframe sets the pace and the direction of the web project, so your designer has to know what he is doing because if he doesn’t, the end would not be as enlightening as you might want.
Designing mandates tools, without them a designer would be helpless. Sketch, Figma, InvisionApp and Adobe XD are some of the go-to options for User Interface designing. The apprehension of these would make a designer adept at his job.Adept at DevOps
In essence, DevOps is an IT service delivery channel that focuses on the adoption of practises that would collaborate your operations with the development team. For this to happen, you need a DevOps Engineer or a System Admin, who would be responsible for deploying websites to the live server.
- Expertise in Linux;
- Expertise in bash scripting and continuous integration;
- Expertise in automations technologies;
- And expertise in IAC (Infrastructure as Code) are essentials for this particular hiring objective.
QA refers to quality assurance. It is a position held by developers to check the quality of work being churned out. They act as the targeted client and see whether what they are getting from the website is up to the standards or not.
Someone with limited knowledge of Drupal, web technologies and the industry requirements would not be a good fit. You would only be able to check something, if you know what to look for, right?Adept at Project management
Like the suggests, this is a skill that oversees the project from the very beginning to the very end. From time deadlines to the day-to-day progress of the project, each and every aspect has to be monitored.
Drupal Project Management requires the manager to be skilled at a variety of things, namely;
- Expertise in team management and segregation of workload;
- Expertise in dealing with the clientele to understand their requirements and acting as the middle ground between them and the team;
- Expertise in analysing and rectifying plausible risks during the project;
- Expertise in the Drupal and all the technologies that accompany Drupal projects;
- And expertise in using reporting tools and implementing sound SEO strategies.
Every Drupal site has a business side, so when hiring the right skill set for decoupling, business analysis holds a key to success. Through business analysis, the business and IT sides of the website find a connection and work together. This is done through the use of data analytics, which help in examining the undergoing processes, analysing its needs and effectively communicating the same to the executives and stakeholders along with running logic/system interference with them.
While using Drupal, it is always preferable to have an analyst that has a development background with knowledge of Drupal. Extroverts are usually ideal for this position, since communication is vital here.The Sum Total
Drupal is a pretty diverse system and an even higher level of diversity is found when Drupal is decoupled. Since you would be trying to capitalise Drupal in addition to capitalising other frontend technologies, you would have to put in an extra effort in the hiring process. Decoupled Drupal developers need to be equipped to handle the diversity it is going to inundate them with. The right skill set would help you and them to reap the benefits of decoupling.blog banner blog image Decoupled Drupal Decoupled Drupal Development Drupal Drupal Developer Frontend developer Blog Type Tech Is it a good read ? On
If you know us at Mediacurrent, you know we create amazing digital experiences with Drupal. Did you know we also support WordPress websites?
Since 2007, Mediacurrent has been the open source expansion partner for enterprises and global brands. As certified experts, we have a reputation for providing best-in-class digital solutions and growing long-term, strategic partnerships for clients like Weather.com, MagMutual, and Emory University.
With thousands of implementations and thought leadership resources completed, we have been continuously looking for ways to add more value to our customers. We've seen a rising need in our Drupal community through hours of partnerships, and that need is more WordPress support.
WordPress in the enterprise has risen 16%, driven largely by the rise of multiple CMS use.
- Source: The Rise of Multi-CMS in the EnterpriseWhy the Expansion?
For over a decade, we have been helping customers migrate from WordPress to Drupal, and we've proven ourselves a trustworthy partner in the migration process. As we've grown, we’ve expanded our Drupal expertise into deep open source strategies—partnering with clients on a long-term basis to solve their technology challenges.
Many enterprise organizations that have standardized on Drupal will still have some non-Drupal sites in their ecosystem. That's where Mediacurrent comes in as a single-source digital partner.
What We've Done So Far
Currently, Mediacurrent is assisting large-scale enterprises with their WordPress sites. What started as Drupal legacy clients have turned into an opportunity to better serve our customers. Our open source software clients came to us with similar pain points, and thanks to our long-term partnership, we were able to provide crucial benefits that provided a valuable impact on their return of investment, including but not limited to:
- Engaging UX - Our recent WordPress customers faced the challenge of creating an engaging user experience. Mediacurrent planned for a full redesign of the website's look and feel, providing randing, design, and value proposition workshops and including considerations for persona needs and critical business objectives.
- Data-driven Strategy - These organizations needed to maximize the return on their digital investment. Mediacurrent is continuing to incorporate best practices for content, page layout, navigation, lead generation, and search engine optimization.
- Open Source Training - Designs were implemented using the Elementor page builder plugin for WordPress. Mediacurrent’s training team provided specialized instruction on Elementor page design to create page layouts and components.
- Post-Launch Support - Monthly support agreements help to optimize for performance and security, providing immediate value to our legacy customers. Security updates to WordPress and plugins can (and do) come at any moment. You must have a dedicated support team closely monitoring and upgrading the code regularly.
Where We're Going
Moving forward, we will expand our support for open source clients who maintain Drupal and WordPress websites within their organizations. If 2020 has taught us anything, it’s that Mediacurrent needs to pivot with our customers' needs and continue to provide the best solutions possible.
As your digital partner, Mediacurrent will evaluate your web properties by assessing several core functionalities including;
- Security - Making sure your WordPress site stays updated and secure.
- Responsive Design and Development - Mobile-first designs backed by data and user research.
- Search Engine Optimization - We consider three factors when it comes to perfecting your on-page optimization: Page load times, Schema.org implementation, and CDN.
- Content Authoring Experience - A seamless publishing workflow is the key to empower content creators. Tools like Elementor let teams create and design new page layouts on the fly using a drag and drop interface. We've found this very similar to Drupal's Layout Builder, but more advanced and easier to use.
We see organizations growing, and the need to evolve our services to support others who have more than one CMS to manage.
49% of enterprises are planning to expand to additional CMSs in the future.
- Source: The Rise of Multi-CMS in the Enterprise
How We Can Help
Mediacurrent is excited to continue to expand our unique value proposition to organizations that aren’t standardized on a single platform and require peace of mind in terms of quality, security, and consistency. We have a reputation as a valued partner that is driven by growth strategy, risk mitigation, solving complex business problems, and producing real, bottom-line value with our solutions.
If you’re already running on Drupal and need help managing additional WordPress sites, or just have a lot of questions about migration, security, or future support, please reach out to the Mediacurrent team. We are available to discuss your websites' future, how we can help you efficiently manage your existing platforms, and provide a strategic roadmap that will keep your multi-CMS organization on the path to success
Building and maintaining superlative web experiences requires a focused team that specializes in delivering quality digital solutions to take your business to the next level. Some businesses have this team in-house while others don't. Mainly because the skills required of this team are not core to their production activities. Or because the activities involved don’t warrant a full-time in-house team. This is where a development partner comes in.
Trust is a clincher when it comes to choosing the right development partner. But finding a trustworthy partner takes some time and research, which will be truly worth the effort after all. Your Drupal development partner must not only be an expert with Drupal but be honest and maintain transparency right from the start; when they assess your requirements and tell you if Drupal is the right fit for you or not. Apart from honesty, transparency and trust, here is a list of pointers you should look out for when choosing a Drupal development partner.
All Drupal development agencies claim the best expertise and tons of experience. You need to find out if the experience is relevant to your technology, and more importantly, your business needs or not. Find an agency that has worked with and delivered at enterprises of your size. Ask for exact case studies addressing the top challenges you face and how the Drupal agency has addressed similar challenges in the past. Challenges could be with respect to specific third-party integrations, stakeholders, traffic or any other aspects.2. Ideal Fit
The Drupal development company you choose to partner with will be an extension of your team. They might be the best in the business but are they the right fit for you? Communication is key here. Interact with people who will be directly involved with the project. Not just the salesperson. This includes the delivery manager, technical architect, and key project personnel. You should get a feeling that the people who you are interacting with belong to your team and will treat your purpose as theirs.3. Understanding of the Project scope
Your ideal Drupal development partner will ensure that your project scope is understood, executed, and delivered in the way you had envisioned. Make sure the team you choose understands what is involved. Don't go with a team that says, "We are compliant ... what is your requirement?". The best way to know if they have understood the project is to ask them to prepare a scope of work and see if it aligns with what you want from the project. This involves one or more detailed discussions with your team. Be prepared for this.4. Quality of Response
This one is often overlooked by organizations while it remains one of the top qualities to be looking for in a development partner. Although the average response time is about 12 hours, it is not only the time factor that matters. The quality of response shows the way the team perceives your problems. More often than not, you will know if the team you are dealing with is responding within your expectations (of time, information). This is a good indicator of interest as well as a benchmark on how they will interact with you once the project is underway.5. Reference calls
Your Drupal development partner’s client list speaks a lot about them. However, what can really help is to ask for reference calls with their customers. This will aid in finding out how their experience has been in terms of technical knowledge, communication, project management and in general about how happy they are.6. Proof of Concept (if you have the time):
There’s so much at stake in terms of time, resources, investment, and more when you dive into a development partnership. Asking for a Proof of Concept (PoC) will not only help you identify the team’s performance but also if the end result matches your requirements. Request the team to develop a PoC. May be a vanilla Drupal release with specific features and functionality that can be done in 1-2 weeks. See how they perform there and if the way they communicate during the PoC meets your expectations.7. Drupal community involvement
If your Drupal partner is an active community member and contributor, you know that they not only have the skill and expertise, but they also believe in giving back to the community. A commitment to Drupal shows that they truly believe Drupal is important for them and that they are in it for the long haul. Do a research on how involved they are in the Drupal community.
Every year, Dries conducts an in-depth analysis of the top 30 Drupal companies and individuals around the world that contribute to the project. That’s a good place to look out for your Drupal agency partner.
Choosing a technology partner who can envision your goals is not easy when you have tons of agencies to choose from. This list of must-haves is not exhaustive but can give you a jumpstart on your process of finding your ideal Drupal development partner. Reach out to us to find how we can help you with your next Drupal project.Drupal Planet Drupal Development Drupal Shefali ShettyApr 05, 2017 Subscribe For Our Newsletter And Stay Updated Subscribe
Leave us a CommentShefali ShettyApr 05, 2017 Recent Posts Image Evaluating a Drupal Partner for your Next Project – Some Unbiased Tips and Suggestions Image How to Import External Feeds into your Drupal 9 Website with the Feeds Module Image What To Expect From Drupal 9.1 Want to extract the maximum out of Drupal? TALK TO US Featured Success Stories
Know more about our technology driven approach to recreate the content management workflow for 7.ailink
Find out how we transformed the digital image of world’s largest healthcare provider, an attribute that defined their global presence in the medical world.link
Discover how a Drupal powered internal portal encouraged the sellers at Flipkart to obtain the latest insights with respect to a particular domain.link
For the past three months, Richard Sheppard has been a financial contributor to ContribKanban on OpenCollective. I'm extremely grateful for his decision to put his money towards my project every month. $5 a month may not seem like much, but the impact is greater than its monetary value. It's a reminder. A reminder that someone finds value in a project I maintain in my free time and has been a pet project for years.
It's a project which could always use some feature development, but usually more maintenance. The monthly contribution doesn't exactly cover labor, but it does keep the project maintained and up to date.
I also want to mention those who have sponsored me in general on GitHub Sponsors.
The success of a CMS project ultimately depends upon the content it contains. No matter how “on-time” or “under-budget” a project might be, editors have to be able to create and manage content, and they need to be able to do it without feeling the need to pull their own hair out.