blogging

A friend just emailed me the following question:

As a Business to Business Company is it better to have your company blog hosted on the company website or should it be more indirect and hosted on wordpress or something like that. 

I am getting conflicting answers from my people and was wondering if you had any advice.

The following is my response back.  Hope this helps you as well.

In answer to your question about whether a B2B company should have their blog hosted on their website or on something external I'd look at the importance of the following:

1. Branding
2. Maintaining the technology
3. Lock-in
4. Reasons to not be on your main company site

Branding

To me, branding is the most important.  If your blog is a key part of your communications strategy then you should have full control over all the elements that show up on the blog:

This is not to say you can't use a service hosted off your current servers.  Just that the logo, design, content, domain, comments system, auto-emails, and even functionality should all reflect your brand.  I recommend the blog be on your company's main domain.  If it must be hosted somewhere else, then a sub domain can work.  The key is that you do not dilute your brand across multiple domains. 

Additionally there should be no third-party content that could show up on your blog without your direct control, such as advertising automatically shown by the blog network you may be hosted on.

Read More »

2009-06-26T17:56:17Z

I wrote this series on how to post to Drupal using Windows Live Writer because I saw a lot of questions and issues about this on the Drupal forums. I had previously gone through the trial and error process to set this up for a number of people who work for me. We now use Live Writer for initial posts and quick updates to a large site we manage.

I'd like other developers and Drupal service providers to see they can provide this option for clients and that Drupal communicates and does well with modern and useful web technologies such as blogging APIs.

Proper Configuration Checks for External Applications to Use Taxonomy Terms

If you want your users to be able to assign terms to their content when they are using an external blogging application, like Windows Live Writer, make sure you have the Taxonomy module enabled, and that you have selected the appropriate content types, those available to the Blog API. I have forgotten to do this a few times when adding a new content type to use with the Blogging API. Each time a new content type is created, taxonomy requires you to go back and specify whether your new content type can use a vocabulary.

Content types section: admin/content/taxonomy/edit/vocabulary/<vocab id>

Getting Good URL Names by Using Pathauto

If you have Drupal’s Path Module enabled to allow users to rename URLs (custom URLs), I recommend using the “Pathauto” module in combination with your external blogging client. You can set it to give the content a URL based on the post title.

http://drupal.org/project/pathauto

Read More »

Read More »

Allowing Tags to be Added in the Post Body Text

Free Tagging when the Blog API Does Not Support It

The following is a quick code sample showing the start of a Drupal module which lets a user add new tags to a post by placing the tags in the body of the post in a format like so:

[tags]blog, blog api, blogging, Drupal 6, weblog, windows live writer, wlw[/tags]

Jump to the Source Code

Use Case

I’m only using code like this for one use case.  It’s for clients who do a lot of editing and posting of their Drupal content through Windows Live Writer.

With Windows Live Writer and Drupal, my clients use the “Movable Type API”.  Without extending the API, it does not yet support adding new vocabulary terms.  Thus, from Windows Live Writer to Drupal sites, one can only tag content with existing terms.  This code allows new tags to be added.

The terms are added to a specified vocabulary id and associated with the new or updated content node.

The inline tags are removed from the body of the text before insert or update.

Steve Pavlina over at Personal Development for Smart People proposes a solution to avoiding the “enormous blob of complexity” when working on large projects.  Many of the regular projects we work on daily have an already well defined path to completion.  Steve proposes breaking those types of projects “down into a lengthy list of ‘microtasks,’ planning it all the way from beginning to end if possible”.  In doing this preplanning upfront, we can move into the project and just flow from microtask to microtask until completion (next action to next action for us GTD users). 

Steve wrote an example list of microtasks involved in writing a new blog article.  You can find his original steps here:  http://www.stevepavlina.com/blog/2007/07/microtasks/

I have modified his list for my own purposes.  Below is Steve’s list with my modifications highlighted in yellow.

Writing a new blog article. 

The steps are in sequential order:

1. Define a primary objective for the article (inform, persuade, entertain, or inspire).
2. Brainstorm topic ideas, or review the list of reader-submitted topic suggestions, starred and shared Google reader items, recent delicious links, article ideas in someday list.
3. Select a topic.
4. Do a quick and dirty, free-form writing session to get ideas down without regard to structure.
5. Decide how to organize the ideas for clarity (chronological, topical, hierarchical, sequential, etc).
6. Sort the output of #4 based on the desired structure.  Define the main sections and subsections.
7. Identify supporting material to include (examples, analogies, quotes, statistics, images, stories, links, Wikipedia, etc), and add it to the outline.
   • Checkhttp://sethgodin.typepad.com/seths_blog/2008/03/where-to-find-g.html
   • http://www.sxc.hu/
8. Refine the outline from #6 and #7 for completeness and balance.
9. Expand each section of the outline into paragraphs (and bullet lists if appropriate).
10. Insert meaningful subheadings into the article.
11. Write the opening.
12. Write the closing.
13. Edit the article for content, clarity, and conciseness.
14. Spell-check the article.
15. Brainstorm possible titles for the article (clear, interesting, keyword-rich).
16. Select a title.
17. Select blog categories for the article.
    • Look at delicious  for examples
    • Look at technorati for examples
18. Decide when to post the article (now or future-post).
19. Publish the article.
    • Post with Live writer or on-line editor.
    • View post on-line.
    • Look for display problems.
    • Verify tags and images are fine.
20. Tag with delicious, digg, and other places.
21. Email and tell people you know who would be interested in the article.
22. After the article has been online for several hours, evaluate reader feedback and fix any reported typos.
23. Make sure I am subscribed to all places this article might receive a comment on.
    • My own blog
    • Digg
    • Delicious
    • Technorati
24. Set date to check back on article in one month for stats.
    • See who’s linking.
    • See where other traffic is coming from.
    • See what search phrases land people on the article.
    • Evaluate opportunities for further promoting.

--modified from http://www.stevepavlina.com/blog/2007/07/microtasks/
--(used by permission)

Steve Pavlina has a number of great articles on his blog Steve Pavlina's Personal Development for Smart People . Another favorite of mine is Freeing Mental RAM at: http://www.stevepavlina.com/blog/2005/08/freeing-mental-ram/ .

Read More »

Read More »

Read More »

Read More »

Read More »