We've just released version 0.1 of WriteFreely, our open source version of Write.as.

Head over to the official blog to read the announcement, and check out the project site.

An evolution into a platform that reaches farther. This is the culmination of what I have imagined for Write.as, the open source platform: enabling disparate writers to publish to a single writer's hub, e.g. read.write.as, to create a reading destination with many different authors, à la Medium.

Goals: Integration with the wider web. Implementation of “social” and other protocols that help writers share their work farther and expand the “tiny island” that is their personal blog.

  • Support for publishing to “writing hubs”
    • Ideally, open-sourcing the backend for the writing hubs
  • Integrations with conventional silos like Twitter and Facebook
  • Support for more publishing mechanisms, e.g. Micropub

Version 1.0 will be stable and production-ready, able to be spread around. It'll heavily incorporate feedback from the alpha stage .

Goals: Stability and ease of use. Uniqueness that makes it an appealing option in the crowded space of blogging platforms. An engaged developer and user community.

  • Easy / automated install and setup
  • Exposed, stable API
  • Compatibility with Write.as mobile apps
  • Incorporate important alpha feedback

Ideally at this point we'll have built up a solid base of interest in the product to start letting the product take on the life of the community. This will be less about us as a central leader at this point if we can help it.

Growth We'll want to leverage other platforms to grow. For example, integrating with web hosts that offer one-click app set up.

We'll release the first version of our self-hosted blog software as an alpha, to get everything out there and start collecting feedback on it as early as possible. This worked well with Write.as, the hosted version.

Goals: Start with the bare-minimum. Add only what we find is truly necessary. Do we really need themes, plugins, comments? We'll put this out into the world and learn the answers, instead of building on conjecture.

  • Manual install and database upgrade
  • Single user configuration
  • Writing / editing done through web client only [based on existing editor]
  • Minimal post management UI [based on existing UI]
  • Raw CSS and Javascript customization [based on existing options]