Learn it fast with expert-taught software and skills training at lynda.com. See what you can learn

Article Center Developer Articles

Your source for news, insights, and inspiration at lynda.com. Come learn with us.

All articles

Featured articles

Article categories

A lynda.com membership includes:

Unlimited access to thousands of courses in our library
Certificates of completion
New courses added every week (almost every day!)
Course history to track your progress
Downloadable practice files
Playlists and bookmarks to organize your learning
Become a member

By Mark Niemann-Ross | Wednesday, July 10, 2013

Developing Cross-Platform Mobile Apps: A New Playlist

iOS Note-Taking App

Creating an app for Android, iOS, or Windows means learning two things: a programming language and the SDK. Even if you use one of the cross-platform frameworks, you’ll still need to learn some peculiarities of each system. It requires a significant investment in time and talents—and you’ll have to repeat it to create the same app for a different phone.

lynda.com can help with this learning curve. We’ve created a playlist of three new parallel courses: Building a Note-Taking App for Android, Building a Note-Taking App for iOS, and Building a Note-Taking App for Windows Phone 8 and Windows Store. Together they provide a roadmap for building a cross-platform mobile app.

We’ve built the same app for all three mobile platforms (actually four; Windows Store and Windows Phone are separate), using the same assets and creating the same functionality for each. We enlisted three top-notch authors to show you how they would implement the application on each platform. Our authors shared outlines and met regularly to coordinate their efforts, only making changes when the particular language or SDK demanded it.

To use this set of courses most effectively, start with the platform you know best and review how that author chose to implement the app for your favored SDK and language. Then choose your next device and watch the related course. Feel free to switch back and forth between the two, comparing the platform you know to the platform you’re learning.

Our authors provide you with insights to each platform, pointing out differences that may trip you up if you’re making assumptions based on a different SDK. In the end, you should be able to map your experience from one device to another.

Please be sure to fill out the survey at the end of each course. We’ll read your comments to see how we’re doing and how we can improve.

Interested in more?

Start a 7-day free trial at lynda.com • Watch Building a Note-Taking App for Android • Watch Building a Note-Taking App for iOS • Watch Building a Note-Taking App for Windows Phone 8 and Windows StoreAll Developer courses at lynda.com

By Morten Rand-Hendriksen | Monday, April 15, 2013

WordPress Under Attack: How to Protect Yourself

WordPress is under attack and your self-hosted site may well be in the crosshairs of people with nefarious intent. I’d like to shed some light on what’s going on, how to protect yourself against becoming a victim, and what to do if you’re hacked.

A bot-what-now attack?

Over the last couple of weeks, WordPress sites all over the world have been subjected to an unprecedented attack. Botnets—essentially thousands or millions of infected computers working in tandem—are executing brute-force attacks on self-hosted WordPress sites, attempting to log into administrator accounts, and taking over the sites. A brute-force attack is when a computer tries to log in using every password under the sun. While this would take forever for a human, a computer can make hundreds or even thousands of attempts per minute and eventually stumble upon the correct user name/password combination. This is one of the most extensive and wide-reaching botnet attacks ever recorded and it’s targeting all kinds of sites, from personal blogs to enterprise solutions.

By Tom Geller | Friday, February 15, 2013

Automatically Back Up Your Drupal Site's Database

You do back up your computer, don’t you? It’s an easy process, even if you don’t use a utility like the Apple Time Machine: you simply move a bunch of files from your one place to another.

But if you try that with your Drupal site, you’ll leave out the most important part—your site’s content and configuration. That’s because those parts live in your site’s database, which is stored far away from the site’s files. The solution is to export the database as a file, then save that file along with everything else. Doing that manually can be a pretty awkward procedure, but the Backup and Migrate module makes it easy. Here’s what I do:

  1. Install Backup and Migrate the usual way (shown in the section “Expanding a Site’s Capabilities with Modules” in Drupal 7 Essential Training).
  2. Define where you want Drupal to store private files by clicking Configuration > File  system. Be sure to secure the destination by following the link on that page. If you don’t, your raw database file could become accessible to everybody.
  3. Configure Backup and Migrate to save the database into that directory. (I set up a schedule to save it once a day.) The video Backing up with the Backup and Migrate module in Drupal 7 Advanced Trainingshows you how.
  4. Save that database file when you save the rest of the Drupal files.

