First Move Module Update 1#826
Conversation
… updated filenames in code blocks
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
| # Your First Move Module | ||
|
|
||
| This tutorial details how to compile, test, publish and interact with Move modules on the Aptos blockchain. The steps in summary are: | ||
| The Aptos blockchain allows developers to write Turing complete smart contracts (called "modules") with the secure-by-design Move language. This means you can do all the blockchain things like sending money, but also write arbitrary code, even games. It all starts with the Move module. Once compiled and deployed with Aptos CLI, you can connect to a published move Module on Aptos like a public API via one of our [many Official SDKs](../sdks/). |
There was a problem hiding this comment.
| The Aptos blockchain allows developers to write Turing complete smart contracts (called "modules") with the secure-by-design Move language. This means you can do all the blockchain things like sending money, but also write arbitrary code, even games. It all starts with the Move module. Once compiled and deployed with Aptos CLI, you can connect to a published move Module on Aptos like a public API via one of our [many Official SDKs](../sdks/). | |
| The Aptos blockchain allows developers to write Turing complete smart contracts (called "modules") with the secure-by-design Move language. Smart contracts enable users to send money with the blockchain, but also write arbitrary code, even games! |
There was a problem hiding this comment.
I think the longer version helps explain the context the Move module is in. Just writing a contract without using the SDK to interact with it is incomplete, so I like mentioning it up front (even though it's beyond the scope of the tutorial).
There was a problem hiding this comment.
We'll find a middle ground for the next iteration
There was a problem hiding this comment.
@jmintuitive I respectfully disagree here, many folks write contracts without using the SDK to interact with it... and I don't see the SDK being used at all here in this tutorial so what's the relevence?
Also to be frank I think the writing here could be stronger — This means you can do all the blockchain things is vague and informal. I'd like the prose to be more concise and professional
There was a problem hiding this comment.
We moved the SDK reference down and used the newer version with more professional concision
There was a problem hiding this comment.
used the newer version with more professional concision
"The Aptos blockchain allows developers to write Turing complete smart contracts (called "modules") with the secure-by-design Move language. This means you can do all the blockchain things like sending money, but also write arbitrary code, even games. It all starts with the Move module. Once compiled and deployed with Aptos CLI, you can connect to a published move Module on Aptos like a public API via one of our many Official SDKs."
This still looks the same?
There was a problem hiding this comment.
Mmm i don't think its in the commit de70beb... Unless I'm doing something wrong, it also looks the same in file view...
There was a problem hiding this comment.
Thank you for your eagle eye and staying with this Andrew, it should now be good to go!
Co-authored-by: Andrew Hariri <hariria@usc.edu>
Co-authored-by: Andrew Hariri <hariria@usc.edu>
|
@hariria Thank you for the feedback, I checked that removing .mdx works, did not know that, thanks! For the intro, we'd like to merge this as is and then work on the intro for the next draft |
Out of curiosity, why not just change it in this PR? |
|
@hariria just part of our internal workflow and backlog |
|
??? 🤣 . These are getting merged to main immediately, idky we would postpone this change? |
Imo the longer intro works well, and we're trying to get an updated version of this merged since it's been blocked for a while, and we want it as a link for in-person events (like Eth Denver this week). The next version @tippi-fifestarr is talking about is based on user feedback (we did some user reviews of the guide) so that will impact the whole guide somewhat when we get to that revision (likely next week / the week after). |
hariria
left a comment
There was a problem hiding this comment.
I like the general flow of the guide and some of the sections you added (i.e., defining move modules for the audience make a lot of sense), but I don't agree with some of the points raised, hopefully my comments provide some more color on my reasoning.
If we want to work on this over several passes that take place over multiple PRs I would suggest we make the appropriate fixes here before merging into main, since main is the production branch and everyone will see your changes immediately.
Another approach is to create branches on top of this branch, and merge into it. Then you can merge this base branch once everything on top of it has merged into this one.
| # Your First Move Module | ||
|
|
||
| This tutorial details how to compile, test, publish and interact with Move modules on the Aptos blockchain. The steps in summary are: | ||
| The Aptos blockchain allows developers to write Turing complete smart contracts (called "modules") with the secure-by-design Move language. This means you can do all the blockchain things like sending money, but also write arbitrary code, even games. It all starts with the Move module. Once compiled and deployed with Aptos CLI, you can connect to a published move Module on Aptos like a public API via one of our [many Official SDKs](../sdks/). |
There was a problem hiding this comment.
@jmintuitive I respectfully disagree here, many folks write contracts without using the SDK to interact with it... and I don't see the SDK being used at all here in this tutorial so what's the relevence?
Also to be frank I think the writing here could be stronger — This means you can do all the blockchain things is vague and informal. I'd like the prose to be more concise and professional
- Updated the opening paragraph for clarity and professionalism. - Moved SDK mention to the bottom of the tutorial. - Condensed the Setup section intro for readability. - Removed unnecessary dashes from headers and formatting. - Removed reference to Developer’s Journey blog. - Updated `aptos --version` to be copyable, while seperately showing the expected output.
|
Thank you again, Andrew! |

Description
Updating this guide, added screenshots, steps, and example code. Designed for Web2 or Solidity developers to get a quick start in writing and publishing Move Modules
Checklist
pnpm fmt?pnpm lint?