Evan Winslow

The main difference is that I don't want the server to take responsibility for specifying the presentation, which drupal's api seems to encourage heavily.

And also that this is focused on just getting something functional, not necessarily beautiful. If people want something pretty they should just be able to override the form entirely and...

Basically, yes -- in order to make them interactive, instant feedback, deep JS integration, and do this maintainably, we are going to have to move away from PHP-generated forms. That...

So I guess how the forms are rendered is not actually the important consideration here. I'd prefer we just do this in an agnostic way so that any language or...

I added further clarification on this above, but I'll just add that ideally you'd be able to take a JSON version of these schemas and generate a native Android form...

So... I was thinking again about this but less from the "get going with custom content types" perspective and more from the core-developer-and-maintainer perspective: - wow, we have a TON...

Oh, and going back to the developer experience, you can imagine maybe wanting the experience to be highly iterative. For example, I start a bookworm community with: ``` return [...

More directly relevant to us: the plugins repository: ``` php return [ 'object:plugin_project' => [ 'slug' => 'plugins', 'container' => ['type' => 'user'], // Uses the "container_guid" property transparently 'fields'...

And of course, lest I forget, the translation string _keys_ would be automatically generated based on this metadata. Authors would have to fill in the values for the ones they...

Here is an example of what the language file might look like for the "object:blog" type: ``` php return [ 'types:object:blog:fields:title:label' => 'Title', 'types:object:blog:fields:title:description' => 'Information-rich titles help attract potential...