Torque Toons: The Most Ambitious Crossover Event In History

Torque Toons: The Most Ambitious Crossover Event In History

Marvel: ‘Infinity War is the most ambitious crossover event in history’

Me:  Let’s Encrypt has now issued over 50 million active certificates.

The post Torque Toons: The Most Ambitious Crossover Event In History appeared first on Torque.

Read Full Article Here

8 Ways You’re Wasting Money As A Web Developer

8 Ways You’re Wasting Money As A Web Developer

Picture the emotions that come to your mind when you think about your web development business. Can you recall the excitement of signing a new contract for building a website or the joy of solving a critical problem that took you most of the last week?

But then there is fear. How you are going to pay your bills this month when the phone goes silent for too long, and you haven’t got a single offer request for a couple of weeks. There is frustration when your customer delays the project. There is anxiety when you are refused to get paid until you add some features that weren’t previously within the scope of the project.

Let’s look at the things that can cause web developers to miss out on money, and how to fix them.

Too Many Hats

The reality of working as a freelancer or running a small agency requires wearing multiple hats. It is apparent that technical skills are essential, as it’s challenging to build websites if you don’t know how to code on at least a basic level. But there’s more to it than that. A freelance web developer needs to be their own manager, accountant, support manager, and salesman.

The last role is usually the trickiest one. It’s almost impossible to be a professional developer and great salesperson at the same time. Selling is difficult, and it requires a different skill set than designing or developing a website. Even your personality type may work to your disadvantage.

Working as a developer or designer requires extensive technical knowledge and a detail oriented attitude which are skills associated with introverts. Most web developers feel much better at dealing with code than with people.

It is no wonder that most people who build websites can feel uncomfortable with selling and thus don’t get the results that they are looking for.

On top of that, selling a service is always more challenging than the sale of a tangible product, which can be presented, tested, and evaluated before purchase.

The main reason why people who make websites can’t make their ends meet is because they are bad at selling. And one of the most common reasons for that is ineffective proposals.

Ineffective Proposals

The most common issue is focusing on the wrong problem. Getting a new website developed is a very stressful experience for customers. Surprisingly, it’s not because they are afraid the site won’t suit their needs. It’s because they are scared of the website development process itself. Exploring this pain and creating a compelling pitch focused on assuring them that you know how to organize the website development process is a key to building an excellent proposal.

Another frequent issue I have seen is making proposals all about the advantages of the websites yet to be made. Customers usually get dozens of quotes for a site, and all of them are full of technical jargon most customers don’t understand, such as responsiveness, optimization, customization, etc. This way they don’t see the reason why they should choose one proposal over another and usually end up making a decision based on price.

Finally, most freelancers focus on the most crowded space which is building new websites. They have to compete with millions of other developers and it is tough to stand out. At the same time, there are over 1 billion websites that are already out there which require changes, updating, and maintenance. The competition on that market is nowhere near the size of the website development market.

Lack Of Recurrence

Regular employees get their salary every week, two weeks, or month (depending on country) in a recurring manner, while freelancers get paid only when the project is done. As the website development projects almost always take longer than expected, it’s impossible to predict when a freelancer will receive his pay.

Unfortunately, rent, mortgage, and other bills are also recurring. It’s not a problem for contract workers because they know exactly when they will get paid. But for freelancers it means a constant struggle to get money wired for projects before bills become overdue. First, it’s about getting new jobs. Then it’s about developing the websites. And if these things aren’t hard enough already, there is also the whole acceptance process which depends on the client’s availability and willingness to cooperate. And once the project is finally done (and paid for) the freelancer needs to start the process all over again to get another job, deliver it and then once again hope for another wire.

No Predictability

People with steady corporate jobs not only know when they will get paid, but they also know how much they get. If the contract stipulates they make $80,000 a year, they will get at least that amount in equal chunks throughout the year unless they get fired.

Freelancers, on the other hand, usually don’t have such comfort. Customers want to get their website done as quickly as possible which makes it difficult to build a pipeline of work that is required to get a steady and predictable source of income. There are also many factors that are out of the freelancer’s control such as delays in delivering content for the website by the customer or a never-ending acceptance process. All of that makes it almost impossible for a freelancer to predict what the income pipeline will be throughout the year.

Lack Of Control

