Author Archive: Daniel Linn

ReadyTalk Goes to Drupalcon

Tuesday, April 3rd, 2012

Until Drupalcon Denver (the annual Drupal convention), I still felt relatively new to Drupal (read: n00b).  Drupalcon featured sessions ranging from design, UI and layout to system administration and performance and scalability.  Many of the top Drupal contributors were in attendance, including module developers, core developers, and even the founder himself, Dries Buytaert.  This offered a great opportunity to learn more about the CMS we’ve been operating our website on for roughly a year now.

Since that time, we’ve seen great improvements in how quickly we can get new content and features up on the site.  Standard maintenance tasks common with our old site are now automated.  Different members of the ReadyTalk marketing team now own sections and can make updates without waiting for me to publish content for them.  This makes everyone happy!

So what did I gain from going to Drupalcon?  First, the knowledge that if I did it all over again I would go to Drupalcon before – not after – starting a Drupal project.  Drupalcon offers a great place to meet people who have been through it all – site developers from government entities to news organizations to corporations were all in attendance.  For instance, CU Boulder’s team gave a great presentation on their rollout, which due to the requirement of supporting years of legacy material from their schools made it many times more complex than our own.

Second, it was great to hear people say, ‘yeah, I’ve been through that.’  Finding out that I’m not the only PHP nerd in the world is comforting, much to the chagrin of some of our developers.

Third, I learned about some pretty advanced configurations and modules and got to see the future of Drupal 8.  The efficiency at which so many contributors can work together to make these things happen is mind-blowing, and the future looks bright.  It’s great to know that the next time we update our site, the next version of Drupal will be ready for us and will be awesome.  I also hope that we get to contribute back at some point.

In any case, now I’ve been there. I’m feeling much less like a Drupal n00b, and much more ready to tackle the world of nodes and entities.  We’d like to hear your experiences with Drupal.  After all, Drupal’s greatest asset is its community.  If you have any tips, headaches, or questions, please share!

 

Daniel has been managing ReadyTalk’s website since 2008 and helps make marketing collateral easy on the eye.  When he’s not hacking away at VIM or tweaking the website, he’s busy improving his Denver Victorian, making/enjoying good brew and offering expertise to local non-profits.

LinkedInEmailShare

Digg This Digg »

Teleworking: Internet Nightmares

Wednesday, March 2nd, 2011

This post is part of ReadyTalk’s ongoing series on teleworking.

My telework day started without Internet. The cable technician had come to troubleshoot the connection, and when he saw the downed line, his shoulders slumped.

“I’ll have to run a new drop to your house. It will probably take me between 2 and 3 hours.”

I made a pot of coffee, and let my supervisor know my status and that I probably would not be available until later in the day. I had considered just biking in to the office, but I had other work scheduled on the house and needed to be home. They technician told me that my cable line had been purposefully cut from the alley along with two of my neighbors’. Meanwhile, a few guys show up to do unrelated work on the house and I am shuffling cars around so they can get a truck and a Bobcat in to my driveway.

I’m watching the technician run a new cable while the contractors jackhammer a strip of concrete next to the house. Finally, after many cups of coffee and a case of the jitters, the cable comes back on line, and I begin working at my desk to the sound of jackhammering.

Many of my coworkers use our technology to work from home during inclement weather and to watch over sick kids. Some even work from the ski slopes. I don’t have kids and am lucky enough to have weather-proof transportation, so when I work from home it’s usually so I can concentrate on what I’m doing for ReadyTalk or to supervise house work.

While the possibility of connection problems might make teleworking seem like a risky choice, it would have been easy for me to work from the local coffee shop had the cable company not been so responsive. It’s hard anymore to go anywhere urban and not find an available wireless connection.

While this day was filled with stress, noise and distraction, I’m looking forward to future days of teleworking with warm weather, a hammock and the sound of the backyard waterfall keeping me peacefully productive.

What are your teleworking horror stories? What steps have you taken to prevent them from happening again?

Daniel has been managing ReadyTalk’s website since 2008 and helps make marketing collateral easy on the eye. When he’s not hacking away at VIM or tweaking the website, he’s busy improving his Denver Victorian, making/enjoying good brew and offering expertise to local non-profits.

