So you’ve got a pretty good feel for what kind of new site you want.  Here’s some advice for efficiently building a site of great value.

1. Start with the content.

• gather all content together in one place
• content = words, photos, video, contact info, graphic art/logos…ANYTHING that will be visible by anyone who uses your site.
• organize it into acceptable file formats for the web (check with your web developer)

This is required work for any web project to be successful. Have it before you need it, or you risk wasting resources during your later project stages…because so many design/development decisions depend on what the final content is.

Too many website projects go awry because no one bothered to organize or produce the REAL content they needed for their REAL site. Everybody said “oh, that will be a demo” or “image area”, or “two or three paragraphs of content” and then assumed it would appear out of thin air. Content is the second-most important thing on your site, second only in importance to having users to appreciate it!  You don’t want to mess this up. Organize, write, edit, or produce the content yourself (or see to it that someone else does) now, not as an afterthought.

This is also a great exercise for you to be sure you will actually “say what you mean and mean what you say.”

2. Consider your users.

• put yourself in the shoes of your best customer
• what does he or she really want to do on your site?
• what do you really want them to do on your site?

Understand that the average web user is in a hurry and does not want to hunt for what he/she wants.  Don’t over think it.  Concentrate on user actions and clarity of information.

3. Assess the ‘minimum viable product’.

• what’s the simplest way to achieve your goals in a timely and efficient manner?
• think goals, not features
• separate the “would be nice to have” stuff from your bottom line “must have” stuff.  Prioritize both lists.

Understand that you can always add more stuff later (and you will want to), the important thing is to have a great foundation to build from.

4. Have a defined decision making process

• commit to being an active collaborator throughout the project.
• when it’s time to give feedback, be clear, be specific, and be engaged.
• when it’s time to decide A or B, be confident and be quick.

You should accommodate for change that will certainly occur during the lifespan of your project.  Building a website is an iterative process.  Sometimes the original vision doesn’t hold up under scrutiny.  That’s okay.  It’s not a failure or a setback…it’s an opportunity to improve and get things right.

Be ready to deal with important decisions in short order so you can keep your project momentum going strong and build a site of lasting value.

ENTERMEDIA has built a lot of websites since 2004 for clients of all types. Over the years we’ve gravitated to build practically every site with Drupal. Why is that?

Drupal is flexible.

From it’s inception Drupal was built with open source in mind. The founder of Drupal was smart enough to realize that predicting where the web will go in the future is a fool’s game, so let’s build it to be as flexible and modular as possible so it can adapt to each clients needs as well as any future developments. Remove as many constraints as possible at the outset. What this means is that you need to understand best practices for development to contribute modules that the rest of the community will endorse and adopt, but isn’t that how it should be? For instance, old site planning methodologies such as the waterfall project management approach, were concerned with concepts like knowing exactly where the main navigation menu was going to be before you would write a single line of code. With Drupal, if you decide that the main nav needs to move to the right side or left side instead of across the top you can make that change in a matter of minutes, so long as you haven’t styled the whole site prematurely.

Drupal is modular.

The devil is in the details when you are developing a website. Unfortunately, the majority of projects do not achieve the initial goal of building the entire scope on-time and on-budget. That’s because unless the developer has previously coded something exactly like what you need now, he’s having to estimate how he can get the job done on assumptions alone.  Building every simple thing from scratch is hard.

But with Drupal, ‘there’s a module for that.

Like the Apple store’s claim ‘there’s an app for that’, there’s most likely a feature rich Drupal module that does what you need and can be configured for your exact requirements. If not, there will be soon. There are over 3500 modules that can be used in Drupal to accomplish just about any requirement you can imagine.  Many times multiple modules are introduced that do the same thing, but over time the best solution emerges and the community gets behind it.  Once a module is adopted and accepted by the Drupal community it will be continuously tested and refined to fix any issues or add any ‘got-to-have’ features due to it’s vast number of implementations and specific feedback.  Developers help developers figure out these problems, and then the rest of us get to share in their solutions.

Drupal is scalable.

Drupal works with practically any type of database, so it doesn’t matter if you’re using an enterprise level Oracle databases or a free MySQL database. Without getting too technical, what you need to know is that Drupal can scale to meet your needs, but you’ll need an experienced Systems/Server Admin toproperly guide you to the right hosting a server setup. The greater point is that Drupal can scale as well as any other technology. The best proof is the number of large web properties who are successfully using Drupal, such as the economist. You can find more example drupal sites on the founder of Drupal’s blog.

Drupal is SEO friendly.

SEO is largely misunderstood from our experience. Drupal makes it easy for you to make your site follow best SEO practices.  It also allows you to write, publish, and correct problems with your site content that the search engines might not like with a little training and without needing a web developer to be involved.  Drupal does a lot of things automatically, such as provide strong internal link structure to make sure each link to pages within the site are tagged in the same way.  Drupal does not do SEO for you, however.  For more information on what you should be doing to practice good SEO, start here for a simple overview, but go here if you’re looking for professional help.

Drupal is free.

