Custom Components/Parsers about wink

[themsaid]

Well it isn't aimed for only developers, it's generally for all content creators.

What you showcase here is very interesting indeed, if we can allow custom editor components to be added and configured just like adding an image or custom HTML that would be great.

Might look into this soon :)

[mattrabe]

If the target is all content creators then I agree that maybe this could be added to the editor components. Perhaps allow the user to enter a Key and a Value, where in my example above the Key would be "OGBadge" and the Value would be "{ "src": "https://completecodesolutions.com/" }". Allow for flexibility so that the Value might accept a string or a number or JSON, etc. Or, probably better, somehow "register" a custom editor component using a Controller/Model/Trait/something, and then that results in a custom button next to Image & HTML in the editor. Clicking on it reveals some sort of input, potentially also defined by the Controller/Model/Trait. At that point, we're pretty much talking about creating "plugins," which I don't know if you have put much thought into yet.

By the way, though I don't like Wordpress's naming conventions, the equivalent to the wrapped-JSON-in-post-body in Wordpress is called a "shortcode". There's nothing "short" about it, but it is a code. I think I'll refer to my JSON POC above as a "custom code" moving forward.