First Reflection

Writing in code is basically learning another language. In order to get a hang of it, you have to practice it on the daily to keep the terms and syntax fresh in your mind. Normally when I’m writing something out, I can imagine what my words and phrases mean. But when you write for code it’s harder to picture in your mind how to code is going to change a web page. It takes lots of mental power, even when presented with the changes that your code made, to process how the code correlates to the changes on the web page. Writing for print can also be similar to writing for the web in many different ways. One must plan ahead to how to they want to design the page or convey their message. For the web it’s based on specific syntax and terms, but for print you have a much larger flexibility to work with.
The writing of code can allow for a web page to be portrayed in different ways depending on the styles used, but it still follows stricter guidelines to allow for other users to also read the code in comparison to the writing of print. I realized that writing code at first is very difficult in terms of remembering to include the opening and closing tags. Oddly enough, I also had to train my fingers to recognize and easily click the opening and closing keys. At first, I found myself never hitting the right keys, but now it’s as easy as capitalizing the first word of sentences and ending them with a period. When writing for the web, I find there’s a much longer process to getting something to the complete draft. In print, there’s usually only several drafts until I produced a finished product. But with coding everyday, my code is its own draft and it requires hundreds of revisions to perfect. Writing for code and print is quite similar in the way that it’s both written in the English language. Overall though, I think my writing in code has progressed in terms of remembering the proper syntax and terms to use when grouping with certain classes or divs.


Second Reflection

I feel that I have progressed in the past two weeks more than any time in the whole class. It was like the moment that everything finally came together. At first the readings from the book confused me because I was always trying to figure out how I’d ever even design a simple website or I would become confused why I needed certain tags or syntaxes. But in this past week and a half, I’ve been redoing my whole resumé page and trying to figure out what I actually wanted it to look like. And for this final midterm project the syntax and terms have lined up and fallen into place much more easily than before. I think my resumé file looks the best when it’s on computer screens. There’s a piece of the code that causes the bulleted circles to not show up when it’s on a screen that’s 767px by 702px or smaller. No matter what I did, I couldn’t figure it out, but I did narrow it down to the code that appears in the top of the CSS file. Code at top of CSS file
I know because I tried to deleting the entire thing and although it fixed my bullet problem, it destroyed the rest of my code’s styling. I also tried a number of different Stack Overflow searches and changing of the above code, but failed. I also have the same problem with getting the background color to cover my bulleted point in table view and smaller. I do think my color palette turned out really well. The color isn’t even black but to me it looks good on the off white background. Everything is a shade of blue. I feel pretty comfortable, but there’s still some gaps in my understanding of certain pieces of the code, but I think they’ll be clarified as we go deeper into learning HTML and CSS. I want to keep working on my resume page even after the midterms because I still have ideas that I just ran out of time trying to figure out.

End of year Reflections

Pt.1

Having a responsive and emotional website is important to me. I think websites with little to no personality are quite boring and a waste of time to even look at. I’ve thought about adding humor to my design, since the very beginning. It was hard to implement the humor because there weren’t many places to add it to. I worked really hard on my contact page. I wanted to excel and go above and beyond and to make it look user-friendly. After designing the front-end of things, which took nine hours, I got stuck for about 16 hours on the back-end or server side of the form.
I never really had any solid sketches of what my site looked like. I never knew what I was going to put onto it or how I wanted it to look. In the beginning I wanted it to be a landing page for my current projects. I had no plan on creating a navbar at all and figured it would just be a place to update my current family and friends on what projects I was creating at the time. But as I went on with it I realized I should add basic pages, such as an about me and/or contact page. I realized that other people would be able to find my website. So by creating an about me or contact page, I could refer those unfamiliar with my site to who I was. Since I already have a domain name that is tied to my name, I never figured out what this website would turn into.
I want to add many additional components that would enhance the design and feel to the website. I want to create sections on my homepage so that a user can scroll down the page and discover me as an artist. I want to switch where I host my domain from so that I can then just use lovethyhoneybadger.art, but code it all by myself. I want to make every page better. I want to create background images for each page with nicer titles. My site isn’t very responsive yet when dealing with mobile or tablet. I tried to create a whole different site for mobile or tablets and I ran out of time while doing so, so I’ve left my site as is without the code. It’s responsive and it works–it just doesn’t look as good as it will.

Pt.2

I had no idea what I was doing on the first assignment. Now I actually have a sense of it, but not a complete one. The parts that I really struggle in is making text segments look appealing to the eye. If I had the time, I would have created a contact page that was completely different depending on the screen type. On a computer, it looks very nice, but on a phone it will be much harder to navigate. Luckily, I kept it still easily accessible.
I’m feeling pretty comfortable with CSS and HTML. I still want to work on this project even after the due dates, so that I can complete it to how I want it to be. I am very proud of my contact page because I didn’t use Wufoo at all and when you fill out the form and hit submit, I actually receive an email with the form information. I even learned a little bit of PHP to help me with my contact form. I also attempted to create a lightbox for my image gallery, but that failed miserably and also wasted about five hours of my time. I also ended up confusing two different CSS codes where one was being used as a test, but then I accidentally got it confused with my main.css and had to go through and match what I was doing into my main.css. Of course, I didn’t realize that until the last minute. I was also very successful designing some cool hover features for my images and also for my navbar. These features both took countless hours and weren't done in one day. My website is the best reflection that I can give. For future students I would suggest working on your code at least every day or every two days. It’s easy to learn it, but hard to retain it. And I ran into trouble when I would code on Fridays, but not touch it until Sunday or Monday.