Change-Id: I9a705764c92a33b15dcfb5a144b3e4d37a2e57f7

Change-Id: I445be04cb61a1a87609aa4a9d2ca8340e83ed701

Change-Id: I26ff172b0ebd37c2794c13316891676659e485a6

TO-690

Change-Id: Id2f08fea7e0607c630b42e1d5f8b987810922ead

This patch cleans up the entry-point(s) into Fuchsia documentation:

 - adds `development.md` as a top-level article to links covering
   development workflow, hw targets and coding conventions. Adds some
   missing links.
 - removes the bits about dev workflow from the Fuchsia book
 - makes README.md point to development.md and book.md, and makes it the
   target of "Home" in the navbar (and not book as before)

Change-Id: Ia437b6f016e51d2a340033128fe94d54bc636053

INTK-118 (tags for peridot)
INTK-121 (tags for topaz)
INTK-127 (tags for garnet)

Change-Id: Ie76b989635b8784c2f54639d4f4b4ac1ab26cbf0

Change-Id: I5b1c671634e2e53ed3da4f299f7b05ac53911377

Change-Id: Idea1d9eb2cbc534f92c5c5d0433c762e25b57f7c

The purpose of this doc is to explain concepts that I repeatedly explain
to Fuchsia developers, about defining our goals when writing tests and
figuring out how to write tests that achieve those goals.

The structure I'm going for is to first define an "ideal test" by
example. The ideal test is what we want tests to look like, and I
explain why. Then, I show how we can take a messy real-world Fuchsia
test and nudge it toward the ideal, based on an actual CL I wrote.

There's quite a bit of stuff that I left out of this doc because I don't
want it to be overloaded with "tips" or a list of "bad practices" versus
"good practices". My idea is that it's more effective to get a single
concept across and then let people work out for themselves how to work
with that concept. This also matches the way I've been working with
individual developers on test techniques: I rarely just say something
like, "This technique is bad". Rather, I point out ways in which a
certain technique succeeds/fails at our goals.

Questions for reviewers:
- Does the concept of "ideal test" make sense to you as a basis for
  reasoning about test strategy?
- Is the example ideal test a good one? Is it too simplified, or
  unnecessarily complex? Is it missing some important aspect that you
  think should be illustrated?
- Is the example real CL well-connected to the concepts?

Change-Id: I4d00bcbf03541f5fd0fa3bb0db40490694ff2a94

Change-Id: I13efec944dc5200a78c7a95d744e83f7700fd007

Change-Id: If89fb26ca50c7dec06eb24c7460674c3170d542e

Change-Id: I4e6e238e39fd34e0772cb1dfef3f4487d349ac36

Link targets suggested by mikejurka@.

Change-Id: Ie67dce2a5b5e7e82cdc212571769f1ef5294b688

Change-Id: I59755a86c74149622e81c01b9c524f4cce3bc50e

with abarth's recommendation

Change-Id: I0c380ecb58fa316d97163d86018ea9d0f5bb2465

Change-Id: Iae728cd237dc8b1fce6b74855ebae8eef534c41a

No longer needed given fix for ZX-1521.

Change-Id: I0dfce4a2a18208424dbfd6dffe3f7375fe25bdd0

Change-Id: Ia22caa0a227d768f10a56c3598172e92baf2adcc

Change-Id: I98708e3f38aad7988539b108ca97db9046b073df

Change-Id: I598ea86551d03d55bdf06650202154385d58ff27

TO-558 #comment general documentation on using variants

Change-Id: Ibc2dcec21299ae3b34d6dfff10d68e1a896ea058

Change-Id: Ic2e8686c03fb95adb6bb4239741969075750fcb6

Change-Id: I70370917ef959e4dc6954a633ab8fbe665c1d87e

TO-669 #done

Change-Id: Iebbf840654fb9f4a43b4ba73fd596297f7575b93

TO-670

Change-Id: I3b6ca8847a6b471ea4c6433d90263c272ab2a9dd

Change-Id: I2e510c7ccfdf4db2e11e0caae817f6ffe366c6f0

If you want to zedboot!

Also, add a note about how to short circuit the boot delay.

Change-Id: I680b82e7325af94233d66714bdb2bfb6f3ccfe8f

Add advice to take updates if this is a first boot.

Relocate 'reboot possibly needed' warning to a more useful place.

Change-Id: I3f33fd33852a538c62a957c24a312486347034e5

Change-Id: Icb736a691e42cff65a63582daa3d26910a4fde8d

Testing shows sometimes an extra reboot is needed to get the shell
to come up.

Change-Id: Id572551a0f961898260f69a20c1795d3928f3330

TO-665

Change-Id: I970556d496a39f255614862318a14d7d53c193de

Apparently, the old instructions could be interpreted
as 'destroying the USB', rather than reformatting it.

Change-Id: I83ed33b64b050ea42294a84a8d0603909bf72d46

 - 'mkvbootzedboot' is now 'mkzedboot'
 - Add language to clarify recommendations for booting after paving

Change-Id: I63202f27a225a91d29f2b76578dfd46083a0ed40

These needs special treatment in markdown.

Change-Id: I525e6f99696f7620eceafcaed49b905c7b0ba9f8

Change-Id: I11fefc189af907ce49599dade0081896735f302d

Change-Id: I730d1cdb2fec11d6ef00c8a9b2badf0802399500

Also add 'how to boot from USB' for Pixelbook

Change-Id: I0e805175ee93a80526300925f36aa6e83eed701b

Change-Id: Ia9722fb8f61dc9ad491129d8189a54157011bd5c

Change-Id: I377807d3b72c553773d8622d281d04de36eb1f30

Change-Id: Ia686efd882ed04e0e8ea1cbf4be65d2db4099823