Getting paid on a per-project basis has one more severe disadvantage. You usually get paid only after the project is completed and at the end of the day, it’s up to the customer to decide when the project is done.

The typical scenario is that the client’s excitement decreases over time, and by the end of the project, they’re often not that responsive to communication which makes it difficult to get them to finally accept the project. Additionally, customers will never deliver the content on time which will introduce further delays. Unfortunately, some customers try to take advantage of the situation and force web developers to do some extra work within the previously accepted recalculation.

No Boss

Being one’s own boss is tricky. Many people choose freelance web development because they appreciate the flexibility and freedom it provides. It may seem that you can work when you want and as much as you want, or that you can be anywhere in the world and you can still do your job.

That’s theory. In reality, it’s more likely that you will need to spend all the time you possibly can on work, often staying up for long hours of staring at the computer screen.

It’s true that it’s easier for a freelancer to take a break during the day to pick up the kids from school, but when an employee is done, they are done. A freelancer, on the other hand, is almost never done with work for the day.

Bad At Collecting

For many freelancers I know, collecting is the least favorite part of the project cycle. There are several reasons for that.

First of all, customers make it difficult. From my time as a freelancer, I can recall that clients usually became much less responsive near the end of a project, especially when it was time to fulfill their end of a bargain. I often had to send several emails asking them for their final approval and later call them many times asking if they got the invoice and when I could expect the wire. There’s an entire set of tactics used intuitively by customers like:

“I’ve lost your invoice. Can you send it again, please?”

“I’m currently on a business trip/on holiday. Could you call again next week?”

“Just add this one small additional feature, and I’ll pay you right away.”

Back then I thought it is unique to the Polish market, but in conversations with web developers from the US, Western Europe, and India I learned that it’s a global trend on the low-end web development market.

Unfortunately, when it comes to collecting, the freelance web developer who needs to reach out to a customer to finally get paid. It is not uncommon that this takes multiple emails or phone calls to get the money for the project.

Many people find asking for payment uncomfortable, even when they are obviously entitled to it. In fact, some don’t feel comfortable about speaking of money at all, not to mention reminding a customer about an overdue invoice. Some freelancers even have internal doubts if their work is worth the money they have agreed on, and thus they feel even less comfortable asking for payment.

Taking On Excessively Big Risks

Why do customers change the scope of the project halfway through so often? Usually, it’s because it’s difficult for them to describe what they had in mind in the first place. Sometimes their vision or the reason why they want to build their presence online is blurry. Lack of a clear goal and a low level of technical knowledge make it tough to communicate successfully.

The inability to describe upfront what they want or need is the main reason for iterations. Often it’s only after the presentation of the graphic design or even the finished website when customers begin to clarify their requirements. Usually, it entails a lot of changes. If you factor in the complexity of responsive websites, search engine optimization and social integrations it often requires up to five iterations before the website gets accepted. It dramatically lowers the profit on the project as most sites are developed for a fixed fee. Some web developers even abandon a project when they are presented with a list of changes that will take too much time to implement, as they know it will mean hours of poorly paid work to get the project closed.

Don’t Miss Out On Money

Throughout this article we’ve talked about a lot of the pitfalls freelancers can run into when dealing with making money. The best way to make sure you get paid correctly and on time is to keep lines of communication open with your client.

Bring up cost right from the start and be clear about when you need to be paid and how much. See if your client would be okay with paying you throughout the project instead of saving it all for the end. This will give you a little more peace of mind throughout the process.

At the end of the day keep your lines of communication open and take your financial needs seriously.

Aleksander is CEO of Perfect Dashboard. A frequent speaker at WordCamps, Hosting Events and Joomla Days around the world. Originally from Poland, this foodie & computer games freak is very excited to blog on Torque!

The post 8 Ways You’re Wasting Money As A Web Developer appeared first on Torque.

Read Full Article Here

The Beginner WordPress Developer’s Guide to wp_enqueue

The Beginner WordPress Developer’s Guide to wp_enqueue

While WordPress is powerful, there are plenty of under-the-hood features that can help you maximize its efficiency. In fact, overlooking inherent functions such as wp_enqueue could even impact your site’s overall effectiveness.

If you optimize your themes and plugins correctly, you can improve your site’s performance while enhancing user experience. The wp_enqueue function is a great place to start. This simple integration can prevent issues with your theme when used with other WordPress plugins.

