I threw together an offline importer for this: rWFM / https://github.com/writeas/wf-migrate -- for reference in building this into the web application.

This could be reopened as a feature request.

Will do.

I'd say the default behavior should be #1, to generate a unique slug for the imported collection.

Commenting here since this affects all the child tasks:

Here's a library I built to start this rolling: https://github.com/writeas/zip-import

I also put up #30 CLI which returns the errors during delete to the user. Then this can close.

Assuming the #117 fix works in your testing, after reviewing everything I do think this is the right solution.

Just to mention, here's some prior art on publishing text files via the API: https://github.com/writeas/writeas-api/tree/master/examples/go-text-importer

This might be good to do in the near future -- certainly before v1.0 -- because of how much easier it'd make the setup process.

Thanks, this all makes sense.

I'll necrobump this and point out that I think @gytisrepecka is talking about something I'm referencing in T576 (a landing page).

So this is likely a comment that is more meta than the ticket itself, but I think that I'd like the "story" to be something like:

@agd Working on this now. I started off making it so that when a user is unauthenticated, all blogs and posts return a 404 (to not reveal the existence of any blog). But I'm wondering if it'd be better to send a user to the login page, instead, for better convenience. If so, we could still obscure existence of individual blogs by simply sending all routes to the login page when unauthenticated. This could be the same for the API -- all routes would just require authentication.

I'm going to go ahead and finish this up.

Current status:

I think we'd just redirect people to the correct route -- this would allow instance admins to set it to anything they want without modifying the app itself. For example, they could even choose a default blog to land on if they're running a multi-user instance.

So let's say I set default landing page to about. Does it means that when visitor lands, he/she will be redirected to /about, or will stay on / but about page will be rendered there?