![]() A brain is a complicated bit of machinery so we've not worked up to it yet, but they understand it with relation to themselves. He obviously does not know all the property types, but he's collecting them and writing notes in a book he keeps by his bed.įinally, the brain and behaviour, the way the website can be interacted with is using the third layer: JavaScript. The syntax is simple enough that he's able to write the CSS selectors, property and values without prompting. For example: we want the foot bone to have a border. I explained that CSS is written differently from HTML, and keeping with tag only selectors showed how the name of the bone/tag is specified. So the skin and the paint on the skin, this is CSS. Some can have different colours, shapes, heights and more. It's what makes each website look unique. The bone have names and they hold the bit of content.īut then, when we put the styles back, this is the skin over the skeleton. I showed them a handful of web pages with all the styles removed and showed them that "this is the skeleton of the web page". ![]() Each bone does it's own special thing, like the tag/bone will show some text. Each bone has a name, we call them tags (or elements). I loaded up a browser and explained that "this is a web page". It's a slow layering of knowledge acquisition for them. There's no point in trying to explain from the outset what HTML is, how it works over HTTP, about browsers and the DOM, let alone CSS, the cascade, specificity and more. It's very cool (if perhaps complicated!). Now that he can export, I connected Netlify to the repository that he was exporting to and all of a sudden he has continuous deployment from a little export button in Glitch - and he's able to make new pages, change things, edit text and more. Once he was using Glitch, I then wired Glitch up to Github and showed him how to Export to Github. This wasn't so bad, but was a little limited and brittle.Īs the lessons continued, I decided to move up from JS Bin to Glitch - this way the boy could make new files, directories and upload images. The workflow would then be: download the file from JS Bin, send it from their Chromebook (a freebie from my upgrading my phone) using Snapdrop (a really great wifi file drop utility) to my machine, I would then put that in a directory and drag and drop into Netlify to release to his web site. There's the obvious added bonus that when I explained that I had written JS Bin - the code that they were typing their code into, it both blew their minds and made me rather chuffed. This worked well because it focuses entirely on HTML at the start and they got real time feedback, along with a bit of code completion (as they were using the unreleased v5). Initially they were both using JS Bin for HTML and CSS. I've published 38 videos for new developers, designers, UX, UI, product owners and anyone who needs to conquer the command line today.
0 Comments
Leave a Reply. |