11–19 of 19 posts
1. An HTML/CSS editor (FireBug for FireFox)
2. Network Traffic Monitor (Foxmeter for Firefox)
3. Cookie Manager (Advanced Cookie Manager)
4. User Agent Switcher (for Firefox)
5. Modify Headers (optional)
6. Javascript Console
Those are your tools for debugging, writing some things.
Technologies you will have to learn...
1. jQuery
2. MVC framework
3. API/JSON content calls
4. AJAX
5. Cookies (same/cross domain)
No WYSIWYG. Virtually all raw HTML. Treehouse was decent when it launched, and I imagine it's improved a solid amount by now. If you're coming from a development background, you'll do fine. If you're building true front-end apps, you're going to want to look at Angular or Node. If the back-end does the heavy lifting, they become less important.
> How do you use node for front-end? I've only ever seen it used for back-end.
Development Tools 1. An HTML/CSS editor (FireBug for FireFox) 2. Network Traffic Monitor (Foxmeter for Firefox) 3. Cookie Manager (Advanced Cookie Manager) 4. User Agent Switcher (for Firefox) 5. Modify Headers (optional) 6. Javascript Console Those are your tools for debugging, writing some things. Technologies you will have to learn... 1. jQuery 2. MVC framework 3. API/JSON content calls 4. AJAX 5. Cookies (same/cr…
To add to your list jsfiddle.net is a great tool for testing out small features and experimentation.
JS frameworks: jQuery, AngularJS, BackboneJS
CSS frameworks: Bootstrap, Foundation
and tons ready-to-use solutions on Github.
Earlier quoted context omitted.
Why is WYSIWYG not used? Is it just that the available tools aren't good? I would have thought that writing raw HTML would be a bit like writing raw WinForms code these days, or writing XAML by hand instead of using the forms designer. Note that's the narrow application of visual editors I'm thinking of here - laying out buttons, binding events to buttons, binding data to elements, etc; not the "create a pretty looki…
You can use WYSIWYG editors but make sure that they comply with latest HTML and CSS specifications, so that when you want to manually modify the code, you will find yourself in a well structured framework and not in a jungle of incoherent code. If you want to go WYSIWYG, I think Dreamweaver is keeping up fine with times and it's still one of the most complete tools https://www.adobe.com/products/dreamweaver.html But…
A modern front-end stack looks like: For structure/content : raw HTML, or less commonly a language that compiles to HTML (Haml, Jade, etc.). If the HTML is being rendered and served from the backend, you might use a templating language like Django's templating or Jinja (Haml and Jade also have these features). If you are creating an application that does a lot of AJAX, you will also often use a JavaScript templating…
A modern front-end stack looks like: For structure/content : raw HTML, or less commonly a language that compiles to HTML (Haml, Jade, etc.). If the HTML is being rendered and served from the backend, you might use a templating language like Django's templating or Jinja (Haml and Jade also have these features). If you are creating an application that does a lot of AJAX, you will also often use a JavaScript templating…
A modern front-end stack looks like: For structure/content : raw HTML, or less commonly a language that compiles to HTML (Haml, Jade, etc.). If the HTML is being rendered and served from the backend, you might use a templating language like Django's templating or Jinja (Haml and Jade also have these features). If you are creating an application that does a lot of AJAX, you will also often use a JavaScript templating…