When I first came into this class, I had a vague idea of what writing in code was. I kind of sort of had an idea of how it worked, but I was more technical with it. I thought it could only be done a certain way and if it was not, it would not work. I began to realize while it is still technical, it is more free flowing that I thought. There were many ways to go about getting something to look the way you wanted it to. I believe that my website first exhibits emotional design through the aesthetic choices. I wanted to keep my website simple, leaning towards more minimalistic. The reason I chose to design my site in this way was to eliminate the possibility for confusion when navigating through pages. For my design philosophy I mentioned that I wanted the personality of my website to be more submissive, than dominant. The way I interpreted this was instead of going over the top in selling myself or skills, I wanted my work to serve as an example in itself. As for responsiveness, I feel that this is where my website falls a bit short. For some pages, it was difficult to maintain a sort of uniformity, namely the contact page and the wufoo form. I had trouble structuring it in a way where it would not shift behind the navigation bar when decreasing the window size. This was a problem for me because it interfered with the ability to use the navigation bar. My initial sketches and my final website are relatively the same, though I think the page that changed the most was the portfolio page. Since it had so many elements, trying to structure them in the way that I wanted resulted in conflicting styling. Although my code looked fine, the images would shift or display in ways I did not intend (though in the end I managed to get them under wraps)
I think my progress from the first assignment until now has grown. Coding in general was a difficult concept for me to grasp since I like to see things visually. It was difficult at first to identify which specific changes in the stylesheet or code related to the finished visual product. I would go back and forth checking to make sure I did it the right way. I feel that now I am more fluent in the language of web design as I know what certain code means, and how it translates to the results. I am much more comfortable going into a new project and coding without fear of ruining what I have. As a result of this I feel more confident that what I am doing will turn out the way I think it will (which is the case most of the time), but even if it does not I think I am now competent enough to look through my code and find out where I went wrong. If I could change one thing looking back at this project, I think it would be more time spent planning. I’m a little bugged with the fact I was not able to really understand the grid layouts at first because I feel in the long run it would have gotten rid of some of the problems I experienced. I have a feeling that if I had gotten my math right and meticulously sketched my drafts, I would have given me more time to continue designing my website to make it the best it could be. I wish I had more time to get things right. I think for future classes it might be nice to have a little more time to go over the grid layouts that we did in class. I feel that in planning the website out and doing the math, while also knowing how to properly apply that to the code, would allow for more time focusing on the aesthetics or to work out kinks in the code. I liked in class how we used solstice to display new things people and how they did it. Maybe sharing more of our work could help people get new ideas or inspiration for their own work.