8 Design Best Practices Every WordPress Developer Should Use

In a perfect world, every WordPress developer would have access to their own crack team of battle-tested designers and front-end wizards, leaving them free to get their hands dirty with the code they love.

However, if you’re working on your own and your platform of choice is WordPress, most clients will see you as a one-man army. You’ll frequently be expected to make design choices you might not be comfortable with tackling.

Like it or loathe it, design is a crucial aspect of every web development project. It doesn’t matter how elegant your code is if your layout makes users wince.

In this article, we’ll take an in-depth look at eight design best practices you can use as a developer to up your design game and expand your overall marketable skillset.

1. Keep up with Current Design Trends

This isn’t Vogue, so we’re not going to devote thousands of words to analyzing the in-and-outs of every current design trend. You’re probably already unconsciously familiar with what’s hot purely by virtue of general web browsing. However, it’s well worth your while taking the extra effort to deliberately investigate major trends in order to stay current.

Topping the “Most Used” list these days is parallax scrolling: a simple but effective motion design technique where foreground images move faster than those in the background. This creates an eye-catching effect, is easy to implement and lends depth and visual interest to the design of pages. You’ll see this effect employed quite often tomake headlines really pop and draw readers in.

Parallax is just a single trend highlighting the overarching scroll-heavy focus of much of today’s design. Infinite scrolling is another popular, though mildly controversial, technique.

Another current trend that rewards close study is material design: Google’s attempt to create a cohesive visual language across their products and services. Material design is focused on providing a seamless design experiences regardless of platform, with a mobile-first mindset.

Moving along, we come to card-based design (of which Pinterest is a classic example), a technique with an emphasis on the elegant visual display of condensed information.

These trends are so popular because they create visual engagement by following a simple set of good design rules. We’ll touch on many of these rules as we go through the rest of our list. Getting familiar with current trends, like the ones we’ve highlighted, is a great way of turbo-charging your learning and almost instantly improving your overall design sensibility.

2. Commit to Responsive Design

Responsive design simply involves the ability to appropriately adjust to every user’s screen size, device orientation and platform. In a mobile-first world, it’s an absolute requirement for modern sites on the front end but can often feel like a duct-taped nightmare of media queries and assorted hacks under the covers.

There’s no getting away from it though: users rightly expect websites and apps to display and function flawlessly across myriad devices. As a developer, you know that a seamless experience across platforms requires a lot of testing and fixing, but that’s no excuse to slack off.

To underline how important this is, overlooking this crucial design element means you could be kissing goodbye to a third of website traffic.

Implementing responsive design needn’t be a daunting task however, and developers these days have it much easier than even a couple of years ago in this regard. Make sure you’re getting this right and not sabotaging your designs for a considerable part of your audience.

3. Make Content Easily Accessible

Bounce rates vary wildly across websites, but one of the uncomfortable truths of online design is that a large number of people will be hitting your carefully constructed content and heading straight for the virtual door.

People make astonishingly quick decisions about whether to stay on a site or not, and your job as a designer is to make it as appealing as possible for them to linger and look around. Poor layout choices, lack of search options and plain old irrelevant or low-quality content are all things that will send visitors packing.

From a design standpoint, you want users to be able to quickly determine which part of your website holds the information they seek. Keep the navigation friendly and label everything clearly to avoid confusion.

4. Remember That White Space Is Your Friend

By the nature of their work, developers are an organized bunch most of the time. More often than not, however, they are optimizing for efficiency rather than aesthetics. This is why they often tend to treat websites like old-timey newspapers – filled to the brim with information, but a nightmare for users to actually consume.

You want users to be naturally visually drawn to the most important information in any section of your website. Effective use of white space is one of the most elegant and time-tested ways of doing this.

Not only does white space serve to highlight important information, it also improves reading comprehension and makes your overall design look substantially sleeker. Add it to your arsenal of design tricks and your sites will instantly start looking more polished.

5. Understand the Importance of Fonts

In design terms, fonts are a very big deal indeed. There’s a reason designers don’t just slap everything up in Comic Sans or Courier and call it a day. Unless you’re running a gallery-based portfolio, the chances are that the vast majority of the content of your projects will be in text form.

