[huem0n]

Do you think you'll ever break out the doc-editor into a standalone web component? Ex: Imagine if VS Code reworked its settings.json and used this as a UI instead. Is that within the scope of the project, or is this supposed to only be a monolith app?

[fdb75017]

By standalone web component do you mean like a React component that you can embed in your own app ? Or something more "bundled" like a VS Code extension ?

In terms of scope, you are thinking of both the "Editor" and the "Schema builder" ?

My initial intention was more to build a monolith app, like a simple version of MS Office for jsons. There are already some strong links between the notions of workspace and document: for example the Link field captures an id of another document or record that you have in your workspace, same for File and Image fields... (I guess a next step in the future would be to incorporate the notions of users & groups...). That could probably be abstracted by having something more plugin-based where you provide to the component your description for "what is another document" or "what is a file".

But I think I got your point as well that, if it is deemed to be a framework, it would be useful to let other platforms or verticalized apps use the same representation !