Tag Archives: week1

HTML, Structuring Page Content

Leave a reply

Codecademy Link: https://www.codecademy.com/alliefoard

Test Repo Link: https://github.com/alliefoard/hello-world

After our first class, I was feeling very apprehensive and overwhelmed by all of the content and vocabulary that web editing and creation brings to the table. However, after the readings and assignments this week, I feel like I have gained a basic understanding when it comes to HTML programming.

The Getting Started: HTML & CSS article and Basic Intro to HTML/CSS article were extremely helpful when explaining the tags, and creating a list of the most basic tags that one will use when coding in HTML. The metaphor about a website being like a house was very helpful when looking at the land as a server, and the structure of the home being HTML. It allowed for me to put things into perspective and understand what before was gibberish.

Prior to these lessons and readings, I didn’t really comprehend that HTML and CSS work together. I originally believed that they were two separate languages. When in reality, CSS can be inserted directly into html tags.

As a PR professional I felt a direct connection to the Getting Started articles concept that to introduce web development to journalists and PR professionals, you must think like them, and how they care about headlines, content, and timing. This is very true and will help me in the future if I need to communicate web development with clients. The Getting Started article also touched on how we forget how to code faster than a foreign language, so I did my best this week to space out the time working on the assignments so that I can continually refresh my memory on the subject.

As far as the assignments go for this week, I found the Codecademy to be very hands on and helpful. However, I didn’t fully understand GitHub. Although the formula was easy to follow, I can’t say with full certainty that I understand the need for using it and how it can help my coding abilities.

 

HTML Introductions

Leave a reply

As I completed the first two assignments on CodeAcademy, I couldn’t help but be super grateful for the detailed instructions that Codecademy gave as it walked me through each piece of the lesson. I found that the first lesson made a lot of sense and I was able to pick up the concept and general structure of an HTML code quickly, but I struggled more on the second lesson and putting even more specific concepts together. I was able to work through most of them, but I definitely wondered how I would memorize and make sure to not miss tiny details that are required for clean, workable code.

The GitHub activity was simple but confused me, as I wasn’t sure how this fit in with our HTML learning – I am assuming that repositories will be where we place our code once we start writing it, but there was less explanation and hand-holding in this exercise compared to the Codecademy assignments. Following the instructions was very difficult for me, and I hope that in this week’s class we will go over the importance of this program, how it fits in with our programming knowledge, and walking us through repositories and how we will be using the pull/merge requests throughout the semester. I’m also not totally sure if I submitted the right GitHub repo test, but I have included the link below. The GitHub guide link that was provided as reading for homework this week was somewhat helpful, but I think it would be even more beneficial to hear this part of our curriculum explained in person — especially how it will be incorporated into our learning this semester. Hoping for a lot more clarity on this topic in the coming week, and looking forward to diving further into our Codecademy assignment and analyzing each piece that we have learned so far!

GitHub test: readme-edits/readme-edits

Codecademy Profile: https://www.codecademy.com/lucynegash

Codeacademy Rescues Girl Drowning in HTML

Leave a reply

First off, I really enjoyed the Codecademy exercises. They are a tad tedious (I’m sure that will increase), but it made a seemingly messy and complicated idea make logical sense. Or, simple sense at least. (My brain isn’t particularly logical.) I’m also glad that I chose to read the articles in order instead of skipping around like I did last week. I liked Mindy McAdams’ piece as it both reiterated what I needed to know from Codecademy and exactly how this process relates back to me–a journalism student. (I’m also not particularly interested to see how Codecademy tackles CSS. I know developers are finicky folks when it comes to the hows of coding, so I’m curious to see how that unfolds.)

OK. The web inspector stuff is mildly blowing my mind. If I’m understanding this correctly it means that I can go on any webpage and then see the code that created it? That’s some crazy talk. Like, I understand that languages like CSS and HTML are totally available to whoever uses them, but don’t huge companies have their own private languages? This has revealed a giant tangled nest of legality questions.