In the bad old days, you could only choose from a limited set of fonts while doing web design, but those days are thankfully gone. Browser support for web fonts means that you’re now only limited by how much time you want to spend finding the perfect font fit for your site.

An ideal font will not take attention away from the content itself, or look out of place in the overall design. Choosing fonts and font pairings is a design decision that rewards careful thought.

Begin with a simple typographic primer, such as Matthew Butterick’s Typography for Lawyers, and you’ll feel those design muscles starting to flex straightaway.

6. Don’t Make Forms Difficult

Nobody likes filling in forms. Whether online or offline, they’re a chore. There’s no getting around them in web design though; they’re the main way users interact with your site: registrations, lost password recoveries, contact pages, submissions – the list goes on.

Taking a little bit of extra time and effort to actually make your forms intuitively usable, friendly and stylishly presented instantly raises the overall design profile of your pages.

You’ve got a slight advantage as a developer here as well. Many designers instinctively shy away from the technical side of implementing forms, but it should be relatively trivial compared to some of the other problems you’re used to wrestling with daily.

7. Provide Friendly 404 Pages

Every website breaks or goes down eventually, even if only for short periods of time. While that’s to be expected, regular users often take this as a sign that your website shouldn’t be trusted, so why not take a bit of extra time in order to build a unique error page to reassure them?

Anything looks better than a default server error message on a white page. A well-designed error page reassures visitors and gives the impression that everything is under control and things will be back to normal soon.

When using WordPress, there are a lot of great plugins that can help you set up a custom 404 page with little effort. You’ll find a great breakdown of these in our article on the 7 Best 404 Plugins for WordPress.

8. Accept That Small Details Are Important

So far we’ve covered basic design trends, responsiveness, accessibility, using white space to your advantage, typography, forms and 404 page designs, but we’re still only scratching the surface of all the elements you could consider in terms of raising your design game.

If you take away nothing else from our article, remember this: design is all about detail.

Considered in isolation, all these small points don’t amount to much but, as they are all piled on top of each other, they form a cohesive whole that people instinctively recognize as good design.

As a developer, you’re used to focusing on details in a very different context, but they’re equally important in this arena. Recognizing that truth goes a long way towards making you a better designer.

8 Tips to Land Your First Client as a WordPress Developer

So you’ve decided to set up shop as a WordPress developer. You’ve got a lot of personal projects under your belt and have set up several websites for friends and family. How hard can taking things to the next level be?

Let’s not mince words – it can be quite rough out there for a freelance developer. There’s an enormous amount of competition and a seemingly endless supply of service providers willing to work for a tenth of what they should be charging.

That doesn’t mean it’s an impossible market to break into, however; it just means you’re going to have to roll up your sleeves and apply some good old-fashioned elbow grease to get things moving.

We’ve put together eight top tips to point you in the right direction. Let’s dive in!

1. Make Yourself Stand out

It stands to reason that the easiest way to get hired is to strongly differentiate yourself from other applicants. To do this, you need to understand what your strengths are and use them as selling points for potential employers. This can be as simple as having an outstanding portfolio or crafting a personalized pitch.

In other words, what can you offer that other WordPress developers can’t?

Some developers take things further by focusing on niches. Are you a cooking enthusiast? You can use this experience to make your food-related web projects really stand out and connect with local businesses in that area. Customers always appreciate dealing with someone who shares their passion and understands their business.

Another way to stand out is to emphasize which programming languages you’re fluent in and showcase personal projects that reflect your expertise in your public portfolio. Just because you’re looking for work as a WordPress developer doesn’t mean you should let your other skills rust away. JavaScript, for example, is likely to be heavily in demand for the foreseeable future.

2. Negotiate and Don’t Undersell Your Services

One of the biggest mistakes you can make when starting your career as a web developer is to hobble yourself with cheap rates just to land those first few crucial clients.

Don’t believe me? If you’ve spent any time in the web development community you’ve likely seen veterans chastising newbies for this repeatedly; it’s basically gospel at this point.

Lowball pricing attracts problematic clients like bees to honey. Good clients – the kind who understand the value of your work and time – will be ready to pay you a decent living wage. You might have to look hard for that first big break, but it’s out there.

