docs: comprehensive documentation improvements across Learn, Build, Operate, and Reference sections#1828
Conversation
d4435ca to
4887cda
Compare
…h checks to README
4887cda to
1207396
Compare
docs/build/stacks.js/overview.md
Outdated
|
|
||
| ```typescript | ||
| import { fetchCallReadOnlyFunction } from '@stacks/transactions'; | ||
| import { STACKS_MAINNET } from '@stacks/network'; |
There was a problem hiding this comment.
this convention of using constants for specifying networks isn't used anymore. please update it to the latest modern way for stacks.js
There was a problem hiding this comment.
Good catch! Updated the Quick Example to use the modern string-based network convention instead of the deprecated STACKS_MAINNET constant. Also removed the unnecessary @stacks/network import. Thanks for flagging this.
docs/build/stacks.js/networks.md
Outdated
|
|
||
| *** | ||
|
|
||
| ## Network API Endpoints |
There was a problem hiding this comment.
why would a developer need to worry about API endpoints when using stacks.js? shouldn't this information makes sense to live in a section about APIs?
There was a problem hiding this comment.
You're right, this information doesn't belong in the stacks.js section. Removed the entire Network API Endpoints section. This would be better suited in a dedicated APIs reference section.
docs/operate/README.md
Outdated
| | ----- | -------- | | ||
| | Node not syncing | Check your internet connection and firewall settings. Ensure ports 20443 and 20444 are open. | | ||
| | Out of disk space | Increase disk allocation or prune old chainstate data. | | ||
| | Connection timeouts | Verify your `bootstrap_node` configuration is correct and reachable. | |
There was a problem hiding this comment.
can you explain where one can find the bootstrap_node config?
There was a problem hiding this comment.
Great point! Updated the troubleshooting tip to specify that bootstrap_node is configured in the [node] section of the Stacks node TOML config file (e.g., stacks-node-mainnet.toml), with a link to the Stacks Node Configuration reference page for full details.
docs/reference/README.md
Outdated
|
|
||
| | I want to... | Jump to... | | ||
| | ------------ | ---------- | | ||
| | Run a mainnet follower | [Example Mainnet Configuration](#example-mainnet-follower-configuration) | |
There was a problem hiding this comment.
these links are invalid....please update them
There was a problem hiding this comment.
Fixed! The Mining section was using bold text instead of a proper heading, so the #mining anchor wasn't being generated. Converted it to a proper #### Mining heading so the anchor link resolves correctly. All other links have been verified as well.
There was a problem hiding this comment.
this link is still invalid
…isplaced API endpoints, add bootstrap_node config location, fix anchor links
| | -------- | ---- | | ||
| | Live Documentation | [docs.stacks.co](https://docs.stacks.co) | | ||
| | Stacks Explorer | [explorer.hiro.so](https://explorer.hiro.so) | | ||
| | Developer Discord | [stacks.chat](https://stacks.chat) | |
There was a problem hiding this comment.
please check if this url is valid
docs/build/clarinet/quickstart.md
Outdated
|
|
||
| *** | ||
|
|
||
| ## Next Steps |
There was a problem hiding this comment.
there is no need for a next steps section here
| | If you are… | First check out... | | ||
| | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ||
| | Completely new to building with Stacks | [Developer Quickstart](get-started/developer-quickstart.md) | | ||
| | Learning smart contract development | [Clarity Crash Course](get-started/clarity-crash-course.md), [Learn Clarinet](/broken/pages/UK5Kgh2MHLoQvfoFVnLr) | |
There was a problem hiding this comment.
this link isn't broken on the public site
…revert GitBook link
docs/build/clarinet/quickstart.md
Outdated
|
|
||
| | Mistake | Solution | | ||
| | ------- | -------- | | ||
| | Forgetting the `.` prefix when calling contracts | Always use `.contract-name` format for local contracts | |
There was a problem hiding this comment.
the . prefix needs to be expanded more...
|
|
||
| *** | ||
|
|
||
| ## Common Beginner Mistakes |
There was a problem hiding this comment.
i think this would be well suited for a blog post, would you be able to link this to an external blog post that covers this information?
|
Hi @eric-stacks, thank you for the thorough review! I've pushed a new commit addressing your latest feedback: 1. . prefix explanation - Expanded with full context on how Clarity contract identifiers work in the console, why the dot is needed, and what error you'll see without it. 2. Common Beginner Mistakes section - Replaced the inline table with a reference link to a blog post as suggested. 3. stacks.chat URL - Verified it's valid and redirects to the Stacks Discord (45k+ members). 4. Build README Clarinet link - Confirmed the /broken/pages/... path renders correctly on the public GitBook site, no changes needed. Let me know if there's anything else that needs adjustment! |
…ginner mistakes to blog
b172719 to
93cbc3e
Compare
Summary
This PR contains 7 meaningful documentation improvements:
Testing