docs: add updated diagrams for node requirements and consensus node#1674
docs: add updated diagrams for node requirements and consensus node#1674
Conversation
WalkthroughThe recent documentation updates enhance clarity and visual appeal in the Celestia node setup guides. Key modifications include changing image formats for consistency and refining visual elements. These enhancements focus on improving user experience and documentation accuracy, particularly concerning hardware requirements. Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
|
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (3)
public/img/node-requirements.jpgis excluded by!**/*.jpgpublic/img/nodes/consensus-node.jpgis excluded by!**/*.jpgpublic/img/nodes/full-consensus-node.pngis excluded by!**/*.png
Files selected for processing (2)
- nodes/consensus-node.md (1 hunks)
- nodes/overview.md (1 hunks)
Files skipped from review due to trivial changes (2)
- nodes/consensus-node.md
- nodes/overview.md
After discussing with @rootulp - we think 2 TB is a good recommendation for now, based on disk usage for different types of syncs that we tested which at maximum were over 1 TB. That being said, as you highlighted, this will always be a moving target. So maybe we can pick a safe value in the future like 10 TB?
No, there is no distinction for this on node requirements. The pruning section briefly covers this though, do you think it needs revision for clarity? |
rootulp
left a comment
There was a problem hiding this comment.
Q: Should we take out the plain text version? I was thinking it could be useful for SEO purposes. But the duplication feels odd.
The duplication feels like a maintenance burden. If we had to take out one of them, my preference would be to drop the image because the plaintext version is easier to edit.
Given the image was already created, I don't think we need to drop it for now. Ultimately defer to you.
|
I'm also leaning toward removing the maintenance burden of this graphic, too, and keeping the plaintext version. Will revisit in a |
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
public/img/node-requirements.jpgis excluded by!**/*.jpg
Files selected for processing (1)
- nodes/overview.md (1 hunks)
Files skipped from review as they are similar to previous changes (1)
- nodes/overview.md
Overview
Summary by CodeRabbit