If you do allow yourself to be bullied into underselling your services, you risk falling intoan endless loop of cheap clients and stressful projects where you work for the equivalent of minimum wage. Make the smart choice and avoid this from the outset.

3. Don’t Be Afraid to Look Offline

As a web developer, your first instinct will naturally be to look for that first gig online. But, since you’re probably not going to have an extensive portfolio or many professional references yet, your best bet might be to try to close the deal in person with those first few clients.

Many businesses have been burned online in the past by less than scrupulous or incompetent freelancers and welcome the opportunity to deal with a developer in the flesh. Being just a phone call or drive away might be enough to actually seal the deal in such cases.

If using this approach, steel yourself for rejection. You’ll likely have to contact a lot of businesses before finding someone who’s interested in hiring you.

Every developer has their own tactics here. Some limit themselves to scouting for local businesses, others target outdated pages or focus only on high-income clients. Find out what works best for you and start making calls and sending emails once you’ve tailored a pitch for each potential customer.

4. Explore Lesser-Known Online Marketplaces

Everyone knows about Upwork and Fiverr, but what about Reddit’s hiring listings, the official WordPress job listings or Codeable.io? These are just a few of the many less densely populated alternatives out there.

That’s not to say there isn’t plenty of competition on these platforms as well, but it pays to cast your net as widely as possible while still maintaining an up-to-date profile on each of these sites.

5. Polish Your Online Presence and Portfolio

If you want clients to find you, you need to make it easy for them. I’m not talking about spamming advertisements for your services across all social media outlets you happen to be a member of here. At the very least, you need to review your job-seeking profiles, ensure that your “current job” statuses are up to date and include links to your portfolio wherever pertinent.

Start by making sure you have an up-to-date LinkedIn profile. The platform attracts a lot of flak, but it’s still the network of choice for a huge amount of potential clients. A polished presence there is a great calling card and might even get you new business all by itself.

A word of warning about social media sites. The first step many clients will take is doing a little background digging on public-facing profiles to get a feel for what type of person they’re dealing with, so make sure you’re presenting an appropriate image online.

As for your portfolio, it’s pretty common for people trying to get into web development to make excuses as to why they haven’t set theirs up yet. Don’t let yourself fall prey tocobbler’s children syndrome. Put yourself in the customer’s shoes; would you hire someone with no previous work experience who doesn’t even have a couple of personal projects to show off?

Not having any completed client work shouldn’t stop you from putting together a portfolio either. Share your most polished pet projects, online repositories, or open-source project contributions – whatever it takes to show clients you’re the real deal.

6. Get Out There and Network

There are thousands of online communities for every kind of freelancer – from designers to WordPress developers – to share their work experiences. These can prove an invaluable resource when you’re just starting out for all kinds of advice.

Some examples of these include the web development and freelancer sections on Reddit and Stack Overflow Careers.

It’s pretty much guaranteed that no matter what doubts or problems you might be experiencing, somebody somewhere online has already gone through the same thing. In many cases, they’ve taken the trouble to write about their experiences and compiled handy lists of solutions that can help you out.

Your networking endeavors shouldn’t be limited to the virtual world, though. Meeting people face-to-face and handing them your newly printed business cards (you have some of these ready, right?) can sometimes make a more lasting impression than email.

There are all sorts of real-world networking opportunities available if you take the time to research options in your area. These could be local WordPress meetups, hackathons or conferences. Keep your ear to the ground and start getting social!

7. Tailor Your Approach

No two customers are the same. If a potential client approaches you with some basic information about a project, make sure to do your due diligence and research his business and market sector as much as possible.

This should help you make informed suggestions about good practices relating to the project in question. For example, if building a portfolio site for a photographer, you’d naturally suggest putting the work front and center. If you’re dealing with a store, the nitty-gritty of e-commerce customer flow is where you’ll be spending most of your time digging into details.

These examples may sound obvious, but you’d be amazed at how many developers simply offer cookie-cutter solutions to clients without taking the time to explore their exact needs.

8. Pitch Solutions, Not Technology

