Blessing Ene Anyebe
Blessing Ene Anyebe
Hi @benjagm, Could you take another look at the outline? It has been updated.
> Thanks Blessing. Is this going to be all in one PR? No, they'll be two separate PRs.
> > they'll be two separate PRs. > > Thanks Blessing. Can you please add the details to the issue? Thank you Ben, I've updated the issue.
Hello @benjagm this issue now has an open PR. https://github.com/json-schema-org/website/pull/819 Decided to have it all in one PR. Thank you.
Hello @gregsdennis, this issue does not re-published nor re-edit the specification. Like @benjagm said "it is only organization". The fix is to organize the look for the already presented information....
Yes, the specification documents are not changing. Thank you @gregsdennis. We will be sharing details about our open docs meeting soon. It'll be nice to join in and get more...
This part of the docs will be updated after work on the rest of the [migration guides](https://github.com/json-schema-org/website/pull/1061) has been completed. Thank you.
> I see you chose to remove the `(legacy)` keyword entries. That's a perfectly fine choice, but if you remove them, it doesn't make sense to keep referencing them in...
> I don't think the migration notes for each release are working out. They still need a lot of work to fix errors and include enough detail to be useful....