APIs were a bit of a taboo for me up until this point. The guide we were given in between these weeks have been really insightful. It was a little dense with information but I found great use out of it. When I was job searching earlier this year, I would steer clear from positions that asked for an understanding or listed required skills in programming, CSS, PHP, and understanding of APIs. I came to the realization that I have been using APIs for a pretty long time through the use of Twitter’s API, Facebook’s API, and lastly Instagram APIs to pull tweets, Facebook friends, and photos I’ve shared and post them on my personal website and those of my clients. I quickly realized this when it discussed authorization keys and how I’ve struggled in the past in finding them through my accounts by going through the website’s developer section. APIs are not the easiest thing to understand, but well documented sites like the ones listed above do make it easier.

I plan on using APIs for my website by the way of an Instagram or Flickr API to make it easier for my family to generate photo content while she is out in the field. APIs will help facilitate substantial portions of my project website in the form of portfolio items. I’ve made substantial progress on the website locally through the admin menu. I have a pretty good outline for the website and I’m looking to limit the website to about five pages. Home, Services, Testimonials, Portfolio, Contact Us. Should I be able to condense certain pages like Services and Testimonials in a way that makes sense, I will. My current struggle is getting images, colors, and etc. agreed upon by my family and I. My mother specifically enjoys bright colors and so finding colors that will be good for user experience has slowed down progress just a tad. I sometimes encounter these same issues with some clients, primarily ones that don’t have an established brand identity. Once I get over this small hurdle the Twitter and Instagram APIs should help build out the rest of the site rather quickly.

I’m having a fear of commitment issue. I know how I want my blog to look, but I’m having trouble vocalizing it, and even more trouble trying to figure out what theme would be the best launching pad. I’m afraid that if I commit to a theme that I later do not like as much as another one, I’ll be stuck.

I’m very excited to keep working with WordPress. I’ve spent a good amount of time going through the themes and beginning to lay out my plan.

What I’m most excited about having learned are the possibilities in general that a site can do. I need to keep myself narrow-minded, though, and focus on certain things and not all of the foreseeable possibilities.

—–

I just finished the assignment to try and create / install a child theme. Consider myself filled with a million new questions.

Anytime I feel remotely confident about something learned, that confidence lasts less than 24 hours until something reminds me that I know nothing. I feel like Jon Snow:

I’m even finding directions confusing at this point. I tried following the WordPress directions on how to create a child theme, and I’m not even sure I did it properly. I’m also not sure how much stuff I was supposed to change, but I tried fixing a few things that I don’t like on the current theme.

The guest speaker from last week was helpful in terms of showing us what is possible with WordPress, but the material was covered so quickly that at the time I thought I understood, but now that I’ve had a week to sit on it, I’m not so sure I can replicate anything that he did.

When I first tried to host my own WordPress site a few years ago, I didn’t know anything about coding, MAMP, Github, or child themes. Everything was automatic, and I picked out a free theme and did little to edit it. I didn’t love the theme, and I had my own ideas about how it should look and what I wanted it to do. It was, however, simple. There were only a few instructions, nothing extra to download, and it was still free.

Getting out of that automatic mindset has been difficult. When using WordPress, there are shortcuts every step of the way. When setting up my hosting, they offered a one-button install, which I did. It gave my WordPress site its title and immediately let me using the site, but didn’t necessarily make it easier to edit. In trying to edit my website, I found myself back to square one.  In class, we set up a sample webdev final project site, but in making High on Endorphins I had a lot of questions, and not enough answers for the series of questions. What was my database name? My SQL username? Should I enter “localhost” or my BlueHost information, if I was going to be running it through MAMP anyway? Are all of these answers different on my actual WordPress than on my localhost version? A lot of these simple problems were easily answered when we did it together, but now working on my own, Google is providing most of the answers to my questions.

Although Codecademy was a challenge, learning to code is only half of the battle. Simply getting the new code into a working website, using multiple applications and dozens of steps, and figuring out how to make it all run once its written is taking a while to get used to. Once I finally become comfortable with all of these steps, then I’ll really be free to really experiment with the code. For now I’m going to just keep Googling, learning, and practicing.

I am not sure what is going on, but since Andy’s lesson, I have felt overwhelmed. I really do not feel like I can actually stand-up a site. I am missing structured type of class settings that follow a book and/or a lab. It has been so hard for me to follow and make any progress with my development skills because the class and subject matter has been all over the place. Last week, I went into class feeling like I understood what was going on, this week I am feeling lost. It might have been information overload.

