@julio4, thank you for your input could you kindly confirm if the approach I used in the last two PRs aligns with your recommendation to make and comment the changes directly here?

Commit 53800b5: Fixed the broken contribute link across multiple pages in the book. It previously pointed to a 404 page, but I changed it to point to the CONTRIBUTING.md file.

Commit 9ca6616: Fixed another broken link.

Does this approach align with your suggestion in your previous comment?

I would say it's not bad but don't create a new md file for the changes, either:

• Directly apply the change in the PR and comment the change on github directly
• First propose the change on github and we can discuss it

And if you use AI tools please be sure to verify by yourself all the suggestions as well!

@julio4,

I'm proposing a suggestion to enhance the user experience for first-time users of this book. Since the main contract code, interfaces, and tests are stored in listings, while the main contract and interface definitions might not be immediately visible to users unfamiliar with the book's structure, I suggest adding a link tag to the location of the visible code in the listings.

Example:

Specifically, I propose modifying the current implementation:

Current:

// [!include ~/listings/getting-started/counter/src/counter.cairo:contract]

Suggested:

// [!include ~/listings/getting-started/counter/src/counter.cairo:contract]
To run the contract, visit: [Simple Counter](https://github.com/NethermindEth/StarknetByExample/blob/dev/listings/getting-started/counter/src/counter.cairo)

This change would provide easier access to the full contract code for users who want to explore the implementation and interface definitions.

Additionally, I suggest introducing this approach throughout the book wherever necessary. For example, we could add similar links at the beginning of each chapter or section that includes listings, providing easy access to the complete source code.