Day 62 of #100DaysOfCode:

Picked up where we left off on building a block with carousel or slider functionality and started adding controls in the block panel.

#buildinpublic

Day 62 of #100DaysOfCode:

Picked up where we left off on building a block with carousel or slider functionality and started adding control in the block panel.

#buildinpublic

Day 61 of #100DaysOfCode:

We created a block pattern with carousel functionality and considered different ways we could support it with the necessary JS dependencies if we kept it as a pattern within WordPress.

#buildinpublic

Day 60 of #100DaysOfCode:

We focused on creating an entire page of designs, the sections of which we could reproduce elsewhere as block patterns in WordPress.

#buildinpublic

Day 59 of #100DaysOfCode:

While continuing to try turning patterns into blocks, it became clear that some smaller parts of patterns are “block” material, but overall designs might be best left as patterns. We created three block pattern designs.

#buildinpublic

Day 58 of #100DaysOfCode:

We attempted to convert our more elaborate block pattern design into a selectable block, using a plugin that we set up to create blocks. The going was rough, to say the least.

#buildinpublic

Day 57 of #100DaysOfCode:

Yesterday we started creating a complex design that could be used within our builder tool, but not sure if it will be a block pattern or a selectable block within the theme.

#buildinpublic

Day 56 of #100DaysOfCode:

We experimented with ways to restyle patterns with CSS custom properties. We created a new palette in the WP 2023 theme and got a glimpse at how we could incorporate this concept in our builder tool.

#buildinpublic

Day 55 of #100DaysOfCode (late):

Today we finished integrating our builder tools into the WP 2023 theme. 👍

#buildinpublic

Day 54 of #100DaysOfCode (late):

Again, this was yesterday: We built a new block pattern and submitted it to the WP patterns directory, then dropped our pattern into the WP 2023 theme. Then we began integrating our builder tools into the WP 2023 theme.

#buildinpublic

Day 53 of #100DaysOfCode:

Today we took a new pattern from the WP patterns directory, integrated it with our theme and ran dynamic content through it. More progress. 🙂

#buildinpublic

Day 52 of #100DaysOfCode (late post):

This was yesterday: We found a way to pull dynamic data through a block pattern on WordPress, which makes these patterns a very attractive option for our builder tool.

#buildinpublic

Day 51 of #100DaysOfCode:

Today we created multiple Gutenberg blocks in a new custom plugin, thinking about how we could store groups of designs on a single WordPress install.

#buildinpublic

Day 50 of #100DaysOfCode:

Successfully set up and activated a custom Gutenberg block plug-in in WordPress.

#buildinpublic

Day 49 of #100DaysOfCode (late post):

Finished setting up a new WordPress environment on my machine.

#buildinpublic

Day 48 of #100DaysOfCode:

Started setting up a new dev environment for WordPress on my machine today.

#buildinpublic

Day 47 of #100DaysOfCode:

I'm back! Got derailed by a combo of sick kids, work getting busier, kids' fall schedule starting up, etc., but excited to be back.

Today was a feeble start, but planned out when I will be able to do this work and browsed some designs.

#buildinpublic

Day 46 of #100DaysOfCode (late post):

On Wednesday we scrapped the subdomain migration and copied our site to a clean WordPress install. We created some test iframes using designs from the WordPress Block Pattern Directory: wordpress.org/patterns/

#buildinpublic

Day 45 of #100DaysOfCode (late post):

On Tuesday we copied our site from a WordPress install running on Elementor to a subdomain of a multisite install where we used block patterns instead of Elementor sections for our iframes.

#buildinpublic

Day 44 of #100DaysOfCode (late post):

On Monday I explored how block patterns in WordPress might be able to be used in our project.

#buildinpublic