PubWriter is a preferred model for both writing and publishing because every time you click save, what you write is both backed up and published simultaneously.
It's an asynchronous publishing.
Having a shareable URL on your own domain allows you to own the authoritative version of your work that can be indexed by Google.
On your own URL. It allows you to have an 'always current' version and avoid having multiple versions of or anything out of date. It's extremely helpful for proposals.
Importantly, since it's on YOUR domain, you own it. If you are using other content providers to publish your content, you are inherently giving up control over how that content is used and ultimately whether or not it's even available!
Is your workspace limiting you?
A large part of my tendency towards PubWriter is the flexibility I have in publishing. Few limitations exists.
PubWriter is different than traditional publishing in that publishing is not permanent. It's a conversation, not a statement. As the writer, you engage the reader. You make it effortless for the reader to engage. Publishing is effortless because when you hit save, what you've written or updates are published within seconds.
Writers write. Readers read. Words are a two-way street. You don't speak without listening, so why should you write without feedback.
The goal of a PubWriter is to gain reader feedback to improve our writing. Before investing hours in a topic, is the topic of interest to anyone besides yourself?
Learn. Do. Teach.
Within my own core set of beliefs is a need to master topics. I found discovered that the surest path to mastery is to learn, do, teach.
I was stuck by the simplicity and speed that utilizing pubwriter as a tool to explain how to do things. It's the ideal tutorial creator.
As words within what you write are linked, giving the reader the ability to zoom in.
As we read something for instruction, depending on our level of knowledge on the topic, we may need to get further explanation on an aspect that another reader may already understand. Slowing down the one who already understands is counter productive.
Comments or suggestions?