Extensions Docs Server: First doc conversions

chrome/common/extensions/docs/server2/templates/private/debugger_intro.html

Index: chrome/common/extensions/docs/server2/templates/private/debugger_intro.html
diff --git a/chrome/common/extensions/docs/server2/templates/private/debugger_intro.html b/chrome/common/extensions/docs/server2/templates/private/debugger_intro.html
new file mode 100644
index 0000000000000000000000000000000000000000..27a1d99543af100b1be951f3358a3609d25022d2
--- /dev/null
+++ b/chrome/common/extensions/docs/server2/templates/private/debugger_intro.html
@@ -0,0 +1,35 @@
+<!-- BEGIN AUTHORED CONTENT -->
+<h2 id="manifest">Notes</h2>
+<p>
+Debugger API serves as an alternate transport for Chrome's
+<a href="http://code.google.com/chrome/devtools/docs/remote-debugging.html">
+remote debugging protocol</a>. Use <code>chrome.debugger</code>
+to attach to one or more tabs to instrument network interaction, debug
+JavaScript, mutate the DOM  and CSS, etc. Use the Debuggee tabId to target tabs
+with sendCommand and route events by <code>tabId</code> from onEvent callbacks. 
+</p>
+<p>
+As of today, attaching to the tab by means of the debugger API
+and using embedded Chrome DevTools with that tab are mutually exclusive.
+If user invokes Chrome DevTools while extension is attached to the tab,
+debugging session is terminated. Extension can re-establish it later.
+</p>
+<h2 id="manifest">Manifest</h2>
+<p>
+You must declare the "debugger" permission in your extension's manifest
+to use this API.
+</p>
+<pre>{
+  "name": "My extension",
+  ...
+<b>  "permissions": [
+    "debugger",
+  ]</b>,
+  ...
+}</pre>
+<h2 id="examples">Examples</h2>
+<p>
+You can find samples of this API in
+<a href="samples.html#debugger">Samples</a>.
+</p>
+<!-- END AUTHORED CONTENT -->