This week was a huge eye-opener! We had a great video and article to read on the history of responsive design, and learned many new things about how to use responsive design in our websites.
I have been wondering, ever since my first web design class, how exactly to make the website responsive to different screen sizes and devices. I have made many sites throughout all of my classes, and when sharing them with friends and family, the website always looked funny on the phone. You could get the jist of the website, but it did not look like how I intended.
I am so excited to continue to learn more about responsive design and get creative with different layouts for different screen sizes and platforms. I definitely want to incorporate responsive design into my midterm project after I make a layout for smaller screen sizes.
I am also having so much fun with the midterm project! When I created my first layout using Figma, I could not figure out how to change the layout of things or use the tools, besides changing colors, images, and text. Then I went back through the videos when I had extra time and did a little YouTubing myself, and I think I am grasping how to use Figma. Some things I haven’t quite figured out yet, but for the purpose of this assignment, it ended up working quite well for me.
I am definitely looking forward to putting all of my layout choices into code and start working on it in Dreamweaver. However, before I do that, I am going to make a sort of wireframe. This is something I did in my AAD 85 class with Ms. Rishe, and I’m not sure if we will be doing that extra step in this class as well after the midterm break. Since we have already created a thorough layout, the wireframe will mostly be a rough draft of how I want to structure my code before I actually start coding it. This helps me really understand what my goals are, and how best to structure my site knowing I will be using things like flexbox and grid. This to me, makes the process much less stressful. Rather than jumping right in, adding or getting rid of things that don’t work as you code, and fixing mistakes as they pop up, you can sort of eliminate a lot of confusion before you really start coding.
I am looking forward to continuing all of this after the break! happy coding.