Gone are the days where a business could afford not to have a web presence. What this means for you as a developer is that in most cases you won’t have to sell customers on the actual idea of having a site; they’re more interested in results.

This means you need to sharpen up your sales skills in many cases. Remember, you’re not selling a simple website or a particular technology, you’re selling a solution.

Maybe your client’s business is leaving money on the table by not being able to process online orders. Maybe they’re crippling their sales pipeline by not letting customers make appointments online, or sign up for a mailing list in order to receive future offers. Find the problem and pitch the solution.

Part of your job as a developer is to sit down with your client, analyze their requirements and come up with ideas that they may not yet have considered. Don’t worry about these ideas getting occasionally shot down. You’re building the ability to identify and solve problems in the wild, a skill that will pay off hugely down the line.

How to design websites developers won’t hate

For the best visual precision, every Web design project eventually requires fully-composed mockups for each page and interface. Informed by technical constraints, these mockups must act as collaborative visual design documents for regular discussions with developers – not just something you hand off as though the person on the other end is a WYSIWIG factory.

Graphics, textures, typography, and other little tidbits all must be transferred from a simple graphic into a living interface. But just because you understand how to design great mockups doesn’t mean that you understand how to design them for developers. In this piece, we’ll provide tips for building mockups that transition as smoothly as possible to development.

After all, if you want the project to move forward, you must always ensure that your works of digital art are clearly understood by developers who think in terms of frameworks and systems.

Plan for Limitations

As recommended in the free Designer’s Guide to Collaborating With Developers, the first step to proper implementation is predicting  UI limitations that may (and usually will) arise during development.

In the design world, it seems like any beautiful idea should be possible to create in code. HTML5/CSS3 specs have certainly come a long way, but some ideas are still very difficult to build with full support.

When collaborating with developers in the wireframe/prototype stage, always keep in mind the limitations of HTML5, CSS3, or whatever your language of choice. That way, you’ll know what to design and how to design ideas visually so that developers can actually build the interface.

Keep a list near your desk (or in Google Docs) with a collection of hurdles, obstacles, and interface ideas to avoid. While It may be possible to add these features later, you should focus initially on prioritizing interface elements that are most feasible. As you progress in the design, review this list on a weekly basis with developers so that you don’t get lost in a high-fidelity design of something that’s actually a technical nightmare.

Now that you have a good starting point for design feasibility, let’s examine some other methods to keep in mind as you design.

Expand on Interactions

When it comes to exploring interactions, prototyping is the most efficient platform for discussing feasibility. Aside from actually coding your designs, prototypes are far more effective than simply describing or annotating flat wireframes and mockups.

Even rough low-fidelity prototypes (also known as interactive wireframes) can show developers the overall framework of content, and the dependencies between content as users click through the experience. While the visual details won’t be anywhere near polished, developers can still provide feedback on design infrastructure.

 

For example, you might be dead-set on an infinite scroll for a large blog design, but perhaps a cards UI pattern can still serve as an elegant compromise between usability and site load times. On a subtler level, developers can also provide you device-specific feedback. Your navigation header might work beautifully in the prototype, but it may be completely hidden by the address bar in certain browsers and devices.

You simply won’t uncover these technical setbacks (some of which may require a complete revamp) unless you let developers play with your prototype. In fact, part of the reason our app integrated with Photoshop and Sketch was to encourage more designers to cross over into the interactive design stage (even if they prefer to first add fidelity to the visual design).

2. Create Browser Fallbacks

The field of Web design is quite different compared to mobile app design.

Android and iOS apps run on a single OS with various screen resolutions. Websites, however, introduce far more variables – they must run on different screen resolutions and on different operating systems, in different browsers, also with different screen resolutions (and devices).

 

The process of designing a website interface feels similar to designing a mobile app interface. But development is vastly different between these two mediums. When designing a mockup,  you’ll want to consider the potential pitfalls and drawbacks of each feature.

This is especially true of newer CSS3 techniques that are not supported in all browsers(ex: transforms, reflections, clip-path, and masking). While Photoshop and most other design programs let you insert notes next to your design, there is no substitute for a quick feasibility discussion with developers as you prepare for a major iteration.

