docs: remove light node from the build section

[jcstein]

Overview

This removes light node from build section, making default way to submit TXs through the transaction client.

Depending on what you think, I'd like to propose whittling down the overview page and/or combining it with the quickstart. I'm a bit too tired at this point in the week to decide rn.

[gemini-code-assist]

Summary of Changes

Hello @jcstein, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request represents a substantial overhaul of the documentation site, transitioning from VitePress to Nextra to enhance maintainability, scalability, and user experience. This migration facilitated a major restructuring of content, particularly within the 'Build' and 'Operate' guides, to better reflect current best practices for interacting with the Celestia network. Key updates include new, detailed tutorials for Go and Rust transaction clients, comprehensive RPC API documentation with an interactive playground, and new sections explaining private blockspace capabilities. The changes aim to streamline the developer journey by clarifying the recommended methods for transaction submission and node operation.

Highlights

• Documentation Platform Migration: The entire documentation site has been migrated from VitePress to Nextra, involving the removal of all VitePress-related configuration and components, and the introduction of a new app/ directory structure with Nextra-specific files for enhanced maintainability and scalability.
• Content Reorganization and Focus Shift: The documentation has undergone significant restructuring, particularly affecting the 'Build' and 'Operate' sections. Content related to light nodes has been re-contextualized, with a new emphasis on transaction clients as the default and recommended method for submitting transactions.
• New Client Tutorials: New, detailed tutorials for Go and Rust transaction clients have been added, providing comprehensive guides on how to submit and retrieve blobs, including advanced features like queued and parallel submission modes for varying throughput needs.
• Enhanced RPC Documentation: A dynamic RPC documentation section has been introduced, featuring an interactive playground, version selection, and detailed method/parameter descriptions for the Celestia Node API, making it easier for developers to explore and test API calls.
• Private Blockspace Documentation: New content has been added to explain 'Private Blockspace,' covering its core concepts, quickstart guides, and various use cases for enabling confidential yet verifiable transactions on Celestia.

Ignored Files

• Ignored by pattern: .github/workflows/** (8)
  • .github/workflows/build.yml
  • .github/workflows/deploy.yml
  • .github/workflows/latest_tags.yml
  • .github/workflows/link-check.yml
  • .github/workflows/lint.yaml
  • .github/workflows/preview.yaml
  • .github/workflows/preview.yml
  • .github/workflows/spellcheck.yml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request refactors the documentation by moving information about light nodes from the /build section to the /operate section. This change makes the default method for submitting transactions via the transaction client more prominent. The changes primarily involve moving .mdx and .js files, updating links, and adjusting the overview page to reflect this new structure. My review identified a broken anchor link and an opportunity to improve documentation consistency for the Go and Rust client guides. Overall, the changes align well with the stated goal of the pull request.