What do you want from Datasette 1.0?

[simonw]

Datasette 1.0 will be the first "stable" release of Datasette: plugins written for 1.0 should keep working until 2.0 (and 2.0 may never happen if I can avoid making a backwards-compatibility breaking change - ideally I'd love to get to Datasette 1.344 and just keep on shipping new features).

Datasette is pretty stable already: I'm trying not to break backwards compatibility if I can avoid it, but 1.0 will still be a big milestone.

I have a 1.0 milestone - but the things that I think are most important are:

• Stable plugin hooks. The documented hooks should not change their behaviour (though more hooks can be added). I think I'm there already.
• I'm going to rename metadata.json - it's mostly about plugin settings now, with actual metadata (title, license etc{ being a small part of this. If I rename it to config.json I'll have to reconsider the name of the existing --config option, documented here. This is mostly a cosmetic change.
• I want to change the default JSON output. https://latest.datasette.io/fixtures/roadside_attractions.json isn't particularly useful and exposes a bunch of internal details I may want to change. https://latest.datasette.io/fixtures/roadside_attractions.json?_shape=array is what I use in most of my own projects - maybe that should be the default, but it doesn't include pagination information which feels important.
• Something I'm still uncertain about: the stability of the HTML templates and Datasette CSS. I don't think it's feasible to promise that custom CSS themes for Datasette won't be broken in future dot-releases as the visible features and HTML change. I'd like to at least provide a stable, documented list of template variables to templates - new variables may be added, but custom templates written against the stable documented variables should continue to work.

Are there any backwards-incompatible changes you'd like to see land before 1.0? Anything else I should be adding to this list?