Starting at the Flatiron School!

This week, I officially started at the Flatiron School NYC Web Development Fellowship! I’m going to start documenting my progress and what I’m learning, so this is my little intro post to start things off.

So far, I’ve been working on the pre-work section. (Open-sourced here!) The HTML/CSS Skillshare course is a lot of review for me so far, but it’s very well-done and every once in a while there are new nuggets of information, or things I had completely forgotten. The course takes you through building a website, so I started on my personal site. It’s been on my to-do list for a while, and I figure this is as good a time as any!

I started by reviewing a bunch of the html tags I was already familiar with – tables, images, headers, links, and lists. Then the course got to forms. I never really had to use forms before, and so while I understood them conceptually, it was great to have actual experience with the form tags.

When creating a form, the element has two required attributes. Action, which points towards the file in which the form data is saved, and method, which dictates how the data should be saved. The two options for method are “get” and “post”. Get will show the information submitted in the page’s URL, so it shouldn’t be used for important information like passwords and credit card numbers.

<form action="#" method="post"> <input type="text" placeholder="text here> <input type="tel" placeholder="phone number"> <input type="email" placeholder="email here!"> <input type="submit" value="Send your information!"> </form>

As you can see above, the form element does need to be closed, but the individual input types do not. It’s great that there are input types for phone numbers and emails, as it will check the format of what’s entered by the user to make sure it fits the type. There are many more than I realized! The Mozilla Developer Network has a comprehensive list of them that’s worth looking at. (There’s even a type for color!) It’s also worth noting that inputs are self-closing elements, but radio inputs, checkboxes, and drop-down menus are not.

Another big thing I learned today was the semantic elements for HTML5. Header, Footer, Nav, Aside, and Section are some of the main ones. You can use javascript (HTML5 Shim) to make sure that HTML5 works in older versions of IE. The Skillshare course uses this handy script to put in your head, so that only old versions of IE will run the JS.

<!-- [if lt IE 9]!>
<script src="http://html5shim.googlecode.com/svn/trunk/html5.js"></script>
<![endif] -->

Those are the highlights of what I went over and learned today. Next, moving on to CSS!

You may also like...

2 Responses

  1. Daniel says:

    Hi!

    I just wanted to say , I’m really enjoying your posts. I just dove into learning ruby/rails/html/css and am having a blast. While I don’t know if a bootcamp is in the cards for me (can’t take a break from work/$$$), I am trying to immerse myself daily in new things, even if it is just reading a tutorial while at work and working more on my landing site.

    I really appreciate your insight, it is good to know that if you put your mind to these things that you can definitely carve out a path. I have much more to do to actually get to build the app I’m thinking of, and today was feeling a bit overwhelmed and discouraged. Looking through your posts helped and I’m looking forward to more.

    Just wanted to say thanks and keep up the good work. Feel free to check out what I have so far, basically a site with some static, pages and a blog/user model so I can post some updates here and there.

    take care!

    • opheliasdaisies says:

      Hi Daniel!

      Thank you for your comment! I’m so glad that you’ve found my blog helpful! Keep up your blog as well – its great motivation to keep learning new things, and helps solidify what you learn in your mind! I noticed in your blog that you’re going through Hartl’s tutorial – that’s a great resource, I highly recommend it! You seem to definitely be on a good track. I look forward to seeing what your app turns into!

      And don’t worry about feeling overwhelmed – everyone does at times, especially when just starting out. But know you’re not alone! I’ve gone through that, and I’ve seen so many friends go through it as well. There’s just so much out there, and programming is hard! It’s like training your brain to think a new way. But you can’t know everything, and the fact that there’s so much to learn means you’ll never run out of things to learn and improve on. That can be pretty exciting too! And as you’re exposed to more patterns and ways of doing things, it becomes more intuitive.

      Good luck and keep up the good work! Feel free to reach out if you ever need any help! You can find me on twitter at @opheliasdaisies.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>