Mostly appreciating this article for the TLDR. Lol. But, also because after the previous article I immediately opened a bunch of webpages and inspected their code. I appreciate being able to now understand what is going on! This seems to be a great learning tool. I can see what it’s SUPPOSED to look like–in it’s cleanest best edited form. I really am curious to delve more into what different code looks like and why. When to use what.

So, is GitHub Flow basically the Slack of GitHub? I’m interested to see–once I actually start creating more branches etc.–if the way they have it set up will be helpful or more confusing to me. It reminds me of being in Video Journalism and having a few different “final” edits of a single video, but rarely making any big changes to the final product. I look forward to learning what is the best practice and why certain branches make it into the master and others don’t. I understand that at my level that the concerns will be fairly cosmetic; however, when a team of great coders are all working together on one project, why do some things make it in and others not? I look forward to class this week!

Codeacademy Profile
GitHub

 

Learning the Web’s Grammar

Leave a reply

As I did the lessons, I was reminded of the many reasons I do not speak another language fluently. Grammar is a beautiful but challenging thing, especially when you just start to learn it. That is exactly what this felt like.

I started learning French years ago. For awhile I was very good at it. So good in fact that I could translate for friends and family. I could read and write easily and quickly. I even had dreams in French, as strange as that sounds. How did I become so fluent? I practiced everyday. I incorporated speaking it into every aspect of my life.

That is what I will have to do to become at least slightly proficient at HTML and eventually all of the other languages. It is actually very simple. Especially since these are the building blocks, but like with English or French grammar understanding and then remembering where to put what is the challenging for me.

I was reminded of this at the end of each lessons. I thought I had absorbed enough and remembered enough of the steps to know where each line of HTML went. But each time, I had to go back and read through the lessons again before completing the assignment. Both fortunately and unfortunately, Codecademy does not save your progress if you hit the back button at the bottom of the screen. While this was annoying, it was actually very helpful. It pushed me to go back over the lessons I apparently did not understand. It made me work just a little bit harder to understand the grammar.

Thankfully after a few tries it is coming along. I am fairly confident that I could build a basic, not so pretty web page. I am also very confident that I can break it, and hopefully then fix it again.

Learning How to Code: Potential Challenges I Might Face

Leave a reply

Codecademy profile

Test repo

Completing this week’s assignments was not difficult. But obviously, I have no experience in coding so I had no idea what I was getting myself into. It turns out that coding is like learning a new language.

After going through all the readings, I made thorough notes on the biggest things I need to learn. I wrote down the tags and the meanings of what terms like <!DOCTYPE html> and <html> meant. Codecademy did a great job of trying to synthesize coding to be as simple as possible, but it still took me a solid hour and a half to complete the exercises. As a tech-loving millennial, I am used to things being fast and instant and I have to remind myself that learning to code will take time. I can’t get good at it right away.

One of my favorite excerpts from this week’s readings were from “Get started with Web coding. Part 1: HTML and CSS,” because the author mentioned that like anything, we have to code every day for us to get better at it. I apply this to all the other skills I have learned in the past: speaking Spanish, singing, playing instruments, and editing video. Obviously, I wasn’t great at them when I started out but after practicing and working at it diligently for a while, those things became muscle memory to me. I realize that if I continue to be diligent at learning how to code, it will be the same for me. We all have to start somewhere, right?

Doing the Github exercise by making my own repository was pretty straightforward. The reading did a solid job of helping me understand how to navigate it better. One thing I love about the Georgetown program is that I have grown from being someone with not a lot of digital skills to learning how to navigate all kinds of programs. After all, that is what I love the most about learning: growing from becoming an amateur to an (almost, maybe, kind of) expert.

“Meet the Web Inspector” was helpful for what we did in class Wednesday. It is going to be so cool to be able to go into a web page and learn how to change things. This will be so helpful in helping me understand how to build content and websites. “How to inspect styles” also build on the details I learned about web development.

 