LinkedInEmailShare

Digg This Digg »

ReadyTalk’s New Website to use Drupal 7

Friday, February 18th, 2011

ReadyTalk will be implementing Drupal 7 for our new website, one of the most feature-rich and secure online content management systems available. Since ReadyTalk has been developing its new site on Drupal 6, we had to decide whether or not it would be worthwhile to move to the newest version. For anyone looking to move up, specifically if you are just beginning or are in mid-development, I’ll explore some of the considerations we made while making the jump.

Most of the modules that ReadyTalk needed were in development (and many are still in alpha or beta as I write this article). Before moving up, we looked at the modules we required and found any critical issues that had not been fixed. Some modules were no longer available but were integrated as standard in Drupal 7. Most notably is CCK. The Drupal team saw the ubiquitous implementation of this module in Drupal 6 and decided it was important enough to include in Drupal 7 core. Others also changed dependencies and as such did not require supporting modules. In most cases, we did not lose any functionality that we had originally planned for version 6, and in many cases we gained features.

We were fortunate enough that all of our required modules were well on their way to being ported. The one speed bump thus far has been migrations. Currently no graphical interface exists for moving data from WordPress or other databases into Drupal 7 (unlike in Drupal 6 with Migrate and Table Wizard), so migrations had to be written using the Migrate API. The Migrate module includes excellent examples for getting started, although at the writing of this article, formal documentation is lacking. Once the migrations were written we were able to pull data from our current website into nodes and taxonomies in Drupal.

While our new site is still under development, we look forward to many of the new features Drupal 7 has to offer. Most notably it offers greater simplicity over its predecessor, which will make it easy for our marketing department to offer quick updates and news to our users and prospects.

If you are looking to make the move to Drupal 7, or if you already have, let us know what you went through to get there. We look forward to showing you what we’re making, but want to hear about your projects as well!

LinkedInEmailShare

Digg This Digg »

Creating a New Website: Integrating a jQuery carousel in to Drupal

Tuesday, November 16th, 2010

In ReadyTalk’s new website design, we’ll provide up-to-date, dynamic information to our customers in a number of ways. One of those will be a carousel on the front page of the website. We want to load data asynchronously on to the front page to reduce loading times and we want it to load from Drupal nodes for easy maintenance. We originally went to find a Drupal carousel plugin, but none existed that met our needs.

We decided to use jQuery Tabs since Drupal comes with jQuery installed. It was easy to integrate in to our theme files using the great documentation provided by jQuery Tools. We also installed the jQuery Update module for Drupal to bring jQuery up to speed.

jQuery tabs offers a slideshow plugin for Tabs that makes for a great carousel with some useful features, such as navigation elements, smooth transitions and pause on mouse hover. The only hurdle we encountered with this setup was pulling nodes cleanly in to the carousel.

Loading a node would also pull all the page layout data with it – any associated blocks or theme data would be pulled in to the carousel – not what we want. This solution is simple and works great for loading the content of a node and nothing else. Appending any address with ?ajax=1 will automatically grab the node content by itself, exactly what we want for loading via jQuery. This solution is also applicable to any circumstance where node data might be pulled asynchronously.

So, long story short:

All done!

Have you done something similar? How did it work? What are other ways to do this?

This is the third post in the “Creating a New Website” series. See posts one and two for other web site ideas.

LinkedInEmailShare

Digg This Digg »

Creating a New Website: A perfect balance of usability, information and culture

Thursday, October 28th, 2010

In my second post about ReadyTalk’s new website, I’m going to look at how the redesign will affect our customers, and what we’re doing to improve the ReadyTalk experience, and what you can expect from our website blog posts. If you haven’t heard, we’ll be working hard in the coming months to move to a new website that should offer some great features to our visitors and make life easier for our marketing team.

