Write.as Development @writeas_dev@abunchtell.com

Ok, adding in the Ace editor for editing CSS and JS.

Okay, not quite tonight. It's late and I need to be up early for an all-day event tomorrow. Looking at a Friday launch for this.

Looks like I'll have all the @snap_as updates ready to go tonight!

Working on revamping our user guides (https://guides.write.as) to be better organized and available directly on our main site.

Have heard about discovery issues, and even I usually have trouble navigating it.

I'm building @snap_as on Google App Engine and was using their NoSQL datastore (because cheaper), but refactored everything today to use MySQL.

Going with something I'm comfortable in is going to mean a more stable, reliable product and less of my own sanity lost.

Yeah, launching a new product that people will rely on from day one and will change a lot in the near future is not the time to try out schema-less databases.

You might've seen a 500 error when updating post metadata in the past day or so -- that's fixed now.

Also a #policy on monetizing your blogs, as it's another question we've received.

Preparing our official #policy on removing content from #writeas, to be published on the site.

A bunch of refactoring necessary to get JS working, but this will make permissions consistent and less error-prone for the future.

#fixed -- put something in place to prevent this on the backend. Will look into what might've caused it on the frontend soon.

Looking into multiple cross-posts. For some reason, cross-post destinations are being added to the `crosspost` form value multiple times.

You can now add custom JS, but it'll only be visible to you. Fixing.

Today: finishing support for custom Javascript on blogs. Will only be available to Pro users using a writeas.com subdomain or custom domain.

Okay, settled on a use for an account here -- updates about development progress.

This will be part me (@matt) rambling to work through problems, part educational background into the things I'm doing with @write_as.