Feature
Post

Category
Homepage News

More Upgrades

Just letting everyone know of some upcoming upgrades that will take place this weekend. As you may or may not know, since the launch of V.3 we have yet to get an updated Authors page up. This will be taken care of this weekend.

I’ll also be working on an improved upper portion of the homepage design. I feel having latest news and a featured box which has yet to feature anything has really been dead space. The upper portion of the homepage will be replaced with a much better way to showcases monthly site happenings, features, and top articles.

Exciting changes.
Stay in the loop.
- Team Devlounge

Feature
Post

Category
Jobs

Molehill: Rich Text Editor for App

Molehill, creators of Tick, are looking for someone to build a rich text editor for a future web application. Details are below:

Molehill requires a rich text editor to be embedded in a Ruby on Rails application. Users will use the editor to format content and upon submission, HTML will be posted back to the web application. Molehill will provide all of the XHTML/CSS design as well as the Rails application programming and requires only the development of the editor.

You should know that we are looking for EXPERIENCE with Javascript primarily and especially with existing RTE editors (sample list: http://www.geniisoft.com/showcase.nsf/WebEditors). If you do not have experience with existing editors, it may be worth your time to evaluate before proposing building one from scratch. We are not opposed to building one from scratch but only if the appropriate research has been done. Please include anything you can to help us evaluate your ability to accomplish this project.

Contact Shaun at shaun@shaunandrews.com if you are interested in this position.

Feature
Post

Category
Code

Custom Reading Width Beta

Custom Reading Width Beta is specifically geared towards those that have liquid, or full-width layouts. Jakob Nielson already tells us to use a liquid layout, but users at higher resolutions suffer when it comes to reading text on screen. Custom Reading Width, when implemented on a site, allows a user to select the desired reading width.

To decide if Custom Reading Width is for you, I’ve set up a test page to give a small demonstration of Custom Reading Width’s capabilities.

If you are sold after seeing the test page (or just want to know more), read on. The rest of this article will focus on customizing Custom Reading Width for your site.

The Source File

The first thing you want to do is download the source file, which includes the test example.

The files you might want to edit in order to customize the script are as follows:

  • resize.php
  • test.php
  • javascripts/readingwidth.js
  • css/lightbox.css
  • css/readingWidth.css

You’ll notice just by looking at the source JavaScript files that I’ve used scriptaculous. One of the downsides of scriptaculous is the large download required. A solution is to compress the JavaScripts, but that is outside the scope of this article. Furthermore, Dustin Diaz says to avoid JavaScript libraries, but the slider control for scriptaculous was just too tempting to resist.

How the Script Works

The script resizes a specified container (in the test case, the BODY container is used) according to a user’s preference. The first thing the script does is display a link to a user. The user can then click on the link to bring up the resize dialog. The resize dialog uses a customized version of Lightbox called Lightbox Gone Wild.

See the script in action. Demo it now

The link that is displayed to the user is only displayed after the page has finished loading. The technique used to show the link after the page is finished loading uses the fantastic addLoadEvent function by Peter-Paul Koch.

After a user has selected a desired reading-width, the script sets a persistent cookie with the selected reading-width. Upon visiting the page again, the cookie is read via php and the container is styled appropriately. If the user wants to revert back to the default width, the user can bring up the reading-width dialog again and set the reading-width to default.

Customizing test.php

One of the first areas you can customize the script is when reading in the persistent cookie.

<?php
	if (isset($_COOKIE["ReadingWidth"])) {
	print($ReadingArray[0]);
	$ReadingArray = explode(",", $_COOKIE["ReadingWidth"]);
	$ReadingWidth = "";
	if (count($ReadingArray) === 3 ) { $ReadingWidth = $ReadingArray[0];}
	if (preg_match("/^\d\d*(px|%)$/", $ReadingWidth)) {
	?>
<style type="text/css">#reading-width-container { width: <?php echo $ReadingWidth ?>;}</style>
	<?php
	}
}
?>

Notice that a style is being set for the ID of #reading-width-container. Also notice that the BODY tag has the same ID. You don’t have to apply the reading-width-container ID to the BODY tag. You can apply the ID to whichever container you ultimately want the user to resize.

You can also customize the way the style is applied. If you’d rather have an inline style, you can easily customize the script to apply an inline style to the container of your choice.

One other area in test.php that you can customize is the display link.

<a id="reading-width-resize" style="display: none" href="resize.php" class="lbOn">Resize Window</a>

I recommend keeping the ID for the display link, but you can change the text link to an image link if you prefer. One thing to make sure of is that the link to the reading-width dialog is relative. An absolute file path does not work in some situations (such as when a user types in devlounge.net instead of www.devlounge.net).

Customizing resize.php

You can customize the default behavior of the reading-width dialog as well.

$SliderValue = 1; //Can be from 0 - 1 (i.e., 0.03)
$IsFixedSelected = "true"; //Can be "true" or "false"

The SliderValue can be set from 0 – 1. The SliderValue is what value the slider will be set to initially when the user opens the reading-width dialog.

IsFixedSelected determines the default selection for the radio buttons. Having a “true” setting ensures that the Fixed radio button is selected, and having a “false” setting ensures that the Fluid radio button is selected.

Another area that can be customized is when instantiating the reading-width object.

var readingControl = new ReadingWidth("reading-width-container", "auto", <?php echo $IsFixedSelected ?>,15, 100, true);

When instantiating the object, the object is passed the container ID, the default width behavior, which radio button is selected, the min-width, the max-width, and whether the min and max-widths are percentages or not.

The default width behavior can be any CSS value regarding width (e.g., “auto”, “1024px”, “100%”).

The min and max-widths can be ignored if you enter 0 for both values. One thing to make sure of is that you specify whether the min and max widths are percentages or pixels. You specify this by entering true if they are percentages, and false if they are not percentages.

One other area you may want to customize is the slider control. You may need to calibrate the slider control based upon the max and min-width values.

var slider = new Control.Slider('handle1','track1',{ range:$R(0.15,1), values:
[.15,.20,.25,.30,.35,.40,.45,.50,.55,.60,.65,.70,.75,
.80,.85,.90,.95,1],

Notice I’ve calibrated the slider control to go from 15% to 100%. The calibration can easily be changed by changing the range and the values.

Customizing readingwidth.js

//Make the overlay (Lightbox) static to fix a bug in IE when using the BODY tag as a container - Comment the next two lines if you don't use the BODY tag as a container
		var overlay = document.getElementById("overlay");
		if (overlay != null) { overlay.style.width = this.GetBrowserWidth() };	

If you do not use the BODY tag as the reading-width container, find the lines in the JS file (should be lines 45 and 46) and comment them out. Internet Explorer tends to resize the Lightbox overlay when the BODY container is resized. The above code makes the overlay a fixed-width.

Customizing the Styles

Obviously you can go into the stylesheets and change the appearance of the reading-width dialog. You’ll find all of the reading-width dialog styles in the file readingWidth.css file. You’ll find all of the Lightbox Gone Wild styles in the lightbox.css file.

Some Other Things…

I’ve modified the code a little in the lightbox.js file. This was to fix a bug in IE where the reading-width script would think the browser was wider than it actually was because the scrollbars were disabled. The commented out lines should be in lines 88-90.

Bugs

As of right now, there are no known bugs in the script. The script has been tested successfully on IE 6, IE 7, FF 1.5, FF 2, and Opera 9. If any of you have some of the lesser-used browsers such as Safari or Konquerer and could provide feedback, it would be much appreciated.

Now I’m not saying there aren’t any bugs in the script. However, all the bugs that have been found have been fixed or have been provided a solution to minimize their impact. The reason the script is being released as a beta is to solicit feedback and find any remaining bugs.

The Future

Please keep coming back to this page for updates on the script (including added features and/or bug fixes). I plan on writing a similar script that doesn’t use prototype or scriptaculous. Stay tuned.

Download Now

Give the Custom Reading Width test a try yourself. Download the version 1 Beta now.

Feedback is Needed

This script isn’t perfect, which is why it was released as a beta. Your feedback is desperately needed for the success of this script.

Support this project. Please give us a digg along with leaving your important feedback.

This script has the potential to change how users read on the web. If you like what this script is trying to do, perhaps you can give it a digg.

Additional Reading: For more information on the inspiration behind the CRW Script, have a look at the Inspiration Behind it post.

Feature
Post

Category
Design

Inspiration Behind “Custom Reading Width Beta”

Custom Reading Width Beta” allows users of a particular website to adjust a reading container in order to suit their preferences. In essence, the user can choose the “reading width” of the layout, and also choose whether the behavior of the website is fixed or fluid.

My inspiration behind writing the script Custom Reading Width Beta comes chiefly from Jakob Nielson and Paul Boag.

“Use a liquid layout”

Use a liquid layout that stretches to the current user’s window size (that is, avoid frozen layouts that are always the same size).
Jakob Nielson

The words Nielson used regarding using a “liquid layout” echoed inside my head for a few weeks. I kept thinking of how inflexible my existing layout (at my personal blog) was, and how horrid my layout would look at extremely high resolutions. For me, there was no compromise. I could indeed specify a max-width and a min-width using CSS, but that wouldn’t be liquid according to Nielson’s definition.

But there has to be some compromise, right?
Enter Paul Boag, who just recently re-designed his blog for managing and building websites. He used to have a fixed design, but now his layout stretches to fill the screen. After launching his forum, there was some debate over his use of a “liquid” layout.

I hate full width designs – I have a widescreen laptop.

One of the users explained that he had a widescreen laptop and hated full width designs. Another user responded saying that’s why browsers can be resized. In fact, that is also Jakob Nielson’s position. He states that at resolutions above 1600×1200, users rarely have their web browser at a maximized width.

Now I wouldn’t be so bold to disagree with Jakob Nielson or even a user of a web forum. However, I am inclined to let the user decide. The same user that expressed grievances over having a widescreen laptop also pointed out that he didn’t want to have to resize the web browser each time he visited a site.

The combination of Jakob Nielson’s comments, Paul Boag’s re-design, and the forum user, inspired me to write “Custom Reading Width Beta.”

Let the User Decide

With the “Custom Reading Width”, the user can choose how wide a reading container is. The user can also choose whether that layout is fixed or fluid. If a user doesn’t like how “wide” a layout is, then the user can easily change it.

The whole point of this tool is to take the control out of the designer’s hand and place it in the users’. The designer can still specify a max and min-width, but the users have the ultimate say as to what width they are comfortable reading at.

The beauty of this tool is that if enough people use it on their sites, then people won’t have to resize a browser window for each site. The user will have their settings saved via persistent cookie for each particular site that uses the tool. There is no need to have to “tweak” the web browser to fit a liquid layout.

Conclusion

Custom Reading Width Beta” was designed to benefit the users of “wide” or “liquid” layouts. I believe in empowering the end users of a website, and if the user wants to read at a specified width, then so be it.

Feature
Post

Category
Strategy

No More “No Replies”

I’ll admit, I have a problem.

It’s not drugs, it’s not alcohol (maybe it is, but ahem, back to the article) – it’s comments. Comments, community response – whatever you want to call it – seems to be on the low here no matter what I do.

Is it the content? Is it the fact that we struggle to get that “first comment” that can so many times lead to many more comments? I sit here dumbfounded by the entire commenting process, a process that apparently, not many of you (the readers), participate in around here.

Without comments, articles are bland

So I sat down to write this article on ways to bring comments to your blog, when I realized I myself needed to find a solution to this. So I decide, enough’s enough – and I started playing music in Winamp and put the article on draft.

What’s the big deal anyways?

As an author, you always want to hear from the audience and get their response to what you’re saying. Did it make any sense to them at all? Was the piece helpful, or just a waste of five minutes of reading? Comments help authors determine what they’re doing wrong, how they can correct things, and how they can improve their writing style to better the connection to their audience.

Like artists (musicians) without a crowd listening to what the artist is producing, there would be little reason to be playing. Imagine drumming your heart out on stage, only to see a motionless audience watching you, without even the slightest body motion. Did you skip a beat? Do you just overall suck? What could possibly be wrong?

The truth is, response is almost as critical the actual piece itself. An blog author without comments is like a dog without a bone – pissed off and laying down in the corner.

Writing Style Matters

Every person is different, and everyone does things a little differently. One thing that seems to determine comments is the authors individual writing style. How they convey themselves on what they’re talking about in each article has a lot of effect on the readers. If the author seems confused what they’re telling the reader to do, the reader will immediately dismiss the article and move on.

To convey readers you have to keep them enticed. The easiest way to do this is to know your audience inside and out, and connect with them on a personal level. I’m not saying if your audience is male dominated that you should use lingerie photos in the middle of posts to keep visitors interested, (although it would probably work), but use the appropriate grammar and spelling based on what most of your readers will understand. For example, if I say XHTML, 85% of our visitors know what it is. But if you were running a sports related website and you decided to drop in “I’m having some difficulties getting the XHTML to validate” to a news post, 90% of your visitors will be saying “What the [explicit] are they talking about!” Put yourself on the same level as your visitors, and talk to them like they’re your friends.

Leave in some openness

Some people tend to forget how open-endedness can really help a posts response. Add in questions that get visitors to think and form logical responses. If you’re dealing with a controversial topic or one that has multiple solutions, once some visitors start voicing their opinions, others will get involved with their own responses. This can lead to a heavy build up of comments, and an ongoing discussion between site visitors, which is always a good thing.

Join In

No matter how many comments an article may have, either a lot or a little, make sure you’re getting involved in the response as well. A lot of times people will ask me questions about “how to do this” or “is this possible” in relation to my multi-article WordPress customization guides. I try to help as much as I can, and point them in the right direction when I can’t give full blown out instructions. Just like you like to hear from visitors, visitors like to hear from authors so they know their comments aren’t falling on deaf ears. This also helps spark some of that back and forth commenting I talked about above.

With response, you can better your writing

You Comment Mine, I’ll Comment Yours

I heard that commenting on others peoples blogs will also help you turn in the comments yourself. I haven’t had much success with this, as I’ve commented on many other peoples blogs but have not received the same response back. It usually take a link to show up in Mint to here something from a fellow site. If you’re going to go with the “1-for-1 exchange”, make sure the comment you left on another site was deeply formulated and well thought out, as it will increase the chances of that author returning the favor to your own articles. Posting a simple “Nice post” generally doesn’t yield many results.

Design Matters

Site design also plays a big part in harvesting comments. If a design is poorly put together, you can expect visitors to not waste much time trying to figure out how or where to go to leave a comment. Make it easier for them by inserting skip to comment links at the top of articles (now added here), and dedicating a clear place for responses either at the top, bottom, or sides of posts. Don’t make readers leave the page unless they really have to (IE, discussing in a forum thread). Make sure if you were a visitor to your site, you would understand how commenting works, because if it’s hard for you to grasp the concept, imagine the difficulty it could cause first time visitors.

Articles + Response = Happy You

In the end if you’re successful with getting visitors to respond to your posts, you’ll feel much better about hitting that publish button, and you’ll probably find yourself doing it a lot more. Make a personal connection with your visitors, and give them something to talk about. Hopefully I’ll see myself having to hear from you in response to this article, otherwise I might have to head back into a corner with a dog somewhere. We’ll see -

Feature
Post

Category
Friday Focus

Friday Focus #5

Friday Focus - Reboot Special Edition

This weeks Friday Focus is a special edition dedicated to the November 1st Reboot that occurred a few days ago. Our weekly “Sites of the Week” has turned Reboot flavored, and I’ll also be going over some “trends” I noticed with this years November reboot.

Sites of the Week

FF - Subcircle

As always I’m a sucker for simple and clean designs, especially with work portfolios because it presents a clear and distinct message. That’s what I felt I was getting with Subcircle in their November reboot.

FF - Inspiration King

The clean Inspiration King layout previously featuring the use of tans and whites has also been updated to a two color palette of white and black. I actually prefer the previous look better.

FF - 49st

While I was at IK I noticed this gallery entry called 49st. While I don’t think it was rebooted – it’s just a new site – I couldn’t help falling for the color scheme and boxy look.

FF - Kineda

Known for following the November and May Reboot patterns, Kineda was updated with the use of a really nice looking subtle background image along with some other touches. Looks like a shiny after party site for celebs.

Digg Weekly

Design: The 35 Sexiest Designed Websites You’ve Forgotten
Fellow 9ruler Phil Renaud reviews 35 designs you may have forgotten about that he considers to show some all time sexiness. This is part three of an article series he has been running.

Programming: API Search (Fast AJAX Resource)
An amazing resource that allows you to search for functions, styles, classes, tags, and more in php, ajax, ruby, and many other programming languages. The ajax search is extremely fast – a real time saver!

November Reboot: Response

The November reboot (both cssreboot and standards reboot) has come an gone, allowing us the chance to sit back and talk about the results. I myself found this November’s reboot to be very unexciting. Upon viewing the galleries of both reboots, nothing really jumped out at me as really groundbreaking designs.

It also seemed like many rebooted designs were enclosed with the latest design trends, and they aimed to match what’s considered a “web 2.0 look” far too much. For example, I saw many designs containing that “layer look”, where the top is lighter or darker than the bottom of the page, looking as though another page is stacked on top. I also ran into some designs that looked nothing more than blog templates that were slightly modified here and there.

There could have been many factors contributing to the lack of anything truly “innovative” this November, one possibly being how late the Reboot seemed to form this year. CSSreboot was on hiatus for a while, and I think by the time it reorganized, it was a bit too late. When word did come out that CSSreboot was taking on submissions, some people probably rushed out an “updated” design, even if it wasn’t very updated at all just to get an extra traffic boost. On the other side of things, Standards reboot was pretty successful for it’s first year, but it’s disappointing to see many designs in the gallery that didn’t even bother to validate their xhtml before submitting.

Hopefully things will come around in time for the spring reboot.

Feature
Post

Category
Homepage News

Chat with Us

Tonight begins the first of what we hope will turn into a very successful weekly series of live chats. Each week as part of our newly launched podcast section, we will hold an hour long chat discussing a range of different design and development related topics. The results will then be put into a sleek audio format, for your listening pleasure. Live chat sessions begin every Wednesday night, starting at 7PM EST. It may be rather slow tonight as it is our first night and we have to spread the word first, but we hope to expand on this if the participants grow each week.

On another note, one of our very talented authors is in the process of releasing a beta of a script we think you’ll find very useful. I don’t want to let the cat out of the bag early, so be watching for it soon! Once it launches, we’ll really appreciate your feedback.

To allow people more time to learn about our upcoming weekly chats, this weeks will be moved to Thursday (tomorrow) at 7PM. Following this week we will revert to our regular schedule of Wednesday nights.

Feature
Post

Category
Podcasts

Want to soup your site?

Thinking about souping up your site? Give this a listen, and hear a few good facts to think about before jumping into to the web 2.0 madness.

Feature
Post

Category
Podcasts

Ultimate BBpress Guide

Our popular bbpress guide is now in audio format! Perfect for those who want to install and customize without reading, or who want to follow along without switching between browser windows or tabs.

Feature
Post

Category
General

Evolution on Audio

Our evolution of design article now in audio format for your listening pleasure.