A conservative strategy: Backup and Migrate set to save six months of backups.

One last step: Be sure to practice restoring from that backup to make sure it works, as a bad backup is the same as no backup! Note that this is not the same as a straightforward MySQL export: you’ll need to use the Drupal Backup and Migrate module itself to reestablish your site. But while unusual, I’ve found this procedure to be far easier (and more foolproof) than noodling with my site’s Drupal database manually.

By Jen Kramer | Monday, February 11, 2013

Open Source—A Two-Way Street

Do you have a favorite open-source software you’re using in your professional work? Most open-source software is created by volunteers, organized as a project where the software is created. If you’re making money from the software, strongly consider giving back to the project.

You don’t have to know how to program to contribute. Answer software questions in discussion forums or social media. Make a financial donation to your project. Many projects would like help with issues peripheral to software development, like accounting, legal advice, marketing or SEO expertise, and more. So get involved and give back to the software you love!

By Tom Geller | Friday, February 08, 2013

Plan for Drupal 8, build for Drupal 7

Rumor has it that early computer maker Osborne folded because it promoted its next-generation (but not-yet-released) model over the adequate (but sellable) one. People decided to wait, starving the company of revenue.

But while Drupal 8′s release is mere months away, there’s no reason to wait. Here’s why you should build your site now, in Drupal 7:

  • Drupal 7 will be good for a while. The community officially supports Drupal with security updates for two major releases. Drupal 6 came out in early 2008; Drupal 7 followed in early 2011. If the pattern continues, Drupal 7 won’t be obsolete until 2015 or later.
  • You’ll (probably) be able to upgrade your site to Drupal 8 later, as core Drupal is always upgradeable. The potential problem is in add-on modules and custom code, which sometimes lag. The good news is the biggie: Views is becoming part of Drupal core.
  • The cost for waiting is too great. While you wait for Drupal 8, your site stays locked in your imagination. There’ll always be something “even better” on the horizon.

So don’t fall victim to the Osborne Effect—build your dream Drupal site now!

By Jen Kramer | Monday, January 28, 2013

Manage unplanned expenses in your web projects

When working on a website design or redesign project, have you ever encountered small, unanticipated fees in the course of doing business? These might include costs for stock photography, fonts, content management system extensions, domain name(s), static IP addresses … the list goes on!

Rather than paying this cost from your own budget, or hitting the client up with a bunch of little fees (which gets annoying on both sides), consider quoting a separate line item for website design and development fees. I typically budget roughly 10 percent of the total for this. This is for any additional costs for assembling the site. There’s no guarantee you’ll use this at all, but if you need it, the money is there!

By Morten Rand-Hendriksen | Wednesday, January 16, 2013

Why WordPress?

Why WordPress?

What makes WordPress a good solution? Why is it so popular? Regardless of the question, the answer is the same, and it can be boiled down to three simple words:

Because WordPress works.

Of course, it’s a little more complicated than that. Let me put it into context from the perspective of the three main users of WordPress: the end user, the site owner, and the designer/developer.

Easy to find, easy to use, easy to share

A poorly kept secret about WordPress is its findability. If someone asked you how to get indexed on Google and you answered “Just set up a WordPress site,” you would not be far from the truth. The way WordPress is built makes it a magnet for search engines and other online indexes. So much so that if you don’t want your WordPress site indexed, you have to take steps to prevent it from happening.

Out of the box, WordPress has great search and share optimization. With the addition of plugins like WordPress SEO, AddThis, and Facebook for WordPress, these built-in capabilities are further enhanced, giving any site the opportunity to become the next big thing on the web. This is provided the content is great, of course. We’ll get to that later.