In this article, you’ll learn exactly what wp_enqueue is all about, and how it can be used to improve your WordPress projects. Let’s get started!

Introducing WordPress’ Template Structure

Part of WordPress’ power is its ecosystem of hierarchies and hooks. Hierarchies are driven by a set of special file names, while hooks can be referenced anywhere within a theme or plugin’s structure. Both work together to ultimately create a cohesive front end that is flexible and compatible with an unpredictable combination of themes and plugins.

Let’s start with the WordPress template hierarchy. This has an impact on the way themes are loaded. Whether you are writing a theme or a plugin, it is important to understand how any front-end loading scripts will be incorporated into the hierarchy.

The website offers a handy overview of the file hierarchy system.

A primary aspect to understand is that each individual page template gets wrapped around the header.php and footer.php files. With few customized exceptions, both of these files will be loaded no matter what individual page templates get sandwiched between. For example, the home page is loaded like this:

  • header.php
  • home.php
  • footer.php

While an individual post will load these files:

  • header.php
  • single.php
  • footer.php

This way, the top containers with the logo and menu (as well as the bottom containers with any additional footer information) get repeated consistently for every page. This ensures your WordPress page will be correctly, and fully loaded.

Bringing all of this together are WordPress hooks. There are two important functions that get loaded, one into header.php and the other into footer.php. The wp_head() function must be present in header.php:

<?php wp_head(); ?>

While the wp_footer() function must be present in footer.php:

<?php wp_footer(); ?>

They both look for any registered hooks within your plugins and themes. If something needs to be loaded in the header of a page, it gets pulled (or hooked) in by wp_head(), and likewise for the footer by wp_footer().

In other words, you can hook into either of these functions to enable specific unique code to show up on the correct pages of a WordPress website. This is important to understand because WordPress is designed for every single CSS and JavaScript file to be loaded into the theme using these hooks.

While hooks are important for understanding wp_enqueue, they are also the secret ingredient for becoming a power WordPress developer. It’s well worth learning more about how they work and where you can use them.

How wp_enqueue Works

The wp_enqueue() function is a hook in and of itself, which then hooks into wp_head() and wp_footer() as needed. Here’s how it all comes together:

  1. You write a function which registers your scripts using the correct wp_enqueue script.
  2. You hook your function into the wp_enqueue_scripts hook.
  3. These hooks all communicate together so that when wp_head() loads on the front end, your script is found and loaded with the others in the exact correct place.

Neglecting this process means that any theme or plugin that consolidates or reviews scripts will break because yours isn’t loaded using the expected WordPress method. We’ll talk a bit more about that in the next section.

Why Every Single Style and Script Must Be Enqueued

Once you understand how WordPress templates are loaded, you see get why it’s so important you load every single style and script this way. If you don’t, WordPress has no idea your file exists. This is WordPress’ way of keeping track of everything that’s going on within a website.

Consequently, it’s impossible to properly optimize the performance of a WordPress site if even one script is missing. Enqueuing loads your script into the system. This way, WordPress can always replicate it at the correct spot in wp_head or wp_footer regardless of any theme customizations.

Many plugins use the same scripts, but enqueuing enables them to share files rather than attempting to load them multiple times or creating version conflicts. Any optimization plugin or plugins that rely on similar or competing script libraries need to be able to detect these types of issues so they can be debugged and resolved without needing to hack your code. Ultimately, enqueueing scripts ensures greater compatibility across multiple plugins and themes.

How to Use wp_enqueue In Your WordPress Project

Before getting started, it’s important to understand that JavaScript and CSS files load differently. This is because they require different HTML tags. You’ll also want to make backups of your code before making any changes to your site.

If you are working on a live site, you’ll need to access your files using File Transfer Protocol (FTP). FileZilla is a great free cross-platform tool for doing this. Without further ado, let’s jump into coding your scripts into WordPress with wp_enqueue!

Load Scripts Using wp_enqueue_script

Loading JavaScript files is possible with the wp_enqueue_script() function. This function can take five arguments, in this order:

  1. $handle: This is a unique string to name your script, such as my-custom-script, and is required.
  2. $src: This is an optional string pointing to the full path of your desired file.
  3. $deps: An optional array of dependencies. If your script requires jQuery or another registered script, you can list all the handles for those required scripts in an array.
  4. $ver: You can optionally keep track of script versions here using a string for caching purposes.
  5. $in_footer: This is an optional boolean value that forces the script to load in the footer rather than the header.

