Divi – for idiots

Divi – for idiots

I am not advertising for Divi or the Divi builder here. I did use Divi to build this website.

Divi isn’t that difficult. Even I can figure it out. There is plenty of information out there on the web on how to use Divi. so I will not go into detail here There are also some spectacular sales out there in Divi land so I purchased a lifetime Divi subscription.

Note: I can’t figure out why this image shows twice. Saving that for another rabbit hole another day.

Divi connects to your WordPress admin panel. My host provider had Divi preinstalled so it was easy to migrate over from the Old Provider we Will Not Name. (ahem, rhymes with clue and ends with Host).

When I started with this website it looked worse than it does now. I am using this website as a learning experience so please be patient as I make changes and edits. Some Divi purists will create a child theme but I have not as I like to live on the wild side.

I created my theme to be generic and in grey tones because blogs can be repetitive. So this is just another repetitive webpage.

I discovered Divi when I was working on a community website as a volunteer. The web developer had used the platform to create a stunning website that makes this website look like a kindergartener made it. I will ask permission and post that site later. I can insert custom CSS if I so choose. I can also create custom pages and post pages that are easier to manipulate than the standard pages in the Gutenberg editor. Which I am actually using Gutenberg to create this post. Ha!

This post was built with Divi!



I was so excited when I discovered Docker!

In theory, I was going to run my documentation setup in this Docker container.  I was going to have it running in a container and I would be so COOL, so NEAT. I am wondering what other delusional thoughts I was thinking at the time.  Not LOL.

This whole thing came about when I was researching an open source documentation solution that I could install and maintain for funsies.  Well that didn’t work out. I got frustrated because I could not seem to do anything meaningful with Docker containers even though Docker desktop said they were running.  I made numerous containers and was able to delete them, start them, stop them in command line.  Yay me!

Maybe I wasn’t supposed to be running the containers on my local machine.  I have no idea.  It was very neat learning about Docker and the seemingly endless possibilities of containers.

I did get Docker running on my old junker Mac and on my Windows machine.  By running I mean I was able to install it, get a container going.  I was even able to install portainer and get an instance of wordpress running.  I was never able to figure out much more than that.  Then it turned into a new year and I found a new thing to play with, and that was this website.

I ran into issues because Docker containers run in a weird file structure.  I could never find the spot on the file directory where I could store my .yaml files to spin up a container.  When I figured out how to spin up a container from a .yaml I could not figure out where to change the admin password.  Aaaargh!  I did learn how to run docker commands through command line.  I was also able to figure out that I just need to give up on Docker and run it in some other way on a different operating system – perhaps on a raspberry pi.

More on that later.  I do think Docker has a lot of potential