Below, you’ll find some of our favorite free open source scripts to help with browser compatibility. These resources may not help you directly when designing, but they are certainly an important conversation point when collaborating with developers.

  • Modernizr – In the world of Web standards Modernizr is a cherished asset for any project. It’s a customizable library for cross-browser HTML5/CSS3 support. Use the download page to customize your own features or just grab the whole library from GitHub.
  • Fallback.js – This tiny JavaScript library is meant to control every possible fallback method and library. By centralizing all of your scripts it becomes easier to check which files aren’t working and provide alternate solutions.
  • Selectivizr – Selectivizr is similar to Modernizr but it focuses more on CSS selectors. This JS library emulates CSS pseudo-classes and attribute selectors to improve support for older versions of Internet Explorer.
  • Video.js – HTML5 video has taken the spotlight but Flash video is still a reliable fallback. Video.js makes it easy to embed any video format into an HTML5 player with a Flash fallback for older browsers.
  • IE7.js – Older versions of Internet Explorer put up a tough fight against common web standards. IE7.js forces older browsers like IE6-IE8 to support typical rendering methods like transparent PNGs and RGBa() colors.
  • Detect Mobile Browsers – This isn’t so much a library as a code generator for mobile detection. You’ll find snippets in all languages from ASP to jQuery for detecting a mobile browser. Developers can choose to execute(or not execute) code for mobile users based on these results.

Even if you don’t understand how these scripts work, you should still bring them up with your developers. In our experience, we’ve found that developers appreciate the proactive gesture and don’t mind spending some time explaining any compatibility issues. After all, it is in both of your best interests since late nights are usually a shared misery between designers and developers.

Dealing With Alternate Pages & Resources

While the homepage design may require the most effort since it’s a portal to the entire site, you also need to apply the same precision to the inner pages.

 

In some large companies, project managers demand full mockups for every single page due to strict internal processes. In other companies, some developers may have design experience, allowing them to build multiple similar pages from a single mockup (freeing up more time for you to work on unique pages). Adapt the level of mockup detail depending on your company protocol.

Now, let’s examine some of the development considerations for your mockup elements.

Inner Page Graphics

A keen sense of graphic design is required for great mockup design.

For example, even if two pages are distinguished only by differences in icons, the safest option is to still create two separate mockups to avoid any confusion. Most of the time, you’ll find it’s safer to create all inner pages and then export icons separately – that way, developers can access the individual icon images and the page designs as reference material.

 

Before wrapping up your mockup design, follow along with this checklist to see if you missed anything. Here’s a quick list of some things to check for:

  • Graphics should be sized exactly as they need to appear
  • Illustrated different JavaScript interaction states (ex: dropdown menu open + closed states). Even if it’s demonstrated in the prototype, it never hurts to leave a paper trail.
  • Logged in & logged out states
  • Label form fields, buttons, and inputs as needed
  • Error/success messages
  • Include separate graphic files for all images including the favicon, animated loaders, 404 page photos, etc.

On larger projects, we’d recommend including a short document for developer notes. Just be sure to clarify the referenced mockup (and page sections) which pertain to the notes. If you’re working in UXPin, you can add a note to the design itself and while you’re in Preview mode, or you can also just upload a separate document into your project folder.

 

2. Separate Responsive Mockups

While mobile app mockups must consider landscape and portrait view, websites must support any view at any dimension from smartphones to widescreen monitors.

If your design is meant to be responsive, then we recommend creating different mockups for each breakpoint to show developers how the layout adapts.

 

Consider a few of the following changes:

  • Do logos, graphics, and/or icons change size or position?
  • Should font size increase or decrease? What about line height?
  • How does the main navigation adapt to smaller screens?
  • Will sidebar columns drop below the main content or perhaps disappear entirely? What about footer content?

There are no right or wrong answers because each project needs to be handled individually.

When in doubt, the mobile-first approach championed by Luke Wroblewski is always a good starting point (once you’ve completed the initial user research). Design around the content for the smallest screen size, then scale it up as the screen size increases. By building upon the essentials first, you ensure a more enjoyable device-agnostic experience.

