[docs] Remove component server and components/docs folder

Remove the component server, the component docs folder and
everything referencing it.

Bug: 414332459
Change-Id: Ia8f9721c8a114597a647473a03ef2524462f1df8
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/7147061
Reviewed-by: Jack Franklin <jacktfranklin@chromium.org>
Commit-Queue: Kim-Anh Tran <kimanh@chromium.org>

Author: ktran

BUILD.gn

@@ -30,10 +30,7 @@ group("devtools_all_files") {
                 "test",
               ]
   deps = [ ":frontend_indexer_tsconfig" ]
-  public_deps = [
-    "front_end/ui/components/docs",
-    "scripts/component_docs",
-  ]
+  public_deps = [ "scripts/component_docs" ]
 }
 
 group("devtools_frontend_resources") {

docs/styleguide/ux/styles.md

@@ -29,7 +29,7 @@ tokens**](https://crsrc.org/c/third_party/devtools-frontend/src/front_end/design
 name e.g. `--sys-color-error-container`). They reference palette tokens and
 incorporate light / dark mode switches and should be used in the code directly.
 You can view all system tokens in their light and dark variant when running the
-component server with `npm run components-server` under *Theme Colors*.
+component server on our [component documentation page](https://chromedevtools.github.io/devtools-frontend/#ThemeColors).
 
 [**Application
 tokens**](https://crsrc.org/c/third_party/devtools-frontend/src/front_end/application_tokens.css)

front_end/panels/timeline/README.md

@@ -14,15 +14,7 @@ The first method is to run DevTools! Load up the Chrome for Testing version that
 
 DevTools, navigate to the Performance Panel and record or import a trace. There are a number of trace files saved in `devtools-frontend/test/unittests/fixtures/traces` that you can use.
 
-#### Option 2: the components server
-
-You can also use the DevTools component server. This server runs standalone parts of DevTools in the browser. To do this, run `npm run components-server` in the terminal, which will run a server on `localhost:8090`.
-
-You can then navigate to the Performance Panel examples using the link on the index page. This runs the real Performance Panel code in isolation, and you can additionally preload a trace by appending `?trace=name-of-trace-file-from-fixtures`. This is a nicer development cycle because you do not have to manually import a trace after each change. Note though that some parts of the experience are stubbed, so you always should test your work in proper DevTools too.
-
-These examples can also be used to create screenshot tests, which are an important tool for the Performance Panel because it is the only way to test `<canvas>` output. We define these as interaction tests (`devtools-frontend/tests/interactions/panels/performance`).
-
-#### Option 3: bundled DevTools in the browser
+#### Option 2: bundled DevTools in the browser
 
 This option loads the DevTools frontend in a browser tab in Chrome, but requires a little more setup to easily load traces.
 

front_end/panels/timeline/ThreadAppender.ts

@@ -135,13 +135,6 @@ const UIStrings = {
 const str_ = i18n.i18n.registerUIStrings('panels/timeline/ThreadAppender.ts', UIStrings);
 const i18nString = i18n.i18n.getLocalizedString.bind(undefined, str_);
 
-/**
- * This appender is only triggered when the Renderer handler is run. At
- * the moment this only happens in the basic component server example.
- * In the future, once this appender fully supports the behaviour of the
- * old engine's thread/sync tracks we can always run it by enabling the
- * Renderer and Samples handler by default.
- **/
 export class ThreadAppender implements TrackAppender {
   readonly appenderName: TrackAppenderName = 'Thread';