Skip to content

docs: comprehensive documentation improvements across Learn, Build, Operate, and Reference sections#1828

Open
Dark-Brain07 wants to merge 11 commits intostacks-network:masterfrom
Dark-Brain07:docs/comprehensive-improvements
Open

docs: comprehensive documentation improvements across Learn, Build, Operate, and Reference sections#1828
Dark-Brain07 wants to merge 11 commits intostacks-network:masterfrom
Dark-Brain07:docs/comprehensive-improvements

Conversation

@Dark-Brain07
Copy link
Contributor

Summary

This PR contains 7 meaningful documentation improvements:

  1. Clarinet Quickstart - Exit instructions, common mistakes, next steps
  2. Stacks.js Overview - Package descriptions table, quick example
  3. Learn README - Prerequisites for learners
  4. Operate README - Troubleshooting tips, community support, health checks
  5. Build README - Fixed broken Clarinet links
  6. Networks.md - API endpoints table, rate limit warning
  7. Main README - Contribution guidelines, quick links, Get Help section

Testing

  • All markdown syntax is valid
  • All internal links point to existing files
  • No breaking changes to existing documentation

@Dark-Brain07 Dark-Brain07 force-pushed the docs/comprehensive-improvements branch 3 times, most recently from d4435ca to 4887cda Compare February 14, 2026 10:14
@Dark-Brain07 Dark-Brain07 force-pushed the docs/comprehensive-improvements branch from 4887cda to 1207396 Compare February 14, 2026 10:16

```typescript
import { fetchCallReadOnlyFunction } from '@stacks/transactions';
import { STACKS_MAINNET } from '@stacks/network';
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this convention of using constants for specifying networks isn't used anymore. please update it to the latest modern way for stacks.js

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.


***

## Network API Endpoints
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

| ----- | -------- |
| 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. |
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you explain where one can find the bootstrap_node config?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.


| I want to... | Jump to... |
| ------------ | ---------- |
| Run a mainnet follower | [Example Mainnet Configuration](#example-mainnet-follower-configuration) |
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these links are invalid....please update them

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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) |
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please check if this url is valid


***

## Next Steps
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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) |
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this link isn't broken on the public site


| Mistake | Solution |
| ------- | -------- |
| Forgetting the `.` prefix when calling contracts | Always use `.contract-name` format for local contracts |
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the . prefix needs to be expanded more...


***

## Common Beginner Mistakes
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

@Dark-Brain07
Copy link
Contributor Author

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!

@Dark-Brain07 Dark-Brain07 force-pushed the docs/comprehensive-improvements branch from b172719 to 93cbc3e Compare February 18, 2026 03:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants