Most years, before visiting WordCamp London, I write a long bucket list of things I hope to achieve. This year it’s no different, although the main focus is on developing blocks for the new block editor, Gutenberg.
| Status | Unknown | Brief notes |
|---|---|---|
| ongoing | How to test JS code | Let’s see if I can use the same solution as Gutenberg |
| ongoing | How to correctly implement issues with “keys” | Avoid those horrible console Warnings |
| got help from JJJ | How to access options from the REST API | for dynamically populating the attributes in generic shortcode block |
| not started | How to lazy load JS / CSS | rework code to use register_block_type instead of enqueue_block_assets |
| not started | How to lazy load REACT code | same as above? |
| not started | How to perform REST queries | to populate attribute select lists – similar to options? |
| tbc | How to internationalize | Does __() support text-domain yet? |
| done | How to support JS in metaboxes | Hey! Looks like I’m already sorted! |
| tbc | How to control block conversion | Especially inline shortcodes |
| tbc | How and when to implement logic for deprecated blocks | Some time in the future? |
| tbc | How to automatically migrate content? | Can this be done using the PHP PEG parser? |
| investigating autocrlf=false | How to tell lint I’ve got CRLF’s | Or do I change my Git config? |
The list is taken from the Unknowns sheet of my estimate spreadsheet which you can find in the bobbingwide/oik-block plugin.
If you’re going to be at WordCamp London this weekend, and can assist with any of the above, then I’d love to hear from you. I expect to be attempting to contribute on Friday, and I’ll be easy to find on Sat and Sun afternoons since I’m the room monitor and rear mic runner for Track A in the main hall.
This post was brought to you by Gutenberg 2.6.0 and oik-block 0.0.0.alpha-20180409.