Working on new editorial tools 

This week I set a goal to get my next generation of editorial tools to a level where I could use them for almost everything I do online. Not yet for others to use, this is how I develop stuff. I do more than eat the dog food, think of it this way -- I am the dog.

So, while I have been writing very actively online for the last few days, very little of it has been appearing here at scripting.com. Eventually I'll figure out how to migrate so that it is. Right now the place to go for it all is protoblogger.com. Which is an apt name, because I feel like what I'm doing now is the prototype for what blogging will be like in the future.

Like the first generation, the new stuff mixes linkblogging and writing of longer posts.

The first time I did this stuff, it was easier, all the content flowed to one place, a static server that I ran.

In the second gen life was more complicated, I was running a dynamic server on the back-end (Manila) and using an outliner for the front-end.

Then I went back to static on the back end, which is how Scripting News currently runs. Then I stopped linkblogging here and started on Twitter, which still must be part of my work environment, but I have a lot more to say than fits easily in 140 characters. The challenge has been to create a tool that does both, in the same place, with agility. And empowers the author. And makes it easy to scatter the writing all over god's creation and at the same time create a feeling of "home" for the author.

After Automattic adopted rssCloud I decided to look at using wordpress.com as the back-end, rather with a static server. As I explored WordPress, I realized it could solve a huge amount of the problem for me, and I had no interest in doing yet another dynamic CMS, so I embarked down this path.

I gotta say, now that it's all working, it's very fucking cool.

I have 8 different WordPress blogs and my links flow through Twitter too, all from one window. This gives me so much more power than I had before, and I suspect a lot of other people are dealing with this kind of complexity too, but I am managing it. I love the complexity instead of it being in my way. It took a lot of work, both conceptual and programming to get this right, but I'm there now.

Anyway there's no purpose to this post other than to Narrate My Work and let other developers know that this kind of editorial system is coming, and it has special needs on the back-end. There's no single rendering of the content, since it's scattered all over the place (the lifestyle of our time). But there is a new position for a static server that stores the user's full content flow. It's a low-tech workhorse of a server, but it's super-important.

I have to maintain a server for the unrendered content. That works fine for me, but won't work when I get users. So the back-ends should probably evolve to not just display the rendered HTML but to allow tools to store the source code for the writing along-side. That's how writing tools should be working, imho.