These are notes I took about my first podcast interview. I have left them mostly as is, not correcting grammar or spelling, because I think that partially reflects my mood at the time. If you are going to launch a website, it’s likely you need to learn WordPress……
I Didn’t Know What I Was Doing When I Started Using WordPress:
So, I wrote and updated every page and blog post that was on my new site….except I didn’t read the notes my partners gave me first! I set every sub heading to the wrong value. Back into the site, page by page, post by post.
Thankfully I don’t have enough content to go live yet, so it only took me a few hours. In the process I also cleaned up more passive language and other issues (on the pages, I didn’t edit any posts).
I also added two people to test the site, but for some reason WP is designed to take ALL roles/uses to the dashboard. This makes about 0% sense, frankly. Now, there are plugins to fix this, but it is a terrible design. If you want read only types, you never want them to see the dashboard or the ribbon or anything else, other than your content.
On the plus side, the developer I am working with is feeling better and is out of the hospital! That makes me happy, because no one should be sick and in the hospital. We are closing in on the 1 year anniversary of me being laid off. We might might might go live (soft launch) then. I remain hopeful. We just need to clean up today’s happy and write about 20 more posts…..give or take.
Oh, and figure out how to edit podcasts and record more……
Looking back, I’d add this on reflection on that day:
Turns out, one or two days isn’t enough time to learn WordPress! It is clear I didn’t know what I was doing after just a few days.
First, I should have read the documents my development partners gave me. They gave me some good information on how to write and format WordPress posts, things I should probably review again.
Then, every single thing I did and wrote about WordPress security above seems to be wrong……I’ve since learned more about WordPress security, partly from my development partners, and partly through trial and error. Really, trial and error is a great way to learn and to improve a site. I learned that in Agile development training and use, and it’s a lesson I’ll never forget.
Let me know your thoughts, by posting in the comments, or by emailing us at firstname.lastname@example.org.