remove 'return' statement to allow Brackets to fall thru to rest of New File code b/c we've already force completed the previous rename
move inline js into external files
add std license header and placate jslint
reorganize Readme

Moved paragraphs around so least technical (most user-oriented) is on top, then tech/contributing (hacker info) is near the end.  This allowed to streamline the prose, but I tried to avoid changing the text as much as possible.

Linked blog in welcome section (great for finding features; helps users decide if Brackets is for them).

Used H4 vs **bold** for sub-headers.
more terse, less repeated text

(note to self; don't Push with only 4 hours of sleep)
more terse, less repeated text, ordered helping steps
add comment for future about no inline scripts
Fix #4333 (files shown as plain text incorretly).

- Added FileUtils.getBaseName (jsdoc and unit tests included).
- Replace usage of path-utils.js with getBaseName.
Fix unit tests for FileUtils.getBaseName.
Add support for project-wide JSLint config.

Related to issues #3269, #4210.
Based on the discussion and suggestions in #3310.

If a project has a .jslint.json in its root, it gets loaded and passed to each
JSLint run within the project. The configuration file gets reloaded each time
it is saved or refreshed.
Revert "Add support for project-wide JSLint config."

This reverts commit 11dbdfdb5d84ecaee826bd722b1053ede0fba60e.
Moved live highlight
From file menu to view menu.
updated pt-br translation for a better readability.
add try/catch to async extension init to fix #4404
reorganize getting help
refactor ExtensionManagerViewModel.

This is to prepare for further refactoring in support of consistent view
between multiple views.
handle more extension load error cases. add new unit tests.
rename init to initExtension
code review comments
fix jshint error for jasmine globals