To register your scripts, you’ll set up a custom function and use wp_enqueue_script to load each one individually. Here’s an example code snippet you can reference in your own theme or plugin.

function torque_enqueue_javascript() { 
    wp_enqueue_script( 'custom-name', get_template_directory_uri() . '/path/to/script.js' ); 

Once you’ve created this function, you need to use the wp_enqueue_scripts action hook to actually register it into the system. Below your function, you can use the add_action() function to connect with wp_enqueue_scripts.

add_action( 'wp_enqueue_scripts', 'torque_enqueue_javascript' );

Here, the first parameter is the hook name, and the second is that of your custom function. You’ll want to leave the hook name intact and customize the function name to match yours.

Load Stylesheets Using wp_enqueue_style

Loading in CSS files is incredibly similar, but you’ll use a slightly different function within your script’s loading function. You can choose to keep things separate with an entirely new function to load into wp_enqueue_scripts, or add onto your existing scripts function. For the sake of clarity, we’ll show you how it works in a new function.

The wp_enqueue_style() function also accepts five parameters. Here’s the breakdown:

  1. $handle: This is a unique string to name your CSS file, such as my-custom-styles, and is required.
  2. $src: This is an optional string pointing to the full path of your desired stylesheet.
  3. $deps: An optional array of dependencies. If your script requires another CSS file to work, you can list all the handles for those required stylesheets in an array.
  4. $ver: You can optionally keep track of stylesheet versions here using a string for caching purposes.
  5. $media: This is an optional string to specify media types. You can use media types like all, print and screen. Media queries such as (orientation: portrait) and (max-width: 640px) will also work.

To register your stylesheets, you can either add to the existing custom function or create a new one. We’ll show you in a new function how to use wp_enqueue_style to load each script individually. Here’s the example code snippet for reference:

function torque_enqueue_stylesheets() { 
    // Load main stylesheet 
    wp_enqueue_style( 'my-theme', get_stylesheet_uri() ); 
    // Load other stylesheets 
    wp_enqueue_style( 'custom-name', get_template_directory_uri() . '/path/to/stylesheet.css' ); 

With this function ready to go, you can use the same process as before to hook it into wp_enqueue_scripts.

add_action( 'wp_enqueue_scripts', 'torque_enqueue_stylesheets' );

Once again, take note that the hook name stays the same. Only modify the secondary parameter to match your custom function name.


WordPress comes packed with a huge number of developer-friendly features. However, if you don’t learn how to use them effectively, you will wind up with an unwieldy and unreliable WordPress project.

In this article, you’ve learned about how WordPress templates work together and load in scripts from themes and plugins. Because of this ecosystem, it is super important that your scripts and styles are enqueued properly. This can be done using:

  1. wp_enqueue_script: For loading in any JavaScript file necessary for your plugin or theme.
  2. wp_enqueue_style: For registering any CSS files necessary to the front-end design.

What questions do you have about enqueueing files in WordPress? Let us know in the comments section below!

Image Credit: LinkedIn Sales Navigator.

John Hughes

John is a blogging addict, WordPress fanatic, and a staff writer for WordCandy.

The post The Beginner WordPress Developer’s Guide to wp_enqueue appeared first on Torque.

Read Full Article Here

WordCamp Europe 2018 Announces Speakers

WordCamp Europe 2018 Announces Speakers

WordCamp Europe, the biggest WordCamp in the world, is just around the corner in Belgrade, Serbia. Users gather from all over to celebrate the CMS.

Organizers have started announcing speakers in groups based on the topic they’re talking about.

Group One: Open Source and the Web

The first group was announced last week and revolves around Open Source and the Web.

  • Paolo Belcastro is going to be talking about “The World of WordPress”
  • David Needham will tackle, “An Intro to Drupal for WordPress Users”
  • Hajj Flemings will talk about “Rebrand Cities: Crushing the Digital Divide, One Website at a Time”
  • Miriam Schwab’s talk is called “Content security policies: a whole new way of securing your website that no one knows about”
  • Heather Burns will discuss, “Developing for Privacy and Data Protection”

Group Two: Design

The speakers in group two are all talking about design.

  • John Maeda will cover “WordPress and Inclusive Design”
  • Morten Rand-Hendricksen is speaking about “The Ethics of Web Design”
  • Simon Cooke’s talk is called “Origins of Design Inspiration”
  • Alberto Medina and Thierry Muller will present a dual talk on “Progressive WordPress Themes”
  • Joshua World is presenting “You, yes you, Need to Sketch!”

This is only some of the amazing speakers that will be presenting at WordCamp Europe. The conference goes from June 14-16 and tickets are still on sale.

Check back here weekly for more WCEU updates!

Emily Schiola

Emily Schiola is the Editor of Torque. She loves good beer, bad movies, and cats.

The post WordCamp Europe 2018 Announces Speakers appeared first on Torque.

Read Full Article Here

Torque Toons: What Makes Up The Other 70%?

Torque Toons: What Makes Up The Other 70%?

It seems like it was only yesterday that the WC3 announced that 26% of all websites were powered by WordPress. That number has recently gone up to 30%, so we decided to find out what the rest of the internet is made of.

The post Torque Toons: What Makes Up The Other 70%? appeared first on Torque.

Read Full Article Here

WordPress Now Powers 30 Percent Of The Internet

WordPress Now Powers 30 Percent Of The Internet

What began as a blogging platform nearly 15 years ago is one step closer to taking control of the entire web. WordPress officially powers 30 percent of the Internet according to W3Techs.

It is also the fastest growing CMS by far, with Squarespace and Wix barely coming close.

These numbers are a huge victory for WordPress and the entire community. The CMS has outgrown its blogging roots and is now the most powerful CMS on the market. Not only does it power personal blogs, but it helps create digital experiences for enterprise companies.

Let’s go over how we got here and where we are going.

How Did WordPress Get Here?

So what sets the CMS apart from the rest? The answer is simple, the community. Because WordPress is open source, anyone can create something to improve it. The support of every developer and volunteer to WordPress core is what has made the CMS as powerful as it is.


Though there are still some people who believe WordPress is unsafe, that’s just not true. There is an entire team dedicated to making sure the CMS is secure. With the inclusion of HackerOne last year, people are rewarded for finding vulnerabilities.

This has led to patches being found and fixed faster.


Unlike many other CMSs, WordPress is incredibly easy to scale. You can turn your personal blog into an ecommerce powerhouse all on WordPress. This is one of the many reasons more and more enterprise companies are choosing it.

Sites like TechCrunch, The New Yorker, and all trust WordPress to manage incredibly high amounts of traffic.


As we stated above, WordPress is open source. This means that anyone can build anything they need to make their website perfect. If you don’t feel comfortable coding your own tool, there are hundreds of thousands of plugins that can fix a problem you might have.

Using these tools site owners can create whatever they want.

Moving Forward

Now the big question is how can WordPress conquer the remaining 70 percent?


While WordPress is incredibly customizable, it can have a large barrier to entry. If you’re not a developer, it can be daunting to get started. Gutenberg could help to fix this. The content blocks are easy for people to understand.

This could bring in users that were previously nervous about starting on WordPress.

Digital Experience

Another way to continue the reign of WordPress is to realize that it can support more than sites, it can support digital experiences. The CMS can create multiple ways to reach readers and customers. You can personalize each person’s visit, so they feel heard. You can gather data to better understand the kind of person coming to your site. You can include video, images, articles, and more all in one place.

WordPress has the range to support all types and sizes of websites, which brings me to my next point.

Enterprise Sites

In the past, enterprise websites would often rely on proprietary custom solutions. Closed systems that make users dependent on their vendors and, as commercial products, also represent a financial commitment. However, if your goal was to build a site for your business, this was the way to go.

WordPress, on the other hand, is historically seen as a blogging platform, tool for personal websites, small businesses, and entrepreneurs. Good for the masses, yet not suitable for Fortune 500 companies.

Yet, that representation is no longer accurate. By now, WordPress has grown into a full-fledged CMS capable of powering websites of all kinds and sizes, including in the enterprise sector.

Let’s go forward and conqure the remaining 70 percent of the web!

Emily Schiola

Emily Schiola is the Editor of Torque. She loves good beer, bad movies, and cats.

The post WordPress Now Powers 30 Percent Of The Internet appeared first on Torque.

Read Full Article Here

Voting for Torque’s 2018 Plugin Madness Now Open

Voting for Torque’s 2018 Plugin Madness Now Open

Let the madness begin!

Voting for Torque’s 2018 Plugin Madness is now open. Modeled after the NCAA college basketball tournament March Madness, we use a bracket-based voting system to pit plugins against one another each week.

This year we asked you to nominate your favorite plugins, and today we’re happy to kick things off with an impressive lineup of plugins. Head on over to to vote for your favorite plugins now.

Vote for your favorite plugins here

The voting schedule is as follows:

  • March 5: The Enchanting 64 (Round 1)
  • March 12:  The Thrilling 32 (Round 2)
  • March 19: The Supreme 16 (Round 3)
  • March 26: The Exceptional 8 (Round 4)
  • April 2: The Phenomenal 4 (Semi-finals)
  • April 9: Championship
  • April 16: Winner Announced!


Emily Schiola is the Editor of Torque. She loves good beer, bad movies, and cats.

The post Voting for Torque’s 2018 Plugin Madness Now Open appeared first on Torque.

Read Full Article Here

WordPress Myths Debunked

WordPress Myths Debunked

Not only does WordPress power 29% of the entire internet, it takes up 50-60% of the CMS market share, making it the most widely used CMS in the world. Whether you are setting up a blog, reviving your website, or launching your online enterprise presence, many will recommend that you use this CMS due to its “jack-of-all-trades’ nature.

However, along with this success comes doubters who think the platform isn’t scalable or secure. We are here to silence those doubters by debunking some common myths about WordPress.

WordPress is Just for Blogging

It is true that WordPress is excellent for blogging as it is not only simple to install, but it is also easy to operate. Even so, it is not right to suggest that blogging is all that this CMS is good for.

Over the years, thousands of developers have helped expand its functionality, which has enabled it to mature into a robust and versatile tool that is capable of supporting even the most complex sites. It can support digital experiences for any enterprise site.

WordPress is Good for Small Businesses Only

That was true a couple of years ago, but not anymore. With advancements and some remarkable features being integrated into it, WordPress has since become a scalable and flexible CMS that is easily adjustable to suit different needs.

Today, this platform has become a reliable solution not just for small enterprises, but also for big web projects. CNN, Ford, and The New York Times are just but a few examples of the big enterprises that rely on WordPress for their web projects.

WordPress is the Least Secure CMS

It is true that WordPress can be susceptible to hacking, Trojan threats, viruses, and other web attacks. But again, is there any software that’s 100% foolproof? Due to its popularity, WordPress may simply be a bigger target, but it does not necessarily mean that it’s the least secure among other CMS solutions.

The beauty of WordPress is that it is open source, which means anyone that finds a vulnerability can create a patch to fix it. This means there are thousands of people working to make sure the platform stays secure. On top of this, there is an entire team dedicated to making sure all vulnerabilities are taken before of before they can be exploited.

SEE: Tips to Protect Your WordPress Website From Being Hacked

WordPress isn’t Ideal for Commercial Use

The fact that WordPress is absolutely free makes some people assume that it’s inept for commercial use. Truth is, WordPress is also an ideal tool that can be utilized for commercial use. While there are many services that will allow you to use this CMS for free, there are other services that charge a premium price for personalized hosting.

With a managed WordPress host, you can run an ecommerce site quite effectively.

WordPress Doesn’t Provide Customer Support

Being an open source platform means that WordPress is not owned by a single person or company. The question that most people ask is – who will we run to when we run into problems? Even though this CMS does not have official support, it does not necessarily mean that customer support is unavailable altogether.

In case you get stuck, the platform provides users with various effective ways and resources where they can get help, including email lists, support forums, groups in social media, WordPress Codex, etc. Your hosting company, plugin developers, and theme developers will also provide excellent customer service.


Opinions regarding WordPress are many and you may not be able to tell whether they are all true. It is always wise to rely on a professional to debunk the myths and separate them from the facts.

Emily Schiola is the Editor of Torque. She loves good beer, bad movies, and cats.

The post WordPress Myths Debunked appeared first on Torque.

Read Full Article Here