What we’re really getting ourselves into

Leave a reply

Going into this class, I had absolutely no knowledge of what coding looked like or how it functioned (besides on MySpace). I really hope to get two major things out of this class. The first thing I’d like to do is be able to communicate with coders/programmers so that I’m not that annoying person coming to them frequently to do the easiest task ever. I’d also like to be able to create and manage my own portfolio website. I know this is pretty easy to do on WordPress, but actually knowing how to troubleshoot and how to make my site more unique is a skill I think it wouldn’t hurt to have. This may come off a little selfish, but it seems like the more you can say you know in this industry, the better of a brand you have created for yourself. It would be very gratifying for me to be able to list that I know HTML (or at least the basics of it).

I doubt very many people are reading our blog, but if they are, I do have a word of advice: If you have the opportunity to learn how to code in high school or college, go for it. I remember having a class similar to this in undergrad, but being an athlete, I — embarrassingly enough — was able to pass the course with flying colors with “help” from my tutor. I was practically handed a site to turn in by the end of the course and learned nothing besides the fact that I never wanted to take that course again. I can’t say I’ll leave this class being a master coder or even wanting to continue to pursue programming, but I do realize how important it is that I know the basics of what’s really going on behind all of these web pages.

Week 1 – May 21, 2013

Leave a reply

Week two homework helped me reinforce the topics covered in class last week, which was great. I thought I would remember everything taught in class, but I was wrong. I went home started working on developing my code and my mind was blank. Thank goodness for Week 2 readings and for the web design course.

As far as the Basic Intro to HTML for Journalism students, I am nowhere near a journalism student, but can appreciate the work, especially with the changing world that we live in. One day you are involved in being a writer and the next day you are expected to become a developer-writer. I have always been intimated by developing, especially after working in IT. I cannot fathom how a journalism student feels. Their entire college curriculum is focused training the brain to identify a story and delivery and then all of a sudden the world changes and they are expected to code. It is a good thing that we have generous technologist out there as the developers and owners of WordPress and Web Design courses which break things down into simple form.

The following stood out from the journalism essentials: “Even if you never write a line of code, you need to be able to communicate with those who do.” Very powerful statement, not only for developing, but for everything in life. As a Public Relations student and a consultant, I find it to be extremely important to communicate in other people’s language. It leaves a huge impact. One huge challenge which is a growing trend in IT organizations today is the inability for IT and the Business to communicate and their inability to appreciate the others gifts. IT always feels that the business is not doing anything and the business seems to underestimate the complexity and challenges which constant change of development requirements brings to the table. My initial thought is that they are not able to appreciate what each brings to the table due to lack of knowledge and/or interest in the others talents. I hope this course helps me better understand what developers do, not only so that I too can join the development and blog craze, but to also work better with development teams.

Other comments: My first impression of this web design class is that it may actually be possible for me to learn how to code and/or blog. I am truly excited, not only about the idea of being able to start my own blog, but also at the idea that I may be able to teach others how to blog. I truly cannot wait to go live.

Week One Post- Mark Dennin

Leave a reply

I’m beginning to learn that code can be layered, and that different languages will allow us to do different things.  Some languages provide the basic structures of a site, while others are markup languages and allow us to “dress up” the structure.  Understanding what language is appropriate for what I’m trying to do will be key.  I’m also starting to learn that coding, even with a markup language is going to require a lot of memorization and exercises in order to keep myself familiar.  Responsive web design is becoming more and more important, as I am almost more likely to view a website on my iPhone than on my computer.  And someone else might view it on their HTC phone, or a tablet of any size, or any variety of devices.  A website, not just an app built for a specific operating systems, has to be able to adapt to any device now, and look like it was designed for just that screen size, width, and length.  At first I’m probably going to have more success working with adaptive layouts, as these are going to be easier to make and more foolproof  from the start.  But once I become more comfortable, responsive layouts are going to be my goal.  It will be way easier to design for for just a few different layouts than hundreds, and I’ll be happy if I can make my website look great on and iPad and and iPhone to start, as these are the devices I see most people using these days.

