Create reference documentation site

[dmethvin-gov]

Here are some examples that we might follow when we get to the detailed per-widget documentation. Emphasis on pics of the rendered form elements and copy/paste of sample code.

https://joepuzzo.github.io/informed/?selectedKind=Inputs&selectedStory=Radio%20Input&full=0&addons=0&stories=1&panelRight=0&addonPanel=REACT_STORYBOOK%2Freadme%2Fpanel

[jcmeloni-usds]

@bernars-usa To your mind, anything to do here?

[bernars-usa]

There's not much that would be wise to spend a lot of time with docs-wise if the library is going to change drastically. Reference documentation is notoriously tedious to manually maintain (which is why it's often managed with tools like Swagger or Postman or older ones I won't mention because it will betray what a dusty old fogey I am).

There are definitely features like copy/paste of sample code or the three panel view that lord/slate has made so popular the last few years, but at that point the discussion becomes building out a full doc site (as Dave's issue title here implies). I'd recommend an epic for a generated docs site, when the time is right.

[jcmeloni-usds]

Roger that.

[dmethvin-gov]

I think any new work would make significant changes to the API so we wouldn't want to do this work for the current design.