The purpose of many websites is to put out easily findable, accessible, and shareable information. And WordPress does this in spades. When you are searching for content on the web today, you will likely find it on a WordPress site. If you are reading or viewing content on a WordPress site, you are able to access and interact with that content through comments and RSS feeds. And once you have read the content, you will have an easy time sharing it with your friends on social sharing sites and social media.

Easy to publish, easy to configure, easy to maintain

WordPress is a prime example of the virtues of open source. It is built, evolved, and maintained by the people that use it and is therefore in a constant state of forward-moving flux. For site owners this means by simply running a WordPress site and keeping it up to date, they are at any time using the most current web technologies to communicate with the world.

Over the past three years, WordPress has undergone several fundamental design and development changes that have made an already easy-to-use application even easier to use. At the same time it has become more powerful and diverse. From how it is installed to how a site owner can publish content and interact with visitors, WordPress leads the way in removing the barriers that prevent anyone from publishing online. Between WordPress.com and self-hosted WordPress, most people with access to an Internet connection are now able to publish their thoughts, ideas, and creations online with minimal effort. With the challenges of web technologies all but removed, the site owner can focus on what matters: producing and publishing excellent content to share with the world.

Easy to build, easy to augment, easy to evolve

For me, the true power of WordPress lies in the back end. Whether you are a complete novice or a seasoned pro, building themes and plugins for WordPress will make your life easier and will enable you to do more in less time. I am walking proof.

With a design in place, building a custom WordPress site from scratch—one that looks and behaves nothing like what is expected of a WordPress site but is still just as easy to use and maintain—takes less time than with any other platform I have tried. When people ask me what WordPress can do I answer, “Whatever you want it to do.” And I stand by that statement. At its core, WordPress is a simple interface between the site owner, the database, and the end user. All the stuff in between (administration, themes, and functionalities) is available for the designer and developer to play with and add to in any way they want. And because WordPress is open source, people can step in and contribute to the WordPress community in whatever capacity they feel fit, from answering questions in the forums and building free themes or plugins to contributing to WordPress Core.

The bottom line

Though it may sound like I see WordPress as the be-all and end-all of web publishing, the reality is I am a pragmatic platform agnostic. The reason I laud WordPress and why I love teaching people about WordPress is because I see it as one of the best available solutions for most websites today. I have and continue to work with other solutions including Drupal and Joomla!, but for most of the websites I encounter, WordPress is one of the best options.

Whether you are just starting to play with the idea of publishing a blog, you want to become a web designer or developer, or if you already know all there is to know about the web and you just want to play with something new, WordPress is a great tool to use. It has both the ease of use and the advanced features to suit pretty much any need. And when that need isn’t met, a theme, a plugin, or an extension is there to fill the void.

Interested in more?

Suggested courses to watch next:

By Ray Villalobos | Thursday, December 27, 2012

Introduction to JavaScript templating using mustache.js

Recently I built a small website for an event in my area. This type of project required me to manage small amounts of data—information about speakers, bios, titles, and a description of the talks. I wanted to have a speakers page, but I also wanted a rotating promo built as a component I could use on the homepage, and on other pages to highlight the event’s speakers. That meant two different views for the same data.

This was the kind of problem I used to throw a quick SQL database at, but it really wasn’t worth the pain for this project as the amount of data was so minimal.  However, I didn’t want to resort to HTML because I knew the information would change often and be a pain to update. To solve the problem, I used a library called mustache.js. It’s pretty easy to use, and solves the problem with just a few lines of code.

Why mustache.js?

Mustache is a library that allows you to read in JSON formatted data and display it using templates you design with JavaScript. There are lots of similar libraries, such as underscore.js, handlebars.js, and dust.js. So why did I choose mustache?

Thanks for signing up.

We’ll send you a confirmation email shortly.


Sign up and receive emails about lynda.com and our online training library:

Here’s our privacy policy with more details about how we handle your information.

Keep up with news, tips, and latest courses with emails from lynda.com.

Sign up and receive emails about lynda.com and our online training library:

Here’s our privacy policy with more details about how we handle your information.

   
submit Lightbox submit clicked
Terms and conditions of use

We've updated our terms and conditions (now called terms of service).Go
Review and accept our updated terms of service.