Building uppy.io/docs VS uppy.io/blog

[lakesare]

Added docs about how to lint/build uppy.io/docs as per our Slack discussion.

[aduh95]

Suggested change

	[github.com/transloadit/uppy](https://github.com/transloadit/uppy).
	[transloadit/uppy](https://github.com/transloadit/uppy).

[lakesare]

Why? I feel github.com prefix makes it more intelligible, and removes the need to remember github-specific shortcuts.

[aduh95]

I don't really understand the "treat as your working directory"

Suggested change

	Now, treat **/uppy/docs** as your working directory, but run the build/lint
	scripts from your **/uppy.io** directory - **/uppy.io** will pick up your
	changes.
	Now, when running the build/lint scripts from the root of your `transloadit/uppy.io` clone, it will pick up your local changes on the `docs/` folder. Note that changes in the `docs/` changes should be submitted to the `transloadit/uppy` repository.

[lakesare]

"treat /uppy/docs as your working directory" means "/uppy/docs is a folder where you will be editing files, then committing the files, and then pushing the files".

[aduh95]

I think the previous sentence was clearer. Can you explain what you don't like about it?

[lakesare]

I want to make it explicit that both /uppy/docs and /uppy.io will be built using this command.

[aduh95]

Suggested change

	This command lints **/uppy/docs** and **/uppy.io**.
	N.B.: These commands will also report lint errors from the `docs` folder that's hosted on the `transloadit/uppy` repository.

[lakesare]

My version is more consistent with the phrasing of other command descriptions.

[lakesare]

@aduh95, could you rereview this again please.
I'd like these changes merged sooner rather than later because currently we're left practically without instructions for contributing to /docs which we do promise here.