Staff Client Dedicated Accessibility / Style Sandbox

[Bill Erickson]

Evergreen 3.12 / Wishlist

The Evergreen staff client has a developer sandbox page at /eg2/staff/sandbox. The page contains mostly development examples, plus a handful of accessibility examples, do's and don'ts.

I propose we migrate the accessibility/style examples to a new dedicated staff client page so devs can use this as a targeted resource for how to create staff client code/interfaces.

/eg2/staff/style-guide ?

Alternatively, it could live on a page outside of /staff/ that does not require authentication, but that would limit the kind of data we can work with in the page and require overall data retrieval to be relatively conservative, since it's accessible to all. Just a thought.

[Stephanie Leary (stephanieleary)]

Related: bug 2023493

I agree, and I'd really like to explore Storybook as a way of building this.

[Mike Rylander (mrylander)]

A big +1 to this idea generally.

Would it be possible/feasible to mark some routes such that they don't get built for release? My first thought was the --configuration parameter to `ng build`, but since there are (AIUI) some subtle behavioral differences between dev and prod build modes (certain error checking/reporting only happens in one or the other mode, for instance) we probably (maybe especially?) want the sandbox and style-guide to be available and testable in both.