Because of the error states that can come back from this, we'll keep collection creation a distinct action, separate from publishing.

On API v1:

This requires too much of an overhaul of all our database calls, and we can live with hand-written SQL if it means backwards compatibility and stability.

Everything is in place; now certain parts of the app simply need to create the login token and deliver it to the user.

We'll need this to also use with the Write.as CLI when a user authenticates and the option to login through the browser is presented (T193).

In T263#3413, @matt wrote:

This should support some kind of "auth" flag that doesn't require user to enter existing password, for cases like forgotten password.

This should support some kind of "auth" flag that doesn't require user to enter existing password, for cases like forgotten password.

Definitely want to launch with this.

Request is DELETE /api/posts/{id} for all owned posts, whether in a collection or not.

What does the request look like? Does it go to /posts and/or /collections/posts? Do we need another endpoint to remove a post from a collection?

?meta=1 is unsupported, as it'll require copying a lot of code just to exclude the content column from the query. If we're reducing bandwidth to the client, we might as well minimize it on the backend as well. Moved that requirement to T176: Support fetching metadata only on posts.