Drupal is open source and is therefore free of charge.  You will need to pay for hosting if you don’t have your own web server, and if you’re not a web developer you will probably need to hire a good team if you’re hoping for something professional.  However, you won’t have to pay Microsoft liscensing fees, the hosting for open source costs less, and the majority of the web is open source, so there are plenty of capable people in this world who can support a Drupal based website.

Drupal has momentum.

Like most movements, what’s critical to the success of Drupal is the huge adoption rate of the development community and the business community in general.  It is one of the greatest crowd-sourcing success stories around.  It is this community that will decide if Drupal deserves it’s success, if it should continue on, and for how long.  The Drupal 7 User Experience Project is a good reason to believe that Drupal will continue to be the best available option for years to come.  Already, some very big and important websites are built with Drupal, like:

• The British Government
  
• The Whitehouse
• Duke University
• Lucas Arts
• Reuters
• CNN

Drupal is simply an efficient tool.

Drupal is a content management system that allows non-technical site owners to manage their own content. It’s open source, which means it’s free as well. It still requires a high level of experience and expertise in web development practices and principles to build a professional website, which is not free unless you are one of those people. Drupal is simply the tool that allows you to do great things like build an online storefront, event listings, a social community, blog, photo slideshow, multimedia video player, forums, discussion groups, etc.

Putting customer testimonials on your website is a time-worn practice and generally a good idea, but there is some debate over their efficacy. One argument in their favor is ‘your users want to know you have them’…like some kind of a credibility benchmark. This is not to say that they will pay any attention to them. Why? Because testimonials are generally so complimentary by their very nature as to be perceived as embellished. They are not “reviews”…so what informational value do they offer? Again, maybe just the simple fact that you can get your current customers to say nice things about you is the entire point.

It’s also possible that users might have a different bias against them…whether or not they are real. Who would know if they are or are true accounts or complete fiction? In our experience, we have sadly come across some fabricated testimonials, that go a little something like this:

“[So and so] is the only [some kind of company] in the [blank industry] that I trust to deliver [x] [with all the trimmings].”

- Kenny S. from Alabama

Thanks for that, Kenny S! Rest assured, all of EM’s testimonials are genuine. (They need to be updated to reflect more of our latest work and clients, but that’s a different issue.)

Recently, one of our clients came up with a great way to present customer testimonials in a way that is genuine, informational, and compelling. Cuatro from CuatroBenefits invited some of his representative clients into his office the other morning and shot a quick video asking them some pointed questions about their experience interacting with his service. Full disclosure, Ethan and Ryan were invited and filmed.

Anyway, we think this is a wonderful and persuasive marketing play in the age of easy YouTube style video sharing. This is going to drive business leads for CuatroBenefits.  We recommend this way of presenting testimonials for similar service-oriented clients.

Check out the video on the CuatroBenefits site:
Cuatro Benefits Blog | Video Testimonials:  Why our Clients Choose to Work With Us

Or check it out right here on YouTube:

A great collection of interviews from the illuminating Jeffery Zeldman starting with the past, present, and future of web standards (and then on to the history of blogging, open source collaboration, and more).

Building a website is thought of mainly as a design and development challenge. And it certainly is. That’s indisputably the bulk of our business…ninety percent or more of our leads come to us seeking “web design” or “web development”, or both. Now those broad terms can mean all kinds of things when we start asking our questions. Every project is different. But ultimately that’s where the demand is, and that’s what our business supplies: web design and web development.

However, at some point (earlier the better) the client, the designer, the developer, or (oops?) the end user will each have to stare down the words on the page, and evaluate the message they comprise (or the damage they cause). There is nowhere to hide when it comes to content. If it stinks, the user will give up on you. So you work on it too make sure you don’t waste your time and money on a fancy website that speaks gibberish to the customer.

Would you believe that very often, almost always, the content strategy task of building a website can be just as involved with and urgently important to your ROI as any aspect of design or development? If that is overstating the case, it’s not by much.

What is “content strategy”, you ask?

In this excellent article published recently on one of our favorite websites, A List Apart, Kristina Halverson writes eloquently on “the Discipline of Content Strategy”:

Content strategy plans for the creation, publication, and governance of useful, usable content.

Necessarily, the content strategist must work to define not only which content will be published, but why we’re publishing it in the first place.

Otherwise, content strategy isn’t strategy at all: it’s just a glorified production line for content nobody really needs or wants. (See: your company’s CMS.)

Content strategy is also—surprise—a key deliverable for which the content strategist is responsible. Its development is necessarily preceded by a detailed audit and analysis of existing content—a critically important process that’s often glossed over or even skipped by project teams.

At its best, a content strategy defines:

• key themes and messages,
• recommended topics,
• content purpose (i.e., how content will bridge the space between audience needs and business requirements),
• content gap analysis,
• metadata frameworks and related content attributes,
• search engine optimization (SEO), and
• implications of strategic recommendations on content creation, publication, and governance.

There’s a lot more to digest in this very enlightening article, plus many others on the subject of writing for the web you should really check out.  We can’t recommend A List Apart enough if you really want to know what goes into building a better website.