To prepare for the transition to development, make sure you label your responsive mockups properly. Filenames must include the responsive breakpoint in pixels along with any other important details(revision date, draft number, retina screen, etc.)

Your goal is to design for every possible situation so the developer doesn’t have to think.

As always, if you’re unsure about how to deliver something, just ask one of the developers what format they prefer. Keep the communication lines open to reduce problems and avoid confusion.

Design Tips to Make Development Easier

Digital design programs come in many forms from Adobe Photoshop to Fireworks and the popular newcomer SketchApp. Despite the differences in capabilities, the overall mockup design process remains relatively uniform across these different applications.

The following tips are geared toward designers who create mockup assets for developers. Some of these ideas are easy to overlook on the surface, but they make a world of difference when it comes time to write code.

Mockup Design Best Practices

Mastering any design program takes time and switching up your workflow can be daunting. But once you try incorporating these tips, they’ll feel like second nature. When you design with developers in mind, it makes everyone’s job a whole lot easier.

 

Here’s a few best practices we’ve learned through the years:

  • Organize and label your layers Developers may not always need to open your PSD/Sketch files, but the contents should always be organized. Use layer groups to rank similar layers together. Also, assign every layer a clearly recognizable name since mockups are very detailed and usually require a lot of digging to find exactly what must be changed or extracted.
  • Prepare a nice asset package Remember that asset preparation saves everyone a lot of time and stress. Once the mockups are finished, export graphics, icons, photos, and other assets into separate files. Developers may not feel comfortable exporting PNG/JPEG/SVG files and it’s a lot easier if you hand off everything in one neat collection.
  • Use in-app export tools In Photoshop, you can export graphics using the slice tool or by manually creating new documents. Sketch includes its own export options designed specifically for interface graphics. Organizing your design files doesn’t take much work and your developers will love you for it.
  • Show, don’t tell – If interactive elements require visualization, try converting your PSD/Sketch files into layered prototypes. In doing so, you’ll be able to actually show complex animations and interactions, leaving none of it to the risk of imagination.

For more practical tips, we recommend the Photoshop Etiquette site which includes advice for dozens of topics like effects, layer organization, and typography. To learn more about the anatomy and process of mockups, check out the free Guide to Mockups.

2. Version Control for Designers

Every developer should at least know about version control systems, which are like digital archives that store previous versions of a script, database, or an entire website. Aside from organizing files, version control is useful for rolling back changes or comparing differences between two(or more) files.

 

Although version control is mostly used in programming it has found small pockets in the design community. While design-based version control is still new, there are some great resources available. Pixelapse is an online storage application for managing design documents in the cloud. And while GitHub is primarily a code storage platform, they’ve recently added support for PSD files.

Now it’s possible for designers to use GitHub as their own version control system for PSDs. Granted, the site is open source and it may not be a great choice for private enterprise projects – but it is a good way to practice and learn about version control.

Here are some alternatives for design-centered version control:

  • Cornerstone – The Cornerstone app is a Subversion client for Mac. This does require some initial setup but it can be great for localized work. Check out this stack answer for more info.
  • PixelNovel – Adobe has released their own version control platform named PixelNovel. This also runs on Subversion but is much less technical to setup. It has a Photoshop plugin and even allows file sharing among multiple users.
  • GitHub for PSDs – As mentioned earlier GitHub does support PSD diffing. While this can be a great method for learning Git, most GitHub repos are free and open to everyone. So this is great for practice but not for large enterprise projects.
  • Kaleidoscope – This Mac OS X application doesn’t offer traditional version control, but instead can be used for file comparison. Kaleidoscope is great if you don’t need a full timeline archive and just need to compare the differences between files and/or folders.
  • Pixelapse – The widely-known version control platform Pixelapse is great for any designer. They have free open source accounts and paid accounts that can support small freelancers and large teams. Pixelapse runs across all operating systems and even includes a project dashboard for team collaboration.

Helpful Plugins

Photoshop and Sketch both support a wide assortment of plugins for automating tasks and improving typical design workflows. Even though Sketch was built from the ground up for Web design, Photoshop has a larger selection of plugins simply because it’s been around longer and focuses on a broader spectrum of tasks (photo editing, print work, UI design, etc).

 

