Starting sometime in January, things around here have really started to heat up.  I have fielded numerous inquiries from head-hunters, experienced a giant step up in project quote requests, and have talked to a handful of new and existing customers about forging a full-time arrangement.  To me, it appears that I have reached a cross-roads with fourfightingfoxes that could easily move forward on one of two different tracks.

This is the first in a series of introductory tutorials created to provide a guide to learning about the basics of the Drupal administrative interface. This tutorial will provide an overview of the following topics:

• Drupal introduction
• Admin login
• Creation of new content
• Find and edit existing content

For one of our current projects we are building a website where the design dictates that most of the content is presented using a dropdown menu approach. Normally, a dropdown functions best when all of the content is already loaded on the page, and just relies on javascript to animate the display and hiding of each dropdown element.  For this design, it is pretty obvious that requiring all of the overlay content to load along with the initial page is excessive for both load times, as well as complicated for the CMS organization and structure. AJAX to the rescue!

No matter how tech savvy you may be, there is often a language barrier when discussing internet technology. Sometimes it stems from a brand new technology that no one has really heard of. Other times it can be a simple issue of "How do you pronounce that word anyways?". Lets take "Wysiwyg" for example. I find myself using that word pretty often when trying to explain to a potential customer how they will be able to change/add content on their own without coding knowledge.