Deprecated: Assigning the return value of new by reference is deprecated in /home/edeifyc/public_html/wp-settings.php on line 520

Deprecated: Assigning the return value of new by reference is deprecated in /home/edeifyc/public_html/wp-settings.php on line 535

Deprecated: Assigning the return value of new by reference is deprecated in /home/edeifyc/public_html/wp-settings.php on line 542

Deprecated: Assigning the return value of new by reference is deprecated in /home/edeifyc/public_html/wp-settings.php on line 578

Deprecated: Function set_magic_quotes_runtime() is deprecated in /home/edeifyc/public_html/wp-settings.php on line 18

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /home/edeifyc/public_html/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /home/edeifyc/public_html/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /home/edeifyc/public_html/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /home/edeifyc/public_html/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /home/edeifyc/public_html/wp-includes/classes.php on line 1244

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /home/edeifyc/public_html/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /home/edeifyc/public_html/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /home/edeifyc/public_html/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /home/edeifyc/public_html/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /home/edeifyc/public_html/wp-includes/classes.php on line 1442

Strict Standards: Redefining already defined constructor for class wpdb in /home/edeifyc/public_html/wp-includes/wp-db.php on line 306

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /home/edeifyc/public_html/wp-includes/cache.php on line 431

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /home/edeifyc/public_html/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /home/edeifyc/public_html/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /home/edeifyc/public_html/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /home/edeifyc/public_html/wp-includes/comment-template.php on line 1266

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /home/edeifyc/public_html/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /home/edeifyc/public_html/wp-includes/http.php on line 61
edeify.com » Blog Archive » Rebranding and Redesigns

Rebranding and Redesigns

January 15, 2008 – 11:11 pm

Cattle BrandingThis weekend, at the monthly board meeting of a local Asian-American association I serve on, we decided to finalize our integration with a similar, larger national organization.

Besides the standard adoption of their bylaws and other miscellaneous paperwork, we also need to fully convert our rebranding from PAAYPA (Pittsburgh Asian-American Young Professionals Alliance) into NAAAP (National Association of Asian American Professionals) Pittsburgh. So basically switching from one long awkward acronym to another…

As Technical Director, I have to revamp our old site to match the basic guidelines of the national organization (which they seem pretty flexible on except the logo). Since the old site is around five years old now, it’s outdated enough that I’m thinking about just rebuilding it from scratch to fit our group’s needs better.

Like many professional organizations, we tend to be very event focused, spending most of our efforts on organizing, scheduling, and announcing future events or recapping past ones. Because of this, I’m inclined to try a blog-style format, which seems to work well for the Cincinnati chapter. I also serve on another local IGDA board and we’ve had good results using a very simple, events-driven blog format. In fact, I think the IGDA actually sets up Movable Type blogs for most chapters nowadays.

So right now, I’m thinking a simple WordPress blog with calendar and RSVP widgets. This will also let us integrate our group Flickr streams and social network hubs in a more seamless fashion. Plus, by setting up multiple author accounts, event organizers can announce events on the site themselves, rather than having to go through me or wait for the monthly email announcements.

Anyone else have experiences doing rebranding or redesigns for professional organizations? What are your thoughts on the blog format as opposed to the more traditional brochure style some groups still stick to? Feel free to share your success stories (and glorious failures too)!

  1. 2 Responses to “Rebranding and Redesigns”

  2. I find that a blog is a great tool for many websites, as long as you keep in mind the expectations and needs of the people who visit and use the site.

    Make sure the menu is prominent and contains the words people will expect to see: About, Membership, Contact. Make sure the date, time, location, and topic/title of the next meeting are featured prominently and not buried along with other posts on the site.

    Also, make sure someone is assigned to update the site — even if multiple people are able to make updates. If multiple people share responsibility, it’s easy for anyone (or everyone) to assume someone else will do it. The website for my company Fat Plum (www.fatplum.com) suffers from this problem.

    The branding part is easy. It’s the on-going maintenance that’s hard.

    By Cynthia Closkey on Jan 16, 2008

  3. I agree with Cindy above.

    Would NAAAP be interested in using an outside entity to create you blog/web site. That would give you the opportunity to focus more on content development maintenance.

    By Norman Huelsman on Jan 16, 2008

Post a Comment