Tag Archives: homepage repo

Design Thinking and the Return of PHP

Leave a reply

Reflections on the Homework

This week’s homework was a good reminder of how fast a skill can atrophy in the face of Spring Break. While searching for the simplest PHP features I could find, I realized that I still don’t really know how PHP interacts with the base of a website’s HTML. I understand that PHP is a server-side language that can create functionality on a website that HTML can’t do alone. But  I never stopped to consider how the two languages “talk” to one another.

I took to Google, hoping for a quick bit of code similar to the one that you use to link a CSS stylesheet to an HTML page. No such luck.

What I found were forums with varying opinions on whether you could code PHP directly into your HTML file. The conclusion I drew was that it’s best to keep files separate (hello, Separation of Concerns), but, like CSS, PHP can work when referenced directly in an HTML file.

I also learned that in order to get the PHP functions to show up, you need to be hooked into a server (makes sense) or server software like Apache. I’m assuming this is where something like MAMP comes into play, but to be honest, that’s where my train of thought ran out of steam.

So, here are some questions I still have: What’s the best way to set up a local server for simple websites like our homepage repos? What’s the best way to test the specific functions of a PHP script? And how do you reference your PHP file in an HTML file?

Readings on Design Thinking

Switching gears to focus on the future, for a moment. I’m grateful to have had these reminders about good design and user experience as we begin to plan out our final projects. I found the Medium reading, “Shh! Don’t Tell Them There’s No Magic In Design Thinking,” particularly interesting, because I hadn’t thought about the tenants of Design Thinking in that way before—i.e., the concepts have been part of good development forever, but now people are starting to pay attention. Here are my favorite mantras/takeaways, which, consequently, are the ones that I think will be the hardest for me to master:

  • We’re going to do things differently from how we’ve always done it before.
  • We’re going to study problems before we jump to solutions.
  • We’re going to diverge on our best ideas before picking the one that matches the solution best.

Welcome to my MySpace

Leave a reply

Good Design(?)

Well, I made my first “homepage” using HTML and CSS, and I have to admit I was immediately transported back to my parents house in the early 2000s. I never used MySpace, but I loved Xanga, a blog-based social site that allowed users to edit their own code. I spent hours researching the correct HTML for important things such as:

  • Background music that played when a user visited the site
  • Cursor options that transformed the mouse into small animals and objects (there was likely malware associated with this)
  • Font colors and styles, etc.

I imagine for many students my age, this was the first experience with HTML they had. What struck me the most in this week’s homepage repo assignment was how complex a simple, elegant web page must be behind the scenes. Yes, it was relatively straightforward to change my font to Comic Sans and add a gif of Neil Degrasse Tyson. However, those notably beautiful webpages (Atelier AM, American Documentary, and others here) must have been painstakingly designed to be beautiful on a range of devices.

CSS Stylesheet

I decided to link an external stylesheet to my HTML file, rather than use inline CSS stylings. The Codecademy exercises on CSS made me appreciate how quickly CSS styles can accumulate, and how much more organized it felt to have them all in one place. (Though I will admit I wished Codecademy had hinted to alphabetize the styles for ease of use—which seems like a no-brainer best practice.)

I struggled for a while figuring out how to link my stylesheet to my HTML file, and finally realized it was a combination of incorrect href syntax AND incorrect CSS syntax, so that even if the files were linked, the changes weren’t appearing in my test browser window.

After a few episodes of trial and error, I was ready to give up on the separate stylesheet and just add in-line CSS styles, but I knew that for my final project I would want them to be separate, and I would be better figuring it out now rather than later. I’m glad I did.

A note about GitHub:

I can appreciate the utility of a tool like GitHub to manage the uncountable tiny changes and bug fixes/additions to code. The mechanism of committing changes is simple enough to understand, but I’m concerned that the more changes you commit, the harder the code is to actually read. It takes practice, I guess…