complete migration of Dart to separate repo & reorg JS docs

[chalin]

Dart items:

• firebase redirects: all /dart --> Dart site, docs(dart): redirect to webdev/angular #2924
• cache sync for Dart docs before breaking single-source links
  • architecture - docs(architecture): add Jade blocks for Dart, and other tweaks #2990, https://github.com/dart-lang/site-webdev/pull/244
  • pipes - docs(pipes/dart): improve FetchJsonPipe discussion #2937
  • toh - docs(toh-6/dart): getHero makes HTTP get-by-id #2936
  • lifecycle-hooks - docs(lifecycle-hooks): Dart sync with TS updates #2952
  • other pages, see [Dart] resync Dart .jade files, post-TS-RC5 #2077
• finalize move of Dart Jade sources to site-webdev - docs: remove public/docs/dart #2956
• move ts/_cache to site-webdev - chore: drop ts/_cache #2974
• move Dart _examples to site-webdev - chore: delete Dart _examples #2976
• build scripts: clean out (remove Dart elements)
  • minimal cleanup so that check-deploy doesn't require or deploy Dart docs - chore(gulp/travis): don't build Dart docs #2931
  • travis
  • gulpfile
    • api + cheatsheet build elements - chore(dart): drop api and cheatsheet scripts and gulp tasks #2970
    • doc build elements
    • example build elements
  • tools
    • tools/dart-api-builder - chore(dart): drop api and cheatsheet scripts and gulp tasks #2970
    • tools/api-builder/dart-package - chore(dart): drop api and cheatsheet scripts and gulp tasks #2970
• TS Jade sources (under /docs): clean out single-source elements

  • _util-fns.jade: mixins, functions, var defs.

  • TS Jade: clean out single-source elements:

    • Jade extends/blocks; mixins
    • inline text (via variables like !{_array})
    • A1 directives like ngio-ex

    from:

    • quickstart
    • glossary
    • guide pages
    • tutorial pages
• A1 directive code & NgioUtils (under /resources/js): clean out Dart elements
• migrate Dart issues to Dart repo

JS items

• firebase redirect to Why TS.
• Clean out JS elements from TS sources (there shouldn't be many of these but I do recall at least one situation where the Jade includes were in the opposite direction from what I expected: i.e., TS Jade file was including a JS Jade file).
• remove language drop down
  • perform any necessary styling / page layout adjustments
• clean out JS issues

[tilwinjoy]

Does the "drop JS" in title mean that there won't be a JavaScript documentation at all..?

[chalin]

@tilwinjoy - the title is indeed misleading, so I've adjusted it. What will be dropped will be the language submenu, not JS. Development of apps using JS will still be documented.