We chose the following plugins specifically for UI designers who create interfaces from scratch. These plugins will help you achieve pixel-perfect mockups with less time and effort than traditional workflows.

Photoshop Plugins

  • GuideGuide – Setup guides and grids based on columns and pixel values.
  • Cut&Slice Me – Cut and export graphics to different devices like smartphones, tablets, and computers.
  • PNG Hat – A faster way to slice & export Photoshop mockups.
  • CSS Hat – Export any Photoshop layer into CSS code.
  • Renamy – Dynamically rename your Photoshop layers in seconds.

Sketch Plugins

  • Sketch Generator – Export all of your design assets with a single keystroke.
  • Text Styles – Export Sketch text styles from a mockup into CSS code.
  • Measure – Obtain the exact dimensions and coordinates of any graphic in your mockup.
  • RenameIt – The best way to rename layers in Sketch.

 

 

12 BEST WEB DEVELOPMENT BLOGS YOU SHOULD BE READING RIGHT NOW

web development blogs developers should read

The more you actually create, the more you’ll learn. And since there are many developers out there who share their experience, it’s a hard game to follow all of them. Because of this, we collected the following resources and present you a list of 12 web development blogs worth reading.

Be on top of the web development game

In order to stay up-to-date on the latest web development trends we put our heads together and curated this list of what we believe are the 12 best web development blogs you should be reading right now. Besides those web development blogs, we also curated a list of 24 great web design blogs, 12 inspirational podcastsand those 20+ web development newsletters.

1. Six Revisions

I wouldn’t call Six Revisions a classical web development blog anymore, rather than a major news site for developers. Six Revisions publishes practical and useful articles for web developers and designers as well. Articles are published on a regular basis every 2-5 days.

2. Specky Boy

The Specky Boy blog calls itself a design magazine. Paul Andrew – the publisher of Specky Bloy – not only focuses on design resources, but also provides useful insights on the latest web technologies. Especially for front-end developers the blog is definitely a great source for staying up-to-date.

3. WebResourcesDepot

WebResourcesDepot is a great web development blog offering new posts every day. Developers will definitely find some great content here. It’s definitely a blog to follow.

4. DailyJS

DailyJS is a great blog when it comes to JavaScript frameworks. It publishes great news articles, tips and resources on a variety of JavaScript frameworks and modules. Also their twitter account @dailyjs is worth following.

5.Smashing Magazine

Smashing Magazine is another well-known news site, which cannot be overlook. With new articles every other day it offers you great resources about HTML, CSS, JavaScript-related topics.

6.David Walsh

If you get yourself comfortable in the field of software development, you’ll definitely stumble upon the blog of David Walsh. You’ll find great articles about CSS, jQuery, JavaScript, PHP, MySQL and many more. Make sure to check out his web development blog.

7. OnextraPixel

I guess OXP is more a web design blog rather than a web development blog. Nevertheless, it provides some really useful articles in the field of development too. Whether it’s an article about some useful HTML5 tips or a new jQuery library. You’ll definitely get some inspiring content.

8. Stoyan’s phpied.com

A great blog worth mentioning is the personal blog from Stoyan Stefanov, who’s a Facebook engineer and the author of some really great books! It’s one of the best places to discover new articles, tools & frameworks.

9. Coding Horror

Coding Horror is a great blog resource from Jeff Atwood. It offers great insights in the developments of software engineering. You’ll get loads of great tips and resources from Jeff sharing his experiences.

10. Alex Sexton

The personal blog of Alex Sexton covers a broad variety of JavaScript related topics in a very plain and easy-to-understand way. You may also discover some new tools and trends on his blog which are waiting to be explored.

11. Paul Irish

As a developer, Paul is well-known for creating tools that improve workflows and make life easier for other developers. He’s currently working on Google Chrome DevTools at Google. You can gather useful insights on his personal blog where he regularly publishes web dev related articles.

12. Scotch.io

Scotch.io is an aspiring site publishing articles, tutorials, videos about AngularJS, node, JavaScript, Bootstrap and a lot more. It’s definitely a place to go when looking for some new inspiration or development resources.