Web . Write . WP.
-
Core Confidence v4
I started off using this post to draft the finalisation of my nthversion plugin that I’ve been working on since Core Confidence v2.8. I opened my plugin’s test site in WordPress Studio, and drafted rough notes: I used the Sync feature in Studio to pull my site from Pressable so that I can test the
-
Core Confidence v3.2
Sometimes learning looks like backpedaling. And that’s okay. I revisited an existing project (Letter Artdio) that had stalled, as my test case for Github connection within Codex and how to write natural language for a code update request. The block plugin had initially been built at a time when I was not as clear as
-
Core Confidence v3.1
Today I started by searching the documentation for the Block Editor, so here: I wanted to add style settings, a CSS class name field, and the radio control button (relocated) for selecting major or minor version into the Settings Sidebar. The Block Editor Handbook showed where these controls live; Storybook showed exactly what to import
-
Core Confidence v3.0
I started this week with a working block of my own, which I had already published in the last post, Core Confidence v2.9. While it was functional, I wanted to see what a “full-featured” version might look like if I let Telex, Automattic’s block creation tool, generate one for me. My thinking was that by
-
Core Confidence v2.9
Picking up from where I left off in v2.8, I know I’ll need to adjust edit.js so that it grabs the version number from the last published post. This function then increments that number, and outputs it via the Block. At first I thought I’d need to change the default: 2.8 key-value pair in my
-
Core Confidence v2.8
So working on this course at Full Stack Digital, and after creating my block, using WordPress’ create-block package, I saw that the src folder has a named folder which then contains the src files. I looked into this and realised that the create-block package supports multi-block support and I thought that was so very cool.