The web inspector has been interesting to use thus far, but is showing me that I have a lot of work to do understanding what each type of code is capable of.  It really is like reading a foreign language at this point, and every type of content seems like it written in one that is different than the previous one.  I’m looking forward to be able to understand what I am reading soon.

Web Inspector: Modern Day Sherlock Holmes

1 Reply

The articles on HTML and CSS brought me back to my migente.com and myspace.com days. Changing background colors, fonts, adding boxes, and frames around photos was all the rage in my youth. Mostly on the HTML front, CSS and the curly brackets make my head spin but I think these articles made it clearer. The way I understood it is; you place certain qualities in a single style sheet and then you just reference certain portions of the sheet in your HTML document. By placing it in a separate sheet you don’t have to read two different styles in one document should you need to edit. This reminds me of the Zen of Python where you want to make things as simple as possible so that anyone can replicate or edit the document.

I really enjoyed the articles on responsive design as well as adaptive layouts.  When I worked at an agency everyone wanted to redesign the websites we made for our clients a few years back in a responsive layout. I imagine it was due to the amount of potential revenue it could drive as opposed to editing their current websites to create adaptive websites. The agency of course would recommend adaptive layouts should the client not want to redesign their recently designed websites. It makes a lot of sense for every website being designed from this point on to be responsive. The sites must be designed with mobile and tablet in mind as Internet usage increases among non-desktop devices. It really is a huge missed opportunity for so many local businesses. As I continue to brand myself as a social consultant that offers web services to local business this will be a big selling point that I’ve underused in my past pitches.

I found the Web Inspector article really interesting. I’ve used it before but I have yet to use the network tab and the files tab, which I will now start to use. I was so fascinated I also read the article on the “Dollars for Docs” project. It’s amazing to think that the drug companies make content very difficult to read to protect their relationships with doctors. It’s equally amazing that with a few keystrokes and clicks you can get a clear and easy to read document with all the information of your health professionals and the financial relationship with the drugs companies. The web inspector tool is the modern day Sherlock Holmes.

Responsive Design vs. Apps

Leave a reply

In “Get Started with Web Coding,” I was surprised and, honestly, a bit horrified to read the author’s recommendation that we never go two days without coding. For someone like me, who wants to learn enough to be a casual, competent coder but not necessarily a full-time programming master, that seems like a lot to ask. By this rule, programmers would never even get a weekend off. I understand the thinking here, and as an amateur guitar player, I know the ease with which skills decay after a period of inactivity, but now I’m scared I’ll never become semi-fluent in code without dedicating every other day to practicing.

The articles on responsive and adaptive web design were interesting to me because, at work, my team is constantly trying to convince our higher-ups that we need the time and resources to create mobile-friendly designs for all of our communications. Their proposed solution is always the same—“Don’t we need an app?”—which is frustrating, because apps are not the best or easiest way to promote our services in most cases, but apps are what everyone thinks of when they want a mobile-optimized user experience. I think as programmers and organizations become more adept at responsive designs, stand-alone apps will become less necessary and less common.

Ethan Marcotte’s “Responsive Web Design” proved to me the idea that, paradoxically, it’s often easier to solve a problem when you have limited resources and choices available to you. I think organizations have been slow to embrace responsive design because it’s so much simpler to design three different sites for three different screen sizes, rather than conceiving a fluid design that can shift to match whatever dimensions it’s given. Folks who work in journalism, especially, are used to seeing exactly how a layout will look in print, and the thought of freeing the elements of a layout to resize and shift in response to a screen size change is frightening. We want to control what the user sees as much as possible—and responsive design is, the thinking goes, a threat to that control.