Doug Bell

Okay. The `read_schema` parser might be getting confused with the `VIEW`. It's not exactly robust code :). It looks like the read schema parser would have to detect the view...

Not presently, no. I do want to make the editor a more-idiomatic single-page application, and making each UI state its own routable endpoint is part of that. VueJS has the...

That's great! The key to the feature is going to be making the item form Vue component do the reading and writing of items (fetching the item when the form...

I mostly concur, though I was thinking instead of `die` when we see something without a valid JSON schema, we read the collection names and configure them as just `type...

Not at the moment, no. I'd certainly accept that as an addition, but for right now I use the migrations feature of whatever Mojo-based database driver I'm using (Mojo::mysql::Migrations Mojo::SQLite::Migrations...

Yeah, because of that auth problem, we might have to hold off on this until the editor is less-integrated and more standalone. Then the auth plugins will have to adapt....

Sorry, done, yes. And as expected this now conflicts, which is fine.

I'm cool with having the ability to have multiple Mojolicious::Plugin::Yancy, and `namespace` config would be a good way to do that, but that's not needed for this. Remember, the editor...

The more I think about this, the more I want it to be a Document subclass. In theory, it could have other prereqs even, for example to enable auto-filling metadata...

This is a guide to more microformats and other federated content for independents: https://indiewebify.me