Update REMIXD tutorial

[smiasojed]

Closes paritytech/contract-issues#7

[athei]

I think we should remove the quick dapp and just use REMIX to show how to compile a contract. But not how to build a Dapp.

Because right now it is confusing because we show people two different ways to create a Dapp. We should prepare a template repository that people can clone to follow the ether.js part that sets them up with a basic Dapp.

[smiasojed]

I think we should remove the quick dapp and just use REMIX to show how to compile a contract. But not how to build a Dapp.

I can remove this, but this PR is more about what to do with the local development section

Because right now it is confusing because we show people two different ways to create a Dapp. We should prepare a template repository that people can clone to follow the ether.js part that sets them up with a basic Dapp.

REMIX supports workspaces from GitHub repository or Gist, which allows us to use them as the default workspace for tutorial

[athei]

Yes the part about local contract development is good. I just don't want to cover frontend development here.

[smiasojed]

Yes the part about local contract development is good. I just don't want to cover frontend development here.

I think that local development could be moved outside the tutorial. If we plan to work on template repo, REMIX should probably clone workspace directly from it.

The content which is not needed for the tutorial like quick dapp or local development could be moved to separate page or deleted if we do not see a value there.

[athei]

The point is to guide people to a workflow to iterate on their contract and frontend. Having the contract in the local file system would be good for that, right? I don't expect people to be keen on editing code inside the browser.

REMIX should probably clone workspace directly from it.

That repo would be concerned with building the frontend. And I don't want to conflate REMIX with frontend development.

[smiasojed]

OK, in this case, we need to start the tutorial by cloning the template repository and connecting to the local filesystem from REMIX.

The drawback is that you need to install REMIXD on your local machine, which is something we wanted to avoid in the beginning.

[smiasojed]

As discussed, we will keep only the basics in the Remix tutorial, without covering DApp deployment or development on the local filesystem.

[athei]

I think we should keep this in the main tutorial. Telling people how to interact with pre-existing contracts is basic knowledge. Just as a separate main heading "## How to interact with already deployed contracts".

[smiasojed]

done

[kianenigma]

I think we should remove the quick dapp and just use REMIX to show how to compile a contract. But not how to build a Dapp.

As discussed, we will keep only the basics in the Remix tutorial, without covering DApp deployment or development on the local filesystem.

Came to a similar opinion about both via #27.