Add "Getting started" guide

[fvictorio]

Incomplete draft of the "Getting started" guide.

Pending sections:

• Using scripts
• Deploying contracts
• Next steps

Some things to improve that I've noticed but I haven't worked on yet:

• Text is still too chatgptish.
• "This task compiles your Solidity source files and generates the corresponding artifacts" -> This should either explain what artifacts are (before or after), use a different phrasing, or avoid mentioning artifacts altogether.
• Inconsistent use of plain "Hardhat" vs "Hardhat 3".
• The term "sub-tasks" is used but not explained. This might be fine; maybe the context is enough.
• Temporary networks are mentioned but not explained. This might be fine.
• "Whether you're compiling contracts, running tests, deploying to testnets, or executing custom logic, tasks are the core of how you interact with Hardhat." -> Added by chatgpt; maybe this paragraph can be replaced by a different way to close the section, or just removed.
• The "Writing tests" introduction might be too detailed.
• Cheatcodes are mentioned but not explained.
• Consider updating the example project and this guide so that the fuzz tests is third and after the unit tests, not in the middle of them.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
hardhat-website	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 29, 2025 8:05pm

[Copilot]

Pull Request Overview

This PR adds a draft "Getting started" guide to help users install, configure, and test their Hardhat projects. The guide covers installation steps, project structure, writing smart contracts, and testing with both Solidity and TypeScript, and the directory info has been updated to link to this new guide.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
src/content/hardhat3-alpha/learn-more/getting-started.md	New guide draft covering installation, project structure, smart contract writing, and testing.
src/content/hardhat3-alpha/learn-more/_dirinfo.yaml	Updated navigation to include a link to the "Getting started" guide.

[Copilot]

Pull Request Overview

This PR introduces a draft of the "Getting started" guide with new documentation for deploying contracts using Hardhat Ignition and updates to the navigation structure for the Hardhat 3 Alpha documentation.

• Added a detailed guide for deploying smart contracts using Hardhat Ignition.
• Updated directory metadata files (_dirinfo.yaml) to reorganize and include new learning topics.
• Added a new dependency in package.json for markdown link checking.

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated no comments.

File	Description
src/content/hardhat3-alpha/learn-more/deploying-contracts.md	Added new documentation for deploying contracts with Hardhat Ignition, including instructions for both temporary and persistent network deployments.
src/content/hardhat3-alpha/learn-more/_dirinfo.yaml	Updated the ordering to include the "Deploying contracts" section and rearranged links in the "Learn more" group.
src/content/hardhat3-alpha/_dirinfo.yaml	Modified the Hardhat 3 Alpha navigation order to add new sections such as "Get started" and "Writing scripts," which may result in similar naming with existing sections.
package.json	Added the "markdown-link-check" dependency to support verifying markdown links.

Comments suppressed due to low confidence (2)

src/content/hardhat3-alpha/learn-more/deploying-contracts.md:3

• [nitpick] The reference to 'Hardhat 2' in this section might be confusing since the guide targets Hardhat 3. Consider updating the version reference to consistently reflect the intended environment.

+Hardhat comes with an official deployment solution: [**Hardhat Ignition**](https://hardhat.org/ignition), a declarative system for deploying smart contracts...

src/content/hardhat3-alpha/_dirinfo.yaml:4

• The section title 'Get started' is very similar to the existing 'Getting started' section. Renaming one of them could help avoid confusion among users navigating the documentation.

- title: Get started