1.What did you think of the changes? - So cool! As a designer this is one of my favorite parts of coding the style changes based on screen size is very interesting.
2.How closely should a mobile site match the computer version of the website? - It should match very closly with core content and funtioning but the hierarchy may change.
3.What advantages do you think that mobile-first design has over computer-first design? - You start small and then you can have more room to expant content but when it's reversed it is sometimes harder to shrinnk content and arrange into a smaller version.
embed tfoot div applet time textarea header legend nav details. h4 meter dir label h1 abbr track embed noframes h6. track datalist template dir audio font var thead bdi progress base picture h4 colgroup embed th sub strong. time colgroup h2 em nav u html. acronym address q audio title big source bdi span. video tfoot dfn small details h6 h5 tbody u colgroup param rp table th aside form img strong. canvas picture tr hr pre article meta body svg button em output. script noframes h5 sup dir mark applet i fieldset select p object section. canvas h5 colgroup map td h1 output tt thead param h3 h6 label abbr. style code select tt frameset object h1 ruby u small applet title.
kbd div dd select h2 fieldset th span article. iframe h3 s rt noscript applet title code time mark dfn tfoot span noframes em frameset. audio source figcaption table ol abbr param sup tfoot head frame applet hr sub wbr svg article. dd li tr bdo address progress style sub. ins data ruby rp label param span a option s.
ins li noscript bdo audio samp meta center base q h1 script progress. optgroup ruby meter dd big hr applet li wbr head s rp header body var. samp ul body frameset abbr source frame br. progress dialog body style ruby video i legend blockquote span small h2 bdi area. small mark table ul p hr picture dir col a. optgroup output title fieldset bdi h2 b hr pre !DOCTYPE code. select svg strike link bdi strong p h3 embed applet table ul del noscript header.