Doc devex upgrade

[poppyseedDev]

@yuxizama

[yuxizama]

https://app.gitbook.com/o/-MIF05xPVoj0l_wnOGB7/s/fls45RcVCyuxax0RVNVY/getting-started/overview-1/remix @poppyseedDev

[poppyseedDev]

@yuxizama the quick start is ready for review :)

[yuxizama]

Quick start page

• Introduce “Standard Confidential ERC-20” early: As a new user, I might not have any prior knowledge of what a "Standard Confidential ERC-20" is. Maybe introduce in this manner:
  - Start with an overview of ERC-20 (basic token standard).
  - Follow with Confidential ERC-20 (its confidential, privacy-preserving variant).
  - Then, explain Confidential ERC-20 Mintable as an extension.

Step 1:

• Add prerequisites section -> Stay aligned with other pages
• Remove hyperlink the “Zama plugin in the official Remix IDE” in the introduction sentence to reduce distractions.
• When installation is complete, include success sign to let users know what happens after clicking "OK".
  "ACL is a valid address.”
  “KMSVerifier is a valid address.”
  “Gateway URL is set.”
• "Deploy and use contracts after configuring the plugin, you can interact with fhEVM encrypted contracts directly via the Zama plugin interface. "=> Need rewording, clean the headline format.

Step 2:

• Using metaMask: Add scribe
• Manual network configuration: the “Currency Symbol” should be SepoliaETH.
• Balance verification: Clarify how much balance is required to proceed with the tutorial.

Step 3:

• Remove blanks in code snippets, otherwise it doesn't compile in Remix.
• Compiling: Include a visual or textual “Success” sign after successful compilation for feedback.
• Second code snippet: Clarify whether it is a continuation of the previous snippet or a new one.
• Add “paste code alert” screen: The default Remix warning -> to assure users that they can click "OK"
• Redeployment clarity: After enhancements, clarify if users need to redeploy their contract or if the original deployment remains sufficient.
• Provide a link to view the actual contract as a reference. ( As it's only imported in the code)
• Button naming: Replace "Click Deploy" with “Click Transact” for consistency with the interface.

Step 4:

• Mint tokens to address: Clarify that users must input their own address (instead of contract address) and sign the transaction in their wallet.
• Include the success indicator
• Balance check:
  - Clearly state that users must input their account address to verify the balance.
  - Specify that the result will be encrypted and appear as a encrypted text
  • Explain that “re-encryption" button is actually decrypting the ciphertext
• Input proof: Add an explanation about the purpose of these steps for better user understanding.

General feedback: The GIFs play too quickly sometimes, making it easy to miss steps. Is it possible to add a play/pause or step-by-step click-through option for better usability?