Skip to content

Syndicated

Tools that work: OpenOffice as a blog writing tool

Syndicated

This is a version of my earlier post, made to the short-lived "Tools that work" blog.

As my first contribution to the Tools That Work blog, why not present a tool to make the process of writing a blog post easier: t he Sun Weblog Publisher for OpenOffice. I still prefer to write text in a word processor, with the best tools for spell-checking, the simplest ways to add links, and Zotero to manage references to sites and literature.

![29c332a9cb651cb393554ed5d4a36f44_MD5.png](https://toolsthatwork.wordpress.com/wp-content/uploads/2010/04/screenshot-send-to-weblog-2.png)

Uploading a post as draft to a blog

But then the text needs to go into the blog: copy-pasting creates endless battles with an online “WYSIWYG” (What You See Is What You Guess) editor, reformatting lists and headers, or losing carefully crafted sentences through browser hick-ups and poor form handling.

Editing the HTML itself isn’t fun either. OpenOffice produces poor HTML output, “Export as” even worse than “Save as”. An unappealing alternative: coding HTML in a text editor, adding things like by hand. I’ve looked at HTML editors that would let me focus on writing instead of coding. KompoZer (follow-up to Nvu) is nice for producing reasonable HTML, but yet another tool and not really supporting the writing process. And it then still is an effort to get the proper part of the HTML into the blog.

I also tried ScribeFire, which lets you write a blog post and interact with the blog software from within Firefox, but it offers no simple way for simple structural mark-up like a

header. And, no support for references.

The Sun Weblog Publisher extension for OpenOffice seems to change the way I work: it adds a button to publish a document to a blog, using a variety of protocols to support different blog software, like WordPress. And another button lets you download existing posts from that blog, to edit them. The process of pushing a post into the blog has become a lot smoother.

![315a16b228566d9b9c94671a68c57fc5_MD5.png](https://toolsthatwork.wordpress.com/wp-content/uploads/2010/04/screenshot-3.png)

Upload and download posts from a blog

There is still some online processing to do, like adding tags and minor HTML cleanup. And I’m not sure how well it will handle images or complex layouts. But writing a post and pushing it into the blog has become a lot easier!

Edit

Getting in the mood for the NetSquared Mashup Challenge with Oneworld Connect

In my third year coming to NetSquared, I find myself in a new role: as one of 21 designated “project leads” who will be trying to connect the featured projects with the developers ready to work on an NGO project.

I’m working with Roshani Kothari and Michael Litz of the Oneworld Connect project, and together we’ve started a wiki page with what we’d like to work on. I’m posting the story here too: please help us develop this further, shape our thoughts, and connect our ambitions to the endless possibilities 🙂

OneWorld in a nutshell

OneWorld.net is the premiere global hub for groups and individuals who care about international issues—a town hall for today’s interconnected world.

Since 1995, OneWorld has developed a massive site: 500,000+ articles and multi-media in 11 languages. OneWorld has a strong track record of innovation in the digital public space including CMS-driven site (1995), radio(1998), video(2001), and first UN speech by US politician through 2nd Life (2007).

Our challenge in a nutshell

We need to make our work more navigable and user customized, and provide new ways for our users to connect to 2000+ partner orgs and to each other.

  1. Map mashup is a first step in enhancing visualization.
  2. Widget will enable users to submit content via website and cellphones, and
  3. Metadata will enable easy sharing of information.

Technically: the current massive CMS is being de-centralized, to better tailor to the regional needs and context of each of the 12 Oneworld editorial centers in the world. OneWorld US and several others are migrating to Drupal, some to Plone, and a few have tailored proprietary systems.

HELP US WITH…

Here are ideas we want to work on. Help us define them in more detail, or help us Just Build Them.

1. Visualization through maps and timelines

  • Geo-tagging existing content. 500,000 articles in 11 languages, from the days before ubiquitous geo-tagging… now what?
  • Showing the underexposed stories. Can we give extra weight to stories that are not (yet) high on Yahoo and Google News, CNN, and the likes?
  • Highlighting the connections. Stories are connected in time, and to organizations and campaigns. How to show those connections on a map? In a timeline?

2. Widgets for feedback and inputs

  • Let our registered users take their selections with them. To their blogs and their Facebook and MySpace profiles. And allow rating from there (would that be mashing FiveStar and Subscriptions into a Widget Generator module?)
  • Allow replies and feedback from those widgets too! Local content, additional stories or links to blogs, video, images.
  • If that works with a good API, it should be easy to make interfaces available for mobile phones and other platforms too, right?

3. Decentralizing, not disconnecting

We need to keep the Oneworld centers connected, and exchange content with rich metadata information. How to keep distributed content in sync?

  • Synchronization with a centralized repository?
  • RDF Synchronization Connectors between sites? Drupal-to-Drupal, Drupal-to-Plone?

(Accidently, having a nice Drupal-to-Drupal content synchronization tool might help a lot with general testing-staging-live deployment setups too!)

Get in touch if you want to help Oneworld Connect! Leave a comment here, skype rolfkleef, email rolf[at]drostan.org, or add to/edit the wiki page!