Kevin Ansfield

Ok, taking a look at the code it seems we don't have validation steps for "known" providers handled by the `oembed-extractor` library which is why Twitter works. I think we...

FYI the `*Node must/should implement` warnings are from the underlying Lexical framework that our editor is built on. They occur because it contains some basic checks that don't account for...

This is potentially something using the handlebars AST could help with. If we see usage of `{{author.slug}}` we can look up the tree to see if it's in a post/page...

I think it will be important to distinguish between HTML comments and Handlebars comments. The above code has HTML comments so the handlebars code is still being run and has...

If I'm understanding it correctly, this is a fairly general problem of accessing properties which don't exist inside the current context. ```handlebars {{#someObject}} {{someProperty}} {{/someObject}} ``` I wasn't able to...

So I think there are a couple of things here... 1. `{{#prev_post}}{{^next_post}}oops{{/next_post}}{{/prev_post}}` will never render "oops" because the logic is incorrect. If "prev_post" is available for the outer context then...

> You could utilise your controller to achieve this. Have a controller property that generates the endDate's `minDate` based on the selected start date. This is actually what I tried,...

The editor experience is intentionally completely separate to the theme. This is true for all aspects of the editor, from the title to the body content and each card. The...

@yohanderose I'm a bit confused as to what versions etc you're using here. Ghost hasn't had a "beta" editor since 5.68.0 released Oct 6th 2023 in which the old editor...

Is this occurring on every post or just with specific content?