Why are we making the move? In my previous post, I explored our reasoning for moving the site to a content management system called Drupal, and how that will make content creation and management a fast and simple process for ReadyTalk. That’s just one of the reasons for our redesign. We’ve also been conducting a lot of user testing to make sure that our site direction meets the needs of customers. For instance, our navigation will be changing to make finding important information easier for our customers and prospects. Our new design has also been tailored to ensure that any changes are comfortable for our current users. As always, logging in to ReadyTalk will be a one-step process, and it will still be the first thing you see on the front page.

In addition to the practical side of a redesign, we also recognize the opportunity to have a little fun, too. Expect to see our culture represented in new and different ways on the website. We love what we do, and we want to make sure the world knows it! If you need any proof, just see JC’s post about our engineering department.

In the coming weeks, you can expect to hear a lot about the website. We’ll be exploring our processes and discoveries along the way. Here are some topics you can expect from ReadyTalk:

  • Usability testing
  • Design and mockup processes
  • Improving SEO with Drupal
  • Integrating a jQuery carousel in to Drupal
  • The power of Drupal and views

Are there other topics of our redesign that you would like to see us cover? Do you have questions about how we are implementing Drupal? If you have best practices or some favorite resources, please share in the comments.

LinkedInEmailShare

Digg This Digg »

ReadyTalk & Drupal

Friday, October 15th, 2010

ReadyTalk first started looking at our ongoing web redesign about a year ago as a way to increase the organization of, and access to, an increasing number of resources provided to our customers. At first we were looking at minor updates and a visual refresh, but as more requests for features and content changes came from across the company, it became apparent that we would need a major overhaul. We decided that a Content Management System (CMS) would be ideal and allow for quick content creation and publishing by the entire marketing team.

What is Drupal?
Drupal is a free and open-source CMS with a huge community of developers making sure it is always up to date and secure. Upon learning about how many high-profile sites run Drupal (www.whitehouse.gov, www.ubuntu.com, and research.yahoo.com to name a few), it was easy to get excited about the possibilities. With the thousands of modules available for everything from automated search engine optimization to automated image resizing, Drupal fits nearly every use case. Using modules, we can quickly add à la carte site functionality and create a site specifically tailored to our users’ needs. Anything that is not already available can be created as a custom module.

Why Drupal?
ReadyTalk uses WordPress for our blog and newsroom, our own CMS for the Webinar Series, and hand coding for most other pages. To unify our site maintenance practices and to reduce the overhead involved in making changes and updates, we began looking to unify the site under a single CMS. We evaluated a number of CMS options, and Drupal came out on top because of its great extensibility and ability to accept custom code, as well as modules that will help us automate search engine optimization (SEO) and improve organic search rankings.

Our dependence upon PHP was a major factor for choosing Drupal. Drupal is written in PHP and handles user-submitted PHP code wonderfully, making it easy to port scripts from our current site. If, down the road, we decide to rewrite these scripts as Drupal modules, this will greatly increase the possibilities for adding additional functionality to our site.

Drupal’s theming possibilities are also extensive. In most cases, all that is needed to make a theme is a few images and some CSS. There is little difference between theming Drupal and theming a hand-coded site. In our case, we’ll also be making a few changes to how Drupal structures pages. One of the more exciting features will be a front page carousel that uses jQuery to asynchronously load nodes into a slideshow. This will keep load times down on the front page and will make updating the carousel’s content amazingly easy.

Major Features

  1. Relevant information and documents can be dynamically displayed on any page
  2. WYSIWYG editor enables ReadyTalk’s marketing team to quickly change and publish new data without the need for a web developer
  3. Automated editorial process for new content ensures it is reviewed by stakeholders before it goes live
  4. Front page will have more dynamic content, including a carousel that loads slides asynchronously via jQuery and caches them.
  5. Resource Center and Webinar Series will be sort-able, searchable and easily updated
  6. New, updated look and UI

Future improvements

  • We will continue enhancing the website by introducing new features.
  • Simplified forms
  • Asynchronous loading and submission of forms
  • Conversion of several scripts to modules to improve functionality and integration
  • HTML 5 and CSS3 support
  • Eventual upgrade to Drupal 7

As a part of our web development process, we will be featuring articles written by our website team on topics such as usability, user testing, design and web development. Stay tuned!

LinkedInEmailShare

Digg This Digg »