It would be great to use class time to work on our sites.  Maybe we can discuss and work on functionality which is common to all our sites during class. This way we can practice and ask questions as we encounter problems. Some of the key functionality that are probably very important to a class filled with Journalists and Public Relationists are: Social Media links, ability to rate and/or leave comments, registration to gather reader information.

As far as the assignment to create a plugin – I have no clue how to create a plugin. The steps discussed in class last week did not register. I also took notes, but they do not seem to be helpful.

I spoke to a friend last week who is going to NoVa about an introduction to web development class she is taking. One month into the course and the class already has their sites up. They are using Google sites which I am guessing are much easier to use than WordPress or it might be that the course is focused on developing the site and not building developers. As I do not aspire to be a developer and want to continue being an entrepreneur, I wish this class really focused on teaching us how to create our sites and not everything development. Covering all the different concepts which have been covered is overwhelming and I do not feel more of a developer than on day one. I cannot wait for this semester to be over.

Changes that I want to make to my site:

Change the title – to Grocery Coach, font color green, add the company modo below the main heading, modify the tabs row either the row fill or the tab colors. For these changes I will be updating the HTML and CSS files. I also want to add social media capability which i am not sure how to add. I would also like to update the layout of the page, I do not care for the menu too much. I rather have a cover page that just contains a picture, the header, and footer. I want to put details on the different tabs.

Attempt to make updates

I tried to make updates to my site and found it to be confusing. I was not able to find root files, it was a lot of code referring to master files, and arrays. I made an update to the footer in order to not break anything and found that the change which I made did not update on my site (sad face).

Tuesday’s class left me exasperated. I felt as if I had gone from floating in the shallow end of the pool with floaties on, to being thrown into the deep end.

The big picture was overwhelming me so I started to look at the smaller pieces one at a time. Since I couldn’t get Cyberduck to work in class, I decided to test it at home. After a number of unsuccessful tries, I reached out to Greg who pointed out that I had spelt my name wrong. Whoops. More tries ensued and still I was unable to connect. Once again, Greg had to point out that I had spelt my name wrong. By stressing about the big picture and rushing through it all, I had sent my brain into a panic and forgotten how to spell my own name. Twice.

This week made me realize that only so much of coding can be taught. At a certain point, I will have to start learning by pushing through the frustration rather than giving in to it. Of course my new rational mindset was quickly challenged when I decided to create a child theme of Twenty Twelve and mess around with it. There were so many different parts to it; I had no idea where to begin! Even though many of the things I tried to do didn’t work, I am eager to continue to familiarize myself with the code and expand my css/php knowledge. In trying to stylize my page, I discovered a neat tool (Image Color Extract) that determines the codes for all the colors found in an image – great for helping me get the exact look I want. I also realized that even though I had all sorts of questions, I knew the right words to search for the answers in the codex – a sure sign of progress!

After a few days of messing around with the code on my own, I’m not as panicked as I was on Tuesday evening. I’ve come to terms with how the learning process will go from here on out and am ready to buckle down. I’m not ready to start swimming without floaties, but I am definitely open to challenging myself by moving into the deep end of the pool. I may also sit down and practice writing my own name a couple times, just to make sure I’m not losing my mind.

After going through what seemed like thousands of free themes, I ended up choosing a WordPress theme that was already featured(go figure). Choosing my theme and getting a visual idea of what my site will look like really made me feel like we just matured from newborn to toddler. I was extremely excited, and then I started going into the files of my theme. In these files were loads of code, some that I understood immediately and others that I have a strong feeling will take me a while to figure out. I am still just as excited to get the ball rolling on this project, but we went from like 30 lines max in Codecademy to, in my case, 573 lines of CSS and that’s just one folder. Looking at all of the files was a little overwhelming and I must say, thank you Greg for NOT making us do this from scratch. I remember asking in the beginning of the semester why in the world other coders would share their codes for free. I look back now and wholeheartedly understand the reasoning. They do it for people like me and I’m extremely grateful these people exist!

What I found most interesting is that I thought I’d have more difficulty understanding the codes but I actually had more problems understanding the comments explaining the codes. Everything has an official/proper name that I’m sure all veteran coders know. For example, in Codecademy when we’d practice, I often found myself commenting like “change box thingy” or “moves grid thing to the left”. That kind of language won’t get me very far in the real world of code and also won’t aid in my understanding of what others are trying to pass along to me.

