Add Chords-Web & chords-Python in Basic & Pro Kits

[bhawnasehgal]

Hey @lorforlinux,

For signal visualization, I have updated the Basic & Pro docs with steps to use Chords-Web and Chords-Python. Please review and merge.

Summary by CodeRabbit

• Documentation
  • Updated and streamlined instructions for the DIY Neuroscience Kit Basic, consolidating software requirements and simplifying usage steps.
  • Clarified and expanded project ideas for both Basic and Pro kits, adding new project links and reorganizing content.
  • Improved internal navigation by adding section anchors and labels for easier cross-referencing within guides and software documentation.
  • Updated hardware descriptions and software requirements for the Pro kit.
  • Adjusted figures and formatting for improved clarity and output-specific display.
  • Added new hidden documentation references to extend included topics in the DIY Neuroscience Kit Basic docs.

[coderabbitai]

Walkthrough

This update revises and restructures documentation for the DIY Neuroscience Kit Basic and Pro, with a focus on clarifying software requirements, streamlining instructions, and consolidating electrode placement guides. It introduces new internal references and hidden toctrees for enhanced navigation, updates hardware descriptions, and adds new project ideas. The software documentation for Chords Web and Chords Python gains explicit section anchors for improved cross-referencing. Figures and formatting are selectively adjusted, and references to outdated tools are replaced with instructions for the current Chords ecosystem.

Changes

Files/Paths	Change Summary
_static/latex/diy-neuroscience-kit-basic.rst	Added four new hidden toctree directives referencing usage and software documentation for gel electrodes, Chords Web, and Chords Python.
guides/usage-guides/using-gel-electrodes/index.rst	Added internal label for section reference; made figure conditional for HTML output only; minor header formatting change.
kits/diy-neuroscience/basic/index.rst	Extensively revised instructions, software requirements, and workflow; unified around Chords tools; consolidated electrode placement; updated project ideas; removed redundant content and outdated tool references.
kits/diy-neuroscience/pro/index.rst	Updated hardware description to include Arduino UNO R4 Minima; clarified and restructured software requirements; added new project ideas; removed kit contents figure; minor formatting changes.
software/chords/chords-python/index.rst	Added internal section label for cross-referencing; no content changes.
software/chords/chords-web/index.rst	Added section anchors for major application sections; removed extraneous blank line; no visible content changes.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Documentation
    participant Chords Web
    participant Chords Python
    participant Arduino IDE

    User->>Documentation: Access DIY Neuroscience Kit guide
    Documentation->>User: Presents streamlined instructions
    User->>Arduino IDE: Uploads Chords Firmware
    User->>Chords Web: Visualizes/records signals (option 1)
    User->>Chords Python: Visualizes/records signals (option 2)
    Documentation->>User: References detailed electrode guides and project ideas

Loading

Possibly related PRs

• Updates in Chords-Python documentation #60: Updates and restructures the Chords-Python documentation, directly related to the new toctree and label references for Chords-Python in this PR.
• Updated chords Documentaiton #61: Revises and expands the chords-web documentation, overlapping with the new toctree entries and section anchors for chords-web introduced here.

Poem

A bunny hopped through docs anew,
Tidied guides for kits and glue,
Chords Web and Python, anchors set,
New projects for curious pets.
With hidden trails and clearer views,
The neuroscience kit gets fresh reviews!
🐇✨

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b32a491 and 0123bda.

📒 Files selected for processing (1)

• kits/diy-neuroscience/basic/index.rst (7 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• kits/diy-neuroscience/basic/index.rst

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[lorforlinux]

@bhawnasehgal Thank you so much for your contribution, I am merging this now.