Add better instructions for running connect

[fbwoolf]

It has been reported that devs had a hard time understanding how to run/test making changes to connect. We should added better instructions for how this works best using yalc.

[markmhendrickson]

Might this be best handled by documentation / migrated to that repo?

[fbwoolf]

Might this be best handled by documentation / migrated to that repo?

Not sure on this? I do think we need better readme instructions for these repos, but it would be great to get some more information about Connect in the docs.

[markmhendrickson]

@pgray-hiro thoughts here on where this sort of content may go best, and who should produce?

[pgray-hiro]

For the case that is raised by this issue (i.e. developer wants to locally run the connect development environment so that they can contribute features to the connect library), I think updating the README is the most relevant. At minimum there should be instructions on the prerequisites for developing against the connect repo, how to clone and build the library locally, and how to run any unit tests locally. This content needs to come from whoever is maintaining the repo, which introduces a resourcing challenge.

Separately it would be nice to move this repo into the Stacks.js repo, but I don't believe it's a pre-requisite for resolving this issue, because the README would also migrate, and it still needs expanded content.

[dartman10]

+1