I meant to ask this in class but when we are in GitHub and preparing to update and sync things, I remember we have to write a note saying what that change does. I’m finding that I may know what something does, but I may not know exactly how to say it. I’m sure the solution to this is just practice, but I probably need to figure that out sooner than later.

To say that my life has changed since learning about child themes would be an understatement. I’m glad that I now know the proper way to edit styles, functions, and PHP code, on the other hand i’m upset that I have not been editing themes correctly since I first learned about WordPress.

My clients have had the misfortune of not updating their themes as they become available because I did not want to lose my styling edits in .css files and edits to html and javascript in .php files. That is one huge mistake I plan on correcting with my Web Dev Project: www.milagrocleaning.com.

I chose a theme titled Big Bang because I really found it to be a great representation of what I was looking for; a responsive and clean theme that will allow me to display the cleaning company in the right light. I think the theme is simple enough that it should allow me to make styling adjustments and edits that I deem necessary. The theme already includes a custom post type for portfolio items. I plan on adding a few custom input boxes on the custom post type portfolio to consistently display information like # of bedrooms, and bathrooms.

After looking through the different .php files in the theme, I am noticing a few discrepancies between what the theme creators have named the .php files as compared to the template hierarchy diagrams Greg has outlined in the readings for this week. It makes it a bit difficult to interpret what is actually in the files but I think I have a good understanding by looking at the code inside the .php files. It’s unbelievable to be in this position after a few short weeks of this web development class. I’m now able to differentiate and narrow down on specific pieces of code and see how I can alter things. I have yet to find redundant code or badly written code in the template .php files, but i’m sure I’ll find a few as no piece of code is perfect.

The inspector tool continues to be my best friend as it allows me to focus on a specific piece of code. I cut the class or id of a < div > or < p > tag and paste it into the child theme style sheet and override whatever the current style is. It almost feels like i’m cheating, which is worrisome because the last time I felt comfortable, JavaScript stepped up to the plate. I’m really proud with the progress I’ve made so far in the class. It couldn’t have come at a better time because my Advil was running low.  I’m positive my classmates feel the same way.

It was great having Andy come in and speak to the class. While I didn’t grasp every single thing he was talking about, I now have a better understanding of the capabilities of WordPress. His discussion about child themes was especially useful for me. I’m happy he listed the 3-4 parent (and very basic) themes he recommends for creating child themes. I initially was thinking about using a very complex theme for my site, but I have now decided to go the more simple route with a theme called magazine basic.

After downloading my new theme, I spent some time looking through the various code and browsing the admin section. Since I’m creating a child theme, I know I definitely will have to create a new directly that includes a style.css file. But what about the other parent theme folders? Do I only drag the ones I want to edit into the child theme directory? I know I want to create a custom post type, which will be done through code, but what file do I create the code in?

I also spent some time trying to understand the differences between the local server and the web server, and how they “talk” to each other – for lack of a better word. I successfully connected to my local server and starting making very minor changes through the Admin section and was able to instantly view the changes on my local site (which was pretty cool!). But I’m having difficulty being able to view the changes on the web (even though I commit/synced files on GitHub and successfully connected to Cyberduck). Is it because I made changes through the Admin and not the code? My new theme is showing up, just not the text changes I made.

Ah.. so many questions still… but finally feel like I’m starting to comprehend what I’m doing.

After a long, frustrating MAMP install, uninstall, reinstall, screw around with numbers and letters, rinse, repeat, MAMP still refused to work on my computer. I started from scratch on my girlfriend’s laptop, and voila! It worked. Now I could finally start playing around with the documents in my chosen theme, Eureka. I wasn’t feeling optimistic after three hours of banging my head against the wall with MAMP, but I’m glad I pushed through. It ended up being a lot simpler than I’d built it up in my head to be.

I was scared to touch the code at first! I did a lot of Command+F-ing for things like “border” and “background” and changing minor things to see if I was working in the right spot. I kept flipping back to the WordPress codex to try and decipher what I was looking at, and it took me a while to successfully make a change and see it reflected on my local host page. But I think the hardest part is over — now that I’m more comfortable with the workflow, I can concentrate on the actual content, look and functionality of the site. And It was cool to see my work show up right away on the page! I think I’ll be comfortable making cosmetic changes to the theme, but less so writing functions in PHP.

I love that the WordPress documents are separated out by their purpose rather than all being shoved into one CSS or PHP file. I think this will make it easy to find and change exactly what I want to, and the WordPress database system makes the PHP files clean enough to understand…kind of. I’m definitely going to keep studying those codex entries.